Binary-to-decimal errors with $FF

   3398   4   1
User Avatar
Member
156 posts
Joined: July 2005
Offline
Am writing out ifds for every 0.1 of a frame using $FF. Works fine until I start getting the binary-to-decimal errors and numbers like 124.199 instead of 124.2.

Is there a simple way to round and specify the number of digits in the decimal portion of the frame number while writing ifds?

Have already gone through “Numbering frames” in the help section.
Floyd Gillis
User Avatar
Member
4270 posts
Joined: July 2005
Offline
Where is the issue cropping up at? In the evaluation of the SOPs? (Like Sequence Blend SOP)? Or in shader parameters?
if(coffees<2,round(float),float)
User Avatar
Member
156 posts
Joined: July 2005
Offline
Sorry… contrary to my previous post… wasn't writing out ifds… was writing out .bgeos with a geometry output driver. Have since worked around my specific problem by using the $N variable… not my first choice solution.

Would still like to know if there's a simple expression solution that can be used in the ROP for the $FF issue.

Thanks.
Floyd Gillis
User Avatar
Member
4270 posts
Joined: July 2005
Offline
I can't reproduce it but would something like, `round($FF*10)/10`, work?
if(coffees<2,round(float),float)
User Avatar
Member
156 posts
Joined: July 2005
Offline
ops:

Rule #1: Drink coffee before trying to work.

Thank you.
Floyd Gillis
  • Quick Links