K
Kallex
Guest
Hello!
I finally got my HL2 modding project going; got the environment set up for Team Foundation Server for proper source code branching, made modifications to get the environment to compile on VS 2005 and did proof-of-contest testing for allowing calls to .NET managed code from HL2 engine.
I have the debugging working (followed the Wiki instructions on that as well), but the problem is that now I realise for some reason my mod does not start as multiplayer properly.
Basically it starts as single player. When I give the "map <some map name>" command through console it loads up the map as some sort of single player mode.
If I use (or let Steam use) the default client.dll and server.dll, the game starts normally as multiplayer. No other changes to the mod.
Starting as single player causes also bunch of errors and in the end the weapon selection and other hud seems to be not working properly.
Now this might be related to VS 2005 build; I have to go on to test fresh mod with VS 2003.
I'm sorry to run such a problem after succesfully finally getting the project going, hopefully there is some trivial fix to this.
Br,
Kalle
I finally got my HL2 modding project going; got the environment set up for Team Foundation Server for proper source code branching, made modifications to get the environment to compile on VS 2005 and did proof-of-contest testing for allowing calls to .NET managed code from HL2 engine.
I have the debugging working (followed the Wiki instructions on that as well), but the problem is that now I realise for some reason my mod does not start as multiplayer properly.
Basically it starts as single player. When I give the "map <some map name>" command through console it loads up the map as some sort of single player mode.
If I use (or let Steam use) the default client.dll and server.dll, the game starts normally as multiplayer. No other changes to the mod.
Starting as single player causes also bunch of errors and in the end the weapon selection and other hud seems to be not working properly.
Now this might be related to VS 2005 build; I have to go on to test fresh mod with VS 2003.
I'm sorry to run such a problem after succesfully finally getting the project going, hopefully there is some trivial fix to this.
Br,
Kalle
