I can upload a new version with that included, if it'd help. I suggest using the ShockEd Toolkit version of the editor if you want to try patching one.I'm not sure why it would be easier to track in ShockEd - perhaps because of the errorlog.txt that the game writes to when it crashes? I actually wrote something for Thief that logs crashes to errorlog.txt in the same way that Dromed does, and stupidly forgot to include it in the.
Those would be easier to track if you made a version of ShockEd with this patch applied (having a version of ShockEd with this patch would be useful anyway). If you can connect to each other without the patch, do you have the same crash there? If not, can you tell me exactly how to reproduce the error if you can get it to happen again? I can't tell what's going on from that error report exactly since it looks like it tried to access memory outside of the game (and probably my DLL too).
I just tried to get that to happen on my LAN however, and was able to get all the way up to the upgrade machines on MedSci1 with no issues. I did make a few changes since we ran through those levels and only tested it again briefly, so it's definitely possible that I made a mistake somewhere. vort and I were able to play through a couple levels past MedSci2 with no issues last night. I forgot to copy the memory address, but this time it was a read operation and not a write operation that failed.Hmm. The first time, we had the ureleased version of SecMod installed, and got this error after climbing up the ladder right at the start:Īfter that, I thought maybe the mod could be the cause of the crash, so we tried again with a vanilla install, and got another crash in roughly the same place. Just tried this twice with TF, it crashed near the start of Medsci1 in both cases. This will probably not be fixed, since it's a fairly small issue. IP addresses are not displayed in the game staging screen for any player other than the host, and the host's internal network IP address will probably be displayed rather than their external one. dll at startup, and connecting to or hosting multiplayer games should be much easier than it was before. The game will automatically load the wrapper. If you are hosting a game and are behind a router, you may need to forward port 5198 in order for others to connect to you.ģ. zip into your System Shock 2 directory, making backups where appropriate if you'd like.Ģ. Stability and latency should also be improved under DirectPlay 8. dll for System Shock 2 that converts the old DirectPlay 4 calls that are made for the game's multiplayer support into DirectPlay 8 ones, thereby making multiplayer playable under Windows Vista and eliminating the need to use Hamachi to connect to a host that is behind a router.
0 kommentar(er)
