Talk:Source SDK Bugs

Any indication on when we will be getting an updated codebase~?
This isn't really a bug, or bug-related, but I thought I'd point out that the flag model for DoD:S has submodels for the US Army Flag, the Wehrmacht Flag, and the good ol' Union Jack... makes one wonder. --Bwmathis 17:44, 22 Nov 2005 (PST)

Brits were in the game for a while but got cut. --TomEdwards 08:41, 23 Nov 2005 (PST)

vvis.exe - Unable To Locate Component

(Posting this in Talk 'cause it may just be I'm an idiot...)

The Beta SDK seems to have broken my cheap and cheerful map compilation batch files - vbsp will run fine, but vvis and vrad come up with 'Unable to Locate Component: This application has failed to start because Steam.dll was not found' error messages.

Here's one of my batch files:

set mapdir=c:\Documents and Settings\Adam Foster\HL2

"%sourcesdk%\bin\vbsp" -low -nolinuxdata "%mapdir%\%1.vmf"
"%sourcesdk%\bin\vvis" -low "%mapdir%\%1.bsp"
"%sourcesdk%\bin\vrad" -low "%mapdir%\%1.bsp"

copy "%mapdir%\%1.bsp" "%vproject%\maps"

I can compile maps through Hammer without problems (beyond the usual "Hammer being an awful front-end for compiling maps" bug and a new "tries copying into a non-existent directory at the end" issue) so I'm a bit puzzled as to what's going on. Am I doing something blatantly wrong here? ;-) --Cargo Cult _{(info, talk)} 14:01, 23 Nov 2005 (PST)

Don't you need either a -ldr, -hdr, or -both option on vvis and/or vrad now? I might have read something like that somewhere. —Maven ^(talk) 14:09, 23 Nov 2005 (PST)

Added it to vrad (vvis came up with a parameter usage list instead of its error!) but to no effect. Here's what I get when vvis runs, for example:

C:\Documents and Settings\Adam Foster\HL2>"c:\steam\steamapps\BALEETED!\sourcesdk\bin\vvis" -low "c:\Documents and Settings\Adam Foster\HL2\metastasis_2.bsp"

Valve Software - vvis.exe (Sep 7 2005)

Can't load c:\steam\steamapps\DELETED\sourcesdk\bin\filesystem_steam.dll.Can't load c:\steam\steamapps\DELETED\sourcesdk\bin\filesystem_steam.dll.

... Then it exits. Same for vrad. As I said, vbsp runs fine... :-/ --Cargo Cult _{(info, talk)} 14:26, 23 Nov 2005 (PST)

The only other thing I can think of is to run it in Hammer once, then copy the command line it uses. —Maven ^(talk) 14:34, 23 Nov 2005 (PST)

Tried that - I suspect there's some PATH weirdness or something going on. I've tried running vvis from the sourcesdk\bin directory, but it comes up with the can't-find-Steam.dll error message whenever I start it with some valid parameters...

Hang on, this is new: I now get the following when I try running vbsp:

SteamStartup() failed: SteamStartup(0xf,0x0012E8A8) failed with error 1: The registry is in use by another process, timeout expired - argh!

Make sure you do not have an old steam.dll somewhere in your path and/or Steam directory. This sounds like it's running the incorrect steam.dll.

Neither -hdr or -ldr are required options. There are no required compile options -- if they were required, they wouldn't be options. The default is LDR-only. --JeffLane 16:54, 23 Nov 2005 (PST)

I've just got the one Steam.dll, in C:\Steam, but I do have numerous FileSystem_Steam.dll files. There's one in C:\Steam\bin and another in C:\SteamApps\username\sourcesdk\bin - they're of different sizes (216kB for the former, 204kB for the latter) so my best guess is that these two are conflicting somehow. I tried temporarily replacing the C:\Steam\bin one with the SDK version, but on restarting Steam the system saw what I was up to and downloaded and replaced it with a 'proper' version. Heh! --Cargo Cult _{(info, talk)} 17:09, 23 Nov 2005 (PST)

Multiple Filesystem_steam.dll files is normal. You can also try deleting your /Steam/ClientRegistry.blob and restart Steam. You may have to Reinstall the Source SDK installation. If these don't work you may have to re-install Steam from scratch, though you can attempt to re-install while keeping your current .GCF files.

Sections

Issues with the hammer tools seem to be interchangeable between General Issues and 3D/2D View issues. Maybe there should be a "Hammer Tool Issues" section? It's difficult, looking through the entire bugs list just to see if a bug you've spotted hasn't already been reported. --Demented 09:23, 24 Nov 2005 (PST)