Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Feature Requests => [Max] Resolved Feature Requests => Topic started by: romullus on 2017-03-29, 21:44:26

Title: CoronaLight texmap - improve behaviour
Post by: romullus on 2017-03-29, 21:44:26

When CoronaLight with assigned texmap is instanced, it keeps texmap instanced too, but when it is copied, it loses instancing in texmap too. I find it undesirable and confusing, because when mesh object is copied it keeps material instanced. I think such behaviour is more logical. So my request would be to keep texmap instanced when light is copied.

I'm writing this in forum, because maybe there are people who thinks that current behaviour is more logical / convenient, so they can express their opinion if they want to.

Title: Re: CoronaLight texmap - improve behaviour
Post by: karnak on 2017-03-29, 21:55:53

+1

Title: Re: CoronaLight texmap - improve behaviour
Post by: Ondra on 2017-04-01, 22:19:13

I think this is handled by 3dsmax. Is there any map/material inside 3dsmax that behaves differently?

Title: Re: CoronaLight texmap - improve behaviour
Post by: romullus on 2017-04-01, 22:43:03

Just tested with VrayLight and it behaves same as CoronaLight - keeps instanced map when it's instanced, and looses instancing when it's copied :[

Title: Re: CoronaLight texmap - improve behaviour
Post by: Ondra on 2017-04-01, 23:14:07

yep... 3dsmax thing, sorry. Probably fixable, but it would fuck up several other cases :/