Latest V7SR very slow load to get into render mode and cycles

Hi,
The current sr and last sr I noticed a regression in how long it takes to get rendered mode to work.
I have two files where I experience slow load times to get into rendered mode. One is 289 meg and the other is 271 meg.

I never save files or rarely with a rendered view active.
When I first open a file and that file has viewports set to wireframe if I click on the “standard default rendered mode” for a viewport it now takes over 3 minutes for rhino to show the scene in rendered mode. But after this big lag if I go back to wireframe and then back to rendered mode it now only takes seconds to get into rendered mode. Seems there is something going on that is taking longer than it was 2 srs back when first opening a file.

Oddly the same happens when I go to render in cycles. For the first render it takes 3 minutes or more for that first cycles screen to appear it seems to the user rhino doesn’t appear to be working but if I wait rhino renders the cycles window finally appearing after 3 minutes. If I render again after this first rendering the cycles window only takes 8 seconds to load or appear on screen.

Kind of an annoyance as it gets worse in my other slightly larger file.

RM

Rhino 7 SR34 2023-9-24 (Rhino 7, 7.34.23267.11001, Git hash:master @ a37d83041828484840f2448d5b3e3770e46694f9)
License type: Commercial, build 2023-09-24
License details: Stand-Alone

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32Gb)

Computer platform: LAPTOP - Plugged in [92% battery remaining]

Hybrid graphics configuration.
Primary display: Intel(R) HD Graphics 530 (Intel) Memory: 1GB, Driver date: 8-20-2021 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- Secondary monitor is laptop’s integrated screen or built-in port
- Windows Main Display attached to adapter port 1
Primary OpenGL: NVIDIA GeForce GTX 960M (NVidia) Memory: 4GB, Driver date: 10-4-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 537.58
> Integrated accelerated graphics device (shares primary device ports)
- Video pass-through to primary display device

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)

Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 10-4-2023
Driver Version: 31.0.15.3758
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB

Rhino plugins that do not ship with Rhino
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Twinmotion Direct Link 2020.2 (e24ee14a-9514-47da-8fe6-f6e61b20160e)\Twinmotion Direct Link 2020.rhp “Twinmotion Direct Link 2020” 1.0.6.0
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.1.1.0
E:\Downloads\elefront411\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\Users\User\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
E:\rhino3d\BoltGen\BoltGen1_62.rhp “Rhino.NET SDK” 0.0.0.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Users\User\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SectionTools\2020.12.7.446\SectionTools.rhp “SectionTools”
C:\Program Files\Rhino 7\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Users\User\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\PanelingTools\2020.9.1.565\PanelingTools.rhp “PanelingTools”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.34.23267.11001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 7\Plug-ins\Calc.rhp “Calc”
C:\Program Files\Rhino 7\Plug-ins\NamedPositions.rhp “Named Position”

  • During the time lag, does Rhino report it’s making render meshes?
  • Are you using the ‘Save Small’ option to strip out the render meshes when saving?

Hi @John_Brock

No nothing on the command line.

No

Perhaps it’s my aging system, something in these files or something in Rhino? I did update my video driver before installing Rhino but this was occurring before the driver update and persisted after the driver update.

Thankfully this behavior goes away after the first time using rendered viewport and then rendering in cycles. I wanted to give the heads up in case anyone else was running into this.

Thanks for your reply,
RM

I’m also interested to hear if you are using the “ClearAllMeshes” command to reduce the filesize since that will force the first display of anything “rendered” such as a Rendered DisplayMode to create the rendermesh it is actually missing. I guess it is also one of the thing which are lost with “Save Small”?

For me it takes 85 seconds to open a file, which is saved with RenderMesh (Only 1 rendered Viewport) and filesize: 942 MB.
It takes only 80 seconds to open the file if it is saved without RenderMesh and filesize: 779 MB
That is a 163 MB reduction (17.3 pct) or 20.1 pct more than the smallest of the two if you save with rendermesh compared to without.

Hi @Cadesign_Base
No I’m not using clear all meshes.
RM

Hi @John_Brock

In this file I’m currently having heavy load times getting into rendered view mode. It seems to be persisting beyond calling rendered view the first time.

I wonder if this block/s is the thing causing this?
I did a selbadobjects nothing bad.

Then I did an audit and got this report:
Rhino reports “object should not be on a reference layer” what does that mean and how can I fix this? The block is a tree from megascans that I reduced the polycounts on. I guess I could explode it and purge the block? Also seems that the texture/materials number is getting quite large I don’t think I have 13.000 materials? I haven’t purged this file because I don’t want to loose certain materials.

Document Manifest:
Texture Mapping: 1949 active, 1 system.
Material: 13472 active, 2 system.
Line Pattern: 1 active, 3 system.
Layer: 128 active, 1 system.
Group: 909 active.
TextStyle: none.
Annotation Style: 6 active, 12 system.
Light: none.
Hatch Pattern: 0 active, 9 system.
Block: 1 active.
Model Geometry: 16483 active.

Total: 32949 model components. 28 system components.

object should not be on a reference layer.
m_instance_definition_table[0]->Object(0) should not be a reference object.
Audit Summary:
1 object errors detected.
0 linetype table errors detected.
0 layer table errors detected.
1 block table errors detected.
0 font table errors detected.
0 annotation style table errors detected.
Table tally:
128 layers
1 instance definitions
6 annotation styles
0 fonts
1 linetypes
13472 rendering materials
Object tally:
15974 normal objects
0 locked objects
508 hidden objects
0 deleted objects (in undo buffer)
0 block definition objects
0 reference normal objects
0 reference locked objects
0 reference hidden objects
1 reference block definition objects
Audit found problems.

If you by any chance are using V-Ray for Rhino as your renderengine, you can simply make a V-Ray proxy of your tree and offload both geometry (polygons) and textures (bitmaps). It will then be loaded in as needed during rendertime. I use that for anything except my design to reduce waisting/waiting time.

Hi @Cadesign_Base
I’m not using vray.
RM

Hi Roland -

Can you send the file to tech@mcneel.com so that we can have a look at this?
-wim