Wireframe - normal
Shaded - normal
Rendered - BLACK
Ghosted - normal
X-ray - normal
Technical - BLACK
Artistic - normal
Pen - BLACK
Arctic - BLACK
Raytraced - BLACK
Just updated drivers, no change.
Turning skylight makes no change.
I can bring display to life by turning OFF some layers, but it is not a solution.
It seems like there is limit to elements Rhino can display.
System info: Rhino 6 SR14 2019-3-26 (Rhino 6, 6.14.19085.9141, Git hash:master @ 5735fd2f55500f5781f40c02b70d7bc0d57d6e4d) License type: Commercial, build 2019-03-26 License details: Cloud Zoo. In use by: Piotr ()
Windows 10.0 SR0.0 or greater (Physical RAM: 16Gb) Machine name: DESKTOP-BNUR9UE
Can I get the example and steps you’re using to reproduce this… If you’re able to reproduce this on two different systems, then most likely it is a Rhino problem…and most likely we should be able to reproduce it here…which means we’ll also be able to fix it…so the more details you provide, the better chance I have of seeing the problem.
Nope, no limits… It’s more like there is something specific about the objects (materials, meshes, etc…) that is causing the display to do wonky things. Again, getting what you’re using is the best way for us to try to reproduce it…
Does this happen immediately upon loading the file? Or does it take a while of usage before it starts happening?
Hi Jeff
As usual, I will send it to tech, adressed to you.
There is, clearly something to do with the number of elements.
As soon as I reduce the number elements on the scene it starts displaying them, and I am talking about various layer combinations, so, mostly, no material-related.
I don’t want to be too quick to judge here, but looking at your plugin list I see XirusCAD and CreateQuadMesh, which are both relatively new and thus potentially more suspect than the others. Have you tried without them?
And as usual, everything is working fine here…even with all layers turned ON… I’ve tried all display modes too…they work as expected… Ugh… this means that finding this one now is going to be a lot more difficult. …still looking, but I’m pretty sure though that this is not an “object type” issue… I’m currently trying to find an AMD card here that has only 2GB. Given your scene and file, that should be plenty…but I want to try to get a system here configured to something as close as possible to yours. How many monitors do you use? What resolutions are being used?
By “turns black”, do you mean the entire viewport goes black? Or certain objects turn black?
Also, please try these one at a time…
Once things go black, does it remain black for any/all view manipulation? (i.e. Zoom, pan, rotate…) don’t turn anything On of Off, just try things that only act on the view and camera… Try doing something like SelAll followed by ZS (zoom selected)… Are you able to get rid of the “blackness” doing such actions? (EDIT: Also try maximizing and restoring the viewports as well as Rhino’s main window)
Once things go black, save the file, close Rhino. Now start Rhino and load the file you saved…are things still black?
Once things go black, are there any display mode settings you can make that brings it back? Note: This is not things like SkyLight or environment settings… I’m only talking about the settings found in the Display Settings pages for a given display mode…and also found in the Display panel tab. Also, are all display mode settings at their defaults when the blackness occurs?
Are you using any kind(s) of command(s) that alter the appearance of your views? This would be things like the GradientView command, which changes how the background is drawn/rendered. If so, does turning it/them OFF (undoing whatever it is they do), bring things back to normal?
WARNING Please make sure you have a backup of your file before doing the next step…
5) If you do a “SaveAs…”, and only check the “Save geometry only” option (i.e. uncheck everything else, especially the “Save plugin data”), then give the file a different name so that you’re not stepping on your original work…(i.e. add “_stripped” to the end of the file name), and then click the “Save” button… Now close Rhino. Start Rhino and load the “stripped” version of the file… Can you get things to go black? If so, which operations cause the blackness to occur?
That’s all for now…in the mean time, I’m going to be trying to put together a system here with similar specs.
To make it even more confused.
I am saving images with castarted scenes and then merging pics in photoshop.
Sometimes, when setting the camera and target display mode, there are some glitches like fake transparency or objects on top of each other, but when I change the display mode for a while and then set it back to desired one, there is a great chance that display will return to normal.
Did you share the model that does this already with @jeff? If not can you please upload it at Rhino - Upload to Support (use this link and I get automatically notified when the upload is done). I’d like to investigate why load time is extremely long.
Hi Nathan
I am not sure, whether it is within scope of your responsibility but it would be worth looking into another problem:
once you have my file, please play with turning on and off the INTERIOR/SHELVES/BOOKS layer and observe dramatic drop of performane (at least here). I know it is a lot of objects (<50k) but there are mesh faces only.
P
I managed to investigate it earlier this morning. Indeed the 48k+ objects is the problem here. To have this scene start rendering fast also with Raytraced select all objects on your INTERIOR/SHELVES/BOOKS layer and use _Join to merge the 48k+ meshes into one. Once done that switching to Raytraced will be under 10 seconds or so.
As an aside, it is pretty useless to turn on the interior objects when they aren’t visible from the angle(s) you are rendering. Turn them off when they aren’t visible and save resources, make the rendering faster.