Author Topic: The new Corona Converter feedback thread  (Read 11019 times)

2021-05-18, 11:48:11

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile


One of the major features of the upcoming Corona Renderer 7 is the new Corona Physical Material. With the introduction of this new material, we also had to update our Corona Converter script.
This thread is intended for collecting feedback on everything related to the new Converter script (its functionality, features, issues, what you like about it and what you don't like).

More about the Corona Physical Material:
https://blog.corona-renderer.com/behind-the-scenes-the-physical-material/
https://forum.corona-renderer.com/index.php?topic=31802

What you need:
- Corona Renderer 6 (to see what the render looked like before the conversion) - https://corona-renderer.com/download
- Newest Corona Renderer 7 daily build (to convert the scene and check the conversion results) - the link to download the newest version is at the top of the newest post at https://forum.corona-renderer.com/index.php?topic=30876.0
- If you just install Corona 7, the converter script will be available under the right-click quad menu as usual. If you are using some alternative installation method (i.e. you do not copy any files into your 3ds Max installation directory), then you can find the new converter script in \Corona Renderer\Autodesk\3ds Max 202X\scripts\CoronaRenderer.
- Before testing, make sure that you are using the converter script version 1.51 or newer! (it is printed in the title bar of the converter window)
NOTE: When using daily builds, the usual precautions apply! Backup your scenes!


What we are especially interested in:
Corona Legacy Material to Corona Physical Material conversion. This is the most important thing for us.
- How similar are the conversion results?
- How complex are the resulting shading networks in the material editor?
The easiest way to test both those things is opening a scene created in Corona 6 in Corona 7, converting it, and rerendering it.

What else is important:
- We improved the conversion of VRay2SidedMtl to CoronaPhysicalMtl. If you have a scene where you used the VRay2SidedMtl, please test this, and let us know if anything does not look or work as expected.
- Please check that all buttons in the "Tools" section of the Corona Converter work as expected. While this may sound like something our internal tests should take care of, there are always some edge cases which we might have missed, so we appreciate testing even very basic features like this.

Known issues and limitations:
- We know that the shading networks created by the Corona Converter might be quite complex in some cases (especially when many texture maps are used). If you have some ideas how to simplify such cases once you encounter them, please let us know.
- The newly created CoronaPhysicalMtl will only use those parameters, which were also available in the original material - i.e. if the original material did not feature sheen or clearcoat (which is the case for CoronaLegacyMtl), the converted CoronaPhysicalMtl will not use neither sheen nor clearcoat parameters (you can, of course, enable these parameters manually).
- It is possible that we changed some MAXScript function names which our users may want to use (i.e. broke the MAXScript API described here: https://www.racoon-artworks.de/CoronaConverter/mxsDocumentation.html ). The reason for this is that we used our coding conventions during the last rewrites of Corona Converter and therefore we changed some function names which weren't conforming to these conventions / weren't descriptive enough. If this proves to be a significant and commonly encountered problem,  we may revert some of these changes.
- We are planning to remove some legacy options / buttons from the Converter. If you rely on the removed functionality, we will consider reverting some of these changes.
- We do not support conversion to CoronaLegacyMtl anymore. The materials are always converted to CoronaPhysicalMtl.

Additional notes:
- Vray Mtl to Corona Physical Mtl conversion may currently not be working perfectly, but big improvements are coming!
- Specular to IOR conversion is a work in progress


If you have any other notes / remarks / complains - please do let us know.
Thank you in advance for your feedback!
« Last Edit: 2021-07-21, 17:58:26 by maru »

2021-05-18, 12:25:16
Reply #1

JG_pictures

  • Active Users
  • **
  • Posts: 107
  • JG
    • View Profile
    • www.gehrcken.de
I run into issues when working with projects, where i want to keep materials in legacy "mode" as it might happen, that these objects will be rendered in corona 6 or before.
So converting materials of selected objects only converts them into physical objects... would be great to have an option to convert them into legacy instead of physical.
its a bit forced into physical, while even lots of scripts doesn't even support physical material yet.

2021-05-18, 13:09:40
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
I run into issues when working with projects, where i want to keep materials in legacy "mode" as it might happen, that these objects will be rendered in corona 6 or before.
So converting materials of selected objects only converts them into physical objects... would be great to have an option to convert them into legacy instead of physical.
its a bit forced into physical, while even lots of scripts doesn't even support physical material yet.

Sorry, but this is listed as one of the limitations in my original post, and it's something we do not want to change. Only conversion to the new Physical material is possible.
Also, you mentioned converting objects and then using them in Corona 6 again. Please note that this is an unsupported scenario and it is not expected to work at all. If something is saved in a newer version of Corona, it must never be loaded back into an older version of Corona.

2021-05-18, 15:50:56
Reply #3

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
I just noticed that my previous message could have sounded a bit underwhelming, sorry for that, I didn't intend it. So just to avoid any misunderstandings: the reason why we are not planning to reintroduce conversion to the Corona Legacy Material is because we believe that the Physical Material offers many advantages over the Legacy one. It's easier to set up, the workflow is more in-line with the leading material creation software, and most importantly the end result that you get is more realistic. We treat the Physical Material as the new standard, and the Legacy Material as, well, legacy. :)

Also please note that the Legacy Material will work just fine in Corona 7, there is no need to convert it if you don't want to.
« Last Edit: 2021-05-18, 16:49:50 by maru »

2021-05-19, 15:51:12
Reply #4

JG_pictures

  • Active Users
  • **
  • Posts: 107
  • JG
    • View Profile
    • www.gehrcken.de
maru.. all is ok, so far.

I wasn't following all recent Infos in detail - i just tried to figure out a way to work with current releases of scripts and plugin - as they not always support those changes made in corona 7 yet.
So i will work with the previous v6 corona-converter for now.


... mainly i use corona converter... if merging objects from various 3d-model sites into my scenes. when they were provided with vray material or other - and for now, when working in an environment, where some coworkers do not want to go the step to corona7 ... its best to work with legacy materials. That might change in future times...maybe
« Last Edit: 2021-05-19, 16:18:44 by JG_pictures »

2021-05-19, 15:53:13
Reply #5

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Ok, so plugin / script support is something we should definitely be aware of. Thanks!

2021-05-19, 20:17:31
Reply #6

tallbox

  • Active Users
  • **
  • Posts: 129
  • George Nicola
    • View Profile
    • Architectural Visualizations | TALLBOX
A material made with Corona 6 consists of 1) after conversion with the latest converted, the newly created material contains many maps and nodes 1) + 2); That's so frustrating; Is there any workaround?
Architectural Visualizations / Deep work practitioner
https://www.tallboxdesign.com

2021-05-19, 22:56:50
Reply #7

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 7187
  • Let's move this topic, shall we?
    • View Profile
    • My Models
I agree, two Corona color nodes mixed together makes no sense at all.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2021-05-20, 00:08:39
Reply #8

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
A material made with Corona 6 consists of 1) after conversion with the latest converted, the newly created material contains many maps and nodes 1) + 2); That's so frustrating; Is there any workaround?

tallbox, romullus, thank you very much for your feedback, we're already working on changes which should result in simpler shading networks being generated.

2021-05-21, 00:07:13
Reply #9

Javadevil

  • Active Users
  • **
  • Posts: 385
    • View Profile
Will the updated material converter convert 3dsmax's Physical Material to Corona?
Models that I bring in from other Architectural apps default to that. It's such a pain to manually convert them all. Even if it just copied the bitmap paths over to the diffuse channel, I can set the rest of the settings.

thanks

2021-05-21, 00:23:51
Reply #10

shortcirkuit

  • Active Users
  • **
  • Posts: 152
    • View Profile
+1

Will the updated material converter convert 3dsmax's Physical Material to Corona?
Models that I bring in from other Architectural apps default to that. It's such a pain to manually convert them all. Even if it just copied the bitmap paths over to the diffuse channel, I can set the rest of the settings.

thanks

2021-05-21, 10:01:04
Reply #11

NicolasC

  • Primary Certified Instructor
  • Active Users
  • ***
  • Posts: 482
  • CG supervisor / teacher / artist
    • View Profile
Will the updated material converter convert 3dsmax's Physical Material to Corona?
Models that I bring in from other Architectural apps default to that. It's such a pain to manually convert them all. Even if it just copied the bitmap paths over to the diffuse channel, I can set the rest of the settings.

thanks
+1
Nicolas Caplat
CG supervisor / teacher / artist

2021-05-21, 15:00:59
Reply #12

lzanlorenzi

  • Active Users
  • **
  • Posts: 7
    • View Profile
hello my friends!

still the same issue with falloff map ...

corona 6 - 1 falloff map in difuse chanel - OK
corona 7 - 1 falloff map in difuse (converted) - lot of CoronaMix maps.

why? wouldn't it be easier not to convert this type of map? (falloff) or rather, create a Coronafalloff?

2021-05-21, 18:24:13
Reply #13

Skalpel3d

  • Active Users
  • **
  • Posts: 16
    • View Profile
when converting legacy material without textures, I am doing sss as an example, the converter sends me coronamix maps to the material I skip the gloss changes on the left material after conversion

2021-05-21, 18:34:59
Reply #14

Skalpel3d

  • Active Users
  • **
  • Posts: 16
    • View Profile
Another issue is incorrect recognition of metal materials, non-metal in the case of vrayblend conversion turns the materials from the machine into metallic

2021-05-23, 21:53:27
Reply #15

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Will the updated material converter convert 3dsmax's Physical Material to Corona?
Models that I bring in from other Architectural apps default to that. It's such a pain to manually convert them all. Even if it just copied the bitmap paths over to the diffuse channel, I can set the rest of the settings.

thanks

Hello Javadevil, thank you very much for your feedback. Conversion of 3ds Max's Physical Material is very high on our "what to do next list", however before adding support for another material to Corona Converter, first we want to make sure conversion of already supported materials works as expected. So currently we mostly focus on simplifying the shading networks, since this is something which troubles lots of early adopters of Corona 7. If everything goes well and we'll manage to address all the issues with currently supported materials, hopefully we would be able to start working on support for Physical Material soon :)

2021-05-23, 21:55:33
Reply #16

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
hello my friends!

still the same issue with falloff map ...

corona 6 - 1 falloff map in difuse chanel - OK
corona 7 - 1 falloff map in difuse (converted) - lot of CoronaMix maps.

why? wouldn't it be easier not to convert this type of map? (falloff) or rather, create a Coronafalloff?

Hello lzanlorenzi, thank you very much for your feedback, we're already working on changes which should result in simpler shading networks being generated.

2021-05-23, 21:56:57
Reply #17

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Another issue is incorrect recognition of metal materials, non-metal in the case of vrayblend conversion turns the materials from the machine into metallic

Hello Skalpel3d, thank you very much for your feedback. Please could you provide us the scene in question? We'd like to have a look at it.
« Last Edit: 2021-05-24, 00:19:24 by selene »

2021-05-27, 09:31:58
Reply #18

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Hi
Not the 1st time mentioned, but here is comparison of Corona 6's and Corona 7's conversion results. Corona 7 tries to keep front/back colors which is really good, but gives a mess of mix maps which (IMHO) have no sense. The tree model taken from Evermotion Archmodels 207 collection where material structure of all models is about the same.

DB 2021-05-20

2021-05-27, 09:37:12
Reply #19

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Thanks for the feedback! We are aware of this issue, and one of the upcoming daily builds will include an updated converter which greatly lowers the number of nodes created in the conversion.

2021-05-27, 09:47:50
Reply #20

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Thanks for the feedback! We are aware of this issue, and one of the upcoming daily builds will include an updated converter which greatly lowers the number of nodes created in the conversion.

Good news, thank you!

2021-05-27, 11:43:06
Reply #21

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Hi
Not the 1st time mentioned, but here is comparison of Corona 6's and Corona 7's conversion results. Corona 7 tries to keep front/back colors which is really good, but gives a mess of mix maps which (IMHO) have no sense. The tree model taken from Evermotion Archmodels 207 collection where material structure of all models is about the same.

DB 2021-05-20

Hello Bormax, please could you provide us the scene in question, so we could make sure it works as expected even for this particular case?

2021-05-27, 12:32:51
Reply #22

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Hi
Not the 1st time mentioned, but here is comparison of Corona 6's and Corona 7's conversion results. Corona 7 tries to keep front/back colors which is really good, but gives a mess of mix maps which (IMHO) have no sense. The tree model taken from Evermotion Archmodels 207 collection where material structure of all models is about the same.

DB 2021-05-20

Hello Bormax, please could you provide us the scene in question, so we could make sure it works as expected even for this particular case?

Done
1622111539_converter6-7-comparison.zip

2021-06-04, 00:37:22
Reply #23

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Done
1622111539_converter6-7-comparison.zip

Thank you very much!

2021-06-11, 14:11:31
Reply #24

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
A material made with Corona 6 consists of 1) after conversion with the latest converted, the newly created material contains many maps and nodes 1) + 2); That's so frustrating; Is there any workaround?

The Corona Converter shipping with Corona Renderer 7 RC1 now contains changes which should result in much simpler shading networks being generated during conversion. Please let us know if it does or does not work as expected or have some ideas for improvement :)

2021-06-11, 14:14:00
Reply #25

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
hello my friends!

still the same issue with falloff map ...

corona 6 - 1 falloff map in difuse chanel - OK
corona 7 - 1 falloff map in difuse (converted) - lot of CoronaMix maps.

why? wouldn't it be easier not to convert this type of map? (falloff) or rather, create a Coronafalloff?

Hello lzanlorenzi , this issue with lot of CoronaMix maps being generated should now be fixed in Corona Converter shipping with Corona Renderer V7 RC1. Please let us know whether it works as expected :)

2021-06-11, 14:19:44
Reply #26

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Done
1622111539_converter6-7-comparison.zip

Bormax I tried to convert the scene you sent us using Corona Converter shipping with Corona Renderer V7 RC1 and the shading network generated during conversion is simpler. In case of this scene, I noticed that there is still a problem with some duplicate nodes being generated during the conversion, which is caused by known bug in one MAXScript function (on 3ds Max side), we are aware of and already trying to fix, however this should have no negative impact on the visual result.

2021-06-13, 15:52:52
Reply #27

lzanlorenzi

  • Active Users
  • **
  • Posts: 7
    • View Profile
Hi friend!

Great work. now falloff maps wasn t converted to a zilion of CoronaMix maps with CoronaColor maps.. great work...the other improvements are great too... thank you very much!


2021-06-14, 15:16:21
Reply #28

FixelFakes

  • Users
  • *
  • Posts: 3
    • View Profile
Please pass the material ID while converting!

2021-06-17, 13:37:22
Reply #29

junchien

  • Active Users
  • **
  • Posts: 14
    • View Profile
Done
1622111539_converter6-7-comparison.zip

Bormax I tried to convert the scene you sent us using Corona Converter shipping with Corona Renderer V7 RC1 and the shading network generated during conversion is simpler. In case of this scene, I noticed that there is still a problem with some duplicate nodes being generated during the conversion, which is caused by known bug in one MAXScript function (on 3ds Max side), we are aware of and already trying to fix, however this should have no negative impact on the visual result.

I think I have encountered an error in Vray3.6.0 converting plants in Evermotion-Archmodels.207, a prompt appears

I tried rendering without using the converter, but the result is incorrect

2021-06-17, 14:19:04
Reply #30

leo_surrealismo

  • Active Users
  • **
  • Posts: 37
    • View Profile

2021-06-17, 14:33:16
Reply #31

junchien

  • Active Users
  • **
  • Posts: 14
    • View Profile
it is because of vray version.  corona guys are looking into this.

https://forum.corona-renderer.com/index.php?topic=33513.msg186483#msg186483

Yes, I have seen their reply, wish they could do something for the old version

2021-06-18, 00:07:16
Reply #32

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Done
1622111539_converter6-7-comparison.zip

Bormax I tried to convert the scene you sent us using Corona Converter shipping with Corona Renderer V7 RC1 and the shading network generated during conversion is simpler. In case of this scene, I noticed that there is still a problem with some duplicate nodes being generated during the conversion, which is caused by known bug in one MAXScript function (on 3ds Max side), we are aware of and already trying to fix, however this should have no negative impact on the visual result.

Hi
Thanks for your affords, material tree looks better now. But I've got pretty different visual results comparing pictures with original materials rendered by Vray3.7 and converted ones rendered by Corona Renderer V7 RC1.

2021-06-18, 09:18:51
Reply #33

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Done
1622111539_converter6-7-comparison.zip

Bormax I tried to convert the scene you sent us using Corona Converter shipping with Corona Renderer V7 RC1 and the shading network generated during conversion is simpler. In case of this scene, I noticed that there is still a problem with some duplicate nodes being generated during the conversion, which is caused by known bug in one MAXScript function (on 3ds Max side), we are aware of and already trying to fix, however this should have no negative impact on the visual result.

Hi
Thanks for your affords, material tree looks better now. But I've got pretty different visual results comparing pictures with original materials rendered by Vray3.7 and converted ones rendered by Corona Renderer V7 RC1.

I have some notes regarding your comparisons:
- they actually look similar (but if it could be even better - we are definitely interested in improving)
- you are comparing two scenes with completely different lighting - there are strong reflections visible on the leaves in the Corona version, but also the overall lighting is different - for example you can see the effect of sunlight on the branches too in the Corona version, but in the V-Ray version there is uniform illumination coming only from the sky - the branches are much darker)
- V-Ray 3.7 is a very old version, I am not sure if we can do proper conversion from it

If you can send this problematic scene to us, that would be perfect.

2021-06-18, 13:38:12
Reply #34

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
it is because of vray version.  corona guys are looking into this.

https://forum.corona-renderer.com/index.php?topic=33513.msg186483#msg186483

Yes, I have seen their reply, wish they could do something for the old version
This should be fixed in RC2 released just a few minutes ago. Please try it out and let me know if you have further issues.

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-06-18, 15:54:20
Reply #35

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile

I have some notes regarding your comparisons:
- they actually look similar (but if it could be even better - we are definitely interested in improving)
- you are comparing two scenes with completely different lighting - there are strong reflections visible on the leaves in the Corona version, but also the overall lighting is different - for example you can see the effect of sunlight on the branches too in the Corona version, but in the V-Ray version there is uniform illumination coming only from the sky - the branches are much darker)
- V-Ray 3.7 is a very old version, I am not sure if we can do proper conversion from it

If you can send this problematic scene to us, that would be perfect.

Hello
Actually scenes are the same, lighting in both scenes are Corona/Vray Sun + Sky in the same position with intensity set to 1.
New pictures are the original Vray scene and the same scene converted by Corona 7 RC2
I've uploaded Vray scene 1624024326_converter7-vray-comparison.zip, so you can try it

2021-06-18, 17:39:02
Reply #36

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Sure, we will check the scene, thank you!
And just to explain what I mean, I am attaching a screenshot showing the huge differences in lighting. Or the materials are just very, very different.

2021-06-18, 18:09:41
Reply #37

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Sure, we will check the scene, thank you!
And just to explain what I mean, I am attaching a screenshot showing the huge differences in lighting. Or the materials are just very, very different.

Thanks Maru.

But the difference in areas marked by you on pictures unfortunately is matter of texture conversion too. Here is the same Vray scene picture and the only difference here is RGB level parameter of trunk diffuse map - it's raised to 4. As you can see shadows look about the same because they are just more noticeable now.
Next question is about Converter - why converted scene looks so different? (I know, the original Vray picture looks not really nice, but it's not about the beauty of this image :))

2021-06-21, 03:51:59
Reply #38

FixelFakes

  • Users
  • *
  • Posts: 3
    • View Profile
We are losing (3dsmax) Material Id Chanel after conversion. Corona Legacy Mtl with id channel = 1 always converted with mtl ID channel = 0. So I lost my mtl channels in materials for postproduction in my scene.
Corona G-Buffer ID override works fine.

2021-06-21, 12:57:37
Reply #39

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
We are losing (3dsmax) Material Id Chanel after conversion. Corona Legacy Mtl with id channel = 1 always converted with mtl ID channel = 0. So I lost my mtl channels in materials for postproduction in my scene.
Corona G-Buffer ID override works fine.

Hello FixelFakes, thank you very much for your feedback. Please, is this something which used to work as expected in previous versions of Corona Converter and only stopped working in the latest versions?
« Last Edit: 2021-06-21, 13:03:47 by selene »

2021-06-21, 17:18:35
Reply #40

FixelFakes

  • Users
  • *
  • Posts: 3
    • View Profile
Good question.
I can confirm that the old converter used material ID Channel from VrayMtl. So Corona(Legacy) Mtl got Mtl ID from Vray mtl in the old converter.
But new converter doesn't get Mtl ID from CoronaLegacyMtl or VrayMtl.

2021-06-21, 17:38:48
Reply #41

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
We are losing (3dsmax) Material Id Chanel after conversion. Corona Legacy Mtl with id channel = 1 always converted with mtl ID channel = 0. So I lost my mtl channels in materials for postproduction in my scene.
Corona G-Buffer ID override works fine.

Reported and passed on to the devs for further investigation, thanks :)

(Report ID=CRMAX-717)
Please read this before reporting bugs:
How to report issues to us!

2021-06-22, 15:57:42
Reply #42

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Sure, we will check the scene, thank you!
And just to explain what I mean, I am attaching a screenshot showing the huge differences in lighting. Or the materials are just very, very different.

Thanks Maru.

But the difference in areas marked by you on pictures unfortunately is matter of texture conversion too. Here is the same Vray scene picture and the only difference here is RGB level parameter of trunk diffuse map - it's raised to 4. As you can see shadows look about the same because they are just more noticeable now.
Next question is about Converter - why converted scene looks so different? (I know, the original Vray picture looks not really nice, but it's not about the beauty of this image :))

Thanks for sending the scene, I confirm that the converted materials are significantly different. We will see if we can improve the conversion. Stay tuned...

(Report ID=CRMAX-725)
« Last Edit: 2021-06-23, 09:58:57 by maru »

2021-06-25, 12:38:12
Reply #43

Bjoershol

  • Active Users
  • **
  • Posts: 23
    • View Profile
Convert by class in corona converter v1.45 does not convert 3Ds Max Physical Material (compile error: Unexpected end-of-script).

I am still on Corona 6 hotfix 2 in 3Ds Max 2022, has this already been fixed, or is this a known bug?

2021-06-27, 00:14:45
Reply #44

Juraj

  • Active Users
  • **
  • Posts: 4312
    • View Profile
    • studio website
Took me bit of time to test the converter, but I finally did (RC3) and it's just weird :- ). And wrong imho. I would love to see some ruleset behind it to understand what is supposed to happen and why.
talcikdemovicova.com  Website and blog
be.net/jurajtalcik   Our studio Behance portfolio
Instagram   Our studio Instagram, managed by Veronika

2021-07-01, 12:03:44
Reply #45

vtrdo

  • Users
  • *
  • Posts: 3
    • View Profile
Hi guys

we are struggling in several cases ( RC4 )

1st  - more than half of the materials are converted incorrectly .. our old library/models ( Evermotion 85 - palm trees (vray)  for instance ) for most of the leafs its converted as metal material.. this is no problem to change .. just letting you know its happening - basically in every convert - when using old converter - pre 7 it as nearly errorless
      - also is most of the time incorrectly convert the 2 sided Vray materials - way to dark and glossy 
      - and preview of conversion into Physical.Mtl does some strange transparency ...

2nd much more crucial - on most of the models ( Vray 5 installed ) this error appears.. so I have to manually re-make affected materials ( basically all below the first affected )

I can send you a sample scene, if helpfull


many thanks




 

2021-07-01, 15:26:19
Reply #46

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
Hi guys

we are struggling in several cases ( RC4 )

1st  - more than half of the materials are converted incorrectly .. our old library/models ( Evermotion 85 - palm trees (vray)  for instance ) for most of the leafs its converted as metal material.. this is no problem to change .. just letting you know its happening - basically in every convert - when using old converter - pre 7 it as nearly errorless
      - also is most of the time incorrectly convert the 2 sided Vray materials - way to dark and glossy 
      - and preview of conversion into Physical.Mtl does some strange transparency ...

2nd much more crucial - on most of the models ( Vray 5 installed ) this error appears.. so I have to manually re-make affected materials ( basically all below the first affected )

I can send you a sample scene, if helpfull


many thanks

Hi,

The 2nd issue we know about and already have a fix in the pipeline, if everything goes well it will be in RC5.

The other issues are a bit more tricky to solve, would you be able to send through some simple examples for each and we will see what can be done.

Cheers,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-01, 20:17:41
Reply #47

vtrdo

  • Users
  • *
  • Posts: 3
    • View Profile

Hi,

The 2nd issue we know about and already have a fix in the pipeline, if everything goes well it will be in RC5.

The other issues are a bit more tricky to solve, would you be able to send through some simple examples for each and we will see what can be done.

Cheers,

Rowan

Hello Rowen


Thank for reply , and good news on the horizon

For the other topics .. here is a small example ... in the material editor you can find problems with 2sided materials and also the strange preview.

https://we.tl/t-6dKJDyJF7o

many thanks

2021-07-02, 14:53:13
Reply #48

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Convert by class in corona converter v1.45 does not convert 3Ds Max Physical Material (compile error: Unexpected end-of-script).

I am still on Corona 6 hotfix 2 in 3Ds Max 2022, has this already been fixed, or is this a known bug?

Hello Bjoershol! Thank you very much for your feedback! We weren't aware of this problem and we'll try to fix it as soon as possible.

2021-07-02, 16:39:27
Reply #49

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
Hi guys

we are struggling in several cases ( RC4 )

1st  - more than half of the materials are converted incorrectly .. our old library/models ( Evermotion 85 - palm trees (vray)  for instance ) for most of the leafs its converted as metal material.. this is no problem to change .. just letting you know its happening - basically in every convert - when using old converter - pre 7 it as nearly errorless
      - also is most of the time incorrectly convert the 2 sided Vray materials - way to dark and glossy 
      - and preview of conversion into Physical.Mtl does some strange transparency ...

2nd much more crucial - on most of the models ( Vray 5 installed ) this error appears.. so I have to manually re-make affected materials ( basically all below the first affected )

I can send you a sample scene, if helpfull


many thanks
The 2nd issue is fixed in RC5. Please can you install it and let me know if you still have issues?

Cheers!
Please read this before reporting bugs:
How to report issues to us!

2021-07-02, 18:08:34
Reply #50

vtrdo

  • Users
  • *
  • Posts: 3
    • View Profile

The 2nd issue is fixed in RC5. Please can you install it and let me know if you still have issues?

Cheers!

IT WORKS LIKE A CHARM..MANY THANKS

2021-07-04, 10:02:19
Reply #51

mos2787

  • Users
  • *
  • Posts: 1
    • View Profile
Hey,

I intended to use the Corona Converter tool  mainly to convert Vray materials into Corona materials. But I always get a mess (so many unecessary nodes) and the result is not convincing. Eventually, I end up making the conversion manually which is very time consuming.

Did the corona team plan to make major improvements in this field ?

Thanks !

2021-07-04, 20:54:06
Reply #52

TomG

  • Corona Team
  • Active Users
  • ****
  • Posts: 3942
    • View Profile
Which version of the Converter are you using, and can you give some examples of the V-Ray materials going in, and the end result that you consider has too many nodes? Thanks!

2021-07-04, 23:10:52
Reply #53

marti_d

  • Active Users
  • **
  • Posts: 19
    • View Profile
Once again June has passed and I don't feel we are even remotely close to the V7 release. The converter is making even the simple conversion from the Legacy material a complete mess. Mixes on top of mixes on top of mixes. If you think people will go through their entire libraries and will have to set up everything manually you got it absolutely wrong.
Stop checking stupid marks from your Trello map that are once again NOT FINISHED [ pink areal perspective] and actually fix this release hopefully before the end of the year.

P.S. Invisible material after conversion too.
« Last Edit: 2021-07-04, 23:25:39 by marti_d »

2021-07-05, 10:44:54
Reply #54

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Hi

RC5

Again the same tree test. Thanks, this time render result is closer to original, but the shader structure is still messy. Sorry, but I can't see the logic in this Mix map chaos, even simple opacity map from original material became two mix maps (original bitmap + CoronaColor?) plugged in to Front/Back map. Actually all simple bitmaps are converted to Mix maps - original bitmap + CoronaColor with no affect of CoronaColor map in those mixes... This structure is very difficult to handle which makes it not usable for further adjustments. It's easier to remake the shader manually from original material, than to handle this mess.

The test scene was uploaded some time ago - 1624024326_converter7-vray-comparison.zip

2021-07-05, 17:09:57
Reply #55

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Once again June has passed and I don't feel we are even remotely close to the V7 release. The converter is making even the simple conversion from the Legacy material a complete mess. Mixes on top of mixes on top of mixes. If you think people will go through their entire libraries and will have to set up everything manually you got it absolutely wrong.
Stop checking stupid marks from your Trello map that are once again NOT FINISHED [ pink areal perspective] and actually fix this release hopefully before the end of the year.

P.S. Invisible material after conversion too.

Well, could you at least provide a sample scene?


Hi

RC5

Again the same tree test. Thanks, this time render result is closer to original, but the shader structure is still messy. Sorry, but I can't see the logic in this Mix map chaos, even simple opacity map from original material became two mix maps (original bitmap + CoronaColor?) plugged in to Front/Back map. Actually all simple bitmaps are converted to Mix maps - original bitmap + CoronaColor with no affect of CoronaColor map in those mixes... This structure is very difficult to handle which makes it not usable for further adjustments. It's easier to remake the shader manually from original material, than to handle this mess.

The test scene was uploaded some time ago - 1624024326_converter7-vray-comparison.zip

Thanks, we will look into this and hopefully there is still room for optimization.
 

2021-07-05, 19:16:38
Reply #56

marti_d

  • Active Users
  • **
  • Posts: 19
    • View Profile
Open Archmodels vol. 251 on the Evermotion website download the free sample and be amazed how the scene works just fine and when you convert it, all goes to hell.
Also, I am not sure why I am even bothering writing about how you are gonna release V7 with a material library only half-converted and when using the converter on the other half the materials are broken with spaghetti mixes and look nothing like they should.

P.S. Also coronadistance refuses to get into any map slot if the converter was used on the material. Only solution is to create a new material with it.
« Last Edit: 2021-07-06, 12:23:32 by marti_d »

2021-07-06, 21:58:09
Reply #57

sdhollman

  • Users
  • *
  • Posts: 3
    • View Profile
I was wondering if there could be a feature added to the Corona Converter. The studio I work at uses Corona to render all of our animation jobs. Our pipeline uses the default Max camera, we usually need to export cameras to Nuke, and we have not had success with exporting Corona cameras. To solve this we use Max cameras in animation, then add the Corona Camera modifier to those cameras for lighting and rendering. It would be great if in the converter there was an option to convert Max cameras to Corona cameras.

I am not sure if there is a technical limitation to this being a feature. Just thought I would be great to have.

Thanks,
Steven

2021-07-07, 10:24:03
Reply #58

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
P.S. Also coronadistance refuses to get into any map slot if the converter was used on the material. Only solution is to create a new material with it.
I wasn't able to reproduce this, can you provide an example please?

Cheers.
Please read this before reporting bugs:
How to report issues to us!

2021-07-07, 10:27:40
Reply #59

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
I was wondering if there could be a feature added to the Corona Converter. The studio I work at uses Corona to render all of our animation jobs. Our pipeline uses the default Max camera, we usually need to export cameras to Nuke, and we have not had success with exporting Corona cameras. To solve this we use Max cameras in animation, then add the Corona Camera modifier to those cameras for lighting and rendering. It would be great if in the converter there was an option to convert Max cameras to Corona cameras.

I am not sure if there is a technical limitation to this being a feature. Just thought I would be great to have.

Thanks,
Steven
Hi,

Thanks for the request, I have logged it in our system :)

Cheers,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-07, 11:20:40
Reply #60

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Open Archmodels vol. 251 on the Evermotion website download the free sample and be amazed how the scene works just fine and when you convert it, all goes to hell.
Also, I am not sure why I am even bothering writing about how you are gonna release V7 with a material library only half-converted and when using the converter on the other half the materials are broken with spaghetti mixes and look nothing like they should.

P.S. Also coronadistance refuses to get into any map slot if the converter was used on the material. Only solution is to create a new material with it.

Thank you, reproduced. I will log it for a review and hopefully we can improve similar cases. We would greatly appreciate providing examples like this when something is not working as expected.

2021-07-07, 12:08:53
Reply #61

marti_d

  • Active Users
  • **
  • Posts: 19
    • View Profile
Sorry If I sound aggressive but at this point, so much stuff just doesn't work It's hard to keep track. I am fortunate to be able to use the daily builds and not be in a company or a team but I can't imagine anyone will use the new release anytime soon if you don't take at least half a year more to work on things. It's fun and games to test out things but for some people, this is a livelihood. Also any comment on the material library, I think you can reproduce that quite easily.

Also are you in the talks with major texture providers such as Quixel, Poliigon. They both have plugins for importing textures and both don't work at the moment. Getting materials as pure glass or with 99 bump and so on.

2021-07-07, 20:12:11
Reply #62

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Hey,

I intended to use the Corona Converter tool  mainly to convert Vray materials into Corona materials. But I always get a mess (so many unecessary nodes) and the result is not convincing. Eventually, I end up making the conversion manually which is very time consuming.

Did the corona team plan to make major improvements in this field ?

Thanks !

Hello mos2787, thank you very much for your feedback. Please do you use the latest Release Candidate of Corona 7? Over the last couple of "Release Candidate releases", we tried to address the issues you mention. Also, please could you provide us the scene in question?  We'd like to have a look at it and to try to improve Corona Converter accordingly.

2021-07-08, 02:25:42
Reply #63

kanyno

  • Active Users
  • **
  • Posts: 14
    • View Profile
some materials are converted with refraction at 1! For now the Rc has disappointed me. I hope the final version of Corona 7 is good.

2021-07-08, 10:37:09
Reply #64

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 7187
  • Let's move this topic, shall we?
    • View Profile
    • My Models
@kanyno, it would be much more useful if you could send a scene with offending materials to the team. https://corona-renderer.com/upload
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2021-07-08, 11:14:19
Reply #65

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Also are you in the talks with major texture providers such as Quixel, Poliigon. They both have plugins for importing textures and both don't work at the moment. Getting materials as pure glass or with 99 bump and so on.

We are in touch with them and reporting such issues regularly. I think the 99 bump issue is already fixed on their side and this should be available in the newest version of the exporter, or at least it is being worked on.

As to your previous report about the Archmodels 251 scene:

1) The appearance of the material changes (some features of the material become invisible):
For example, the cracks are becoming invisible - this is because they are fully refractive in the original material.
Please understand that if the original material was constructed in a highly un-physical / fake manner, then it may not be possible to recreate it with the Physical Material. The converter tries to keep similar appearance, but that is not always possible.
In this case it seems like keeping the Legacy Mtl may be the best solution.


2) Generating Mix nodes on top of Mix nodes:
This is actually related to point 1. The converter tries to keep similar appearance, and since the material is set up in a "tricky" way (using diffuse color, reflection map, glossiness map, IOR map, opacity map,....) for a simple asphalt material, it becomes problematic.

I am afraid this may be a case of "the converter cannot fix what was originally broken".

But still, we have this logged and will see if there is a way to keep better appearance and simpler shader networks (can't promise anything though).


2021-07-08, 12:51:28
Reply #66

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
some materials are converted with refraction at 1! For now the Rc has disappointed me. I hope the final version of Corona 7 is good.

Hello kanyno, thank you very much for your feedback. If the original materials do not use refraction and the converted materials become refractive, this is indeed a problem, but as romullus already mentioned, we are not able to fix this issue unless we have the scene available. Please, would you be so kind and send us the scene in question? We'd like to have a look at it and to try to fix / improve Corona Converter accordingly.

2021-07-09, 15:38:41
Reply #67

dumbrava.traian

  • Users
  • *
  • Posts: 4
    • View Profile
Does anyone have problems with Forest pack and Corona 7 RC 5? when i try with corona-7-3dsmax-daily-2021-06-03 work good but with Corona 7 RC 5 i think with the new converter desen't even start the render if i have a forestpack obj on the scene

2021-07-09, 16:54:11
Reply #68

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
Does anyone have problems with Forest pack and Corona 7 RC 5? when i try with corona-7-3dsmax-daily-2021-06-03 work good but with Corona 7 RC 5 i think with the new converter desen't even start the render if i have a forestpack obj on the scene
Hi,

Pleas only post your questions in one place on the forum. I have replied to you in the daily builds thread.

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-14, 16:23:55
Reply #69

Kris H

  • Corona Team
  • Active Users
  • ****
  • Posts: 17
    • View Profile
We are losing (3dsmax) Material Id Chanel after conversion. Corona Legacy Mtl with id channel = 1 always converted with mtl ID channel = 0. So I lost my mtl channels in materials for postproduction in my scene.
Corona G-Buffer ID override works fine.
Fixed in RC6 :)

2021-07-14, 16:24:17
Reply #70

Kris H

  • Corona Team
  • Active Users
  • ****
  • Posts: 17
    • View Profile
Convert by class in corona converter v1.45 does not convert 3Ds Max Physical Material (compile error: Unexpected end-of-script).

I am still on Corona 6 hotfix 2 in 3Ds Max 2022, has this already been fixed, or is this a known bug?
Fixed in RC6 :)

2021-07-14, 22:48:08
Reply #71

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Hi

RC5

Again the same tree test. Thanks, this time render result is closer to original, but the shader structure is still messy. Sorry, but I can't see the logic in this Mix map chaos, even simple opacity map from original material became two mix maps (original bitmap + CoronaColor?) plugged in to Front/Back map. Actually all simple bitmaps are converted to Mix maps - original bitmap + CoronaColor with no affect of CoronaColor map in those mixes... This structure is very difficult to handle which makes it not usable for further adjustments. It's easier to remake the shader manually from original material, than to handle this mess.

The test scene was uploaded some time ago - 1624024326_converter7-vray-comparison.zip

Hello Bormax, we tried to make some changes in the Corona Converter code to create simpler shading networks when converting VRay2SidedMtl. These changes are included in Corona Converter which is shipping with Corona Renderer 7 RC6. Please let us know whether the shading networks created during conversion now look as expected or whether there is still some room for improvement.

2021-07-15, 10:45:09
Reply #72

Skalpel3d

  • Active Users
  • **
  • Posts: 16
    • View Profile
The RC 6 version of the converter constantly badly detects metal / non-metal materials when converting, Very annoying situation, e.g. in the case of many objects, such as books .Link to the scene after converting, original vray materials in the editor  https://drive.google.com/file/d/1QV2Bx3_FdbIcoBxPBFkn4r9vbNAEY-mY/view?usp=sharing

2021-07-16, 10:41:01
Reply #73

tallbox

  • Active Users
  • **
  • Posts: 129
  • George Nicola
    • View Profile
    • Architectural Visualizations | TALLBOX
The RC 6 version of the converter constantly badly detects metal / non-metal materials when converting, Very annoying situation, e.g. in the case of many objects, such as books .Link to the scene after converting, original vray materials in the editor  https://drive.google.com/file/d/1QV2Bx3_FdbIcoBxPBFkn4r9vbNAEY-mY/view?usp=sharing
I can confirm that. I have decided to test the daily onto a real-life working scene with many trees and guess what - all leaves went as metal.
Until further solution to this, I've decided to use one of the old converters and it's been working fine.
Architectural Visualizations / Deep work practitioner
https://www.tallboxdesign.com

2021-07-16, 11:52:15
Reply #74

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
The RC 6 version of the converter constantly badly detects metal / non-metal materials when converting, Very annoying situation, e.g. in the case of many objects, such as books .Link to the scene after converting, original vray materials in the editor  https://drive.google.com/file/d/1QV2Bx3_FdbIcoBxPBFkn4r9vbNAEY-mY/view?usp=sharing
Hi,

Could you please send over a scene saved before the conversion has taken place? It's a little difficult to figure out what went wrong if we can't see the original materials.

Thanks,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-16, 11:53:19
Reply #75

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
I can confirm that. I have decided to test the daily onto a real-life working scene with many trees and guess what - all leaves went as metal.
Until further solution to this, I've decided to use one of the old converters and it's been working fine.
Hi,

Which version of the converter did you test? Would you be able to send over this scene?

Thanks,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-16, 16:28:55
Reply #76

Skalpel3d

  • Active Users
  • **
  • Posts: 16
    • View Profile
In the link to which I linked in the classic material editor there are original vray materials

2021-07-17, 20:08:15
Reply #77

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Hello Bormax, we tried to make some changes in the Corona Converter code to create simpler shading networks when converting VRay2SidedMtl. These changes are included in Corona Converter which is shipping with Corona Renderer 7 RC6. Please let us know whether the shading networks created during conversion now look as expected or whether there is still some room for improvement.

Thank you!
RC7- now the shader tree looks much simpler and reasonable. No more unnecessary Mix maps - that's good :)! (Converter7_vray-corona_mat-structure_RC7.jpg) and rendered result is visually the same as it was with RC5 and close to original look of the shaders (Converter7_vray_original-converted_mat-RC5-7.jpg)
This time material structure is much cleaner for further work with it which is great, now I understand how almost all maps were converted in order to use all aspects of Vray 2sided material within single Corona Physical material using FrontBack maps (Converter7_vray-corona_mat-structure_RC7-1.jpg), but:
1. could you explain, please, the meaning of use maps in Vol. adsorption and Vol. scattering of leaf material and why the map which was used in Vray material to map translucency (Map #11) is used here, not in translucency slot of Corona Physical material (Converter7_vray-corona_mat-structure_RC7-3.jpg)?
2. Why IOR parameter of the trunk material is mapped with some Mix map? Is it the way to imitate mapped reflection parameter of Vray material (Converter7_vray-corona_mat-structure_RC7-4.jpg)? And would be interesting to know about the usage of CoronaColor map with applied Solid HDR color higher than 1 in IOR mapping, like IoR map from this example has.

Also would be interesting to hear what do you think about the way of conversion of Vray 2 sided material which I used in my experience. I used two Corona materials plugged in to Corona Layer material with Corona FrontBack map used as mask. Here is a very quick example of this kind of conversion (Converter7_converted_mat_RC7-layerd_2sided_mat_strc.jpg). Material structure is pretty simple, render results you can see also here (Converter7_vray_original-converted_mat-RC7-layered_mat.jpg and Converter7_converted_mat_RC7-layerd_2sided_mat.jpg)
« Last Edit: 2021-07-17, 20:28:42 by Bormax »

2021-07-20, 01:24:42
Reply #78

OH_BOY

  • Active Users
  • **
  • Posts: 9
    • View Profile

2021-07-20, 21:13:46
Reply #79

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
The RC 6 version of the converter constantly badly detects metal / non-metal materials when converting, Very annoying situation, e.g. in the case of many objects, such as books .Link to the scene after converting, original vray materials in the editor  https://drive.google.com/file/d/1QV2Bx3_FdbIcoBxPBFkn4r9vbNAEY-mY/view?usp=sharing

Hello Skalpel3d. Thank you very much for your feedback. To be honest the metal / non-metal detection was probably one of the most difficult things to implement in Corona Converter, since CoronaLegacylMtl has no "metalness" parameter (and for a long time also VRayMtl had not "metalness" parameter), therefore there is no "clean" / "exact" way how to determine whether the original material was intended to represent a metal or not. As a result, Corona Converter can only make some "educated guess" based on available parameters which sometimes unfortunately leads to false negatives or false positives. We are aware of this limitation and we are already working on some improvements, however we decided not to include them in V7 anymore, since it will require huge amount of testing to make sure the new heuristics works better in all / most cases than the current one. Once the testing will be finished, we'll include these improvements to Corona Converter bundled with Corona Renderer 8 daily builds.
« Last Edit: 2021-07-20, 21:26:13 by selene »

2021-07-26, 09:03:41
Reply #80

kino_unico

  • Active Users
  • **
  • Posts: 6
    • View Profile
in addition to detecting false metals, when you manually convert from metal to non-metal it creates an IOR value: 1.01 the problem is that if you had written that value down, you have to manipulate it again.

2021-07-26, 19:11:08
Reply #81

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Thank you!
RC7- now the shader tree looks much simpler and reasonable. No more unnecessary Mix maps - that's good :)! (Converter7_vray-corona_mat-structure_RC7.jpg) and rendered result is visually the same as it was with RC5 and close to original look of the shaders (Converter7_vray_original-converted_mat-RC5-7.jpg)
This time material structure is much cleaner for further work with it which is great, now I understand how almost all maps were converted in order to use all aspects of Vray 2sided material within single Corona Physical material using FrontBack maps (Converter7_vray-corona_mat-structure_RC7-1.jpg), but:
1. could you explain, please, the meaning of use maps in Vol. adsorption and Vol. scattering of leaf material and why the map which was used in Vray material to map translucency (Map #11) is used here, not in translucency slot of Corona Physical material (Converter7_vray-corona_mat-structure_RC7-3.jpg)?
2. Why IOR parameter of the trunk material is mapped with some Mix map? Is it the way to imitate mapped reflection parameter of Vray material (Converter7_vray-corona_mat-structure_RC7-4.jpg)? And would be interesting to know about the usage of CoronaColor map with applied Solid HDR color higher than 1 in IOR mapping, like IoR map from this example has.

Also would be interesting to hear what do you think about the way of conversion of Vray 2 sided material which I used in my experience. I used two Corona materials plugged in to Corona Layer material with Corona FrontBack map used as mask. Here is a very quick example of this kind of conversion (Converter7_converted_mat_RC7-layerd_2sided_mat_strc.jpg). Material structure is pretty simple, render results you can see also here (Converter7_vray_original-converted_mat-RC7-layered_mat.jpg and Converter7_converted_mat_RC7-layerd_2sided_mat.jpg)

Hello Bormax!

Answer to question 1:

The same phenomenon which is defined by Translucency Fraction parameter in CoronaPhysicalMtl is defined by Translucency color in VRay2SidedMtl (not by VRayMtls' parameters connected to the VRay2SidedMtl).

The Map #11 is not used in Translucency color slot of CoronaPhysicalMtl, because VRay2SidedMtl automatically uses base color of the opposite side as a translucency color (that's why we pick Map #10 and Map #16).

CoronaPhysicalMtl ignores both Volumetric Absorption and Volumetric Scattering parameters when its Thin-shell parameter is enabled, but Corona Converter always propagates all maps from the original material, even when they do not contribute to look of the converted material. If VRayMtl uses some other Translucency modes - e.g. SSS, we plug the corresponding maps to these slots so we decided to do the same in this case to be consistent.

Answer to question 2:

Because the original VRayMtl uses reflection amount parameter / reflection amount map, however this parameter is not physically plausible (that's why it's not present in CoronaPhysicalMtl). Since the only CoronaPhysicalMtl's parameter which may affect its reflectivity is IoR (if the material is not metal), we try to create a new IoR value by decreasing the original material's IoR using the reflection amount parameter / reflection amount map in order to preserve look of the original material. However note that this is a "hack" created to preserve look of the original materials. Alternative (more strict) method would be to ignore / drop such parameters / maps, but this could lead to many look-breaking changes during the conversion.

Answer to question 3:

To be honest I have never tried this before, but it looks like a good idea :) May I ask you whether the results look identical? And which approach leads to better render times?

2021-07-27, 01:40:00
Reply #82

Bormax

  • Active Users
  • **
  • Posts: 529
    • View Profile
Hello Bormax!

Answer to question 1:

The same phenomenon which is defined by Translucency Fraction parameter in CoronaPhysicalMtl is defined by Translucency color in VRay2SidedMtl (not by VRayMtls' parameters connected to the VRay2SidedMtl).

The Map #11 is not used in Translucency color slot of CoronaPhysicalMtl, because VRay2SidedMtl automatically uses base color of the opposite side as a translucency color (that's why we pick Map #10 and Map #16).

CoronaPhysicalMtl ignores both Volumetric Absorption and Volumetric Scattering parameters when its Thin-shell parameter is enabled, but Corona Converter always propagates all maps from the original material, even when they do not contribute to look of the converted material. If VRayMtl uses some other Translucency modes - e.g. SSS, we plug the corresponding maps to these slots so we decided to do the same in this case to be consistent.

Answer to question 2:

Because the original VRayMtl uses reflection amount parameter / reflection amount map, however this parameter is not physically plausible (that's why it's not present in CoronaPhysicalMtl). Since the only CoronaPhysicalMtl's parameter which may affect its reflectivity is IoR (if the material is not metal), we try to create a new IoR value by decreasing the original material's IoR using the reflection amount parameter / reflection amount map in order to preserve look of the original material. However note that this is a "hack" created to preserve look of the original materials. Alternative (more strict) method would be to ignore / drop such parameters / maps, but this could lead to many look-breaking changes during the conversion.

Answer to question 3:

To be honest I have never tried this before, but it looks like a good idea :) May I ask you whether the results look identical? And which approach leads to better render times?

Hello Selene!

Thank you for so detailed answers! Now it's clear for me how converter works in this case. Great!

As for the way I used to convert Vray 2sided material, I've done some quick tests. Basically I've used converted by Converter original Vray scene, pictures of single tree and small forest made with Forest Pack. Adaptivity ON, noise limit 4%. Here are results:

Converter7-single_tree_converter.jpg - Passes 25, rendering time 1.38
Converter7-single_tree_manual.jpg - Passes 25, rendering time 2.24
Converter7-FP_converter.jpg - Passes 115, rendering time 14.25
Converter7-FP_manual.jpg - Passes 110, rendering time 23.15

Material structure is a bit more clear and easy to control in manually converted version, but rendering time grows really much. But if you want to test it yourself, I've uploaded scene with private uploader, there you can find all 3 types of materials assigned to different trees and forests.
1627342416_converter7-vs-manual-2sided.zip

Edit:  1627358880_converter7-vs-manual-2sided.zip



« Last Edit: 2021-07-27, 06:17:04 by Bormax »

2021-07-27, 12:50:43
Reply #83

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
Installed offical 7 release... My converter saying 2.0??? That normal? not converting properly

2021-07-27, 13:27:54
Reply #84

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
Installed offical 7 release... My converter saying 2.0??? That normal? not converting properly
Hi,

That's the correct converter version. What is not converting properly? Do you get some error?

Thanks,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-07-27, 17:12:18
Reply #85

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
Installed offical 7 release... My converter saying 2.0??? That normal? not converting properly
Hi,

That's the correct converter version. What is not converting properly? Do you get some error?

Thanks,

Rowan

Vray2sidedMtl not converting, nor vray lights.. was fine on corona 6

2021-07-27, 17:21:25
Reply #86

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
No errors from what can see

2021-07-27, 18:13:18
Reply #87

selene

  • Corona Team
  • Active Users
  • ****
  • Posts: 31
    • View Profile
Vray2sidedMtl not converting, nor vray lights.. was fine on corona 6

Sorry to hear that INVIZ. Please could you send us the scene which manifests this problem?

2021-07-27, 19:23:04
Reply #88

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
Installed offical 7 release... My converter saying 2.0??? That normal? not converting properly
Hi,

That's the correct converter version. What is not converting properly? Do you get some error?

Thanks,

Rowan

Vray2sidedMtl not converting, nor vray lights.. was fine on corona 6

I am guessing it could be too old V-Ray version. You need V-Ray 4 or newer. It doesn't have to be purchased or activated, just installed.

2021-07-28, 15:32:45
Reply #89

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
Installed offical 7 release... My converter saying 2.0??? That normal? not converting properly
Hi,

That's the correct converter version. What is not converting properly? Do you get some error?

Thanks,

Rowan

Vray2sidedMtl not converting, nor vray lights.. was fine on corona 6

I am guessing it could be too old V-Ray version. You need V-Ray 4 or newer. It doesn't have to be purchased or activated, just installed.

I see, so I installed demo of lastest vray.. now cannot see or select corona renderer in choose renderer??

2021-07-28, 16:22:14
Reply #90

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
I see, so I installed demo of lastest vray.. now cannot see or select corona renderer in choose renderer??

That's definitely not expected... Can you try reinstalling Corona 7?

2021-07-28, 17:21:40
Reply #91

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
I see, so I installed demo of lastest vray.. now cannot see or select corona renderer in choose renderer??

That's definitely not expected... Can you try reinstalling Corona 7?
Tried that first, tried uninstalling, then deleting all files.. no luck..

Then uninstalling 3ds max, clean install, clean install of corona 7... still nothing. going nuts D: Mid project and 2 days gone going round in circles.

2021-07-28, 18:31:12
Reply #92

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
I see, so I installed demo of lastest vray.. now cannot see or select corona renderer in choose renderer??

That's definitely not expected... Can you try reinstalling Corona 7?
Tried that first, tried uninstalling, then deleting all files.. no luck..

Then uninstalling 3ds max, clean install, clean install of corona 7... still nothing. going nuts D: Mid project and 2 days gone going round in circles.

Sorry about that. Please try following this guide step by step:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000694496

If it doesn't help or you are having some difficulties, please contact us here https://coronarenderer.freshdesk.com/support/tickets/new and we will assist you ASAP.

2021-07-28, 20:21:51
Reply #93

INVIZ

  • Active Users
  • **
  • Posts: 36
    • View Profile
    • INVIZ
I see, so I installed demo of lastest vray.. now cannot see or select corona renderer in choose renderer??

That's definitely not expected... Can you try reinstalling Corona 7?
Tried that first, tried uninstalling, then deleting all files.. no luck..

Then uninstalling 3ds max, clean install, clean install of corona 7... still nothing. going nuts D: Mid project and 2 days gone going round in circles.

Sorry about that. Please try following this guide step by step:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000694496

If it doesn't help or you are having some difficulties, please contact us here https://coronarenderer.freshdesk.com/support/tickets/new and we will assist you ASAP.

Great stuff, went straight for Solution 6 and worked!! Thank you!!

2021-07-29, 13:25:13
Reply #94

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile

2021-08-09, 15:27:10
Reply #95

Zray

  • Active Users
  • **
  • Posts: 43
    • View Profile
    • 3darcspace studio
 can I convert material to the old CoronaLegacyMtl, I am still not familiar with Physicalmtl
« Last Edit: 2021-08-09, 19:42:29 by Zray »

2021-08-13, 12:19:36
Reply #96

Drawehn

  • Active Users
  • **
  • Posts: 5
    • View Profile
I just tried to convert a timber floor from Vray to corona with the Corona Converter of Corona 7 and it gave me a metall in return. If we have to manually adjust all materials  after converting from Vray, this will suck bad. The old converter to the legacy material worked great. Can you please include the option to convert to the Corona Legacy. Or else just improve the converter to the Physical material.
« Last Edit: 2021-08-13, 12:24:22 by Drawehn »

2021-08-13, 16:14:36
Reply #97

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 10882
  • Marcin
    • View Profile
can I convert material to the old CoronaLegacyMtl, I am still not familiar with Physicalmtl

I just tried to convert a timber floor from Vray to corona with the Corona Converter of Corona 7 and it gave me a metall in return. If we have to manually adjust all materials  after converting from Vray, this will suck bad. The old converter to the legacy material worked great. Can you please include the option to convert to the Corona Legacy. Or else just improve the converter to the Physical material.

Sorry, but there are currently no plans to convert to the legacy mtl.
As a workaround, you can try running the V6 version of the Converter script.

If you ever encounter a material which does not seem to convert correctly - please send it to us and we will do our best to improve the converter.

2021-08-16, 10:43:47
Reply #98

Freakaz

  • Active Users
  • **
  • Posts: 129
    • View Profile
    • Website
Any chances there could be a "Ignore Legacy material" checkbox in the converter so the corona materials that comes from old scenes remains unchanged?

2021-08-16, 12:47:26
Reply #99

LorenzoS

  • Active Users
  • **
  • Posts: 184
    • View Profile
Quote
Any chances there could be a "Ignore Legacy material" checkbox in the converter so the corona materials that comes from old scenes remains unchanged?
+1

2021-08-16, 13:03:58
Reply #100

scionik

  • Active Users
  • **
  • Posts: 144
    • View Profile
Any chances there could be a "Ignore Legacy material" checkbox in the converter so the corona materials that comes from old scenes remains unchanged?

Yeah, please +1

2021-08-17, 08:00:44
Reply #101

philipbonum

  • Active Users
  • **
  • Posts: 16
    • View Profile
Any chances there could be a "Ignore Legacy material" checkbox in the converter so the corona materials that comes from old scenes remains unchanged?

+1

Ideally the converter should "just work" like the old one did, so hopefully we won't need these functions
(I haven't dared to install Corona 7 because of how broken the converter seems to be right now. At least based on the feedback I see on the forums)

2021-08-17, 16:11:21
Reply #102

LorenzoS

  • Active Users
  • **
  • Posts: 184
    • View Profile
Quote
(I haven't dared to install Corona 7 because of how broken the converter seems to be right now. At least based on the feedback I see on the forums)
I think you can install corona7 and move out CoronaConverter.ms, put coronaConverter_v1.42.ms on the same folder.

2021-08-20, 11:23:15
Reply #103

marti_d

  • Active Users
  • **
  • Posts: 19
    • View Profile
I don't think I've actually seen anything more broken in a corona release than this converter. Converting from V-ray is a complete spageti mess. Metal non-metal materials get completely messed up. Again Front and back and mix maps all over the place. Converting from legacy materials to new materials is also absolutely broken.
I tried to start a simple library update after the third asset I gave up. You have to spend a good 5 minutes on each model to fix the materials after the converter has "done" its thing.

2021-08-20, 12:00:25
Reply #104

TomG

  • Corona Team
  • Active Users
  • ****
  • Posts: 3942
    • View Profile
I don't think I've actually seen anything more broken in a corona release than this converter. Converting from V-ray is a complete spageti mess. Metal non-metal materials get completely messed up. Again Front and back and mix maps all over the place. Converting from legacy materials to new materials is also absolutely broken.
I tried to start a simple library update after the third asset I gave up. You have to spend a good 5 minutes on each model to fix the materials after the converter has "done" its thing.

A few specific example materials where things "don't work as expected" would be super useful - otherwise we don't have anything to look into. Thanks!

2021-08-20, 14:20:02
Reply #105

LorenzoS

  • Active Users
  • **
  • Posts: 184
    • View Profile
Hi,
this is one example where cnverter don't work, it's an old files, so i suppose old vray version, but i have a lot of 3d library like theese that i cannot use because of the new converter unforunately.

2021-08-21, 06:57:49
Reply #106

BULUW

  • Active Users
  • **
  • Posts: 15
    • View Profile
Incorrect result of low-version material refraction to physical material,
Refraction level 1, the color is pure black, the conversion result is as follows:

2021-08-23, 14:11:36
Reply #107

marti_d

  • Active Users
  • **
  • Posts: 19
    • View Profile
Not sure if you are just trolling at this moment or what. Take any Evermotion model and I mean any and it's a complete mess.

2021-08-24, 17:44:25
Reply #108

brr

  • Active Users
  • **
  • Posts: 10
    • View Profile
Not sure if you are just trolling at this moment or what. Take any Evermotion model and I mean any and it's a complete mess.
Almost all Evermotion models have very outdated and ugly shaders... (too complicated nodes tree with a lot of garbage textures, overstaurated and overburned colors, old BRDFs and so on..) Did you tried some actual volumes, like 200+?  All older volumes must be reshaded to get normal looking result...

2021-09-04, 02:06:28
Reply #109

miskokral

  • Users
  • *
  • Posts: 2
    • View Profile
That is what i encountered. I have added to a scene a wardrobe with clothes and the converter messed up the fabric converting them into metals.
I had to the materials and reset them to default one by one which was so frustrating. I understand that the Physical material will be the new standard but i think you have failed with the converter on corona 7
You have to add a reversible process to the conversion into Physical material something similar like you have convert bitmaps to corona bitmaps and vice versa.

2021-09-07, 13:58:08
Reply #110

rowmanns

  • Corona Team
  • Active Users
  • ****
  • Posts: 1304
    • View Profile
Hi,

I can understand the frustration here, we are doing our best to look into the issues with the converter. However in some cases where the original material was not set up in a realistic fashion then it is very difficult for us to decide how this should be converted.

Please do send us over some scenes/materials which don't convert correctly and we will look into it.

Cheers,

Rowan
Please read this before reporting bugs:
How to report issues to us!

2021-09-10, 16:58:51
Reply #111

Juraj

  • Active Users
  • **
  • Posts: 4312
    • View Profile
    • studio website
original material was not set up in a realistic fashion

That is the case for 99perc. of existing content, even post-PBR era of materials.

The converter does one thing wrong (because otherwise the way it converts proper materials is very nice, it takes into account everything, but that's not what people use converter for mainly):
It tries to correct those materials that were setup incorrectly. Majority of use for converter is 3rd party assets, not our own scenes. So Evermotion, 3dSky, DesignConnected, etc.. And it fails for all of those.

It converts perfectly my own LegacyMaterials. But I don't need that as much.

I believe there are ways to alleviate that by simply having the converted material remaining weird nonsense even if it was like that previously. The new PhysicalMaterial can be abused enough to map over most of content. That is much better result than ending up with metallic books.
talcikdemovicova.com  Website and blog
be.net/jurajtalcik   Our studio Behance portfolio
Instagram   Our studio Instagram, managed by Veronika

2021-09-10, 20:50:08
Reply #112

lupaz

  • Active Users
  • **
  • Posts: 659
    • View Profile
Hello,

I have a case of conversion here that doesn't make sense.

It converts what it looks like a matte object into a metal.

I think the reason the converter does that is bc the IOR is very high. Still, the reflection is at 0, so it shouldn't convert it into a metal IMO.

Steps:
1- open the scene, and render IR
2- Convert, and render again.

Thanks.

EDIT: I'm using Corona 7 hotfix 1, Max 2020

2021-09-13, 10:28:44
Reply #113

Dariusz

  • Active Users
  • **
  • Posts: 19
    • View Profile
I need to batch convert a few thousand of assets.
When I run corona converter, there is no script output.
How can I use the corona converter to do the work for me? It's an insane amount of work for handwork.
Is the corona converter open-source/on git somewhere? How can I access it & configure & run it?

TIA

Ok as far as I can tell original author released source, but since Corona picked it up is no longer open source?! Why, ffs. Why is it not open so people can use it on bigger projects ?!

Ok found it, glad its public and not private bs! YAy! off to batch my scenes >.> tia!
« Last Edit: 2021-09-13, 11:32:48 by Dariusz »

2021-09-13, 16:59:40
Reply #114

Kris H

  • Corona Team
  • Active Users
  • ****
  • Posts: 17
    • View Profile
Hello,

I have a case of conversion here that doesn't make sense.

It converts what it looks like a matte object into a metal.

I think the reason the converter does that is bc the IOR is very high. Still, the reflection is at 0, so it shouldn't convert it into a metal IMO.

Steps:
1- open the scene, and render IR
2- Convert, and render again.

Thanks.

EDIT: I'm using Corona 7 hotfix 1, Max 2020
Hello lupaz,

Thank you for reporting your issue to us, I've been able to reproduce it on my side as well. We will investigate it.

Kris

(Report ID=CRMAX-959)
« Last Edit: 2021-09-14, 09:41:40 by Kris H »

2021-09-14, 12:52:39
Reply #115

Ryuu

  • Corona Team
  • Active Users
  • ****
  • Posts: 650
  • Michal
    • View Profile
I need to batch convert a few thousand of assets.
When I run corona converter, there is no script output.
How can I use the corona converter to do the work for me? It's an insane amount of work for handwork.

I think it wouldn't really be a problem to modify the script so that it's easier to use from some scripting environment instead of the GUI. Could you please describe your requirements in more detail? What exactly do you need the script to output?

Is the corona converter open-source/on git somewhere? How can I access it & configure & run it?

TIA

Ok as far as I can tell original author released source, but since Corona picked it up is no longer open source?! Why, ffs. Why is it not open so people can use it on bigger projects ?!

Ok found it, glad its public and not private bs! YAy! off to batch my scenes >.> tia!

The converter script is still open source. Although it's a bit hidden in v7. You can find it in C:\Program Files\Corona\Corona Renderer for 3ds Max\YYYY\Scripts (you can also get this scripts path by using the getScriptsDirectory maxscript function).

2021-09-17, 12:26:15
Reply #116

romullus

  • Global Moderator
  • Active Users
  • ****
  • Posts: 7187
  • Let's move this topic, shall we?
    • View Profile
    • My Models
Daily build Sep 06, Converter 2.02

After conversion from standard materials, base bump strength is set to 0.3, eventhough original materials had bump at 100.
I'm not Corona Team member. Everything i say, is my personal opinion only.
My Models | My Videos | My Pictures

2021-09-17, 13:00:13
Reply #117

FinAi

  • Users
  • *
  • Posts: 1
    • View Profile
I just noticed that my previous message could have sounded a bit underwhelming, sorry for that, I didn't intend it. So just to avoid any misunderstandings: the reason why we are not planning to reintroduce conversion to the Corona Legacy Material is because we believe that the Physical Material offers many advantages over the Legacy one. It's easier to set up, the workflow is more in-line with the leading material creation software, and most importantly the end result that you get is more realistic. We treat the Physical Material as the new standard, and the Legacy Material as, well, legacy. :)

Also please note that the Legacy Material will work just fine in Corona 7, there is no need to convert it if you don't want to.

Actually this is a problem when you wanna convert the scene from 3ds Max to Unreal because Unreal does not support the Corona Physical Material. Corona Legacy works fine.