First post here. Thank you for a fine product.
Our current goal using Transmutr is to achieve a smooth workflow for importing e.g. Megascans assets from Quixel Bridge for rendering in V-ray for Sketchup. I tried this workflow for the first time yesterday.
I identified an apparent Transmutr bug.
I used Transmutr on a Megascans fbx asset exported from Quixel Bridge to generate a simplified Sketchup proxy component pointing to a full vrmesh. Or, so I thought. When rendering the result in V-ray for Sketchup, however, no vrmesh was rendered. The object rendered in V-ray was just identical to the proxy.
It turns out that the V-ray asset editor did not contain any vrmesh object, nor did the Transmutr output folder. So, I looked at Transmutr’s log file. Row 3223 and 3224 read:
[0h 0m 0.5s] [16 MB] error: [VUtils::subdivideMeshToFile] Cannot create file "C:\Febe\SLÃ?â??NGES\Wood Root 08.vrmesh"
[0h 0m 0.5s] [16 MB] error: [PFileStream::Create] (123) The filename, directory name, or volume label syntax is incorrect.
The likely culprit here is that the output path contains a non-ascii character, apparently obstructing the vrmesh generation. So I changed the output path to all-ascii characters. This fixed the problem.
Still, non-ascii characters are used natively by 100 000 000 + people just in Europe. So this error will affect other people.
The bug probably arises through an issue in Transmutr, or in V-ray’s ply2vrmesh.exe, or in both.
1 – Would you please fix this, so any unicode output path still yields correct results?
2 – Would you please show a clear error message in the Transmutr UI whenever a vrmesh generation fails?
