Custom attribute number decimal points

[AlexOddbratt]

We're currently using a custom number attribute for FPS but during our latest project we noticed that the number attribute type seems to round of the amount of decimal points to 2 which caused some issues for us as the project was running at 23.976 FPS and fTrack rounded it of to 23.98 FPS. Is there a reason for the limit of 2 decimal points and is there a way around that without having to switch to a text type attribute?

If we have to switch our FPS attribute to a text type will it keep the values it had for all existing and old projects or will it be erased/reset?

[JPrydz]

Hi Alex,

I transfered this into the Support channel.
Sent you an update from there.

Regards,
Johan

[Eric L]

Hello, sorry to re-up this topic, but have you any ETA on this feature ?
Will we be able to manage in settings the number of decimal digits ? As we do for version number padding :)
we can manage some assets attributes with almost 4 or 5 digits behind the coma (displacement values on very precise materials)
For the moment we are using text attribute as work-around, but it would be safer (avoid typing mistakes) to use numerical one.

Thank you very much :)

[Daniel Fleming]

Hi @AlexOddbratt and @Eric L,

in 4.12.current.8 the feature to set how many decimal places a custom attribute has, has been added.  you can set the number of decimals up to 6 places

NEW Allow setting the number of decimals to use on a custom attribute.

please let us know what you think

regards,
Daniel