Oh, that never occured to me, thanks, SMD works fine.

Not sure if this is a bug or if I'm doing something wrong. I have a model I'm attempting to export with a vertex animation I created with simple keyframing on the default action. When I play the animation from the Vertex Animation window it appears to be properly applied, but no matter what I do, when I try to export the DMX I end up with this error in console:


When I remove the vertex animation, the DMX exports fine. Using Blender 2.74 with Source Tools 2.6.2

Yep, you're a hero.

That's the last of the bugs from this thread, looks like I can finally ditch 2.69.
Thanks so much for your scrutiny.

Okay, the normals are exporting correctly now, however I'm still getting the blackened tongue issue.

Taking a closer look at this, I see now that none of the wrinklemaps are being taken out of their default state. I guess I was so concerned with the tongue I failed to notice this. That would explain the tongue being black, as that is how it appears in a non-flexed position.

Don't know if any of this info will help, but here are a few details:

-I'm using an external txt file as the controller source, rather than a generated source embedded into the .blend

-My Input Controllers are structured in this manner, each with a unique element ID:
http://i.imgur.com/AFTQ3Jv.png

-No errors are generated upon export, a few warnings appear referencing corrective shape keys that go unused, although this appears to be inconsequential.

-Using Binary 2 DMX encoding with Model 1 format

I'm gonna go ahead and mention this, not that I need this fixed right away or anything, but just so you are aware of it; in that original screenshot I posted of the spy, you may notice that the tongue on the right side picture is blackened compared to the tongue on the left.

I figured this was also a result of the corrective shape key normals issue, although your new branch resolved the tearing and lighting issues, the tongue is still black when exported from the new set of tools.

The tongue uses wrinklemaps to simulate AO, controlled by the positions the flexes are in. Could this be another issue unrelated to the corrective shape keys?

Again, I don't need a hotfix or anything, the old tools still work, but just letting you know something else is up.

Yep, that fixed it. Thanks a ton.

By export compatible I just meant that using the latest Blender and Source Tools versions, opening a .blend scene that was originally saved with an older version of Blender will result in all the objects in the scene being unexportable. I've only been able to get it to work by manually appending the contents of the old scene file into a new scene spawned from the more recent Blender installation.

This is the error that appears: http://i.imgur.com/iyCb4wY.png

As for the corrective normals issue, I'm just glad you're aware of whats going on now, I'll try out that new branch, and the older tools still work if need be. Hopefully you'l be able to work out a proper fix for the main branch.

Doesn't matter, this bug is present in official releases, as I stated. The fact that I'm using 1.5.0 only goes to show that it is still unresolved.

I'm not exactly sure what is happening here, but this is an issue that has been present for a while now. The most recent revision to not have this problem is all the way back at 2.1.0.

It's a pretty serious issue, so I figured someone would have reported it and brought it to your attention by now, apparently that hasn't been the case, so I'll bring it up.

This screenshot demonstrates the issue, the left side image is an HWM export from BST 2.1.0, and the right side image is the result of exporting the same setup from any newer BST revision. Something goes wrong when the flexes are compiled, and creates this tearing.

http://i.imgur.com/RRwVuBf.png

Here is the exact same setup to test this with, everything is in relative paths and ready to be compiled, all you need to do is export from the blend and hit the compile button.

http://www.mediafire (dot com) /download/keslcki528tmedb/Enhanced_Spy_Head.zip

Sorry this isn't more detailed but I really just have no clue what is causing this or the circumstances surrounding it.

--------

Another thing to note, although I'm not sure if this is just a natural result of updated code, but older Blender files (like my 2.69 scenes) aren't export compatible after opening them with Blender 2.74 using the 2.5.0 tools.

Is this something that can be fixed? Appending the old object data to a new scene solves the export issue, as long as the scene isn't directly opened first, but for someone with a ton of scene files that would need converting this can really create an annoyance. If it's something that can't be helped though it's not a primary concern.