¿why is my pixel-based drawing program slower than the vector-based GDPaint?

Sosasees

i tried my pixel painting program, and something unexpected happened: it runs Worse Than GDPaint.

while GDPaint reaches 12FPS quickly on my phone (with just ~1000 Brush Objects, which is barely any painting time at all), my pixel-based drawing program is 12FPS At All times, and that's just 16×16 pixels instead of GDPaint's 930×720. ¿how does this happen? logically, my project should be faster since it uses just pixels, while GDPaint uses vectors that have to be converted to pixels first. please explain why the pixel-based drawing program is Slower than the vector-based one.

cybereality

Pixel rendering is not always faster than vector. When you render to a texture, you need to lock the image first, than draw, then unlock, and then the engine copies the texture to the GPIU. But this can be expensive. It also depends how it is coded, you should get better performance that 12 fps, so maybe something is wrong with your code.

Sosasees

@cybereality said: It also depends how it is coded, you should get better performance that 12 fps, so maybe something is wrong with your code.

by clicking on "my pixel painting program" in the first sentence of the beginning comment (or here, for convenience), you can see my source code and try it in Godot after downloading it.

maybe then you can be much more sure what the issue is.

likely this has to do with 256 of the nodes in my pixel painting program being a TouchScreenButton that is a child of the "Pixel" scene that is instanced 256 times to create the full 16×16 pixel image.

Sosasees

i just made a modified version of my program that creates the pixel image at 930×720px (the same image resolution as GDPaint), and when i started it with the Playtesting button it's stuck at the "Godot Engine" splash screen (probably to protect the computer's OS because it might freeze otherwise).

this version of the program is a failure, but it's fast failure (only 1 afternoon to make and 2 days to test) which means that it's a success because i know a better direction for my project: making it a GDPaint mod.

cybereality

@Sosasees said: likely this has to do with 256 of the nodes in my pixel painting program being a TouchScreenButton that is a child of the "Pixel" scene that is instanced 256 times to create the full 16×16 pixel image.

That's probably why. That's not a good way to do it.

cybereality

Just to elaborate, you should probably just check for touch the top most node, you can use Input events to check for mouse and touch movement. The event will have data, like event.position, which will give you the global position of the click/touch, which you can use to draw.