Tracker

[adrian.licuriceanu]

Hello,

We are trying to use tracker to control various of our systems parameters (Unigine 2.13.0.1). Most parameters are included in properties for our system. So we have some issues, some of them making the tracker basically unusable for us, in case we don't find an workaround:

- Tracker don't have support for vec3 and vec4 for properties. Choosing color will force input to 0..255 per channel. Choosing string (so somehow in the end we parse space/comma separated float values from it) behaves very strange (when you add a key value you are presented with file open dialog which doesn't do anything).

- Changing the .prop files while one parameter from them is being referred by current track most of the time crashes the editor. 

The later we can learn to avoid, but how about the first issue? How can we add support to control vec3/vec4 values? Maybe an alternative would be to choose node.position, but, while also an ugly hack, it also possesses other issues for us (you need to indicate an actual node from the scene, while we want our tracks to be scene independent).

Regards,
Adrian L.

[silent]

Hi Adrian,

Quote

Choosing string (so somehow in the end we parse space/comma separated float values from it) behaves very strange (when you add a key value you are presented with file open dialog which doesn't do anything).

Yes, that's an odd one, but you still can type a string into the filename string and it will work. vec3/vec4 were not added more likely because they are mostly needed for colors / positions, but there are already separate parameters exists for these.

We can probably improve this behavior in the future versions, but not right now.

Thanks!

 

 

 

[adrian.licuriceanu]

Hello and thank you for the response.

In the end, instead of vec3 and vec4, we've changed our system to accept 3 or 4 separated float properties (named like prop_x, prop_y, prop_z and parsed accordingly to detect which component goes to which property). It works but it complicates the code on our side. So any change to this would be greatly appreciated in the future.

Any news on the new tracker? Preferable implemented in native C++.

Regards,
Adrian L.

[silent]

For tracker a lot of background work should be done first, including implementing the new concepts of animations inside the engine.

Right now I can't really say the exact date when it would be done, but native C++ / C# API would be a for sure a default option.