Status:
Vuo version:
Fixed in Vuo version:
OS version:
- OS X 10.11
Steps causing the bug to occur:
- Render a scene in the Render Scene in Image Node.
- Set multisampling to any parameter > 1.
- Get glitches.
I join the modified example composition "Render Sphere". Hope it's not my Graphic card again :( I can post my computer specs again if needed.
How did the result differ from what you expected?:
No Glitches.
Have you found a workaround?:
Not really. Set no multisampling >1 ;)
Screenshots:
Compositions:
| Attachment | Size |
|---|---|
 DisplaySphere RenderScene Mod.vuo | 2.28 KB |
Comments
Render Scene to Image also
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.
1: Render Scene to Image.vuo
2: Render Scene to Window.vuo
Alpha 3.png
Alpha 4.png
After reflexion It could also
After reflexion It could also come from the "Render Image to Window" node but I doubt that.
Hmm, we aren't seeing either
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.
I will update the In 1.2.0
I will update this thread's title to Intel HD GPU instead of ATI.
@smokris
Steve
Mmm. Actually I don't have an ATI graphic card on my MBP 13" but an Intel HD 3000 (0x8086)
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 !
A - Solved Bugs on my HD Intel 3000
B - Unsolved bugs for my Intel HD 3000.
High CPU usage for high frequent events + meshes render on CPU instead of GPU This is still the case. Add noise to call rendering at 5 fps etc. (Perhaps the new OpenGL Vulcan version will allow nearer GPU access and solve this).
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.
In 1.2.0-alpha4 (but not alpha3), "Render Scene to Image" outputs a glitchy image (+ slows framerate down) is the latest alpha 4 bug we are commenting here. The Vuo team changed this title to add ATI gpu but it's on the Intel HD 3000. I should have always post my graphic card specs again, my fault.
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.
Hope I clarified this ;)
About this mac.png
GPU Info.png
@smokris
Steve
Just ran the test received by email.
The only app that does not glitch is CC-Byte. Both -Int and -Short glitch.
I did however not notice any difference in the glitch performances ;)
The only app that does not
Great; thanks for testing.
The final Vuo 1.2.0 release used the technique in
cc-byte, so that part of this issue should be fixed.…but I'll leave this bug report open to address that issue.
Vuo 1.2 solved this for
Vuo 1.2 solved this for multisampling up to 4x on my GC but still happens with 8x.
Could the CC-byte have been omitted for the 8x ? Or it could be just my graphic card not able to multisample at 8 ;) !
Also saw this The parametric grid does not display hope it is not related.
LayersInImage Image Protoc.mov
SceneInImage Image Protoc.mov
4x - 8x : Requested Frame : No Protocol.mov
We'll look into it.
We'll look into it.
Vuo 1.2 solved this for
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.