Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: jan on 2016-03-14, 16:57:20

Title: CMasking renderelement´s manual selection is not saved in renderpreset
Post by: jan on 2016-03-14, 16:57:20

...not sure if it´s max or corona.

Title: Re: CMasking renderelement´s manual selection is not saved in renderpreset
Post by: jan on 2016-04-09, 14:43:56

SOLVED - just recognized that Max doesn´t save object lists in renderpresets at all - so it´s the same for include/exclude lists in Material Override.
It´s not a bug in Corona, it´s a feature of Max - Render-/Passesmanagement within Max is just frustrating...

Title: Re: CMasking renderelement´s manual selection is not saved in renderpreset
Post by: rfletchr on 2016-04-10, 16:39:46

all of corona's objects expose their properties to maxscript (as do regular render elements)

if you execute something like

Code: [Select]

ele = CEssential_Direct()
arrElementProperties = getPropNames ele

for propName in arrElementProperties do
(
propValue = getProperty ele propName
propClass = (classof propValue)
format "Property Name:% \n\tProperty Value:% \n\tProperty Class:%\n" propName propValue propClass
)

you can collect this data and serialize it
We have an XML serializer/deserializer I've been developing at work which we use in place of render presets.