Not a stupid question. I'm using 4bytes/32bit floats.
I remmeber that post, but I thought it was to do when you try to print it out. I didn't know it would screw floats up when you simply pass it to a dll function.
Ok I pass the float '1212.122' to my dll. Immediately I get '1212.121948'. '1212.121948' is stored like that in the dll. Then when I peek it back to blitz, '1212.121948' becomes '1212.12'.
Now I ask is that acceptable floating precision tolerance? Ofcoarse the bigger the floating point number, the more the precision flys out the window( yeah, given regular single precision on it's inaccuracies, but this is just plane out there in left field. ).
I remmeber that post, but I thought it was to do when you try to print it out. I didn't know it would screw floats up when you simply pass it to a dll function.
Ok I pass the float '1212.122' to my dll. Immediately I get '1212.121948'. '1212.121948' is stored like that in the dll. Then when I peek it back to blitz, '1212.121948' becomes '1212.12'.
Now I ask is that acceptable floating precision tolerance? Ofcoarse the bigger the floating point number, the more the precision flys out the window( yeah, given regular single precision on it's inaccuracies, but this is just plane out there in left field. ).