JT File importing multiple versions of the same parts

Unity Asset Transformer
, ,
1

Hi,

We’ve received a JT file from one of our customers and when importing it using PiXYZ SDK it contains multiple copies of the same part all on top of each other. When opening the file in JT2Go only one copy of each part is imported and I can’t see anything obvious that would cause PiXYZ to include multiple copies.

It looks as if the duplicates may be previous versions of the part as some parts include just one duplicate while other has 5+ duplicates and in some cases they differ slightly. I was looking in the metadata for an indication of what might be the true version, but all duplicates have identical metadata.

I thought maybe PMI may include some useful information. When setting the LoadPMI preference to True I can see there is PMI components on some occurrences, but I’m not sure how to interrogate the PMI data. There doesn’t seem to be any PMI specific calls for extracting the data. I was expecting something similar to scene.getMetadatasDefinitions but for PMI components which would let me get a table of properties.

Two questions:

  1. How can get at the information in a PMI component?
  2. Has anyone seen this issue of multiple copies of parts in JT files before and offer any advice for dealing with it?

Thanks

2

Can anyone offer any insights?

3

Hi @FracEdd !
Thanks for your question.
It’s actually quite specific and it’s hard for us to help you without having the JT file and screenshots showing your issues. Can you please open a ticket here? Thanks!

4

Thanks for the response @AxelJacquet

Unfortunately, this particular file isn’t one we can share so I was hoping it might have been a common issue that someone can help with. I’m going to trace back the source of the JT file to see if there are any special export settings that I can adjust.

If I can get anything I can share I’ll submit a ticket. I’ve already been submitting quite a few tickets and very happy with the reponse time so far :folded_hands:

5

If you can produce a dummy JT file that represents the issue, that’d be perfect