V6 rendered mode - I really don't get it

Been meaning to complain about this for awhile, but today’s result is now worse than ever…

Rhino’s on-screen rendition of our terrain meshes in rendered mode has gotten simply awful. Normally I look at terrains in rendered display mode because it turns off the mesh wires. In V5, it was perfect to see the result. In V6, in Rendered mode with AO on as standard, up until recently it was very fuzzy; I ended up making a special Shaded mode sans mesh wires which worked OK. Until today. Here is how a terrain mesh I just generated looks in both V5 and V6:

V5 (Rendered display mode):

V6 (Rendered display mode):

Even my V6 Shaded mode without wires looks bad:

My V6 Rendered mode has not been modified (it’s not blue, but I punched the "Restore defaults button anyway):

image

All I can say right now is… ugh.

–Mitch

Hi Mitch- can you send me that model?

thanks,

-Pascal

Yep, sorry, forgot to upload it in the previous post - here it is, thanks…

MeshRender.3dm (2.4 MB)

Hi Mitch - it looks like this here as I open the model:

OK, right?
What happens if, in the Rendering panel, you poke the ‘restore defaults’ button at the bottom…?

-Pascal

I did… no change…

Hm. And if you delete the rendered mode completely, in the Display Modes list, then restart Rhino?

-Pascal

Nope, no change there either… tried twice. :cry:

Here is the ini just in case… RenderedDefault.ini (11.4 KB)

Hum… I am sorry for the hassle… I don’t have a good idea at all right now, but, just before I call for a Jeff intervention, the image I posted from my machine is what you expect, right? and you’re still getting the high contrast image as you show above

-Pascal

Yep and yep… I’ll try from home tonight on a different machine - different video card. The driver on this one is from October, so not all that old.

Raytraced looks bad as well…

I get that as well in Raytraced with this mesh - looks like some self-shadowing thing going on… Far from the origin… @Helvetosaur - the thing is miles from the origin… Move it in, does that look correct?

-Pascal

Yep, it does… However, that’s unfortunately not going to help as these things are geo-referenced and we need to keep them that way. :confused:

Hi Mitch, and V5’s display handles it at its outer space location, is that right? that gets back to the original point, I guess. The problem is it looks clean here in the shaded (not raytraced) modes in V6 so I can’t yet just point and grunt and say ‘look, regression’ to the display mavens…

-Pascal

Yeah… V5 handles it fine (always did) in the outer space position. I’ll test at home and perhaps on a couple of other machines here and see if I can see some differences.

@pascal - Exact same issue here at home with an Nvidia 780 (the other was a 980Ti), the driver is somewhat older though… (January 2018)

However, here is the result from my laptop:

This is a way older card - K2000M from like 2012, but the driver is from September 2018. I’m still on SR9 right now though.

Rhino 6 SR9 2018-9-28 (Rhino 6, 6.9.18271.20591, Git hash:master @ 4cf7435f08f51c972347c8558d28355cfc0471ca)
Licence type: Not For Resale Lab, build 2018-09-28
License details: Cloud Zoo. In use by: Mitch Heynick (Team SwissRhino)

Windows 10.0 SR0.0 or greater (Physical RAM: 24Gb)
Machine name: SR-ROADBOOK

Quadro K2000M/PCIe/SSE2 (OpenGL ver:4.6.0 NVIDIA 411.63)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

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

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 9-18-2018
Driver Version: 24.21.14.1163
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB

C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.9.18271.20591
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoCAM 2018 for R6\RhinoCAM 2018 For Rhino6.0.rhp “RhinoCAM 2018 - The cutting edge CAM plug-in for Rhino 6.0 from MecSoft Corporation”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 6.9.18271.20591
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\RhinoCAM 2018 for R6\RhinoArt1FileExporter For Rhino6.0.rhp “RhinoArt1FileExporter”
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.9.18271.20591
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.9.18271.20591
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”

Will update Rhino on the laptop and see if it changes anything…

Also try disabling your third party plug-ins and restart Rhino. Just want to eliminate those as a potential cause

Not sure there’s any need Steve. Updated Rhino first to 6.10 on the laptop and it still looked fine, like SR9 above. Downloaded SR11 RC and suddenly the laptop looks like this:

Just like the others. So something got really messed up in SR11…

Here is SystemInfo with SR11 on the laptop and no 3rd party plug-ins…

Rhino 6 SR11 2018-11-19 (Rhino 6, 6.11.18323.19181, Git hash:master @ 0200b43a48c2d93d905df89b7bd77bf8678fdd21)
Licence type: Not For Resale Lab, build 2018-11-19
License details: Cloud Zoo. In use by: Mitch Heynick (Team SwissRhino)

Windows 10.0 SR0.0 or greater (Physical RAM: 24Gb)
Machine name: SR-ROADBOOK

Quadro K2000M/PCIe/SSE2 (OpenGL ver:4.6.0 NVIDIA 411.63)

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

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

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 9-18-2018
Driver Version: 24.21.14.1163
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB

Rhino plugins
C:\Program Files\Rhino 6\Plug-ins\Commands.rhp “Commands” 6.11.18323.19181
C:\Program Files\Rhino 6\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 6\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino 6\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 6.11.18323.19181
C:\Program Files\Rhino 6\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 6\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 6\Plug-ins\RhinoCycles.rhp “RhinoCycles” 6.11.18323.19181
C:\Program Files\Rhino 6\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 6.11.18323.19181
C:\Program Files\Rhino 6\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 6\Plug-ins\Displacement.rhp “Displacement”

@jeff or @DavidEranen, do you think this may be due to the recent gl_frontfacing changes?

Possibly… but I won’t go there again.

@DavidEranen if you know the build of the day right before the gl front facing changes, we may be able to get Mitch to see if that build exhibits the bug (if we ask really nice)