I have a button that launches a floating viewport in 16:9 or 4:3. the view is perspective, but not the angle in the previously active perspective view. I have a number of named views in the file so I restore the preferred view to the floating viewport and switch to raytraced. The object renders nicely and all is good.
If I restore a different named view, the object disappears the moment cycles starts it’s passes. The raytrace proceeds to the 500 passes VERY quickly but nothing is visible at completion. If I switch to shaded view the object is there and perfectly oriented. I can go through all the view modes and the object shows but when I switch back to raytraced mode the object disappears again. If I restore the previous named view the object raytraces as expected.
Any thoughts on how to mange this. we are trying to work with a consistent set of named views across product variations.
I’m not sure I understand the procedure here. At times Raytraced works, and at times not?
Can you maybe create a simple Rhino file with a few boxes and spheres and a couple of named views and give a step by step recount of what you do to get the behavior you see?
It also would be useful to get the text output of the Rhino command _SystemInfo.
I have attached a file with 8 named views in it. Views 1-4 were created in that file. Views 5-8 were imported from another file using the attached python script by Clement. I then launch a floating perspective viewport. I restore a view to that floating viewport and switch to raytrace mode.
All views work fine here except p-4 & V-2. Those views exhibit the problem behavior with the objects disappearing when switching to raytrace mode. Switching to rendered mode shows the objects but going back to raytrace they disappear as soon as cycles gets going. Same in non floating viewports.
Thanks for your help. ~ Robb
System Info -
Rhino 6 SR27 2020-6-24 (Rhino 6, 6.27.20176.05001, Git hash:master @ ba2c30de00be5a8b210bc297715204e941911799)
License type: Commercial, build 2020-06-24
License details: Cloud Zoo. In use by: Robert McDougle ()
Windows 10.0 SR0.0 or greater (Physical RAM: 32Gb)
Machine name: HEPHAESTUS
Hi Robb - I didn’t get as far as testing this with a floating viewport but ran into an issue that I reported here - RH-60131.
The objects aren’t disappearing but the view isn’t getting raytraced.
-wim
Not that it makes me happy, but I’m glad you are seeing the same thing I am. Our goal is to establish a standard set of views that can be imported into the range of product variations for rendering. Looking to create continuity in our presentations. Is it possible that some aspect of the python script overlooks attributes of the view?
The problem here is the ground plane. Raytraced can’t see objects on the other side of the ground plane, even if it is set to shadows-only. That gets you only the background environment through the ground plane.
The view is getting raytraced, in your file it just ends up completely white due to the background environment showing through, apart from a small bit where you can see z-fighting.
Wow… it seems so obvious now that you point it out. It is true that the views that disappeared were seen from below the fixed ground plane. I suppose we could rotate our products 180 degrees around the X axis to see the underside with a shadow. This could be managed with Named Positions.
Is it possible to create a macro that under a button would give me a named view and a named position?
Thanks for your help with this - obviously not a bug.
One could probably come up with a simple Python script that would go through all your named views one by one, set the groundplane so that it is on the side of the scene bounding box that can be considered bottom for that view and then do a raytraced capture.
I believe I already posted on this forum a script that goes through snapshots or materials and do raytraced captures for each of them automatically. I’ll see if I can find it tomorrow when I’m not about to go to sleep (already 00:21 over here )
)