Now I tried to create a new coordinate system that is a copy of an existing one - but with units cm instead - to see if this "tricks" FME to think it is already in cm - even if it is in meter.
The issue is that the opening software (Navisworks) seems to try to convert the geometry but not the material/texture/raster-coordinates. Anyhow it might be usefull to be able to write to m instead of cm.
Didnt seem to change anything using a custom coordinate system with centimeres as the units instead of meter.
Hi @sigtill,
I came across an existing issue (FMEENGINE-37545) that might make this a bit better in the future. Currently it looks like the FBX reader has a parameter to convert source units to meters, but the writer is labeling the output units as cm.
The example from the issue, if I'm understanding correctly, is that if the translation was from FBX to FBX, only if the source is originally cm would the output be 'correct.' This issue requests to add support for writing or setting the correct unit on the writer, and I'll let you know as soon as the issue has been addressed.
I've created an Idea here as well that you can upvote and share your use case. With upvotes indicating interest, this could help bump up the task to visibility for our development team.
Hi @sigtill,
I came across an existing issue (FMEENGINE-37545) that might make this a bit better in the future. Currently it looks like the FBX reader has a parameter to convert source units to meters, but the writer is labeling the output units as cm.
The example from the issue, if I'm understanding correctly, is that if the translation was from FBX to FBX, only if the source is originally cm would the output be 'correct.' This issue requests to add support for writing or setting the correct unit on the writer, and I'll let you know as soon as the issue has been addressed.
I've created an Idea here as well that you can upvote and share your use case. With upvotes indicating interest, this could help bump up the task to visibility for our development team.
Great, thanks for sharing! Looking forward to try it, hope it solves a major issue moving data to Navisworks!