But I thought by specifying the type like so
"values[0] = (double)2.862738448796;"
over-rode that limitation, and left it with that type's limitations.(in this case double)
Or are ALL 3DGS variable types limited to 3 decimal places? Even floats?
(Note: Ive never had to deal with numbers this "precice" in this ot any other language before)
So if 3DGS cant handle this precision of number (apparently being returned by a DLL)
Any suggestions on work-arounds? Precision data CANNOT be lost...
Thanks and sorry for not being a bug.
how do you compile that piece of code?? my SED is returning sintax errors of cant convert at values[0]=double...
error: CONV:DOUBLE::DOUBLE
This for me is a limitation.. not a bug of function... this happened once when on space game.. but not this precise, like GPS are.