Around line #490 in utils.py
There's a function that is constantly updated, which checks if the active object is in a group, and does something.


Whatever that whole thing is supposed to do, if the active object has a group, it lags viewport fps to like 66%.



I'm using Blender 2.79;

I commented out the try/finally section and replaced the scene_update_guard variable with False (the end result to skip the whole check)

Here are images showing this, as well as what it looks like in source
(head only)
https://imgur.com/ReCuJq7
And this is an image of the 2 main parts separated, and showing one with/without shapekey (can you spot the difference?)
https://imgur.com/ymx156H

Note: the black neck thing is a second piece of cloth, unrelated

I don't really use workshop models (the process is longer), and because reasons, so I'm less likely to have an example that I can 100 guarantee should have something but isnt working.

Did you try v1? Because as I said, that one's a bigger problem.
I remember v2 being slightly wrong (if you look close) so I reset blender and imported these again. I cant guarantee the thighs are supposed to work on the cloth (because it's not, and it's the only relevant item), but

v1 definitely not work, even for the first mesh.

Im aware of another specific model with only separation issues but again (nudey),

Sorry, wasn't expecting a reply anytime soon, then completely forgot.
Character is clothed, though she has nudey parts. Origin: https://sfmlab.com/item/2537/
Decompiled (importing):
mega.nz /#!1ptARIJQ!Qm4A9NRt_oOBPJ0JzMYt-Zxnh55q7cO-v6H_v_BTqTE

If you're actually going to check it, v2 is the one to go with. The first one works in source but imports the shapekeys more troublesome than v2.
v2 will at least isolate this specific thing for now.

Currently when importing, only ONE mesh will receive shapekeys.
Sometimes Flexes are set for multiple objects (for example body+face, then cloth+etc).
All the flexes (including for other items) are added to the ONE mesh, and if it's not meant for it, it becomes a spikey glitch.


On practically every import I make, I get an error saying VTA failed to import something, then it creates an object made of nothing but vertices as a "reference".

I decompile as qc with crowbar, all the flexes are unified and working in hlmv, when imported, only one mesh will receive flexes, and trying to just import the vta onto the "reference" object, still results in incorrect shapes (spikey distortion)


One particular mesh i have has the face split apart (making all the keys useless right now), plus some of the vertices are wrong on the part that actually imported.



Is there a particular method to getting all the flexes imported on all the meshes?

Starting Blender with --enable-new-depsgraph , enables the new dependency graph that's going be default in 2.8.
It allows using certain constraint combinations that are broken/lagged in default/current dependency graph.
For example targeting rig1.bone1 to rig.2.bone.1 while also targeting rig.2.bone.2 to rig.1.bone.1
will cause the bones to get stuck/overshot/offset from what seemed like the obvious intended transformation.


Anyway, Blender just crashes, and in the command prompt, these were left:

SMD IMPORTER: now working on orcfemale_earrings1
- This is a mesh
- Imported 116 new bones
- Imported 1 frames of animation
Error: EXCEPTION_ACCESS_VIOLATION

Happens on everything, and disabling import animation still says imported animation before crash. new depsgraph works in 2.78c (and I believe it worked in the daily 2.78.5 builds) but now in 2.79 it crashes.

There is a console error that pops up when loading a .blend file and every time un/maximizing a window (shift+space). After removing everything I could from the entire blend file, yet still getting the error, I noticed this small thing I did with my screen layout. After removing it, I found the problem (then I tested a little further to see where exactly it starts).

While [Source Engine Exportables] is open with the Scene tab open, upon the window reloading (I.E. load/un-maximize) a red error is sent in the console and info panel at the top.

The error occurs when [Cube] is not in the blender file.
There may be more to it but while the default cube is deleted, the error occurs, and upon adding the cube again, it stops.

I updated because another addon modified other addons and had an error or whatever, so the new version was 2.8 (last 2.7.1).
So anyway after re-adding 2.7.1 or just disabling the addon, the bug is gone.

The bug is that you can't Shift+select grouped items.
Which is super odd because this is supposed to be an importer, yet it's messing up controls elsewhere, so what's going on?

I'm using 2.78 64-bit windows (particularly a daily build but that doesn't matter because I tried it on the regular 2.78a build as well)

;343787920117065394 lähetti viestin:

No, because that would change the layout of the armature. Every time you connect a bone to its parent you are also rotating it, which will mess everything up when you come to combine it with other animations or reference meshes.

The only issue with that is when you connect the child to the parent. I don't know why but the way the rigs import into blender is that the parent's head and tail are in one spot when the TAIL is suppose to be down at the child, this connecting all bone chains correctly except for endpoints and bones with multiple children (such as the hands), and for those points, I just guesstimate.
I don't know if the source location is suppose to be at the center of the bones or the head, so I just use the head because that will stay the same no matter how many tails I move.

This gives a far more usable armature in Blender. For example IK kind of works as is but in order to do more proper/common IK methods, you have to move the tail of the parent bone to where the IK is (at the child).
Also, auto IK doesn't work at all and BEPUik (a custom IK solution) freaks out with these kind of bone layouts.

Maybe fixing the bones is a problem for importing animations because of bone normals or exporting animations to Source but for someone like me that has ZERO intention of importing animations or exporting to source, the lack of fixing bones is a major hassle for me. We should at least have the option of how it imports.