Render Scene to Image also slows the framerate a lot.
For example the joined composition A runs at 60 fps in alpha 3, drops to 30 fps in alpha 4.
What makes me think that Render Scene to Image is the concerned node is that the same composition rendering directly to the window instead of in an image (composition B) stays at 60 fps, even if in alpha 4.
The only difference when running composition A in the two Vuo versions is the fact that the points are not shaded in alpha 3 (that bug I mentioned and that has been solved).
PS : I could have used the new Make Random Points Object to build the points but I wanted to be sure no other new nodes were used.
Hmm, we aren’t seeing either of these problems (glitchy rendering or performance difference) on any of our systems here. I guess it’s your very special graphics card again :^/
However, I think I know which change may have caused this to break. I’ll see if there’s an alternative that will work better on ATI GPUs.
Mmm. Actually I don’t have an ATI graphic card on my MBP 13" but an Intel HD 3000 (0x8086)
I once originally started a bug report from another computer, an iMac with an ATi Graphic Card and could reproduce it on my Intel HD 3000 too… It was this bug here Built-In Sample Compositions using Displace With Image Bug Alpha 3.
Alpha 4 solved the issue on my Intel HD 3000 MPB, I will be able to test this on the ATI iMac in December. Partially solved !
ALL THE OTHER BUGS I REPORTED ARE FOR THE Intel HD 3000 graphic card. I will try to clarify these bugs again so you can mark some solved bugs !
Lagging Compositions on Startup seem a little better in alpha 4, but still not smooth. Make rugged terrain still take starts choppy, needs some seconds to smoothen.
Perhaps the Vuo team could want to merge my Intel HD 3000 bugs and copy-paste this text under a “Some Intel HD 3000 bugs” for easier overview. Don’t know.
Vuo 1.2 solved this for multisampling up to 4x on my GC but still happens with 8x.
It turns out that multisampling is only supported up to 4x on the Intel HD 3000. In Vuo 1.2.2, we added a check to avoid the glitch if 8x is requested.
In your first comment you mentioned a performance drop. We couldn’t reproduce it on our Intel HD 3000. Could you retest at Vuo 1.2.2? If you still see a problem, please create a separate bug report.