1. Existing FBX file. Imperial units (feet), conventional X,Y, Z up orientation. File opens with proper orientation in ReCap Photo, as well as with proper scaling across several AutoDesk products and viewers.
2. Open that FBX in ReCap Photo, then save again as FBX.
3. Saved FBX has lost the original orientation and scaling when opened in any of the viewers or programs that recognized those parameters in the original.
Is there a way to open an FBX scaled in feet, edit the file in ReCap Photo, and save the edited FBX with the original scale?
Interestingly, Scale and Units can be set in ReCap Photo, but feet aren't an option. Microns, millimeters, centimeters, inches, and meters are.
Ideally a file could be export the same way it came in. Right now I don't know how to edit a file within ReCap Photo and export it out so it scales properly. I'm doing something wrong.....
Steve
Solved! Go to Solution.
Solved by karthik.nathan. Go to Solution.
Hi Steve,
Thank you for reporting this. We looked into it and found an issue in the fbx reader of ReCap Photo. We should have a fix for the scaling and units issue in the next update. We will also be adding support for more unit types to ReCap Photo.
One thing to note about orientations. Maya, but default, has it's up orientation to be the y-axis. ReCap Photo's default up orientation is, however, the z-axis. Both softwares allow you to transform the mesh to y-up or z-up during export. Something to keep in mind when taking meshes between the two softwares.
Hope this information helps. Let us know if you have any more questions or feedback!
Thanks.
-Karthik
Hi @swelebny,
Thank you for your feedback. As @karthik.nathan mention in his last post saying that they have identify this issue and will correct in next update, we will give you an update via Forum post once this issue is deployed in production environment.
Thank you and have a great day!
Karthik, coming from the geospatial side of things I've become used to some of the 'gymnastics' required trying to retain geospatial information while working with 3D models, but had hoped Autodesk would require less of it. Glad to hear this was acknowledged as an issue.
Steve