craig.biggs_ Posted January 17, 2013 Posted January 17, 2013 This is not so much a bug, more of an inconvenience/suggestion. I was looking to use the functions in core/scripts/euler.h and found that they are not currently supporting double precision. It would be nice if the instances of mat4 could be replaced with Mat4 and vec3 with Vec3 (I found this problem in the Nov 12 SDK so you may have fixed this already in the Dec release). I'm starting to feel like I'm the only person on this forum using double precision!
manguste Posted January 17, 2013 Posted January 17, 2013 Craig, No, but feel like you are an active and proficient user of it instead :)) Will surely pass a word to developers.
silent Posted March 13, 2014 Posted March 13, 2014 Hi Craig, I'm afraid we have no plans to implement double precision of coodrinates support to this functions, sorry. How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN
ulf.schroeter Posted March 13, 2014 Posted March 13, 2014 Sorry, but why not ?!? This looks like a trivial replacement of mat4 with Mat4 and vec3 with Vec4...
ExBemined Posted March 14, 2014 Posted March 14, 2014 Double precision is typically used for positions only, not for rotations. So I wouldn't really expect decomposeRotationZXY to return dvec3 in double precision builds.
Recommended Posts