Quote from Freeman|TR on August 1, 2015, 11:36 am

CamBen wrote:

Also, in model viewer or the hammer model browser click the tickbox "wireframe". If your mesh shows up in wireframe mode but not regular mode, you probably used the wrong type of shader on your textures and the model itself is fine.

If it doesn't appear, it's a model issue.

Let me check it out! Thanks!

Quote from josepezdj on August 2, 2015, 5:09 am

OK, I asked you to post ALL files, including the material files... I wanted to check out what material files you prepared and the coherence inside your reference.smd file, but this way I can't.

Anyways, it's weird inside your ref.smd file:

This is the only really weird thing I found in your files. The .QC file, as mentioned before, didn't seem to be the problem... Here inside the reference.smd file you usually find actual material files: "whatever.VMT", "whatever_02.VMT", etc.

Nevertheless, I checked inside your compiled model file (board.mdl) to see what the compiler did, and found this:

This could mean that, despite your weird ref.smd file, the compiler made it so that your model could be looking for the following 3 material files:

- default.vmt
- material.vmt
- danger.vmt

So I made those material files and the corresponding texture files (I simply made 3 plain colours: orange, yellow and pink):

- default.vtf
- material.vtf
- danger.vtf

And placed them into materials/models/props_custom.

And it worked:

SO... your model file seem to have been compiled correctly... All you have to do is to have those 3 material files inside materials/models/prop_custom/.

2nd Approach

I also used a different approach: I replaced those 3 material references inside your ref.smd file by the following ones:

- board_mat_01.vmt
- board_mat_02.vmt
- board_mat_03.vmt

Now, check out in the below image, this is closer to how it should always have looked like:

This way it is referencing to actual material files (.VMT), and therefore after compiling the model and placing the 3 materials files and the 3 texture files (.VTF) in the folder models/props_custom/, it works fine and the model is compiled with the correct materials and paths inside:

This is how it looks like in-game:

I'm attaching all the files (model + materials) of this 2nd approach.

I'm also attaching the material files that your current model is looking for inside your materials/models/props_custom/ folder so that you can put them in place and check how your model file does also work out.

I hope you get all this.

Cheers!

Quote from Freeman|TR on August 8, 2015, 11:09 am

josepezdj wrote:

[url=http://posCheers!

Wow! Thanks again for your detailed analysis!
So the problem is clear now. I realize that, when doing the material work in blender, I actually made a .png picture using mspaint, and imported that into blender. I also used built-in material tool to make another several material with plain colors black, pink, and wooden brown. I thought that it will work out easily. But I didn't know I need .vmt and .vtf material files.
So I guess I need to learn how to make vmt and vtf too. First the QC. Then these two stuff. This perhaps gonna be the last map I do with hammer. Other engines just outsmart source 1...
Many thanks to your effort! I learned a lot from you. Good luck!