PLMXML loading and structure

[bgledhill]

Hey there,

I've got 2 problems with my PLMXML imports. First off i'll try and explain the scenario and then the problems.

So, i've have this set-up which uses a competitors software for the rendering. First off, i'd export using a custom script an assembly from CAD, into corresponding folders and subfolders (to keep is simple: Bodies, Equipments and Product Assemblies:

• all parts in the assembly to .STP 
• all sub-assemblies to a simple PLMXML file, as in, name of file to link to and vector coordinates (no material nonsense etc). In this file, all parts/sub asm were referenced to using a "../../folder" structure, and .3XF or .PLMXML extension depending on the file type

We'd then run the converter which would convert all .STP into .3XF (keeping NURB info) and so the PLMXML could find all the parts necessary when opened.

Now, after a bit of testing i managed to convert my .3XF files into a .FBX with NURB info, and VRED can import these no problem --> Bloody great, it keeps all info from my old software, including material names etc (just need to re-create materials in the asset library)

I also used Notepad++ to change all instances of "3XF" into "FBX" in all PLMXML files --> Perfect

So, i've got my database pretty much running as before, i'll still have to change a few things around process wise, but that can wait.

Now i've come accross 2 problems it seems:

• Whenever a PLMXML references another PLMXML file, i get an error (see image 1)
  • While writing this post i tried with VRED 2021.1 Pro (instead of VRED 2021.3 Design) and everything loads correctly --> Bug in 2021.3? or Design limitation?
• For parts that are instanced twice in the PLMXML, only one is visible, it seems the geometry isn't "duplicated". Now i can manually copy/paste, but i was wondering why it won't load like this out of the box (see image 2)

One extra question, is there anyway i could use the asset manager for some of the geometries that are used often? or even for all of my exported parts?

Thanks a lot

Benjamin

[seiferp]

There should be no difference between Pro and Design when loading PLMXML files. The second problem with the non visible instance looks interesting buggy. Can you share your example to reproduce on our side?

[bgledhill]

So i've recreated the file/folder structure for this particular case.

The PLMXML to open is in: Product Assemblies -> BUMP -> STK

Tried it with 2021.3 Design, and it doesn't load the second level PLMXML as stated in original post. I haven't tried with 2021.3 Pro though yet.

I'll let you take a look and get back to me 😉

Thanks

[seiferp]

Thanks for the reproducer 👍 To answer your questions...

PLMXML is not (should not be) supported in VRED Design. See here. As you have already realized it is half possible loading the top level PLMXML 😂 This is not our intended behavior. We will discuss internally if we will support PLMXML properly in VRED Design in the future.

That the cloned references do not load properly is a bug and I have created a ticket for that. For now you can only fix it manually by unloading and loading the references again. Open the Reference Editor and select all References that appear multiple times in the file. Context menu > unload and load again.

VRED - Reference Editor

Thanks for your help

Cheers

[bgledhill]

So you induced me into error when you said there should be no difference between Design and Pro 😋

My bad for not looking at your linked post earlier, i only saw the features on the VRED home page...

Obviously in my case it would be useful to have full PLMXML import feature in the Design version, as the team who use it don't need the extra functionality the Pro version offerts (basic rendering really)

Thanks for the tip regarding the bug, i'll pass it onto my users.

Regards

Benjamin

[seiferp]

Yeah, sorry my bad. It´s often hard to spontaneously remember the features for the different VRED flavors 😂 Thankfully I said should not!!!

[seiferp]

You reported PMXML bugs should be fixed in the latest VRED 2022 release! Also VRED Design now supports PLMXML assembly files.

[bgledhill]

Just saw that the new version was released, and i've been going through the changes !

Great news, i'll be installing ASAP.
Thanks !