1. Forums
  2. Discord
  3. About Mapcore
  4. Patreon Supporters
  • Login
  • Register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • More Options
  1. Mapcore
  2. Discussions
  3. Level Design

Model Problems (Source)

  • Quakis
  • March 29, 2008 at 12:34 PM
  • Quakis
    • March 29, 2008 at 12:34 PM
    • #1

    This is driving me mad, and everytime I think I'm getting somewhere, I run into another problem. Basically, compiling my models and writing the VMT works fine when the model is located in, "mysourcemod\models" and the material is found in "mysourcemod\materials\models\"

    However, when the model is in, "mysourcemod\models\folder1\folder2" and the material is in, "mysourcemod\materials\models\folder1\folder2" the model won't work with either the model or material. These DO work with the above settings.

    I realised it had something to do with compiling the model, so I tweaked the QC file a bit and when I compile it, the model is now found in, "mysourcemod\models\folder1\folder2" which is exactly what I wanted. I now put the materials back into, "mysourcemod\materials\models\folder1\folder2". Upon loading the model in HLMV or Hammer, all I get is a pink/black checker texture. The VMT is written correctly. THE TEXTURE WORKED WHEN THE DIRECTORY STRUCTURE WAS LIKE MY FIRST PARAGRAPH.

    I don't know what I'm doing wrong. No filename/directory/vmt spelling errors. And yes, there is a reason for the folder structures. Any help or ideas would be good. This is really unmotivating to work with.

    VMT FILE CONTENTS: qcratea.vmt

    "VertexLitGeneric"

    {

    "$baseTexture" "models/folder1/folder2/qcratea"

    "$model" "1"

    "$surfaceprop" "metal"

    }

    DIRECTORY STRUCTURES:

    models: mysourcemod\models\folder1\folder2

    materials: mysourcemod\materials\models\folder1\folder2

  • hessi
    • March 29, 2008 at 1:00 PM
    • #2

    post your QC file plz

  • e-freak
    • March 29, 2008 at 1:03 PM
    • #3

    How did you compile your VTF and is it placed correctly?

    Second: Take MoM (Model Modifier - a tool by Jodokus [Download]) and check for the linkage in the MDL. It might occur that the converter corrupts your filelinks.

  • R_Yell
    • March 29, 2008 at 1:05 PM
    • #4

    Hmm, check the path in $cdmaterials is correct.

  • e-freak
    • March 29, 2008 at 2:48 PM
    • #5

    OK, i just tried to compile some things my self. I ran into the very same problem. The SMD-File saves the texture name it uses in your modeling software or just says: "Material". If you use MoM you can alter the "Texture" Name. Just overtype the current value with your new VMT Filename and you are good to go.

  • Quakis
    • March 29, 2008 at 3:47 PM
    • #6
    Quote from R_Yell

    Hmm, check the path in $cdmaterials is correct.

    I just tweaked it (below) and the pink/black checkers just got smaller this time.

    Quote from hessi

    post your QC file plz

    $modelname folder1/folder2/qcratea.mdl

    $cdmaterials "models\folder1\folder2"

    $scale 8

    $staticprop

    $surfaceprop "metal"

    $body studio "qcratea.smd"

    $sequence idle "qcratea_idle.smd" fps 1

    $collisionmodel "qcratea_phys.smd"

    Quote from e-freak

    How did you compile your VTF and is it placed correctly?

    VTF plugin for Photoshop. And the VTF is placed in the same directory as the VMT.

    Quote from e-freak

    Second: Take MoM (Model Modifier - a tool by Jodokus [Download]) and check for the linkage in the MDL. It might occur that the converter corrupts your filelinks.(...)

    OK, i just tried to compile some things my self. I ran into the very same problem. The SMD-File saves the texture name it uses in your modeling software or just says: "Material". If you use MoM you can alter the "Texture" Name. Just overtype the current value with your new VMT Filename and you are good to go.

    Just checked it and the file structures are correct. But I already used a hex editor to check this several times before. The texture name is also the same name is used in my software, and all of that is also correct. The only difference that did anything was tweaking $CDMATERIALS in the QC file as explained above.

  • hessi
    • March 29, 2008 at 4:03 PM
    • #7

    open "qcratea.smd" with notepad or what ever and check if the triangles use the correct texture name too. probably something with the SMD export went wrong!

  • Quakis
    • March 29, 2008 at 4:11 PM
    • #8
    Quote from hessi

    open "qcratea.smd" with notepad or what ever and check if the triangles use the correct texture name too. probably something with the SMD export went wrong!

    Checked them and they're also correct. =(

  • Quakis
    • March 30, 2008 at 2:30 AM
    • #9

    I don't know what I did, but I think it was the way I saved the VTF file. Something so simple cause such a hassle. Either that or because it's so late I'm dreaming. Maybe I'll know for deffinite when I wake up and see this post. Jeez... Thanks to those who helped!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login
Discord

The Mapcore Discord is our lively IRC channel of the 2000s reborn. Chat about level design, gaming, and more.

Latest Posts

  1. Tangerine

    Harry Poster
    July 18, 2026 at 11:10 AM
  2. Any of the old guard still around? D:

    Warby
    July 12, 2026 at 8:23 PM
  3. About our archived forums

    Thrik
    June 30, 2026 at 2:12 PM
  4. Mapcore Discord

    mason_fan123
    June 24, 2026 at 8:52 PM
  5. [CS2] Valley

    Serialmapper
    June 22, 2026 at 11:56 AM
  6. Free Music / SFX Resource - Over 2500 Tracks

    Eric Matyas
    June 18, 2026 at 12:32 PM
  7. Pango [WIP]

    Elowen
    June 11, 2026 at 10:13 AM
  8. [CS2] Dvina

    Jeremy Rivera
    June 11, 2026 at 10:03 AM
  9. Bridges 2.0 by NEXSIDE, MAP SHOWCASE. ( Steam Workshop )

    MrTrane18
    June 1, 2026 at 7:46 PM
  10. Classic Maps Reborn For CS2

    SillySpaceCat
    May 31, 2026 at 10:33 PM
  1. Privacy Policy
  2. Contact
Powered by WoltLab Suite™