N°42
Bug Report: RH-75561
I’m using a standard cube and PBR
But
I try, and it did not work.
- A new box surface
- Making new UVs
- In the PBR, deleting and creating a new detailed Base color node
- Assigning a different texture
- Opening in a new Rhino
- Restarting Windows
- Lowering texture Resolution
Let’s start with your Rhino “SystemInfo”.
If there nothing obvious, we’ll need your file and everything needed to duplicate the problem.
My initial guess is the image resolution used for your material is too high so Rhino is dropping it to something manageable but fuzzy.
Hello John,
In the Rhino file was included in the Bug Report: RH-75561 . Is a specific isolated Rhino file.
Wall.3dm (14.3 MB)
My monitor resolution: 6256px X 3840px
Rhino 7 SR30 2023-6-12 (Rhino 7, 7.30.23163.13001, Git hash:master @ f695e494df78377a81b2b95edb99c6067e324b33)
License type: Commercial, build 2023-06-12
License details: Cloud Zoo
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 96Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3090 (NVidia) Memory: 24GB, Driver date: 4-8-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 531.61
> 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: 4-8-2023
Driver Version: 31.0.15.3161
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24 GB
Rhino plugins that do not ship with Rhino
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.1.1.0
C:\Users\ALanMAttano\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\Bella (813de3fb-18eb-405f-bfcd-b0b4d3da91fb)\23.3.0.0\bella_rhino.rhp “Bella” 23.3.0.0
C:\Users\ALanMAttano\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\SubstanceImporter\2.0.3\Substance.Win.rhp “SubstanceImporter” 2.0.3.0
C:\Users\ALanMAttano\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\IntelDenoiser\0.6.4\IntelDenoiser.Windows.rhp “IntelDenoiser.Windows” 0.6.4.0
C:\Users\ALanMAttano\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.30.23163.13001
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.30.23163.13001
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.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.30.23163.13001
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 7\Plug-ins\Calc.rhp “Calc”
Okay.
I assigned a subsystem so a developer will have a look.
Your SystemInfo looks really good.
I do see a lot of extra plug-ins.
I doubt they are an issue, but as a test, I would try disabling all of the plug-ins that did ship with Rhino, restart, and see if it has any effect.
I will try it,
I rebuild the surface and make different UV mapping. Same problem. This time notice that starts the Raytraced (Cycles) rendering at some point after several samples. It starts again but with the correct texture resolution.
rhino may decide to bake a lower res texture, and then a higher one; the same happens when my plugin asks it for textures
1 Like
YES! It looks like there is more than one bug here.
Use a lower resolution if a surface (presume with a big texture) is moved.
Later (like 30 seconds later), after the Raytraced is completed, if you move the camera a new Raytraced is launched with the correct texture size. And you need to move one more time the camera (or another similar action) to update the view.
The video shows better:
FWIW Rhino 8 WIP no longer bakes textures for Raytraced/Rhino Render.
Thanks for the heads-up about the bug. Is this something that’ll get fixed in an update for Rhino 7, or is it only sorted in Rhino 8? I only use LTS versions, so I need to know if I should start thinking about upgrading to Rhino 8. All I want is for Rhino to run well, you know? Cheers
does that also mean there will be less out of memory issues? i turned settings to high and never saw the result of it due to out of memory issues 
(well actually it was not so funny… but i managed to get over it)
1 Like
I mentioned earlier that lowering the texture resolution (from 4k to 1k) in my case did not fix the problem. My GPU video card ram is 24Gb, and was using less than that.
I also found another similar bug but not exactly the same that overlaps with this one, so I make a new thread: Unexpected Texture Flipping in Raytraced - Anyone Else Experiencing This?