STEAM GROUP
Blender Source Tools BleST
STEAM GROUP
Blender Source Tools BleST
250
IN-GAME
1,583
ONLINE
Founded
8 November, 2013
All Discussions > Bug Reports > Topic Details
Zappy 8 Feb, 2014 @ 12:17am
[WONTFIX] Strange distortion of .vta flex imports with mis-matching mesh
Yeah, a bug, alright, so, I tried importing an .smd model (vz_mare_nolash) and .vta flex (l_angry.vta), now that the tools allow up to .0625 or such variation of vertices, like StudioMDL... but the compiled model's flex doesn't look like http://sta.sh/01ckk4qi0o3u.

Related .smd and .vta files: http://sta.sh/21az7a9q17b4
Upon checking, it seems the .vta imports just fine on vz_mare_lash, but is derpful on vz_mare_nolash. Therefore, I uploaded vz_mare_lash, too. Note that the .vta is based on the mesh with eyelashes.
Last edited by Artfunkel; 10 Feb, 2014 @ 8:43am
< >
Showing 1-8 of 8 comments
Zappy 8 Feb, 2014 @ 12:40am 
Also, semi-related, do you think you can make a checkbox somewhere that if checked or unchecked, you decide, .vta imports where not all vertices are "found" will not make a .vta vertice object? It will still say that 188 (0%) vertices or such were unmatched, of course, just without the .vta vertice object being created.
Artfunkel 8 Feb, 2014 @ 3:45am 
I can't change the way that Blender shrinkwraps vertices. You're just going to have to import better data, or import the shapes onto the correct mesh then make modifications to that.

Importer settings aren't stored so you'd have to check the box every time. Not much of an improvement over deleting an object. :)
Zappy 8 Feb, 2014 @ 3:59am 
Originally posted by Artfunkel:
I can't change the way that Blender shrinkwraps vertices. You're just going to have to import better data, or import the shapes onto the correct mesh then make modifications to that.
...Oh.

Originally posted by Artfunkel:
Importer settings aren't stored so you'd have to check the box every time. Not much of an improvement over deleting an object. :)
Tell that to this model which has 50 or 51 .vta files for the flexes (I don't know why, either). :P
Edit: Nevermind, I misunderstood that. But I meant like placing the checkbox somewhere outside the import place.
Last edited by Zappy; 8 Feb, 2014 @ 4:00am
Zappy 10 Feb, 2014 @ 10:13am 
Also, what about the fact that if one imports 2 or more .vta flex files, or has made a Basis shape key before importing flexes, then there will be Basis.001, Basis.002, Basis.003, and so on, since it makes a Basis shape key for every import (even though they do nothing and are unused)?
Artfunkel 10 Feb, 2014 @ 10:56am 
OK, that can be done. It'll be in the next release.
Last edited by Artfunkel; 10 Feb, 2014 @ 10:57am
Zappy 10 Feb, 2014 @ 11:27am 
...What can be done? As in fixed and such? Also, apparently, if you are "viewing" a shape key when importing .vta flexes, the flexes will be relative to the viewed flex, which also distorts the model in pretty much the same way as up above.
Artfunkel 13 Feb, 2014 @ 4:10am 
Yes, fixed. I've also made sure that VTAs are always imported relative to the object's first shape.
Zappy 13 Feb, 2014 @ 4:16am 
Actually I'd find that "import relative to current shape" more as a feature than bug, but sure, other people would definitely find it a bug. :P
< >
Showing 1-8 of 8 comments
Per page: 1530 50

All Discussions > Bug Reports > Topic Details