-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Material #39
Comments
Hiya!
So if your material in your map is called "tex_concrete.vmt" located in the "custom" folder ( I guess it's a little unintuitive since you're placing your custom content directly into the "tf" folder instead of a separate custom content folder somewhere. There's nothing wrong with that, but it makes this folder thing a little strange :D This is something that I want to fix with #8, but unfortunately I've been dealing with a bunch of health issues the past couple months and haven't had the chance to get it done. Let me know if this works for you! |
thank you I will try it out, good luck with the health issues |
I guess I'm still confused, what should my full file structure be? my materials need to be in materials folder for hammer to load them, do I copy the files to another folder? do I put custom_content inside tf? |
or do I add custom_content inside tf/materials. I think that's what this is saying. I suppose there's no reason hammer wouldn't recursively load folders |
alright I figured it out after re-reading. gotta keep my file structure where I have tf/materials/custom and add the tf folder. my bad |
I can't find any documentation on this so I opened an issue. Basically I added a custom texture to Hammer by putting vmf and vtf files in materials/custom of tf2. It works just fine in Hammer. But once I try to run this program, it says Missing Material. I tried adding those textures by the folder, by making a vpk, and by a folder of the raw png files. How do I add these custom textures?
![image](https://user-images.githubusercontent.com/8770485/212780699-ab7477d2-8689-4c87-a04b-c100a1a6fed9.png)
The text was updated successfully, but these errors were encountered: