Assembly .jt file is not loading properly on Mendix 3D Viewer

0
Hello Mendix Community,   I am using Mendix 3D viewer to search part from PLM Teamcenter and Viewer it in Mendix 3D viewer.   Part  or Assembly JT file , when searching from Teamcenter is loading successfully and i can see all details. But for Some Assembly  JT file or Part File is not loading fully in Mendix 3d Viewer without error. It is loading Partially. And Progress bar keeps running on Webpage. Not able to see all details attached to JT file.   But if same JT file is opened in TC Visualization tool, then it loading properly and able to see all details.   In Mendix console and log file, there is no error shown.   Please help me for this issue.   Thanks & Regards, Sanjay Kumar Yadav E-mail: - y.sanjay3@tcs.com  
asked
1 answers
1

Hi Sanjay, this sounds like a JT file compatibility or conversion issue between Teamcenter and the Mendix 3D Viewer.

 

If the same JT file loads correctly in Teamcenter Visualization but only partially in the Mendix 3D Viewer (with no errors in the logs), it’s possible that:

  • The file contains unsupported geometry types or metadata that the Mendix viewer can't fully interpret.

  • Some subparts or PMI data might be excluded during conversion or not recognized by the viewer.

  • Large assemblies may hit performance limits or timeouts on the client side, which causes the loading bar to keep spinning.

A few things you can try or check:

  • Make sure the JT file version is supported by the Mendix viewer (some newer JT formats might not be fully supported).

  • Try viewing a simplified version of the assembly (fewer parts) to see if it loads completely.

  • Check if there’s any custom conversion or export setting in Teamcenter affecting how the JT file is built for external viewers.

Also, enabling debug mode or network inspection in the browser might help you spot if the viewer is getting stuck while loading a specific resource or subcomponent.

 

Mendix - 3D Viewer - > Check this documentation

 

 

Hope this helps! :)

answered