# Retexturing props

Discussion in 'Mapping Questions & Discussion' started by Mystic Monkey, Jan 21, 2017.

1. ### Mystic MonkeyL4: Comfortable Member

Messages:
181
Positive Ratings:
18
I got two model-texture based problems. One involving props, the other involving capture point hologram.

So, I know how to replace default textures in TF2 (this tutorial helped) yeah haven't actually tried it on a TF2 default model, but I have with a custom model and it worked.

But for my map, I would like to use certain props that TF2 has, but with new skins, especially more than one.
I didn't want to replace TF2 default props skins as then I would see it throughout the game and those who want to play my map will not see it. Plus I want to add more than one skins to make team variants for both sides.

So through GCFScape I made copies of the models, assosiated files and skins I wanted to replace (update_poster001, update_poster002 from teaser folder and bannerflag from medieval folder) I put them in their own folders in my models and materials folder, gave them new names to make them more recognisable for Hammer, .vtf and .vmt, made sure to address the $basetextures properly and so on. (update_sonic_poster001 and update_sonic_poster002 to all the .vtx, .vvd and .mdl) Because flags and posters are flat and easy for novices like me to retexture, I reskinned update_sonic_poster002 default skin, I changed the .vtf and renamed it update_sonic_poster002.vtf and addressed update_sonic_poster002.vmt to where it can find the model in it's designated folder but for some reason the poster is still using TF2s default Mann.co texture for it. I tried it again with the medieval C-point flag which is simply renamed bannerflag_sonic and saving over it's default .vmt before renaming it and re-addressing it. But still it's using default TF2 textures despite being a renamed copy, in a new folder, with it's own skins addressed to it. If this can't be resolved, I'll resort to just making them overlays, but given they would be too flat to be posters and flags I hope it won't be. Last edited: Jan 21, 2017 2. ### aaCrowbarperfektoberfest Messages: 1,441 Positive Ratings: 1,192 I think you need to recompile the model for it to use more skins, or ones from different files. 3. ### aaTumbolisu I ⌄ I Messages: 951 Positive Ratings: 937 You can not rename model files. The .mdl is basically a list of all the other files, and if you rename or move those, it can't find them anymore. It also stores where to search for the material files, which you can't change by simply renaming. Appart from figuring out how to edit a .mdl with notepad, you have only the following choices: 1. Accept to only use the number of skins the model has and simply tell the .vmt to use a different basetexture. Then, pack the .vmt and .vtf into the map. The .vmt can not be in a different file path as the original. 2. Decompile the model and recompile it again with a different name, model path, material path, and skin count. This gives you the most control. Also, loading a file over another can be glitchy anyways, so this is much more consistent. Obviously, this also requires much more work. 4. ### Mystic MonkeyL4: Comfortable Member Messages: 181 Positive Ratings: 18 I could try the notepad option... looks easy. >Hammer crashes when loading map. Damn. And since I dunno much about compiling models, all I can do is flat overlays which look too flat to be posters or flags. 5. ### aaPocketfunc_croc Messages: 4,489 Positive Ratings: 2,219 Also, TF2 sometimes does and sometimes doesn't accept packing a modded version of a stock model into the map. I know for a fact it doesn't work for item pickups; dunno about static props. 6. ### aaTumbolisu I ⌄ I Messages: 951 Positive Ratings: 937 I already mentioned that with It's the exact opposite of easy. You are basically playing around with 0s and 1s if you want to edit a file like this. Well, you know, you could always just ask for help or even have somebody do it for you. 7. ### Mystic MonkeyL4: Comfortable Member Messages: 181 Positive Ratings: 18 I know, I just hate how inaccessable at times Hammer can be, especially for someone starting out. Makes me angry. I figured I was doing the right thing but some small detail I was overlooking, like not addressing the$basetexture or not putting the files in the right place.
And I did consider it was some problem on the model folders side but because GCFScape or VTFedit couldn't open those files for me to check I figured "well, it can't be that then, that would just over-complicate things."

But, apparently it is that so. And my only fault is believing it be as straight-forward as it is with retexturing custom models.

And yeah. Would like help. I do have other programs like Blender if that is used in model compiling.

8. ### aaTumbolisu　I ⌄ I

Messages:
951
Positive Ratings:
937
Here's what the process basically looks like:
1. Extract .mdl and all the other files with their weird file extensions to the same folder. This can be anywhere, even your desktop.
2. Drag the .mdl into crowbar and decompile.
3. Edit the .qc file that has been generated. different name, model path, material path, and skin
4. Drag the .qc file into crowbar and compile.
If you need further instructions, I would like to do this in a chat (steam, discord) instead of the forums.

• Thanks x 1
9. ### Mystic MonkeyL4: Comfortable Member

Messages:
181
Positive Ratings:
18
May take awhile for me to fully figure out, but thank you for helping me with this.

10. ### Mystic MonkeyL4: Comfortable Member

Messages:
181
Positive Ratings:
18
I'd say I made a bit of process than yesturday. They're no longer default textures but instead purple/black missing textures. I've yet to figure out how to fix this but still kind of glad how far I got.

Problem is I'm sure I'm doing it right but still not coming through.
In my Team Fortress 2\tf\models\Mystic_Monkey thats where the .mdl, .vtx and .vvd files are. The .qc, .smd and _anim folders are in the decompile folder.
In my Team Fortress 2\tf\materials\models\Mystic_Monkey folder:
I also made sure the _reference.smd files had their triangles named for my models.

Heres a picture: http://www.tiikoni.com/tis/view/?id=a2a8e64
It appears that the model has found it's textures but not sure what to do with it.

But if it's best to help me over Steam than here, my account is http://steamcommunity.com/profiles/76561198034988670

11. ### aaTumbolisu　I ⌄ I

Messages:
951
Positive Ratings:
937
Well you seem to have figured most things out yourself already. The only problem here is that the model can't find the material that is specified within the SMD, aka the original name of the material. To fix this, you need to use $renamematerial. I have never used that parameter myself, and the VDC says that it works weirdly with$texturegroup. There's also some excess garbage from decompiling, so this is how I would make the QC:

Code:
$ModelName "mystic_monkey\bannerFlag.mdl"$Body "body" "bannerflag_reference.smd"

$SurfaceProp "default"$CDMaterials "models\mystic_monkey"

$texturegroup skinfamilies { { "bannerflag_sonic" "[original material name]" } { "bannerflag_egg" "bannerflag_egg" } }$renamematerial "[original material name]" "bannerflag_sonic"

$Sequence "ref" "bannerflag_anims\ref.smd"  12. ### aaTumbolisu I ⌄ I Messages: 951 Positive Ratings: 937 Sorry for double posting, but I noticed that you are specifieing a normalmap in your material. I'm asuming that you are simply copying the original model's normalmap. If that is the case, you do not need to ACTUALLY make a copy of it. Simple reference the original normalmap. Materials and their textures do not need to be in the same folder! Most people don't seem to realize this, considering the game is stuffed with countless examples of the same texture existing up to 10 times instead of ever being reused. 13. ### Mystic MonkeyL4: Comfortable Member Messages: 181 Positive Ratings: 18 Do you mean the bannerflag_reference.smd file? Because I've already readdressed the "triangles" for my model. Or shouldn't I? It still ending up checkered, but I am starting to see the logic in the coding. May require me to recheck my .vtf files to make sure. You mean models/props_medieval/pendant_flag/bannerFlag_C_normal instead of models/mystic_monkey/bannerFlag_C_normal? Yeah, that would make much more sense now that I think about it. I think I'm starting to see the error, just yet to figure out how to change it right. Last edited: Jan 23, 2017 14. ### Mystic MonkeyL4: Comfortable Member Messages: 181 Positive Ratings: 18 The models are still not recognising the textures, but this is what I worked out so far:$renamematerial "[original material name]" "bannerflag_sonic" doesn't help because I've already changed the _reference.smd files to respond to the new materials. In doing so it was confusing it a bit with it believing there was a "bannerflag_sonic_sonic" material. The compiler believes there are three.

From my texture files I deleted the TF2 default bannerflag files incase that was causing the confusion but it still seems a bit confused. (The originals are still in my addon folder so I can easily recover copies.)

O maybe I do need \$renamematerial "bannerflag_c" "bannerflag_sonic" and rename the _reference triangles bannerflag_c as that was the original default TF2 .vtf it was catered for?

I feel like the cause is some minor overlooked detail.

15. ### aaTumbolisu　I ⌄ I

Messages:
951
Positive Ratings:
937
All this renaming stuff seems so weird that I would just do something I know for sure works: Import into Blender, change material name in there, export again. This also gives you the oppotunity to fix any smoothing errors from decompiling.
I have now added you on Steam. I would be ready to do all of this for you as it's just getting increasingly complicated for something this simple.

Tags: