Hi,
After I use VRay Scene Converter to covert Corona scene to VRay, I get this error:
unknown property: “overrideToneMapping” in $CoronaCamera001
How to sovle this problem?
In the Corona version i have, the parameter seems to have been renamed in MXS, without an alias.
It’s now called .colorMappingOverride
You can do one of two things: edit the script yourself and rerun it, or wait for us to make the fix and then publish it (that will take longer, by virtue of us having to move the change through the necessary phases).
Hi Lele,
Thank you for your reply. May I know where can I find the script? I am using the vray scene convertor (right click menu) in this case.
Uff, sorry for the late reply Jackie, i thought i had sent the message, but clearly i hadn’t.
The path to the file is in the maxscript editor toolbar (under programdata, and so on.).
Thank you for your reply 
I just wanted to start another thread, but my problems are not far away from @jackieteh , so I post it here.
I also have some corona8 hotfix 2 → vray6 hotfix2 conversion issues:
Error 01:
Unknown property: "mode" in Map #(mapname): CoronaMultiMap. (plz see attach error-01.jpg and error-01-detailsRandomExample.jpg )
Every single mat, that has CoronaMultiMap inside, gives me the error.
Temporary solution was for me - get rid of CoronaMultiMap.
Error 02:
Unknown property: “overrideToneMapping”. (plz see attach error-02.jpg)
Exactly what @jackieteh had.
Temporary solution was for me - delete corona cameras
Error 03:
Argument count error: convertFrom_CoronaPhysicalMtl wanted 3, got 2
Temporary solution was for me - also get rid of CoronaMultiMap.
Is there is a better way to solve Error 01 and Error 03?
Hope this will be fixed soon.:shock:
Best Regards
please remove this message
Please remove previous message, I have accidentally logged with another account.
Today I looked at the scene more detailed and found some very strange conversion results.
You can see the cases attached.
Object 01: corona legacy mat-> vray mat.
vray converter simply removed all diffuse nodes and created red color
Object 02: corona legacy mat-> vray mat.
same here - frontBack deleted, instead of thin walled + translucency improvement we get old fahion messy translucency material.
Also some strange pink color nodes with mix nodes created.
Object 03: corona legacy mat-> vray mat.
also here - frontBack deleted, some strange pink color nodes in bump slot created, translucency ignored.
This results are simply unusable, please improve the converter.
I have attached object 01 issues as pictures and another objects as zip because of 5 attachment limit.
Best Regards
conversion fails.zip (1.61 MB)
Some of the stuff you’re trying to convert isn’t supported, and that’s why it’s coming out with red or pink colors.
There’s a table of the supported nodes, and their results, here: V-Ray for 3ds Max
Thanks for the info. Let’s say we take as example Object 01.
may I ask you, what is the reason behind such “conversions”? CoronaRaySwitch → vray color? why ?? only because Vray does not have override as map node?
The converter must convert, not destroy. If some nodes are not convertable for now, then they need to be skipped without cutting off all the stuff which was behind such nodes. Also, some warning should appear.
Object 02,03.
same situation here. Vray does not have FrontBack map (why? i) and converts this map to simple vray color node. All the nodes behind it are also ignored and get lost.
---------
https://docs.chaos.com/display/VMAX/…cene+Converter - on this page we have the information that CoronaMultiMap is converted to VrayMultiSubTex, but this does not work. (see my message #7).
There is also no info about CoronaColorCorrect node on that page.
Same issues here. Vray 6, Corona 8. Trying to convert a scene< scene is not very complicated, got error: “can’t convert corona multimap” and after I click ok, 3ds max is shutting down with an unexpected error. I don’t get this considering you got Corona and consequently make it closer to Vray. But completely ignore to make this converter work properly.
The crash is problematic, we’ll look into it. If at all possible, keep the crashing scene ready, should we not be able to repro the crash locally.
This could be due to changes in the corona multimap properties, or other unintended issue on our side, or something local to your specific setup.
On perfect conversion: when Corona became part of the family, we promised at great user request to *not* make it a clone of V-Ray.
To have a 100% successful conversion we should have an 100% identical set of maps, and workflows, and that is counter to what we promised, and what we believe to be best for users of both camps.
Conversion is but a tool to help automate, it won’t magically support what it cannot, and so, bugs aside, you should always check the compatibility table against your needs.
On perfect conversion: when Corona became part of the family, we promised at great user request *not* make it a clone of V-Ray I got it. No one is expecting to produce two products identical. But do not overcomplicate things like writing another line of code for the specific event. We all understand that it is not easy to have this "specific line " written and not conflict with something else. But comparing the corona converter and vray converter, I only wish it would work better. Good luck.
Nobody wants that corona become a clone of vray. You can leave vray feature gaps “as is”. At the first place, the customers want more consistent workflow between two engines at first. And proper converter plays a huge role here.
Again, converters job is to convert. It must be smart and intelligent. Of course, it can not 100% be identical, but simply cut out all what is behind unsupported nodes is not a good solution. You can skip unsupported maps, but it is necessary to keep all the main nodes behind them.Currently, the converter has the same problematics as TX conversion.
The goal of conversion is to save the time. When converter destroy the shaders and delete a lot of stuff without any warning messages, then it is simply no reason to use it.
Let’s look even at latest official converter webpage:
https://docs.chaos.com/display/VMAX/V-Ray+Scene+Converter
What we have here ?
01. Just look at the supported materials and nodes list. (please, look at 01-comparison.jpg and 02-comparison.jpg in my attachment)
- it has completely chaotic order and look not like in 3ds max. Why ?
- some materials and a lot of nodes description are simply missing. Why ?
- there is no information about coronaLegacy material. Not all users know that it is pervious CoronaMaterial.
- unsupported, but listed nodes are converted as vray color. First question of all users is why and what is happening with child nodes? Threre is zero information about it.
02. There is zero information about current bugs and limitations. You expect that it will work fine, but it is not.
03. Does vray converter have any version number? how can we know that it got updated?
Sorry, but right now it looks as a technical table of facts without any descriptions, counterintuitive and user unfriendly.
I hope you can understand my comments and critics, and please don’t take it personally. We just want to have a better products and workflows.
Best regards.
The converter does a great job, provided the user follows guidelines, which are restrictive compared to freeform scene setup and material creation (f.e.: PBR standards, no custom maps, etc.).
Again, converters job is to convert. It must be smart and intelligent. Of course, it can not 100% be identical, but simply cut out all what is behind unsupported nodes is not a good solution. You can skip unsupported maps, but it is necessary to keep all the main nodes behind them
What would you propose? That we left the non converted nodes in the scene, and then attempted rendering them to possibly crash?
Currently, the converter has the same problematics as TX conversion.
What would the shared issues be?
The goal of conversion is to save the time. When converter destroy the shaders and delete a lot of stuff without any warning messages, then it is simply no reason to use it.
Conversion is *always* lossy, the user needs to be aware they need to keep their original files.
The listener will print out a wholesome set of info, one just needs to bother going through it.
You are right, however: expecting the converter to convert just anything is not reasonable.
Let’s look even at latest official converter webpage:
https://docs.chaos.com/display/VMAX/V-Ray+Scene+ConverterWhat we have here ?
- it has completely chaotic order and look not like in 3ds max. Why ?
A list built over many years, in order of support.
We’ll reorder it alphabetically, if it’s easier for you to read.
- some materials and a lot of nodes description are simply missing. Why ?
It’s a “supported features” list: meaning what isn’t there is not supported.
- there is no information about coronaLegacy material. Not all users know that it is pervious CoronaMaterial.
Not all users are planning on converting current Corona version scenes. We’ll add the name in brackets.
- unsupported, but listed nodes are converted as vray color. First question of all users is why and what is happening with child nodes? Threre is zero information about it.
Which would these be?
02. There is zero information about current bugs and limitations. You expect that it will work fine, but it is not.
It’s always going to be trial and error, you -or anyone else- wouldn’t read forty-three pages of technical limitations if we had them written in the docs.
The only suggestion is to be sensible, and stick to minimum common denominator setup, if conversion is of paramount importance.
03. Does vray converter have any version number? how can we know that it got updated?
It’s as current as the V-Ray version you’re running.
The newer the V-Ray version, the newer the converter.
Minor caveat: some feature may be back-ported to previous V-Ray version.
Sorry, but right now it looks as a technical table of facts without any descriptions, counterintuitive and user unfriendly.
That is the spirit of translation.
A dictionary hardly provides for entertainment, after all.
I hope you can understand my comments and critics, and please don’t take it personally.
I think i do understand you, and i definitely do not take it personally (i haven’t written the converters that have been giving you issues, either.)
We just want to have a better products and workflows.
On this in particular we are wholly aligned.
Best regards.
Likewise
Hello Lele,
yes, if the shaders are completely simple it works of course. But in MOST of the cases the scenes are more complex.
If it impossible to SKIP the unsupported nodes and LEAVE all that nodes which was behind of UNSUPPORTED node CONVERTED , then yes, it is better to leave them unconverted.
Because right now vray converter simply ignores and then deletes completely all nodes which was behind of unsupported one. Only in my simple example I have damaged about 30% of shaders and lost the textures, corrections and so on.
It converts, but there are the same UI/UX issues as in vrayConverter: almost no options, menus and warnings.
Yes, please! Arrange them as they arranged in 3ds max and like the users remembered it via visual memory.
It will be great to have the same table as you have now but 3ds max vise arranged with all the corona mats and nodes. You can simply grey out or leave result empty with note that some things are not supported yet.
Currently converted result of CoronaFrontBack and CoronaRaySwitch is vrayColor.(please, look at my attachments) Sorry, but this not a conversion. Only logical reason I see here is to somehow indicate problematic nodes. But like I said, all the stuff behind this nodes get simply deleted.
thx !
Please, look at my attachment. I have lost all the stuff behind of CoronaFrontBack, CoronaRaySwitch nodes.
It is always good to mix the styles to be understandable for wider range of audience. Look at corona’s alternative. They describe it well.
https://support.chaos.com/hc/en-us/articles/4526289638033-How-to-use-the-Corona-Converter-Corona-7-and-newer-
Yes, I understand. But vray has endless versions of nightly builds. Because of that it’s hard to follow the versions. You need always to check the logs manually if something get improved in converter or not.
Best regards
Hello, @lele
today I have tested the conversion of the same objects with maxtools converter. This converter has a tons of settings- nothing is touched, just clicked “convert”.
Please, look at the attachments - there is directly comparison between Vray6 converter and maxtools converter.
I hope now you can open support tickets for this.
Best regards.
As i said, we will fix the bugs, and try and improve it.
We will *not*, ever, leave unconverted stuff laying around, and we will strive to *not* make one such mess of nodes for mix modes that are photoshop bound.
We have strong opinions, and stronger constraints still, on the way conversions should happen.
Feel free to use what you see best fit to your workflow, we won’t take offence. 
Hello Lele,
just to clarify to make sure that we understand each other :
01. converter fatal errors :
- Unknown property: "mode" in Map #(mapname): CoronaMultiMap.
- Unknown property: “overrideToneMapping”.
- Argument count error: convertFrom_CoronaPhysicalMtl wanted 3, got 2
//you said ok to this
02.technical documentation on https://docs.chaos.com/display/VMAX/…cene+Converter page:
- rearranging the list of corona materials and maps to match 3ds max lists //****you said ok to this
- same time, adding all Material types and nodes of corona in the table. If something is currently not supported-> note info in notes column. //not sure if you told something about this
- adding the name of CoronaLegacyMateial //you said ok to this
- current state of CoronaFrontBack,CoronaRaySwitch-> vray color is wrong, It needs to be improved //not sure if you told something about this
03. converter does shader corruption
- if there is something behind of CoronaFrontBack,CoronaRaySwitch (and probably other unsupported nodes), it just got ignored and deleted. But we need this child nodes to be also converted. This is critical issue (shown comparison between current state of vray converter and how maxtools converer works) //not sure if you told something about this
no problem, if all issues will be resolved, then its fine.
sorry, but I do not understand what you mean, were there such examples from my side ?
because of that, I made this clarifying post at first.
Best regards.