• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Stark43

Private
13 Badges
Sep 26, 2017
12
0
  • Stellaris
  • Stellaris: Galaxy Edition
  • Stellaris: Digital Anniversary Edition
  • Stellaris: Leviathans Story Pack
  • Stellaris - Path to Destruction bundle
  • Stellaris: Humanoids Species Pack
  • Stellaris: Apocalypse
  • Stellaris: Distant Stars
  • Stellaris: Ancient Relics
  • Stellaris: Lithoids
  • Stellaris: Federations
  • Crusader Kings II
  • Stellaris: Synthetic Dawn
Hi everyone!

I have faced problem exporting ANY existing ship model that was earlier imported by published tool (import io_pdx_mesh;reload(io_pdx_mesh))

after choosing the material in Hypershade and clicking add 'shader' attribute in PDXExport below error occured:

pdx_export_ui.mel line 453: The -en/-enumName flag is only valid with attributes of type enum.

please see below screen:
enumNAME_Flagce988.jpg


If any one new how to fix it quickly, will be very glad.

problem in strings:

line: if ( !`objExists ($root + ".shader")` )
addAttr -ln "shader" -at "enum" -en ($tmp) ($root);
else
line 453: addAttr -e -at "enum" -en ($tmp) ($root + ".shader");

For what purpose we are trying to add enum attribute for not enum type objects, i do not know...
Note: Adding new enum attribute to existing (imported) material does not fix problem,
The only way to fix that i have found, is to create new material with attribute enum...


Yes, of course if You use JoroDox--> collada--->Maya there is no problem, but there is big loss of data.
The same using OGRE, to big loss.

Your HELP is needed...
 
If you've used my tool (io_pdx_mesh) to import an existing mesh, then you will have to remove the existing "shader" attribute from any imported materials before trying to add one via the PdxExport tool. Otherwise you're trying to add something to the Phong material that already exists, and my tool will not create an "enum" attribute but a "string" attribute... so you get this conflict because you are trying to use two different tools.

You can remove the existing "shader" attribute by going to "Modify > Delete Attribute" etc... then re-add the attribute using the original Paradox tool.
It should literally just be two clicks and then your export will work. :)