since SubD geometry is getting more common, i wanted to use them and apply UV mapping and textures for use in Rendered Viewport. While doing so, i ran into multiple issues:
Issue 1: Textures are displayed very blurry compared to meshes, below shows a SubD on the left and a mesh (the extracted RenderMesh of the SubD) on the right. Can the (simulated) texture display be improved for SubD as it has been done for meshes recently ?
Issue 2: Once i have used _Unwrap on even the simplest SubD geometry and try to switch back from RenderedViewport to ShadedViewport, i get a noticable delay until the operation completes. This happens even if no texture or material has been applied to the SubD object. If i have multiple textured SubD objects, in takes even longer to switch back to ShadedViewport, sometimes up to 5 seconds which interupts the workflow quite a lot.
Issue 3: When turning off a layer with multiple textured SubD objects and at a later time turning the layer on while beeing in RenderedViewport, all textures are regenerated and it takes quite some time until i get the final preview. Sometimes this can take up to 1 minute, however my textures are not very large (1K or 2K). Why does Rhino re-generate the textures at all when i did not change anything despite the objects visibility ?
Issue 4: Converting a perfectly UV mapped mesh to SubD seems to mess up the mapping. Could there be an option please to transfer the texture mapping from the mesh to the SubD object ?
Issue 5: Using _OffsetSubD on a custom mapped SubD object messes up the mapping of the offsetted result.
Issue 6: Display speed using textured SubD objects in RenderedViewport is noticably slower compared to using textured meshes. I’ve set the “SubD meshing parameters for raytracing” for all my textured SubD objects to the highest level and extracted the render meshes. Then i’ve turned Off mesh wires and SubD wire display in the RenderedViewport and compared the display speed using TestMaxSpeed with 76 textured objects:
SubD objects - 15fps
Mesh objects - 60fps
Is this normal ?
Issue 7: Using ExtractRenderMesh on SubD objects does automatically assign the material used on the SubD to the resulting mesh. However, decal assignments are lost.
i hope that at least issue 1 can be fixed in Rhino 7, it is basically the same problem i had with meshes and was fixed in a recent SR.
There is a another small issue with textured SubD display in RenderedViewport. If you open below example which uses a constant colored dark texture, some wires of the SubD get visible when zooming out far enough even when SubD Wires is turned Off in the display mode options:
This would be great. Not sure if this is a bug but if i use the UV Editor on a SubD and then try to select an (naked) edge loop from the unwrapped mesh by holding Shift + Ctrl and double click on it, it does not select the edge loop. Instead it selects the single edge with the first click, then after the second click it shows a popup to choose if i want to select the (single) edge or connected face ?!
Texture baking a.k.a. ATP (Advanced texture preview) in Rhino 7 is causing issues 1-3. ATP kicks in as soon as you use Unwrap or UVEditor. In Rhino WIP ATP is no longer needed for unwrapped objects.
Filed this bug: RH-69045 ToSubD: Texture mapping is not transferred correctly from mesh objects
Texture mapping tools in Rhino were designed to be used after the geometry is finished. We have seen that this is generally not what our users want to do. We are working towards improvements on this area. Filed this specific issue: RH-69047 OffsetSubD messes up the mapping on the offset part
If you need to turn off wires in Rendered mode it sounds like you may have tweaked something. Does that also happen with standard settings? I see 40 FPS for SubD and 60 FPS for meshes.
thanks for adding this to the bugtracker. I’ve found another issue where ExtractRenderMesh fails to transfer the correct mapping from the UVMapped SubD to the extracted RenderMesh. I’m awaiting permission to send an example file via PM so you can repeat all these issues.
In my case, i had the SubD geometry and applied first only the Thickness modifier which did not behave as it usually does when used on meshes. The mapping was messed up. Then i’ve tried the command OffsetSubD to see the same.
I’m attaching my Rendered display mode below. The things changed are disable curve drawing and all wires for meshes and subd objects.
I’ll need to test this. But i generally do not want any wires in Rendered display since we’re using this as the main presentation for materials. Btw, is there a setting maybe which i am missing to change the resolution of subd display meshes without extracting the RenderMeshes from them ?
I’ve found the setting in the document properties under Mesh>Custom>Level. While checking my density using ShowRenderMesh, i’ve discovered another issue, to repeat it please follow below steps:
Create a SubD box
Switch to Shaded display mode
Select the SubD box and enable ShowRenderMesh
Under Document Properties>Mesh>Custom>Level change the slider value
Click on the Preview button
At this point, the ShowRenderMesh is removed from the display conduit of the SubD object, like if you would have typed HideRenderMesh. If you OK the Document Properties dialog and use ShowRenderMesh again on the SubD box, you can actually see that the render mesh has changed.
@nathanletwory, imho the textual description under Document Properties>Mesh is wrong and misleading: “SubD meshing parameters for Raytracing” is a setting which affects the SubD render mesh and counts for all display modes not only Raytraced. You can validate this by changing the Level value and using either ExtractRenderMesh or PolygonCount.
I may have misunderstood this issue. I thought this has to do with texture baking on SubD objects. But if you’ve had the same issue with meshes then it can’t be because meshes never use texture baking. If you still have that file and you can find it could you upload it here so I can check what other factors there are that could be causing this issue?
This happens because custom object texture mapping triggers texture baking on the SubD. Rendered display mode samples the baked texture in a way that makes some of the unbaked pixels visible along the SubD edges. That does not happen in Rhino WIP anymore.
Thanks. Logged RH-69182 UVEditor: can not select edge loops by ctrl + shift + double clicking
Hi @Jussi_Aaltonen, below is the same file i posted above with a different embedded texture. This is issue 1, it shows the blurry texture display on the UV mapped SubD, for comparison i’ve included the extracted rendermesh of the SubD which displays the texture much sharper.
The file also shows the problem with visible edges on the SubD If you zoom out, there are some leaks as shown in below image. SubD is left, mesh is right: