R0J0hound's Forum Posts

  • To make it one object you can either use a tilemap or use a paster/canvas object.

    You can draw the terrain to the canvas or paster object, so you'd have only one object. It doesn't do anything for collisions though.

    With a tilemap you just set the tiles with events and you get collisions no problem.

    As far as wrapping you'll not want a single object.

    With just sprites as you have you could do this:

    sprite: x < viewportLeft

    --- sprite: set x to self.x + layoutWidth

    You could also reduce the number of objects to one's on screen and just update them from the array as the player moves.

  • Why not just create your graphics with outlines?

    Another option would be to use the paster object to only create outlines for the stuff on screen. Basically paste all the objects you want to have an outline to it. Make it all black by pasting a all black object to it with a blend mode. Then finally pasting it to a second object in all 8 directions.

    The shader would likely be the fastest. I don't use webgl anymore so I haven't touched the effect in a while.

  • Look at the canvas or paster plugins. A search will also give some examples of doing this.

  • The latest version of nw.js:

    https://www.scirra.com/nwjs

  • You just select file->export project, and select html5.

    https://www.scirra.com/manual/122/expor ... publishing

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • "every tick" isn't the issue, even with nothing in the project the mem usage goes up slightly in NW.js. When run in the browser the profiling tools say the mem usage is basically constant, so it's probably an issue with NW.js. Do you have the latest?

  • Use a layer. Make the objects not be transparent at all, instead make the layer they're on transparent.

  • You can use the .asJSON expression to get a copy of a object's state, then you can use the "load from json" action to load it later.

    One way to utilize that is to save it to a global variable on the end of one layout and load it at the start of another. Or another idea would be to make the object global so it wouldn't be destroyed.

    If you don't want the warmup at all then you could temporarily add a edit box and set it's text to the particles.asjson once they cover the screen. Next copy that text to your favorite text editor and replace all the " with '. Then put " around the whole thing, it is now a valid text that can be used expressions. So you can make it load that into the object at the start of the layout.

  • There isn't one, but if there was it would do the same thing as setting the layout angle and scroll position.

    I guess you could look at the magicam plugin but that's mainly for camera transitions.

  • No, it's just an issue with my plugin.

  • Put it in another event sheet and include that sheet in the level event sheets.

  • It's probably happening because the plugin expects the points to be placed in a certain direction (cw or ccw). The fix would involve detecting the direction and re-ordering the points.

  • Yeah. So if your polygon is like this:

    1----2
|    |
|    |
|    |
|    3----4
|         |
|         |
6---------5[/code:3r7n7a4h]

drag the points around so it's like this:
[code:3r7n7a4h]1----6
|    |
|    |
|    |
|    5----4
|         |
|         |
2---------3[/code:3r7n7a4h]

  • Changing the collision polygon so the points are ordered opposite what they are now seems to fix it. I'm backlogged on plugin fixes, and I've been avoiding them, so no eta on a proper fix.

  • Bodhran

    All the effect does is distort the image or sprite to be on a 3d plane. Positioning stuff like walls requires math matching the distort or using the plugin by rexrainbow. To do something like keyo is doing, you'll have to use separate objects with different mode7 settings. There's a capx with the math earlier in this topic, but i still recommend the plugin.

    What I mean by collisions is to design the objects and walls in top view so they move around as wanted. Then you take those positions and map them to the distort as explained above. It's probably a bit tedious to do though.