GRUP STEAM
Blender Source Tools BleST
Alătură-te grupului
GRUP STEAM
Blender Source Tools BleST
6,635
MEMBRI
221
ÎN JOC
1,492
ONLINE
Creat la
8 noiembrie 2013
Sumar Anunțuri Discuții Evenimente Membri Comentarii
De către: ZeqMacaw
< 1  2  3 ... 9 >
Se afișează 1-10 din 83 intrări
În forumul „Blender Source Tools Help”
7
Having problems exporting as an smd
Yes, it is a bug with the plugin.
5
[PR?] Reducing file sizes by improving animation compression when linear interpolation is used.
The following is from memory, and most of this is from working on the model decompiler within Crowbar. Some of it might be a little inaccurate, but should at least give you some ideas to research. I would give more info, but life is messy for me right now.
  1. There are two main ways that the animation data is stored within MDL and related ANI files, using a model compiler that compiles to MDL 49 format. You will have to check if Garry's Mod's model compiler (studiomdl.exe) compiles to MDL 49 format. If it does not, then another game's model compiler might work.
  2. Using an ANI file (via the $animblocksize QC command) might compress the animation data more than without it, but I think the compiler stores a copy of the first frame of each animation in the MDL file and all frames in the ANI file.
  3. There might be other interpolations you can use to reduce the size of some animations.
  4. Try out different options for each animation to see which compress more.
  5. The compile log might show exact byte sizes of the animation data.
În forumul „Blender Source Tools Bug Reports”
10
Not sure if this is a Blender or Add-on Bug. Same Material Names - Different models
This sounds like a new option should be added to the import options pane, similar to the "Bone Append Mode" option, but for materials.
În forumul „Blender Source Tools Help”
9
How to import Flex/Shape-keys for multiple objects?
About 3 years later and I fixed this issue in Crowbar 0.71. Importing the QC file for each of the two given cases in above posts seems to work fine for the various shapekeys I checked. Noting it here in case anyone discovers this via search.

Relevant changelog note:
FIXED: MDL 44-49 - Writes incorrect info to VTA files beyond the first one.
În forumul „Blender Source Tools Bug Reports”
2
ValueError when attempting to import a .SMD
I downloaded the linked SMD file and discovered the cause of the reported problem. The "nodes" section of the SMD file is using invalid carriage return and line feed characters in some of the bone names.

I have pasted the entire nodes section so others can see the cause is from the invalid names for nodes 11, 12, 13, 76, 78, 79.
nodes 0 "c7130_body" -1 1 "master_1" -1 2 "center" 1 3 "Pelvis" 2 4 "Spine" 3 5 "Spine1" 4 6 "Neck" 5 7 "Head" 6 8 "HeadNub" 7 9 "Jaw" 7 10 "Jaw Nub" 9 11 "L Eyelid " 7 12 "R Eyelid " 7 13 "Glasses Bone " 7 14 "L Eye" 7 15 "R Eye" 7 16 "R Lip" 7 17 "L Temple" 7 18 "L Forehead" 7 19 "R Forehead" 7 20 "R Temple" 7 21 "L Lip" 7 22 "L Clavicle" 6 23 "L UpperArm" 22 24 "L Forearm" 23 25 "L Hand" 24 26 "L Finger0" 25 27 "L Finger01" 26 28 "L Finger0Nub" 27 29 "L Finger1" 25 30 "L Finger11" 29 31 "L Finger1Nub" 30 32 "L Finger2" 25 33 "L Finger21" 32 34 "L Finger2Nub" 33 35 "L Finger3" 25 36 "L Finger31" 35 37 "L Finger3Nub" 36 38 "L Finger4" 25 39 "L Finger41" 38 40 "L Finger4Nub" 39 41 "master L ForeTwist" 23 42 "master LUpArmTwist" 22 43 "R Clavicle" 6 44 "R UpperArm" 43 45 "R ForeArm" 44 46 "R Hand" 45 47 "R Finger0" 46 48 "R Finger01" 47 49 "R Finger0Nub" 48 50 "R Finger1" 46 51 "R Finger11" 50 52 "R Finger1Nub" 51 53 "R Finger2" 46 54 "R Finger21" 53 55 "R Finger2Nub" 54 56 "R Weapon" 46 57 "R Finger3" 46 58 "R Finger31" 57 59 "R Finger3Nub" 58 60 "R Finger4" 46 61 "R Finger41" 60 62 "R Finger4Nub" 61 63 "master R ForeTwist" 44 64 "master RUpArmTwist" 43 65 "L Thigh" 4 66 "L Calf" 65 67 "L Foot" 66 68 "L Toe0" 67 69 "L Toe0Nub" 68 70 "R Thigh" 4 71 "R Calf" 70 72 "R Foot" 71 73 "R Toe0" 72 74 "R Toe0Nub" 73 75 "Apron1" 3 76 "Apron2 " 75 77 "Apron3" 76 78 "Apron4 " 77 79 "Apron5 " 78 80 "ClothEsc" 3 81 "Model_Dmy_81" -1 82 "sfx_dummy_82" -1 83 "体力ゲージ_83" -1 end
2
Error importing an .smd
I downloaded the linked workshop item, decompiled the survivor model with Crowbar 0.68, and imported the QC into Blender 2.91.0 via Blender Source Tools 3.1.0. All meshes and shape keys imported without error.

I also imported just the main body mesh and the hair mesh SMDs into a clear Blender, and they imported without error.

Maybe you decompiled the model with an older version of Crowbar that had a bug with decompiling that model.
În forumul „Blender Source Tools Help”
8
Unable to compile (aka another Traceback error)
Try getting the model from the older Blender into newest Blender somehow (using different file formats, if needed, or maybe via blend file itself). Then, use the latest Blender Source Tools for export in the newest Blender.
2
Japanese unicode problems while exporting
Try this Blender plugin to help with renaming stuff:
https://github.com/GiveMeAllYourCats/cats-blender-plugin

Its primary goal is to help with getting models to work with VRChat, but many of its features also help with getting models to work with Source.
În forumul „Blender Source Tools Bug Reports”
1
SMD with a bone name that has a hash character fails to import
Blender 2.90.1
Blender Source Tools 3.1.0
Example model: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=312134319

When decompiled with Crowbar 0.68, these 2 lines are in the "Outfit_Casual.smd" file at the end of the nodes section:
93 "spine 3 attached_Lightning's necklace #2 necklace 1" 2 94 "spine 3 attached_Lightning's necklace #2 necklace 2" 93
Changing to this allowed it to import (i.e. removing the the hash [#] characters):
93 "spine 3 attached_Lightning's necklace 2 necklace 1" 2 94 "spine 3 attached_Lightning's necklace 2 necklace 2" 93

I have confirmed that both the original and the recompiled model with the hash characters show up correctly in Garry's Mod model viewer, so the hash character seems to be a valid bone name character.
În forumul „Blender Source Tools Help”
8
Issue with vertices from HybridPhysx models from l4d2
I decompiled with Crowbar 0.56 and 0.68; the decompiled files are the same. I compiled from the decompiled 0.68 files and viewed the "boom" sequence in L4D2 HLMV and compared it with the original model; the recompiled sequence looks the same as the original one.

I do not understand why the vertices look weird when animating in Blender, but the model seems to animate correctly when recompiled.
< 1  2  3 ... 9 >
Se afișează 1-10 din 83 intrări

Reguli și ghiduri pentru discuții