Odd export bug [fixed] :: Blender Source Tools

STEAM-GRUPPE

Blender Source Tools BleST

Deltag i gruppe

STEAM-GRUPPE

Blender Source Tools BleST

6,844
MEDLEMMER

385

I SPIL

2,299

ONLINE

Grundlagt:

8. november 2013

Oversigt Meddelelser Diskussioner Begivenheder Medlemmer Kommentarer

Alle diskussioner > Bug Reports > Trådoplysninger

NimrodX 20. aug. 2014 kl. 18:35

Odd export bug [fixed]

I'm running into this error when trying to export a scene:

Traceback (most recent call last): File "C:\Users\Robert\AppData\Roaming\Blender Foundation\Blender\2.71\scripts\addons\io_scene_valvesource\export_smd.py", line 194, in execute File "C:\Users\Robert\AppData\Roaming\Blender Foundation\Blender\2.71\scripts\addons\io_scene_valvesource\export_smd.py", line 409, in exportId bone_parents = collections.defaultdict(list) File "C:\Users\Robert\AppData\Roaming\Blender Foundation\Blender\2.71\scripts\addons\io_scene_valvesource\export_smd.py", line 804, in writeSMD for mod in id.modifiers: File "C:\Users\Robert\AppData\Roaming\Blender Foundation\Blender\2.71\scripts\addons\io_scene_valvesource\export_smd.py", line 419, in getWeightmap IndexError: list index out of range location: <unknown location>:-1

This might have something to do with me using an Armature modifier with a single bone. (There are no weights because the bone is only used as an attachment point.)

The blend file where this happens is here: https://www.dropbox.com/s/2asrbq3qjhr0ilu/exportbug.blend

This was happening in the previous version of the export plugin as well, but I hadn't gotten around to reporting it. A workaround appears to be to export single objects one at a time and not the whole scene at once.

Sidst redigeret af NimrodX; 21. okt. 2014 kl. 13:52

< >

Viser 1-5 af 5 kommentarer

Artfunkel

21. aug. 2014 kl. 12:04

Thanks, fixed it.[steamreview.org]

NimrodX 21. aug. 2014 kl. 22:53

awesome. thanks. is the fix in the current download?

Artfunkel

22. aug. 2014 kl. 1:16

It wouldn't be anywhere else. :)

Zappy 17. okt. 2014 kl. 12:34

Hm. I think you forgot to append "[FIXED]" to the start of the title after fixing this, Artfunkel (and/or NimrodX), making it seem like an unfixed bug when browsing bug reports...