@nathanletwory may i ask you if there is a way to speed up the viewport manipulation while being in raytraced? currently it does not seem to degrade the preview at all which would speed it up usually i assume, when i change the camera or do any kind of geometry moment etc. the initiation takes a long time and the viewport rotation is very sluggish. besides that the initiation always seems to take a bit time before the cycles start counting. for the viewport manipulation i thought that RhinoCycles.DpiScale could be an answer, yet does that not change anything setting it to 2, 4 or whatever. is there anything else i could try?
i also tried RhinoCycles.StartResolution setting it to 4, while RhinoCycles.UseStartResolution is set to true without changes.
oh and i also tried changing the shadow settings in the display modes hoping that these would affect the manipulation at least, i believe it does not effect the actual rendering.
Check if clicking the star icon on the HUD for Raytraced to turn off post effects (denoise) makes a difference. Also check if having the viewport smaller helps.
yes that is the first thing i always turn off, i requested for this to stay off by default since it makes such a mush out of the viewport in the first moments till it picks up rendering.
though i have a 4 k screen, making it ridiclously small helps a bit but really not much. i still feel that there could be something optimised, i had the feeling that this was better in an earlier version v6 maybe when the start resolutions where changed, right now nothing seems to increase the speed. was there something changed or is all that thanks to my 4 k screen (scaled)?
just to be sure, i am only talking about rotating camera and stuff, i am aware it could be super pixelated during manipulation but at least it would allow me to manipulate the viewport without growing grey hair
Cycles behind Raytraced in Rhino 8 now automatically does the resolution division if it thinks it is necessary to do so. I have not touched the heuristics for it to determine when to do resolution division.
The DpiScale advanced setting doesn’t do anything in Rhino 8, nor do StartResolution and UseStartResolution.
In Rhino 8.12 the startup of a render (be it Raytraced or _Render) has been improved by parallelising many parts.
its a default template with a cube, no materials not extra light, i can upload you a file but that would not change anything i guess?
i actually had 8.12, but the most recent candidate shows improvements, maybe i am imagining it.
but bottom line is that viewport navigation can not be improved currently? can it not switch off all the bells and whistles while being manipulated? could it switch to rendered view while being manipulated? its just about being able to rearrange the geometry quickly anything that would help. its currently really difficult to work in. of course i can set it to rendered but then i have to change to raytraced, with this forth and back that would become bothersome..
side questions:
was does RhinoCycles.Threads mean, it was set to 18 i assumed its the amount of cores and set it to 46 which seemed to have improved rendering speed can also be coincidental now.
There were some speed improvements during 8.12 cycle, and some further during 8.13 cycle.
Not easily no, and big (code-wise) changes will only go in Rhino WIP. Either way rendering performance is already much better in Rhino 8 than compared to Rhino 7.
It will already drop to a form of OpenGL/Metal if some time limit exceeds. It probably could be useful if the moment to show rendered mode could be configurable. Because in smaller scenes this all is very fast.
Here a big scene (900MB, 2200 objects, 259 materials) on my M2 Max, where you can at times see the fallback happening.
And here a simple 1-27 cube model
That is used when rendering with CPU. It is controlled by the CPU Utilization slider
The time between moments to signal Rhino that there is something to draw. Actually, setting this to say 5 may make the viewport feel smoother (as many more frames are potentially drawn, especially with less heavy models). As comparison both scenes of the prior two recordings but with 5ms throttle.
ok, so that sluggs arround quite a bit either hmm i tested the 5 ms or 1 ms or anything i could not feel a difference…
that sounds like what is needed, some form of drop, the moment i let go it can start rendering again, but right now it feels like pulling a hundred horses, when the hundred horses should be pulling me
if you get around to cooking something up as a test feel free to hit me up to try pls. some setting in the advanced or what not would be great.
For the less complex models I find Raytraced is pretty smooth in the viewport manipulations. The big model sure is slow.
Even the brick models I use, with a couple of thousand block instances of over 200 block definitions is responsive in viewport manipulations - but then again it isn’t that complex in rendering because there aren’t as many objects with glass materials in.
Anyway, bigger performance improvements most likely will go in Rhino 9.
well its unusable on my computer even with a simple file. i have an m1 mac studio ultra with 48 cores gpu which costed 4.500 euro 1,5 years ago… am i a due for an update?
hmm i tested the 5 ms or 1 ms or anything i could not feel a difference…