First time poster here and new to scripting and errors. I’m trying to convert a Corona scene I downloaded to VRay, in order to use Chaos Vantage, but I receive an error and can’t for the life of me figure it out.
If anyone has an ideas, please help!
Also, both VRay and Corona are installed on the PC, both latest builds.
LE: Uninstalled OneDrive, didn’t do anything. Error still persists.
I did. I get the same error. Now that I think of it, when converting the scene, would it be possible that Max tries to write some temp files to certain directories/folders it doesn’t have permission to? Thus showing errors? I remember installing OneDrive after a clean reinstall of Windows, just before Christmas, and I struggled with many apps to install different stuff because the anti Ransomware of OneDrive kept refusing to allow software to write files in /Documents.
I don’t quite understand your latest response: You should simply download one of the linked builds, install it in place of your current one, and retry the conversion.
It works for me, i checked the code, there are *two* parameters passed to the function, as it wants now.
The conversion writes absolutely no file, nor it attempts to save the max file currently open.
The issue in the OP is something that we saw, and fixed, months ago: i feared we had a reversion.
LE: I did try on a clean scene, created a simple cube, added a CoronaMtl to it and a simple CoronaSun. It did convert the scene with no issues. So it must be something to do either with how the scene is configured, or a bug I encountered.
I did reinstall VRay 6 standalone (stable build) for x64 as you suggested, from the link you provided. It still doesn’t work. I didn’t try on a clean scene with just a couple of objects and materials, instead of a complex scene. Regardless, it doesn’t work as of yet. If you have any other suggestions, I’d highly appreciate!
This is a wholly different error.
It looks like something changed on the corona side, and a property that used to be on the map isn’t there anymore.
We’ll investigate it, thanks for the report. (filed as VMAX-12937)
Bug confirmed, filed as VMAX-12938, thank you very much for the report.
As the code owner will have had a chance to look into the issues, we’ll make sure to let you know of the timing.
Hi Lele,
I’m curious if there’s been any movement on solving the convert Corona MultiMap bug, or any suggested work-around?
I’m encountering this issue today, with the latest versions of both Corona and Vray (and quite some time after the bug was originally flagged).
Fingers crossed!
Thanks
Hi,
I have V-Ray 6 Update 1.2 [6.10.08], and i don’t want to install the nightllies version [it’s not the official version], so what can I do!?
Can you Share the (vrayutils.ms) file, so we don’t have to install new version on a bunch of PCs, for replacing this file only!?
Thanks in Advance.
We can’t share the vrutils file, it may risk erroring out in other places, from time to time.
It has to be delivered with the V-Ray build it’s intended for.
You can safely download stable builds (not nightlies!) as they’ve gone through QA and are as safe as the next official release.
I Tried using 6.10.09 converter on 6.10.08 and I got The Following Errors:
1- vrDistTex.objects = inTexture.nodes Error (if the node is <deleted>).
need to check if all nodes in the array are valid nodes.
2- vrm.refraction_fogDepth = units.decodeValue formatted Error (Runtime error: Unable to decode value: “inf”, In convertFrom_CoronaPhysicalMtl(), cpm.attenuationDistance = inf.0).
I don’t know at any stage the value become inf.0 (it’s a float value), but units.formatValue can’t be applied to it! need to be replaces with 0.0.
This Errors not related to V-Ray Version.
I’ll poke the relevant dev about the first error (but you can fix it by removing any deleted node from your Corona distance textures.).
For the second i will need the material in question and the otherwise empty scene it lives in, as it seems the standard max method to convert scene units (which we need because we always express the value in cm) is throwing up an error with the value encoded in the Corona material, which shouldn’t happen.
To fix the latter error, you can try and pick a much bigger display unit scale (from mm to m, f.e.) and if at all possible (but this will rescale your scene) a more granolous system unit scale (meters, cm, instead of miles or KMs), to close the gap between the two.
For example, with system unit scale set to 1 mile, and display unit scale set to 1/100th of an inch, the method fails with a value slightly above 33000.0 in the Corona material’s SSS Radius, which is still a very big and unlikely entry in a shader.