lennaert's Forum Posts

  • Without a capx or examples, I doubt anyone can.

  • Without examples, or references, that is very hard to determine.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • set angle to angle + (RAINBOWSPEED * dt)

    you will likely have to increase your rainbow speed variable though

  • In the project properties there is a "first layout" which you can have indicate that after export it will default start up with.

    During development with the previewer, if you hit F5 or preview, it will start up the layout with focus, or the last layout that had focus.

  • How about making the peer objects global ?, and destroy them when a player leaves/disconnects, and hide the peer in menu screens. (if needed)

    Solves a lot of creation issues

  • The peer its targetx , targety are not known on the host, nor synched, nor transmitted.

    Hence the host never fires the events for peer related movement in event 75.

    I would try and add a mouse button clicked (getbit on host's end) to grab the current lookx and looky and set those as targetx and targety. (would prevent synching more variables)

    Also, the movement related bit on event 75 is run under a Multiplayer.MyID, that will never fire on the hosts end for other peers, it would need to be in a loop for all peers and host.

  • [ > any .capx to understand better ? thanks > I forgot it after I saw it the first time, I had another example of something similar with a platformer going round in loops with layouts. But I made a small new one to show.

    demo

    capx

    I used red circles as images, but they could all be separate images of a larger image placed strategically on the right corners.

  • Look at the standard RTS example template, in there is exactly what you need.

    It has group movement with pathfinding. Even has a nice trick to slow speed when getting close to one ahead.

  • The video looks very good, and impressive to see space sim and ground force rts game play combined.

    Would be nice to see and play a demo

  • Should be:

    for 0 to array.width-1

    Redundant ... it would not have been > 0 anyways

  • ninja'd but here we go:

    global number highest=0
    
    +----------------------+
    |                      | set highest to array.at(0)
    +----------------------+
       +-------------------+
       | array: for each x | set highest to max(highest, array.curValue)
       +-------------------+
    [/code:2svqpcd9]
    

    fancy

    I'm always fumbling with the build in array options :\ and tend to use:

    var = 0

    for 0 to array.width

    (compare 2 values) array.at(loopindex) > var set var array.at(loopindex)

  • use local var = 0

    loop through the values in the array

    if array value > local var set local var = array value

    local var will have highest value from array

  • > Do as google does, slice it up in parts.

    >

    Which will only help if you dynamically load and unload them from memory, right?

    Which construct 2 doesn't do as far as I know..

    All images on a layout are loaded into memory at start of layout..

    https://www.scirra.com/blog/112/remembe ... our-memory

    Slicing it up in parts will aid the rendering. (Image not on screen etc)

    Also, some devices are unable to handle image of enormous sizes.

    He could, divide the sliced parts over layouts too. i.e. have 4 pieces on each layout, the cross section in the middle, if you come close to one of the layout edges, load the other layout corresponding to images.

    example, the 4 squares would be layouts, the transparent squares image parts.

    This could greatly reduce the performance problem. It just requires a bit of smart approach <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

  • Do as google does, slice it up in parts.

  • As a solo developer, you will need great descipline to finish up on certain elements or aspects, or have enough insight/restraint to not get lost in nitpcking details of your creations.

    Being able to step back and pick up another aspect of the current development project can be a massive time saver.

    I have grown accustom to working max 2 hours on a single issue at a time. Often, having taken a step back and looking at the same issue a day later, does wonders for thinking up applicable sollutions.

    This obviously can work well in collaboration too.