Check Blender materials, do you have an eyeball_R and and an eyeball_L material on the model?

As a further aside, I get the same import results from a TF2 Game cache Demoman player model after extract, decompile (Crowbar 0.67) and qc import using BleST 3.0.3.

https://i.imgur.com/nO5FXhD.png

https://www.dropbox.com/s/jnz3ev7nq2bxmbv/HWM_SFM_Scout.zip?dl=0

I've been playing a lot with scout models lately and have been decompiling the main player models found in the TF2_misc_dir VPK (both player low and HWM), the Source Filmmaker HWM and the the player model found in SFM models\player. (I'm trying to find out why the models are derping out in SFM when importing DMX animations made in Blender.)

This is the SFM HWM model found in the SourceFilmmaker\game\tf_movies\models\player\hwm folder.

I used Crowbar 0.67 for the decompile with Blender 2.8.2 .7 (Current Steam version) and BleST 3.0.3 for the import.

QC and SMD files from the Decompile are not modified.

Included a picture of the import I get using default settings in the main scout folder

As an aside: I get the same import result when using Blender 2.8.1.16 and try to import the QC.

Thanks Artfunkel, I think that coding around the problem would be the best. These hard limits have been there for ages and looking at the response gotten back, I don't think things are going to change (at least anytime soon) in Blender proper.

That being said and if you have any contacts into the Blender Dev Circle, you might want to make a request as well. Being a programmer, you would be the best at explaining the circumstances and the consequences if these hard values aren't increased. As you say, long names are a hard requirement and will remain so.

Now would be the perfect time for Blender to make the switch. 2.8x was a major update and is still evolving. We're seeing that in each new update or release now.

Yup, Give me a few to put them together

@artfunkel

FYI.

I've receive some info in regard to the 63 character limit and this might be huge for both Crowbar and for BleST in future developments (maybe more on the DMX side because of long name).

Anyway, one of my contacts has a connection into the Blender Dev circle. He has had minor tweaks made to Blender during the past development and is alpha testing 2.83. He had made a suggestion to have shapekey names extended to be larger and this is the answer he got back.

This is not such a simple change.
It's not just shapekeys that have this 63 character limit.

All makesdna structs names have this limit set (#define MAX_NAME 64)

RNA functions often work with that defined name size.
For example, for some cases a hash for the name is created for quick access.
Also, saved files have a struct size defined for each datablock, so it is good to avoid changing this size between versions.

Therefore, unless it is an essential change, this request is unlikely to be accepted.

And they have avoided this all the way back to Blender 2.6x and maybe earlier. LOL

Anyway, it looks like add-on devs are going to have to start screaming for changes or have to find some way to program around the MAX_NAME limitation.

Not sure if you already knew about this limitation but I thought I'd just throw it out there in case you weren't aware.

My contact has followed this response up with a formal change request and has also reached out on other unofficial channels as well, but judging from the initial response, I'm doubtful that anything will be done about it unless the voices of add-on and 3rd party devs who are creating software that creates content to be used in Blender join the plea for change.

Another FYI, my contact says this about 2.83...
"wow lots coming". So, one can only wonder what?

Stand-by to Stand-by!

You have 8 different eyes and 8 different mouths for this model?

(Nvm, I think I see what you're trying to do here now and writing a $texturegroup statement to change them out using textures would just be to difficult.)

Here...

$bodygroup "zoey"

studio "zoey.dmx"

No Curly brackets, the statement is not contained and thinks the next lines are part of the bodygroup.

Should be (if you want to use $bodygroup)

$bodygroup "zoey" {

studio "zoey.dmx"
}

(or because there isn't another mesh object or you don't want to blank it out it can be writtenlike this)

$body "zoey" "zoey.dmx"

One way or the other.

And the modelname statement has an error as well

$modelname "David\Pokemon\Gen 5]zoey.mdl"

I think the ] character between Gen 5 and zoey should be a \ character.

So you didn't follow my guide exactly after all. LOL

I never use a $CD command in any of my QCs. I always put the QC in the same folder that I extract to, that way I don't have to use it.


The problem your having (I think) is here.

$sequence "idle" {
fps 1
}

The command is not complete.

You forgot to include the DMX file to use the animation from and StudioMDL thought that name
was FPS1.dmx because that is the next thing available in the statement.

The command should be

$sequence "idle" "pokekidgirl_reference.dmx" {
fps 1
}

That object doesn't exist. For some reason, BleST created a FPS Collection from the Sequence animations. Post your QC here so we can see it. Encase it in
squarebracketon code squarebracketoff
QC paste here
squarebracketon /code squearebracketoff tags