More Property parameters

[carl.sutton]

I am currently making use of the node import/export feature and applying a custom properties to my nodes. This seems to be a really powerful feature, but the lack of property parameter types such as vec3 mean I have to store 3 individual floats to store any custom vec3 data. Ideally I want my .prop files to be in the following format:

 

<?xml version="1.0" encoding="utf-8"?>
<properties version="1.00">
<property editable="1" name="fold">
 <parameter name="offset" type="vec3">0.0 0.0 0.0</parameter>
 <parameter name="axis" type="vec3">0.0 0.0 0.0</parameter>
 <parameter name="angle" type="float">0.0</parameter>
</property>
</properties>

 

I believe it would be of advantage to also include quat, vec4 and mat4 parameter types in a property too, even if they weren't intended to be editable through the editor as this may be more convenient for some.

[danni.coy]

you could cheat and use ParameterColor (which is a vec4)... for vec3,vec4 and quat classes.

If you access the data infrequently you can use a string.

 

But yes I would like this addition to the property system too :)

[manguste]

Our developers have added vec3 and vec4 support for properties to the to-do list.

[danni.coy]

Thankyou very kindly

[manguste]

Done, will be available in the next SDK.

[danni.coy]

Can we have a mat4 as well?

[frustum]

I think it's quite difficult to edit 16 components of matrix directly.

In Unigine script you can easily convert string to matrix and vice versa:

mat4(getParameterString(id))
setParameterString(string(mat4_identity));

[danni.coy]

will this make a difference to performance if the parameter is being accessed frequently?

[frustum]

It depends on access frequency. It's a problem if you have more than hundreds of accesses per frame.