Yes the problem persists in Blender 4.3 Alpha.
Morning @iss I've attached a video example showing 4.2 vs 2.93 👍
@OmarEmaraDev Yes this one can be closed down now thanks to the fixes you made 👍
@3di Which commits exactly caused the slow down?
Ignore, i'm mistaken, it was also 4x slower in 4.1. I must have had frame dropping when testing previously.
In your patch above I'm getting a crash when creating a new panel during playback now. Log attached.
Thanks @OmarEmaraDev the build above has resolved the fps gradually getting slower and leading to a crash!!! Brilliant, thanks.
Regarding the GPU fps now being around 4x slower than CPU since…
If it helps shed any light, here's a new crash log generated from the same steps as the report, but in GPU mode without the backdrop or image editor present. GPU mode was fine prior to the two…
Morning @Sergey , the above demonstration is when using render.render(). I was following the exact steps of the report, only this time I was demonstrating that the problem has worsened in GPU…
Also, GPU mode now get around 1/4 the fps as CPU mode.
I've just done some further tests too, and found that the slow down and crash now happen in GPU mode even if the compositor's backdrop…
Here you go, third time the charm :)
ah, i'll bet it's because the property was previously 'execution_mode' when I created the file.
I'll try again, but this time swap to gpu and back to cpu before I do anything, just in case the visible property is not representing the actual value.
was 100% using cpu compositor, I double checked. But now you mention it, the other day I had it set to CPU but it was calculating lens distortion nodes at GPU compositor speeds. I thought my cpu…