DrawingCanvas - is there a way to paste sprite/tile without having to wait?

That's how Construct works - if the object doesn't exist on this layout, it takes time to load its texture. You can try running "System Load object images" action in advance. A wait will still probably be required, but you can reduce it from 0.1s to a single tick - "Wait 0".

But the best solution would probably be keeping an instance of this sprite on the layout.

dop2000

Hello, I added the action, but it still is not working.

Yes I need the wait to reduce as much as possible but in my game, it will not be a good idea to set all sprites or tiles on the layout because there are 10-15 sprites and are nearly 400*400px which may affect performance.

Maybe I did it wrong.

Or I should do that on start of layout? But still there's too many sprites to be loaded in memory

In construct 2, there were no such issue using the Canvas plugin. So this looks like a step down to me of how the DrawingCanvas works.

Alright,

For the time being, I'll put them in the layout, since it is working fine without any delay.

I'll still file an issue later on why the Canvas plugin is working better in C2 compared to DrawingCanvas in C3. For Ashley

Thanks! dop2000

Ashley

Hello, my issue is the render time before we can paste on the drawingCanvas object. I have noticed that when the object is on a grave layout and will be created on a new layout via code... it takes few m/s before I can paste it on the drawingCanvas. This is worst on low/mid end devices (Tested on J7, A30 and few others).

1st solution is to add it to the layout itself but having too many objects will increase the image memory on low end devices. Right now I have approx 15 tiles. Later I might have 30 or even 50, so this solution is not the best.

2nd solution is to use wait 0.1s if there's none of the sprite/tile on the screen. Or use "wait for previous actions" when creating and pasting... but this doesn't work all the time.

Anyways... on C2, the canvas plugin was updated by R0J0hound and currently this is fast and works on low end devices without any issue.

On C3, even though it is not the same plugin... it still is a step down for me, since the waiting time is so much visible on some devices; and players will see unintended items while the wait is in process (yeah even by m/s). The issue below happens when the sprite/tile is in grave layout and this works and sometimes doesn't, because it need to wait for it to render completely. It will work if I use 0.1s but I don't want to.

I know that Construct 3 can do better. So please check it out.

If you create an object that is not placed on the layout, Construct loads its textures on the fly, and that can take a moment on low end devices. In that case the 'Create object' action is effectively asynchronous and you won't be able to immediately paste the object to a canvas, because the object hasn't loaded its textures yet, and so cannot draw itself.

The easiest solution is to place the object on the layout, and destroy it on startup. Then Construct pre-loads its images when the layout starts. (See Memory usage in the manual.)

Otherwise you can use the system memory management actions, e.g. the 'Load object images' action, before creating the object. Something like Load object images, wait for previous actions to complete, and then 'Create object' for the same object, will then ensure it is ready before creating and so it should be able to paste to a canvas straight away too.

(FWIW Construct 2 loaded objects synchronously, and that could jank the game. Construct 3's approach ensures a smooth framerate and better performance loading lots of objects. This is not 100% compatible with C2 projects though and so is a documented compatibility issue moving from C2 to C3.)

Ashley

Okay, I understand now. So it's more about how C3 handles the creation/loading of the objects.

I'll stick to this like before... "The easiest solution is to place the object on the layout, and destroy it on startup"

Thanks.