Talk:Compiling a model: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
No edit summary
Line 32: Line 32:
EXCEPTION_ACCESS_VIOLATION I suspect that message has nothing to do with shadowlod. It' doesn't matter how I write the shadowlod line and it's brackets, or if I delete it entirely, the message does not go away. [[User:Camaron|Camaron]] 07:24, 10 Jun 2007 (PDT)
EXCEPTION_ACCESS_VIOLATION I suspect that message has nothing to do with shadowlod. It' doesn't matter how I write the shadowlod line and it's brackets, or if I delete it entirely, the message does not go away. [[User:Camaron|Camaron]] 07:24, 10 Jun 2007 (PDT)
::I also have this problem. I'm not sure if it's related to the recent SDK update for me or not. I was never using shadowlod to begin with.--[[User:TheDistur|TheDistur]] 12:20, 10 Nov 2007 (PST)
::I also have this problem. I'm not sure if it's related to the recent SDK update for me or not. I was never using shadowlod to begin with.--[[User:TheDistur|TheDistur]] 12:20, 10 Nov 2007 (PST)
For EXCEPTION_ACCESS_VIOLATION, try compiling with the hlmv.exe running --[[User:Xteven.xenderson|Steve Henderson]] 07:01, 24 Dec 2007 (PST)

Revision as of 08:01, 24 December 2007

What happens if you want to make a model for your own mod? This article says nothing about making models for your own models in your own mod except for models in cstrike or hl2mp etc.

--Mflux 22:23, 13 Jul 2006 (PDT)

If you want to follow the 'file structure etiquette' (see Source SDK Files and Directory Structure.) you would use C:\Program Files\Valve\Steam\SteamApps\SourceMods\mod_game_directory\modelsrc ... if there isn't a modelsrc folder there already, just create one. So what you should have is:
SteamApps\SourceMods\mod_game_directory\modelsrc\your.SMD
           "           "               "        \your.QC
SteamApps\SourceMods\mod_game_directory\materialsrc\models\your.TGA
           "           "               "          "       \your.VMT
SteamApps\username\sourcesdk\bin\ep1\bin\Studiomdl
           "           "            "   \Vtex
SteamApps\username\sourcesdk\bin\orangebox\bin\Studiomdl
           "           "               "      \Vtex
However, to me it seems more convenient to use a single desktop folder for 'temporary' files (TGA, SMD, QC) and Shortcuts to the compilers (Studiomdl & Vtex, or StudioCompiler) instead of spreading them all over. eg
Desktop\Source1Modelling\your.SMD
   "      "       "     \your.QC
   "      "       "     \your.TGA
   "      "       "     \your.VMT
   "      "       "     \Shortcut_to_ep1_Studiomdl
   "      "       "     \Shortcut_to_ep1_Vtex
The important thing is that the final, compiled MDL, VMT and VTFs go in the correct game_directory folders, which the compilers will do automatically if your SDK Tools -> Current Game is set to whichever game you're compiling for. Beeswax 07:34, 11 Nov 2007 (PST)

What are important -

  • Put .smd files and .qc files in a same directory.
  • To write .mdl into your mod directory, set Current Game to your mod, or use -game option pointing to your game directory.
Note you have made your Mod using Mod Wizard, you'll get your mod source directory with modelsrc and a .bat invoking studiomdl for your mod. I usually use this studiomdl.bat(which has -game option) to compile my mod models. I export .smd files from XSI, write the .qc in the same directory, then drag .qc into the .bat file - then I can get my .mdl. (If there is no error present!) --n-neko 01:43, 1 Dec 2006 (PST)

EXCEPTION_ACCESS_VIOLATION I suspect that message has nothing to do with shadowlod. It' doesn't matter how I write the shadowlod line and it's brackets, or if I delete it entirely, the message does not go away. Camaron 07:24, 10 Jun 2007 (PDT)

I also have this problem. I'm not sure if it's related to the recent SDK update for me or not. I was never using shadowlod to begin with.--TheDistur 12:20, 10 Nov 2007 (PST)

For EXCEPTION_ACCESS_VIOLATION, try compiling with the hlmv.exe running --Steve Henderson 07:01, 24 Dec 2007 (PST)