Issues with changing decks in System Shock multiplayer. - by PSiKoTiCSiLVeR
PSiKoTiCSiLVeR on 21/2/2009 at 20:28
Hey there! I've been playing some SS2 multiplayer again with my brother Yusef and we've been encountering the same bug for quite some time. When playing any mod that changes the mission files, we experience crashes upon entering new decks such as going from Medsci to Engineering (Pop's and Sec mod), or from training to Medsci (Alya mod).
We've gone through quite a lot of troubleshooting, using Vanilla SS2 as a reference and we think we've narrowed it down to a specific issue: some decks may not be outfitted with multiple spawn points and thus the 2 players spawn inside each other causing a crash.
Here is a list of mods in which we have encountered this error:
- Populism's difficulty 1.0-2.5
- Secmod 2.7
- Alya Mod 1.0
Here is the SS2 installation procedure we have used:
- Installed SS2 from a retail final edition ISO
- Installed Kolya's SS2tool. Originally we used 1.0 but have changed versions everytime a new one is released, we are now up to 2.7. When installing SStool, we selected ALL TWEAKS. We have experimented using only certain tweaks with no positive results.
- Fix resolution
- Installed ModManager 0.2, later we used 0.3 and now 0.4.48
- Activate SHTUP beta6
- Activate Rebirth
- Activate Difficulty / Enhancement mod (and if needed, as with Sec mod, a rebirth patch)
- Start the game, a complete run of Medsci or a straight run for the Engineering Maintenance shaft
We do NOT encounter this problem in single player, even with all these mods activated.
Are we doing something horribly wrong?
Nameless Voice on 21/2/2009 at 20:53
Lack of multiplayer "landing points" will just cause all players to appear in the same spot, it won't trigger a crash.
Having no multiplayer spawn points will just make death permanent without a QBRM active.
SecMod certainly has valid landing and spawn points for multiplayer on every map, as I'd assume any mod based on the original missions would.
PSiKoTiCSiLVeR on 21/2/2009 at 22:51
Oh ok, I was just putting forth a hypothesis, since I don't mod for SS2 I am glad you could explain this to me.
Do you have any idea why this may be happening? Mostly it crashes going from Medsci to Engineering, as soon as we spawn in engineering both players get errors with our games.
Nameless Voice on 21/2/2009 at 23:37
You're certain that all players are using the same mods and have the same version of the eng1.mis file?
PSiKoTiCSiLVeR on 22/2/2009 at 01:22
Absolutely positive. I made a master copy and he copied it to his computer over the network.
We're playing the exact same copy over a local area network, non himachi. Operating systems were XP and XP, but now are XP / Vista. We had the same problem on each combo.
C0rtexReaver on 2/3/2009 at 04:57
Quote Posted by PSiKoTiCSiLVeR
We're playing the exact same copy over a local area network, non himachi. Operating systems were XP and XP, but now are XP / Vista. We had the same problem on each combo.
Could be as simple as a file locking issue. Try two local copies of the game.
-CR
PSiKoTiCSiLVeR on 10/3/2009 at 10:37
I should have phrased that differently, my bad. They are two local copies, one was simply copied from the other computer to make sure we had the exact same installation; we have two CD's but we're trying to rule out everything possible. We were trying to play the different copies over our local area network without Himachi.
Today we retried Alya mod, but used the .mis files from the Unified and Revamped mission mod. This fixed our problems with the Alya mod, however it will not work with any other mods due to incompatibilities with their respective gamesys files not supporting the new Medsci doors.
It feels like most of these mods are not tailored for multiplayer, is it possible someone missed something, or there's a setting that we could change in these mods to get them working for multiplayer?
