DMX has corrupted UV maps

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Import a .dmx file (for example VALVe's Hard-Ware Morph Demoman from the 
Source SDK).
2. Export the .dmx again.
3. Compile it to an .mdl.

What is the expected output? What do you see instead?
Expected: Everything works. Noticed: The UV Map is completely scrambled up. 
(Seemingly it gets scrambled upon import.)

What version of Blender and the SMD Tools are you using? On what operating
system?
Blender: 2.68a (64-Bit version)
SMD Tools: 1.9.0
Operating System: Windows 7 64-Bit

Please provide any additional information below.
Earlier (with older versions of Blender and the SMD Tools), I have been able to 
do the exact same thing, and with a working Demoman/UV as export.
I also did select a vertice on the Demoman's patch, hit Ctrl+L (select 
connected mesh), and then delete it, and give his left eye the material 
eyeball_l (personal reasons).
The "SDK directory" points towards Source FilmMaker's bin folder.
I did rename the objects (like head=zero to demo_head, game_grenades to 
demo_grenades, and game_meshshape to demo, and such), and tick "Supress" 
(export all objects individually).
I did make sure to set the "flex type" to Advanced, and link it to the 
demo_morphs_high.dmx I imported.
This is ridicolously annoying (just thought I'd let you know).
This sentence is true.
These last 3 lines of "additional information" are jokes, and not related to 
the issue. The other lines are related, though.

Original issue reported on code.google.com by TheZeroT...@hotmail.com on 15 Oct 2013 at 10:58

[GoogleCodeExporter]

I have replicated the problem as well. It seems to be a compatibility problem 
between the io_SMD_Tools Script and Blender 2.68a.  After the mess up with the 
uvs in smd_Tools 1.9.0, I have 1.8.6 back into Blender 2.68a and ended up with 
the same UV mess up as with 1.9.0.  Both io_smd_tools 1.8.6 and 1.9.0 work fine 
in Blender 2.67a.   

This only seems to affect .dmx imports, .smd imports are fine in 2.68a.

Attached file show the unlit texture results in Blender between 2.67a, 2.68a 
and io_SMD_Tools 1.90

Original comment by pte...@gmail.com on 21 Oct 2013 at 10:46

Attachments:

• UVProb.png

[GoogleCodeExporter]

I have successfully confirmed that using Blender 2.67b (I degraded due to this 
bug) and version 1.9.0 of the SMD Tools also give correct UV Maps, just like 
for the other guy here. It seems to be a compatibility issue with Blender in 
general, not the SMD Tools itself. A little (or big, I don't know) code change 
may be able to fix it.

Original comment by TheZeroT...@hotmail.com on 21 Oct 2013 at 1:21

[GoogleCodeExporter]

I can reproduce this too, but it seems to have been fixed in Blender 2.69. 
Please give that release a shot (should be out very soon) and let me know.

Sorry for the delay BTW, my bug alerts stopped arriving!

Original comment by cont...@steamreview.org on 29 Oct 2013 at 10:56

• Changed state: Accepted

[GoogleCodeExporter]

Since 2.69 is not in an installer on the official download page yet, I'm not 
going to use it until that. For now, I'll be using 2.67b.
But alright, I shall wait for that release, give it a go once it's out, and 
then tell you how the UV Map works for the same model for me in 2.69.

Original comment by TheZeroT...@hotmail.com on 30 Oct 2013 at 9:21

[GoogleCodeExporter]

2.69 is out now.

Original comment by cont...@steamreview.org on 1 Nov 2013 at 11:19

[GoogleCodeExporter]

Yep, it is, and I need to check my mail more often. Oh, well, so far, .dmx 
import works for lowpoly models. Haven't tried with the highpoly Demoman again. 
But I believe it works.

Original comment by TheZeroT...@hotmail.com on 2 Nov 2013 at 2:17

[GoogleCodeExporter]

Original comment by cont...@steamreview.org on 5 Nov 2013 at 11:57

• Changed state: Fixed