Difference between revisions of "Talk:Configuring the Source SDK for Dreamball"

From Valve Developer Community
Jump to: navigation, search
Line 1: Line 1:
Either something is screwed up that I can't find, or the SDK configuration you list on this page is messed up.  I can compile and run the sdk maps, but textures that come with DreamBall show up as black in the game.  For example, in the sdk_checkpoints.vmf map, your custom dev textures show up as black in the game.  The ball shows up black when I test my map as well.  Only the skybox and the brush with the hl2 orange dev texture are not black. The problem is originating in the compile process, because VBSP.exe is giving errors that it can't find a few textures.  So it appears that the compile tools can't see the textures in the Dreamball\Materials\ folder for some reason.  These textures show up fine in Hammer though.  Does anyone know what the problem is?  I wanted to play with mapping for this, but I can't seem to solve this problem :(   
+
I'm am having an SDK problem relating to this game.  I can compile and run the sdk maps, but textures that come with DreamBall show up as black in the game.  For example, in the map '''sdk_checkpoints.vmf''', the red and blue dev textures show up as black in the game.  The ball shows up black when I testrun this map as well.  Only the skybox and the brush with the orange dev texture are not black. Does anyone know what the problem is?  I wanted to play with mapping for this, but I can't seem to solve this problem :(   
 +
<br><br>'''Solution:'''<br>
 +
I finally figured out the problem, so I'll just post the solution here in case anyone else finds themselves in a similar situation.  I am running the compile tools outside of Hammer from another program.  I had steam make a desktop shortcut for DreamBall, so I could look at its properties to see how to launch the game.  I copied the command line arguments from that shortcut into the setting in the compile manager program that tells it how to launch this particular game.  This was the problem.  The shortcut that Steam made launched the game like this: <br>
 +
 
 +
"''-gameidlaunch 11957139809064976602 -game "f:\games\steam\SteamApps\SourceMods\Dreamball''"<br>
 +
 
 +
I tried compiling in Hammer and observed that Hammer launches the game like this:<br>
 +
 
 +
"''-applaunch 218 -game "f:\games\steam\SteamApps\SourceMods\Dreamball''"<br>
 +
 
 +
So I went into that compile manager program I'm using and changed the setting to make it launch using the -applaunch approach above instead of the -gameidlaunch approach.  And with that, the textures are now showing up properly in the game.  I'm not sure why the first launch method shown above causes this problem, but it does.
 
<br>--[[User:Font38|Font38]] 05:14, 17 September 2009 (UTC)
 
<br>--[[User:Font38|Font38]] 05:14, 17 September 2009 (UTC)

Revision as of 06:29, 17 September 2009

I'm am having an SDK problem relating to this game. I can compile and run the sdk maps, but textures that come with DreamBall show up as black in the game. For example, in the map sdk_checkpoints.vmf, the red and blue dev textures show up as black in the game. The ball shows up black when I testrun this map as well. Only the skybox and the brush with the orange dev texture are not black. Does anyone know what the problem is? I wanted to play with mapping for this, but I can't seem to solve this problem :(

Solution:
I finally figured out the problem, so I'll just post the solution here in case anyone else finds themselves in a similar situation. I am running the compile tools outside of Hammer from another program. I had steam make a desktop shortcut for DreamBall, so I could look at its properties to see how to launch the game. I copied the command line arguments from that shortcut into the setting in the compile manager program that tells it how to launch this particular game. This was the problem. The shortcut that Steam made launched the game like this:

"-gameidlaunch 11957139809064976602 -game "f:\games\steam\SteamApps\SourceMods\Dreamball"

I tried compiling in Hammer and observed that Hammer launches the game like this:

"-applaunch 218 -game "f:\games\steam\SteamApps\SourceMods\Dreamball"

So I went into that compile manager program I'm using and changed the setting to make it launch using the -applaunch approach above instead of the -gameidlaunch approach. And with that, the textures are now showing up properly in the game. I'm not sure why the first launch method shown above causes this problem, but it does.
--Font38 05:14, 17 September 2009 (UTC)