Page MenuHome

Unable to import more than one PSK file
Open, ConfirmedPublic

Description

System Information
Win10 x64
Intel Integrated (HD 4000)
Nvidia GeForce 610m
i3-3110m
8GB RAM

Blender Version
Broken: 2.79 5bd8ac9 (plugin: 2.2.0)
Worked: n/a

Short description of error
Unable to import more than one Skeleton Mesh (psk)
Engine: UE3
Game: Paladins/SMITE (same format)

Exact steps for others to reproduce the error
The exact models are from the UE3 game Paladins, Evie's character, default skin.

The entire model is split into two parts: hair+eyes+mouth and everything else

Import either of the parts, import succeeds.

Import the second of the parts, import fails with:

Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\io_import_scene_unreal_psa_psk.py", line 779, in execute
    self.importmultiuvtextures)
  File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\io_import_scene_unreal_psa_psk.py", line 719, in getInputFilenamepsk
    pskimport(filename, importmesh, importbone, bDebugLogPSK, importmultiuvtextures)
  File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\io_import_scene_unreal_psa_psk.py", line 673, in pskimport
    for bone in ob_new.data.bones:
UnboundLocalError: local variable 'ob_new' referenced before assignment

location: <unknown location>:-1


Details

Type
Bug

Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Apr 4 2018, 10:43 AM

Could you upload the files in question here (.psk), please?
Not sure about the legal status of those files, if this is a problem, can you provide example files that show the same problem?

added the files to the task description for convenience

Philipp Oeser (lichtwerk) raised the priority of this task from Incomplete to Confirmed.Apr 5 2018, 12:11 PM
Philipp Oeser (lichtwerk) claimed this task.

Can confirm that the script will fail on second import [code already checks for previous imported object (namebased) but fails to handle that case properly -- it's probably an easy fix, will look into it later if original author is unavailable].

Workaround for the time being: just rename the Armature called "ArmObject" to something else prior to importing the second time.

@John Phan (darknet) : are you here and want to have a look?

Ok, thanks for the workaround, I'm looking forward to an updated version of the plugin. :)