craig.biggs_ Posted January 29, 2013 Posted January 29, 2013 Whilst using the double precision build of Unigine (SDK Nov 2012), we found that we encountered a problem with regards to precision when saving and reloading ObjectMeshDynamic. In script we'd 1) Modify the ObjectMeshDynamic in the world 2) Save the ObjectMeshDynamic to file 3) Shutdown Unigine 4) Start Unigine again and load the world containing the ObjectMeshDynamic After loading from file we noticed that the mesh would not look the same as it had previously (we were using ObjectMeshDynamic to create overhead wires and they'd gone from looking good to very blobby). We were able to work around these problems by expressing the ObjectMeshDynamic coordinates in terms of local coordinates (which is the right way to do it anyway) and then move the ObjectMeshDynamic object to the desired location in the world. Previously when expressing the ObjectMeshDynamic vertice coordinates in world coordinates, we were only at a position that was about 7000m from the origin so it was a little surprising. Since we have solved the problem, its no big deal. I thought I'd just notify you guys in case this causes problems in future. If you need some test data to reproduce then let me know.
necris Posted January 29, 2013 Posted January 29, 2013 Thanks for info, Craig Could you send us your test scene for stable reproduction?
Recommended Posts