This is a n00b question. Only recently I got into PBR rendering. I just don’t know where to look: When I import a rectangular surface from Rhino into D5, the textures of the PBR materials are stretched according to the aspect ratio of the surface.
If it doesn’t, which is likely in my experience with external renderers, use a box or planar mapping method for the rectangular surface in it’s texture mapping properties within the Properties panel. Then set the plane or box mapping widget to a square aspect ratio using the grid when defining it.
Thanks for the explanation, @BrianJ! On my system, a PC, it looks a bit different. But I did apply box mapping, and I did draw a cube as a box. Still, the mapping is distorted when previewed with _UVEditor:
I was also on Windows for the last screenshot, but it shouldn’t matter either way. Here I don’t see the issue you mentioned in the UVeditor.
Here’s a file so we are on the same page… BoxMap.3dm (2.7 MB)
This screenshot shows the mapping widget displayed for the copy of the surface that has Box mapping applied and the box map being set to one unit square.
Thank you! I did some more tests. All I did was create a plane and _ApplyBoxMapping to it. I didn’t assign a texture. Results:
2024-03-26_box_mapped_plane.3dm (on the left in screenshot below): When imported directly into D5, which can read 3DM, then the texture is stretched. I scaled the texture uniformly by 100.
2024-03-26_box_mapped_plane.fbx (on the right): This is the above file exported to .FBX. The texture is not distorted. I scaled the texture uniformly by 0.1 to match the size. I have no idea, why there is a difference in scale. Apparently, 3DM files and FBX files are handled quite differently when it comes to textures.
In a nutshell: _ApplyBoxMapping plus export to FBX solves the issue.
However there is one thing that I still don’t understand, and it may be something fundamental. As you can see in the screenshot below, the preview texture in the _UVEditor still shows up stretched. Why is that?
Thanks, I should have a look, but I also want to understand what is going on. Rendering is not really my thing. I try to avoid it as much as I can. But if I continue working on that project, then I may also look into other renderers, maybe even native Cycles. My major gripe with D5 is that it doesn’t support realistic looking semi-transparent materials.
I don’t see the texture stretched in the UVeditor here with your 3dm file. Your box map size looks fine too as shown so I am wondering if the issue on your end is somehow system specific. Provide the results of the SystemInfo command and I can tell more.
Regarding needing to use FBX for D5 to understand the mapping assigned to the surface, this is not surprising. I’ve found that often external renderers can’t read the mapping and repeat values in the 3dm due to limited support for the format on their end. Using FBX, OBJ or gLTF as open file formats that can carry UVs can help. Alternately, custom mapping where you use the Unwrap command is also the most successful means of getting UVs out of Rhino in my experience.
The only thing I see in your system info is the old driver for the Intel GPU. Run the command Notifications > In the Notifications panel you will see messages about driver updates for the graphics cards in your computer > Double click the “i” in the blue circle to get a link to “Check Now” from the respective manufacturer. Download and install the latest driver for the Intel card and then restart your computer.
@Jussi_Aaltonen Does the UVE use the GPU set for OpenGL or the Primary display?