Rhino 8.5 Ghosted display slow

Hi,

In the new RH8SR5 the ghosted view port is quite slow. Its hard to make an accurate test about this because im using linked blocks that are saved in RH8, so I can’t test is 1:1 in Rhino7.

I could reinstall Rhino 8. To the latest SR version instead of a SRC version, but I dont know if that is the best path to go.

Right now I have made a copy of my drawing and have embedded all linked blocks. I also have made 2 copies of this file, 1 in RH8 and one in RH7.

Both are _Zoom Selected to my main object (a block with alot of nested blocks with even more nestedblocks etc. Containing Crv’s and PolySrf’s)

Displaystyle: Ghosted, transparency 50%

Using the command _testmaxspeed
RH8SR5: Time to regen viewport 100 times = 45.25 seconds. (2.21 FPS)
RH7 SR36: Time to regen viewport 100 times = 6.03 seconds. (16.58 FPS)
:exploding_head:


RH8SR5


RH7SR36

I dont think that there are differences between the settings I have for them:
_OptionsExport

RH8 SR5
_OptionsExport RH8SR5.ini (447.3 KB)

RH7SR36
_OptionsExport RH7SR36.ini (396.6 KB)

Visibly you can already see a huge differance between these versions, and the testmaxspeed provides the numbers to back these up.

  • Are my RH8SR5 ghosted setting wrong?
  • What would be best settings for this? (I would rather not work in Shaded. I really like the RH7 ghosted view, it gives alot more info when drawing.)
_systemInfo

Rhino 8 SR5 2024-2-20 (Rhino 8, 8.5.24051.15001, Git hash:master @ 8ad7c99e58df0a8c09e572ba1ae2b52a6f429060)
License type: Commercial, build 2024-02-20
License details: Cloud Zoo

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.0

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2060 (NVidia) Memory: 6GB, Driver date: 1-18-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 551.23
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port 0
- Secondary monitor attached to adapter port 1

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: 1-18-2024
Driver Version: 31.0.15.5123
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 6 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
C:\Program Files\Rhino 8\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\BlockEdit.rhp “BlockEdit” 8.5.24051.15001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

Thanks
Martijn

Could be a block related bug. As a test, if you explode all blocks completely, do you see the same difference?

Hi Gijs,

Yes, it made a difference! When exploding the model in RH8SR5 the transparency came back to what I expected it to be.

My model is currently like this:
Main block (1) containing sub blocks (2).
In that sub block (2) are more sub blocks (3). Tis last layer of blocks (3) contains the PolySrf’s that aren’t correctly ghosted.

After some quick testing I found out:

  • Exploding Main block (1) makes no difference.
  • Exploding sub Blocks (2) made a difference.

My conclusion is that the ghosted view only works 1 block layer deep. So: PolySrf inside a block is :white_check_mark:, add that block in another block and problem accurse.

To test this a made a really simple test model, 3 cubes nested inside one another. You see when I start _explode and _Undo that the visibility changes.


240223_RH8SR5 Ghosted problem.3dm (64.9 KB)

Secondly what is strange, I checked my drawing on another device there the file was fine (Also on again another device there the file was not fine). So I think its also a hardware related problem. This is harder for me to test, hopefully you can look into that using my System Info posted above.

Ow almost forgot:

I _explodeblock both models

RH8SR5: Time to regen viewport 100 times = 5.31 seconds. (18.82 FPS)
RH7SR36: Time to regen viewport 100 times = 5.30 seconds. (18.88 FPS)

Selection details

4961 points, 23091 curves, 123 surfaces, 2740 polysurfaces, 86 extrusions, 18 linear dimensions, 229 texts, 170 hatches added to selection.

So yea, the problem is undoubtedly something in the way nested blocks are rendered/loaded.

hi Martijn,

in my test all the shaded modes are significantly slower.
RH-80594 Blocks are slower in Rhino 8 than in Rhino 7

A post was split to a new topic: Nesting blocks affects object transparency

Hi @Gijs,

I saw that in YT this bug has mostly been solved. Do you have an idea when this could be implemented in rhino?

Personaly I still work in shaded mode just because ghosted mode just isnt working for me.
RH-80621 would also be nice, but I’m ready something in YT that: Ghosted looks again the same as in Rhino 7 now.

So yea I’m looking forward to work in ghosted again.
tnx

Not sure what you mean, both yts are closed and should be in current SR

What prevents you form working in Ghosted right now?

To me it still feels like RH8 is slower in ghosted.

Let me reinstall RH7 to test this out.
Exporting a part of a current project in .step to load both in RH7 and RH8 (needs to be step because al my linked blocks are in RH8 that will cauls problems this is the easies route for now).

Personally I would say there quite the difference between RH7 and RH8.

As always

SystemInfo

Rhino 8 SR10 2024-7-30 (Rhino 8, 8.10.24212.13001, Git hash:master @ bf71fa5917a747cb0d08481b3fcbd3bce0923e77)
License type: Commercial, build 2024-07-30
License details: Cloud Zoo

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.0

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2060 SUPER (NVidia) Memory: 8GB, Driver date: 3-8-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 531.30
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1

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: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-8-2023
Driver Version: 31.0.15.3130
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\export_STEP.rhp “STEP Export”
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\BlockEdit.rhp “BlockEdit” 8.10.24212.13001
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

It is.

@Martijn let’s make sure we test one thing at a time. Do you see the same speed difference when that block is exploded?

Is the ghosted mode in both the stock ghosted mode?

What is the HUD in the lower right corner of your Rhino 8 viewport?

The hole thing is now a linked block in this drawing, do you want me to

  • embed it?
  • ExplodeBlock to just objects?

Just resetted both display modes

Should be nothing interesting, just a listening script to check if the viewport is parrallel or not, ( to set Project snap on or off) ( We still need to check if we can retire that script since RH8 now as a simmilar function). Let me close both scripts.

yes, just as a test to make sure we cut out blocks out of the equation.

what’s the polygoncount you get in both?

In my testing here with a large nested block, after exploding things get a magnitude faster.

Okey, done. Purged drawing, saved drawing, closed and reopend file

Testing it again, would say it has gotten better but still you see a big difference in frame rate.

Also, this exploding the blocks is only an advantage to RH8, RH7 didnt have any problems with the hundreds and hundreds of blocks and nested hundreds that are in this file. (980 I saw in the purge report). This it self is a problem in RH8.

RH8:
Command: polygoncount
Select objects
There are 942.342 quadrilateral polygons and 1.575.491 triangular polygons in this model
There would be 3.460.175 total triangular polygons in this model after forced triangulation

RH7:
Command: polygoncount
Select objects
There are 945.955 quadrilateral polygons and 1.561.641 triangular polygons in this model
There would be 3.453.551 total triangular polygons in this model after forced triangulation

This I agree, but in a magnitude of this drawing (and me this is a normal file) this is not tipping the bucket.

I was testing with this file:

testing 1024 x 768 viewport I get:

~1fps with the block in ghosted vs 10fps exploded in Rhino 8
~5fps with the block / exploded block in ghosted in Rhino 7

I’ll ask if there is something that can be done to improve performance for blocks

1 Like

RH-83267 Display speed for blocks in Rhino 8 in Ghosted mode

Something is definitely not right with transparent blocks and isocurve drawing…Not sure what yet…

If you turn OFF “Show isocurves” in your Ghosted mode (but leave edges ON so you still can see some wires), then you’ll get a huge performance boost… This is not a solution, I’m just pointing out the potential bottleneck here, and where I’m currently focusing my investigation.

-J