-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pump related crash on the Unstable version #61
Comments
|
Let me look into this. I'm not sure why it's failing to load. |
I can't reproduce this; @Imouto-Kaede can you send me the full log if that run/instance? |
launch dedicated server with the current unstable build, happens everytime you launch it |
|
Hey @Torca2001 , It might be related to this error from 2 weeks ago; Also, I did follow the steps. All turning on the generator does is kick me from the server in relation to the above error. |
You have to launch the luadedicatedserver.bat to see the full error, you won't see it on the client or if you host the server using the in-game hosting menu |
I always test with the Dedicated Server, that screenshot was from the dedicated server console. This is why I asked for full logs. I just also tested with the unstable workshop version and that's how I got the above error. Not saying the error @Torca2001 post isn't happening, but I can't reproduce it on my side. I got kicked after turning on the Diesel Generator and it's because of the above error. This produced the error that @Imouto-Kaede is having: @Torca2001 This error is the one from a couple of weeks ago in dev chat where it wouldn't be registered. Let me see if I can fix it. |
|
Oh thought it was similar due to both being message misalignment. I have managed to reproduce the issue but the Central Pump has no extra networking information attached to it so not sure how it would misalign the network message |
Ah ok so the server isn't loading the C# and then the client is desyncing itself expecting more data it seems |
Should be fixed by PR #70 . Will leave this open until testing is completed. |
Unable to reproduce in latest build, pr should also fix possible abnormal behaviour. |
Addressed in #71 . |
Steps to reproduce:
The error message looks as follows:
Error while reading a message from server.
Exception thrown while reading segment EntityEvent at position 32.
Inner exception: Message byte position incorrect after reading an event for the entity "Central Water Pump (ID: 3)" (ID 3). The previous entity was "Barotrauma.Hull" (ID 1887) Read 160 bits, expected message length was 8 bits.
at Barotrauma.Networking.ClientEntityEventManager.Read(ServerNetSegment type, IReadMessage msg, Single sendingTime)
at Barotrauma.Networking.GameClient.<>c__DisplayClass116_0.b__0(ServerNetSegment segment, IReadMessage inc)
at Barotrauma.Networking.SegmentTableReader`1.Read(IReadMessage msg, SegmentDataReader segmentDataReader, ExceptionHandler exceptionHandler)
I've tested a bit and it seems to be an issue relating specifically to mechtrauma. (Loading it with just the dependencies still causes the crash)
The ship I loaded only consisted of an inner wall, hull, spawnpoint, a Water Pump T1, a Central Water Pump and a Water Drain.
Loading in a vanilla submarine with the mod active doesn't cause a crash.
The text was updated successfully, but these errors were encountered: