Viewport Raytraced issue

Rendering
1

Dear McNeel, dear Forum,

I know my PC is old… but is it ‘so’ old?
Intel(R) Core™ i7 CPU - 950 @ 3.07GHz, 3068 Mhz, 4 core, 8 logic processor
12 GB Ram Corsair Dominator
Nvidia GTX 1060 6 GB

  1. When I use Raytraced viewport Rhino gets painfully slow. It gets almost impossible move and rotate objects, till waiting several seconds to get an answer from the program: clicking menù, trying to get a selection… whatever you want to do. Raytraced Viewport big or small… it’s all the same

  2. When I change Type of Mapping, Size of textures and so on, to get the refresh of Raytraced Viewport I have to activate another Display Mode and then come back to the Raytraced Viewport: i.e Raytraced Display Mode to update- > Shaded Display Mode → Raytraced Display Mode updated

I have tried a lot of things, reducing viewport quality settings, creating mesh before to go to Raytraced Viewport, reducing raytracing passes and several others attempts but nothing help

I have attached two videos just to show some of the issues I note, sometimes a little better, sometimes much worse: (for what I know ‘XBox bar’ doesn’t record new windows, just the first one you select, so menus and rendering viewport will not be visible)

‘Raytraced Viewport Selection.mp4’ Video shows how much time I sometimes have to wait to get selected or deselected object: 5 seconds (8-13 seconds and 20-25 seconds)

‘Raytraced Viewport.mp4’ Video shows the need to pass through another Display Mode to refresh Raytracing Viewport (20-26 seconds) and the greatest difficulty to Move and Rotate objects (45-75 seconds). It seems that starting and ending Rendering degrades peformance, to say… eats up resources without releasing them (Raytraced Viewport Selection.mp4’ Video at 43 seconds)

In Blender Cycles I can manage much more complex objects and in great number without slowing down at all, so may be my PC isn’t so old, true… they are different program, but that is.

Reading a recent post ‘Rhino 8 release - too early?’ I think so too, reading the posts maybe there are too many issues after three promo months, but each of us will continue to love Rhino, and I’m sure very soon we will go running in the savannah with him again. True what some users say: better improve what’s on the plate rather then add new features, but it is not an easy task for a commercial product, if not impossible. Neither FreeCAD do it, and it’s a great pity.


SystemInfo.txt (2.1 KB)

Thanks for help,
Bartle

2

A 1060 and 12GB of RAM has never been adequate for ‘working’ in a raytraced view in Rhino since such a thing existed. Bare minimum would be 1080ti-level–I have one, and I don’t actually ‘work’ in raytraced.

3

Yes. That is severely pushing it really. You’re really likely into the realms of at least Skylake to keep going now.

Also, you have paired a 2016 GPU with a 2008 CPU? This is likely to cause architectural imbalance.

You may even be strangling that card with the lack of PCIe lanes, as the card will merely drop down to whatever it has.

My (rubbish) advice is that if you wanted to spend as little as possible, you may be able to get down to $400 which will at least get you to an Alder Lake 12100F quad core, which isn’t great; but it gets you somewhere that you can at least upgrade from. You can carry the GPU over.

4

Hello everybody, thanks for reply.

It’s not encouraging, it’s just a cube, but I fear your are right. I figured the cpu could be the bottleneck.

Looking at others post I thought could be a poor Rhino performance, looking at System Requirements my PC seemed not so bad, and having no problem with Blender…

It’s all the same. If that’s the case nothing I can do, Motherboard is too old, and I can’t change PC.

I will give up to raytraced Viewport. Thank you for the bad news :sweat_smile:.

Best regards,
Bartle

5

@Bartleboom if you go to Tools > Options > Rhino Render then you can bump down the viewport sharpness one notch to begin with, then bump more to the left until you think you can deal with the coarser image result, but have also the responsiveness as you feel comfortable enough. Note that you have to restart Raytraced after every change to the sharpness.

I hope to have adaptive sampling in Rhino 8.6 which should get faster results as well.

6

Hello @Nathan, thanks for reply. Much appreciated, like always.

I think to have found a way to use raytraced Viewport without many compromises, I will also follow your advice to improve your peformance (Argh… I didn’t restart Rhino :man_facepalming:). Isn’t my pc, just a bit, it’s old but not so old, and it is not a Rhino perfomance issue; if anything, it’s about procedure.

This is my walkaround:

Open a File and disable Denoise in Viewport Post Pro.

Then I activate Raytraced Viewport. At this time I’m able to manage most raytraced objects, with the most complex I just have to wait a bit the automatic conversion from Nurbs to Mesh… in this case the processor is the bottlneck, but that’s all.

I hit Render… at the end of the Render, close the window… here are the problems. Difficult to move, to Rotate, to Select… I had to change View Mode to refresh Raytraced Mode and so on.

It seems that Render doesn’t realease resources after closed, so I click the little arrow at bottom left of the raytraced window to restart raytracing inside Viewport, in this way I can Move, Rotate, Select, using menu… smoothly.

Thanks a lot. Look forward for new SR.

Good job to you, I think you are busy as ever. I appreciate a lot your commitment.
Best regards to all McNeel crew,
Bartle

PS For what I know ‘XBox bar’ doesn’t record new windows, just the first one you select, so menus and rendering viewport will not be visible, but they are there

7

Once you start a Render in the render window any active Raytraced view will be paused, because otherwise everything would become even slower. You can see in the HUD that the Raytraced view is set to Paused and the two vertical bars that are essentially a pause button turn into a Play button. After a render you will have to press that play button to continue interacting with the Raytraced view. This is what you see and how it is designed to work.

8

Thank you Nathan, sorry for abusing your time.

From now on I think I have to:

Write less
Read More
Experiment deeper
Think better

And forget a bit of Blender: different sotware, different procedure. You can take things for granted when they’re not.

Thanks a lot.
Bartle