I have made a small discovery which I think centres a visibility problem we have with objects created in Grasshopper and visualised in Rhino 7. It is we presume in the mix of settings for Rhino 7 that we have created in running through the standard install, and the use of LadyBug Tools v1.3 plugins for Grasshopper. This happens on a whole bunch of student lab computers. I have created a small animated visualisation to show what we encounter.
Essentially, the LBT 1.3 script creates all the input geometry, runs the analyses and outputs the graphics to Rhino 7. In this situation, controlling what we see in the standard Rhino ports is something over which we have limited control. Sometimes they are there. Sometimes not. When we first run LBT 1.3, not.
The script has a bunch of model visualisation tools provided to help the users visualise the model prior to running the model (e.g. a graphic representation of the rooms and their R-values). Turning these on and off seems to trigger the visualisation of the other objects. But even this is not reliable. Zooming in and out amongst the various graphics produces oddly variable visibility.
In the past 24 hours, we have discovered an apparent cure: draw any object in the Rhino window. All the objects appear AND zooming in an out has no effect on visibility.
I have created a youtube demonstration of the phenomenon (not a solution, but a way of working around the issue, so if this provides insights into what Rhino settings we need to change, I would be ever so grateful):
Basic model in first picture. Second picture shows zooming in orthogonal views seems to function well, but in perspective top fight model has half-disappeared due to some camera clip function over which I seem to have no control. One more click forward of the scroll wheel and the whole model disappears…
Just returned to this forum from a long absence avoiding this problem with various workarounds, and noted this is incomplete.
The SystemInfo requested on November 21 was posted here on September 21:
Please note the most recent example in this stream used an imported fbx file that is from a source from whom I may not share the original file. My apologies if this was not clear. I was hoping that there might be a generic issue that I was missing about perhaps clipping planes and imported files - or some kind of import scaling issue that I was unaware of…
Ah, interesting. We use Remote Desktop to run lectures from rooms where the display computers are not as capable as the students’ or my desktop. However, as the problem occurs consistently on whichever computer configuration I have, it had not occurred to me to do anything than log in to the wrok/school computer to report the issue. The desktop for the continuing problem has the following Sysinfo report
Windows 10.0.19043 SR0.0 or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro K1200 (NVidia) Memory: 4GB, Driver date: 5-23-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 516.25
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
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: 7-2-2021
Driver Version: 188.8.131.5296
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\packages\7.0\LadybugTools\1.36.135\Ladybug.RH.Loader.rhp “Ladybug.RH.Loader” 184.108.40.206
C:\ProgramData\McNeel\Rhinoceros\packages\7.0\Pollination\1.3.3\Pollination.RH.Loader.rhp “Pollination.RH.Loader” 220.127.116.11
Thanks, Michael -
There are situations where the camera’s near and far clipping planes can cause some geometry to be clipped. You could use the Camera command to try to troubleshoot this, but if you want us to be able to say anything meaningful about this, pictures nor videos will do any good and we’ll need actual Grasshopper or Rhino files.