OBJ, FBX, etc

[I_Megaman_i]

Hey

Why is it so slow to export those formats?!??? It completely disrupts my workflow which makes me really sad, because I like to work in fusion 360. Will you look into this somehow please?

Thanks!

[TrippyLighting]

These exported basically are online exporters and run in the cloud. It would indeed be very helpful if they ran locally!

The explanation that has been given previously is that they only run on one OS so running them in the cloud allows the users of the other OS to use them as well.

However, FBX and OBJ are both formats that Autodesk does not have to license from someone else so it shouldn't be too hard to compile those to run locally. I would not imagine that a converter would require a lot of OS-specific libraries (but I might be wrong!)

[I_Megaman_i]

Neither of those formats are saving UVs upon export or 360 importing only the mesh. why is it so broken?!  Industry standard formats are not even working correctly, whats wrong here really. lol I can live with the clumsy UI but omg this beyond frustration.

[gus.grubba]

It is a royal PITA to have this done on the "cloud" and I see no real excuse for it. The amount of wasted time waiting for this round trip by all users in aggregate is orders of magnitude greater than the time it would take to make it right (run locally, that is). 

[steveKLAWS]

I entirely concur with this complaint.  OBJ export is so frigging slow that in my opinion Fusion 360 goes from a 5 Star app to a 3 Star app.   Either add more squirrels and cages to the cloud or make it a built-in export.  It's not like OBJ is a format that is constantly changing, thus requiring it to be in the cloud.  An OBJ that can take more than 15 minutes to export is for a file that takes 5 minutes to print. Seriously slow. 

Steve