werner.poetzelberger Posted March 21, 2019 Share Posted March 21, 2019 We are always having some troubles with units. Normally we work in cm rather than in m. The translation into m from cm can become painful in certain workflows. Can the fbx format respect the units? werner Link to comment
silent Posted March 22, 2019 Share Posted March 22, 2019 Hi Werner, How do you think - scale on import will work in your case? That would allow you to keep your FBX files in any units. Thanks! How to submit a good bug report --- FTP server for test scenes and user uploads: ftp://files.unigine.com user: upload password: 6xYkd6vLYWjpW6SN Link to comment
werner.poetzelberger Posted March 26, 2019 Author Share Posted March 26, 2019 If the fbx file knows the units working in, then e.g. 156 cm would result in 1,56 m in Unigine. Atm its 156 m when I import. So I scale down the file on import by 0.01 which gives the same visual output. But sometimes a scale factor results in weird behaviors. So we would prefer a scaling of 1 for all elements in Unigine. On the other hand, I know it can be tricky if you have material from different sources. In our current project we work with files from Maya, and Animations from a different package. It would be great if I dont need to scale convert etc. files. Does that make sense what I say? Best. Werner Link to comment
Recommended Posts