Thanks again Artfunkel.. Grabbing it now.

Thanks Artfunkel, really appreciated.

@Artfunkle, this may be a valid bug find. Animation files are not loading properly in 2.90.1 using the most current version of BleST. They open fine in 2.79b.

(From Blender using the update tool.
Source Tools update...
Info: The latest Source Tools (3.1) are already installed.)

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=2237843501

This is using the model from the link that XDShot provided.

I don't know about that, any model I've worked with has. Especially if I'm taking it back to a different Valve game.

Not sure what your real problem is, this imports fine for me. The weapon animation (reload) loads fine as well.

HOWEVER, the weapon itself is not finished. it has no armature modifier or vertex groups.

These pictures are the V-wpn imports into the current Steam version of Blender (2.90.1) of the link you provided.

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

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


Make sure you have the proper version of BleST (Blender Source Tools) install in Blender.

Firstly you DON'T extract the files.

Watch this Cappy, it will show you how to install.

https://youtu.be/eYug3WVpgcQ

You need to go to the previous versions for Blender Source tools and download version 2.10.2 for 2.79. the BleST 2.3x variants are for Blender 2.8x and above.

https://steamreview.org/BlenderSourceTools/archives/

So, changing the characterset to ASCii fixed the problem? Yes/No?

It may be the Russian(?) characters in your OneDrive File path. Not all the language packs are available for Blender yet. Try using a standard ASCii Characterset for the folder name.

Not sure if this is a Blender, BleST, SudioMDL or a combination of the 3 type problem, but I'm receiving compile errors about UTF-8 characters being passed but might not be compiled properly.

This usually happens with Cedilla c ( ç / &ccedil / &#231 ) and other UTF-8 type characters in bone, mesh and material names. Looking at the Code produced in SMDs/DMXs I find the characters converted to a the usually ASCii gibberish that unknown types create.

I know that they have compiled in the past because I have tons of models that have these type of characters in bone and material names that have been compiled and work properly.

This seems to be happening more since Blender 2.8x was released and I know that language packs are still being developed for the series, so I have been writing the error off as a result of the packs for these type of characters not being released.

However, that said, I'm just throwing this out there to find out where the problem actually lies and a warning to others that might be wondering why they are getting errors like this.