Hi all,
Does anyone know how I can export a georeferenced FBX file (ie. real world co-ordinates) from a 3d DGN. I can export out an OBJ fine, but im looking at having all the materials included.
Regards,
Mark
Dear mark shamoun,
Have you found the solution? then how to write export code to export a dgn file to obj or fbx file with C#? thank you?
regards
James
Hi James,
You can do it all using vba. Have a look at the keyins to export and use a modal handler to prefill the dialog. I also get the macro to fit to window with the upper range of the model and the 0,0 origin.
OpenRoads Designer 2023 | Microstation 2023.2 | ProjectWise 2023
It depends on coordinate system you use. If it produces large coordinates with many digits then because of floating point rounding it loses accuracy and some view artifacts(flickering) can also start to appear. FBX or OBJ doesn't support SRS only local coordinates so expect trouble if exporting in real coordinates.
For example for OBJ format each software has different approach how to georeference OBJ but none of this is implemented in Microstation even that for example Contextcapture produces such OBJ files - https://realitymodeling.ideas.aha.io/ideas/RMI-I-46
Hi James, Please could you share this solution with me ? I am not familiar with VBA and macros
Try to record macro.
Hi Stephen,
If you are still experiencing this issue and its using a Reality Mesh, one recent thing ive found is that if you set your Reality Mesh to have the minimum export resolution value and then drop your reality Mesh to a normal textured Mesh (using the Drop > Applications Elements command) - it will not lose detail or precision on export to FBX when the 0 origin point is included. This should hopefully resolve the issue you are seeing.
This FBX issue is still present in Microstation 16.2 frustratingly...
Apologies, forgot about this - after trying a few things, simply running the keyin: window origin 0,0; point absolute should get the export to come out correctly georeferenced - you just may need to keep an eye out for the level of detail/resolution of the resulting FBX in the event the view is zoomed out too far.
Very suprised that something like FBX export is so reliant on the zoom of the active view...