Corona Renderer 8 for 3ds Max - Daily Builds Discussion

[romullus]

Hmm, are you aware that V7 is out? There won't be no more release candidates.

[cjwidd]

Sry, the terminology I used was incorrect - I am referring to version 8, the upcoming version for which this thread is dedicated. Same questions^

[rowmanns]

Hi,

The materials will be updated over the coming versions, due to the amount of materials it wasn't possible to do them all for v7.

Cheers,

Rowan

[ArchSpideR]

hello. conversion error.

[ArchSpideR]

1.42 don't error

[maru]

hello. conversion error.

You are probably using V-Ray 3 or older. You need V-Ray 4 or newer. We are working on some improvements to make it work with older V-Ray versions too, so stay tuned!
The solution for now is just downloading and installing V-Ray 4 or newer. You don't need a license. It only has to be installed.

[Jpjapers]

Has anyone jumped onto v7 for live projects yet?
How are you finding the changes, specifically the changes to the material workflow?
Im on a long term project at the moment so dont want much downtime from having top get to grips with the new shader. Have you found yourself needing to do anything drastically differently?

[cjwidd]

It took a minute to get used to thinking about the shader mapping metalness directly in a metal-rough workflow; I'm so used to mapping reflection color / fIOR. The sheen also presents a sort of challenge if you are used to thinking about fabric shading in terms of falloff maps, etc; I'm not totally sold on sheen, but it can be pretty powerful if you map the sheen amount directly.

[Jpjapers]

It took a minute to get used to thinking about the shader mapping metalness directly in a metal-rough workflow; I'm so used to mapping reflection color / fIOR. The sheen also presents a sort of challenge if you are used to thinking about fabric shading in terms of falloff maps, etc; I'm not totally sold on sheen, but it can be pretty powerful if you map the sheen amount directly.

These are precisely my worries about switching during production. It seems like a completely different approach to the way you think about materials. Its annoying to be unable to have two versions installed within max without a workaround.

[cjwidd]

Legacy shader is still supported though, so you don't have to implement physical shader in your workflow, yet, if you don't want to. Siger is still using legacy shader too.

[Jpjapers]

Legacy shader is still supported though, so you don't have to implement physical shader in your workflow, yet, if you don't want to. Siger is still using legacy shader too.

Oh i know yeah its still there for now. I just dont want to switch because mid production its usually a stupid idea!
Im looking forward to trying it out alot!

[Jpjapers]

Can we get some info on the Decals?
How will they work or is it too early to tell?

They are an object you apply a material with opacity mask to, that is it. No additional setup necessary

I have to admit the last time I was this excited for a feature was lightmix. This will improve the ease of use and quality of images so much

[cjwidd]

wait, what about decals? Was this added already, how did I miss that?

[lupaz]

wait, what about decals? Was this added already, how did I miss that?

I thought it was just me!

[twoheads]

Has anyone jumped onto v7 for live projects yet?
How are you finding the changes, specifically the changes to the material workflow?
Im on a long term project at the moment so dont want much downtime from having top get to grips with the new shader. Have you found yourself needing to do anything drastically differently?

I had the same impression on new material workflow but it turned out just fine, materials saved in v6 work as they should though. In ongoing project I left most legacy materials untouched but I changed some of them to physical material just to try them out. I enjoy roughness workflow a lot and corona physical is becoming my material of choice. Great thing is now I can finally use old roughness maps as designed.