And, last but not least, we have a winner. Process Explorer knows all. Stick this in a batch file, and modify to reflect your paths. You're welcome.
D: cd d:\Steam\steamapps\spektre1\sourcesdk\bin\orangebox\ "d:\steam\steamapps\spektre1\sourcesdk\bin\orangebox\bin\hammer.exe" -allowdebug -game "d:\steam\steamapps\SourceMods\destiny" Hammer must be started with a working directory as shown, must be passed the -game argument, otherwise it freaks out about missing resources. After I tried this, I'm no longer having any complaints from hammer. Runs like a champ. On Thu, Jul 1, 2010 at 8:30 AM, Spektre <spekt...@gmail.com> wrote: > After that, you should be golden. >> > > I apologize for spamming. There's more to it than that. I know this has > also been answered a hundred times as well. > There's something else being passed to hammer when you start it from the > launcher. More than just the environment paths. Hammer will still tend to > freak out in a number of other wierd ways too, even with the paths. I have > SDK launcher open, and I checked that the vars are set, and Hammer opens, > but on map load complains about: > "Failed to load the default scheme file. The map views may be missing some > visual elements." Fairly accurate. I get purple checkerboard on prop models > in the 2D views, but it renders fine in 3D. Unusual. Your mileage may vary, > of course. I'd expect some people have seen other bugs. I remember cases > where it wouldn't render wireframes right in the past. > I'm curious if anyone has a way of tracing what the launcher is passing as > data/arguments when Hammer is executed? Anyone know of a way to trace that? > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlmappers
