[DS]

Originally Posted by ajstorey915 ##### Sys_Error: Host_Error: IDLLFunctions::DLLInit returned false

I've not been able to reproduce this on 10.7 (or even 10.6).

However, I did start getting a crash that I don't think is related. I've updated the packages linked in the first post with a fix for that. It might be worth giving that a try.

If that still doesn't work, make sure you've got a recent copy of the engine binaries extracted (the bin directory). Depending on which Steam option you're using (A or B) either make sure the CS:S client has been run recently or extract a fresh set of files from the "multiplayer ob mac binaries" GCF file.

[redacted]

I'm also getting the same error, trying with option A, all I get is,

./srcds_run -game cstrike -console +map de_dust2
Auto detecting CPU
Using OSX binary.
Server will auto-restart if there is a crash.
Using breakpad minidump system
Using breakpad crash handler

Console initialized.
Game.dll loaded for "Counter-Strike: Source"
Host_Error: IDLLFunctions:LLInit returned false.


Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
found breakpad via in process memory: '/Applications/Steam.app/Contents/MacOS/osx32/../Frameworks/Breakpad.framework/Versions/A/Resources'
Installing breakpad crash handler

##### Sys_Error: Host_Error: IDLLFunctions:LLInit returned false.
./srcds_run: line 376: 17970 Bus error $HL_CMD

[DS]

For Steam options A or B, you need to add -steam to the command line.

[Peterpants]

I'm trying out option A, and getting the following:

~/library/Application Support/Steam/SteamApps/xxxxxxxx/team fortress 2 $ ./srcds_run -game tf +map ctf_2fort -steam
Auto detecting CPU
Using OSX binary.
Server will auto-restart if there is a crash.
Failed to get steam client engine interface!
Add "-debug" to the ./srcds_run command line to generate a debug.log to help with solving this problem
Mon Oct 31 16:31:28 CDT 2011: Server restart in 10 seconds
^CMon Oct 31 16:31:31 CDT 2011: Server Quit

Anything significant changed over the past couple months?

I'm running OS X 10.7.2 with both Steam.app and SteamApps installed in their usual places.

I'll move on to option C next, but I figured I'd ask. Thanks so much for putting so much work into this!

[DS]

Peterpants: Thanks for bringing this to my attention. The packages in the first post have been updated with a fix for this.

[Peterpants]

Fantastic! Works like a charm. Thank you!

[Peterpants]

So here's an odd one. Using method A, again, the TF2 server would advertise itself as game "tf" but with the game id set to 310 (in the udp server browser packet I found in a few places hex 36 01, representing 0x136 = 310), not 440 (0x1b8 or b8 01 in the packet) as it should be. As such, TF2 clients could not connect to it, being told they had the wrong game.

I found the ASCII string "310" in srcds_osx, and on a lark changed those three bytes to "440" and voila! TF2 works now.


Thought I'd report what I found, in case it was useful.

[DS]

The reason 310 is being used is because that's the appid for the Source Dedicated Server tool on Steam. Setting it to 440 (or whatever the game id is) prevents the game client from running at the same time since Steam thinks it's already running. I guess this doesn't matter if you only care about running the server anyways, but some people like myself want to be be to run both for testing plugins or something.

That said, I was pretty sure connecting to the server was working before, but I guess something must have changed. I'll have to look into this more. Thanks for mentioning it!

[DS]

It looks like I was able to come up with a solution more quickly than I anticipated. Packages have been updated once again. You should be able to run both the server and the client at the same time if you wish, but the correct appid should now be there as well.

There don't seem to be very many users of this, so I'm sorry if it seems like you're a guinea pig. Thanks again for telling me about it!

[leekaiwei]

Can this server be accessed outside of the LAN?