Page 1 of 1

[Kovarex] [14.21] Crash after desync.

Posted: Thu Dec 22, 2016 9:13 pm
by MrDoomah
Hello,

I've had a desync twice now and both times i've crashed after reconnecting. Here's the log

Re: [14.21] Crash after desync.

Posted: Thu Dec 22, 2016 9:28 pm
by Loewchen
As always please post a link to the desync report and the .ziped mod folder, see my signature on where to find the report.

Re: [14.21] Crash after desync.

Posted: Thu Dec 22, 2016 10:00 pm
by MrDoomah
Please note that not only I desync, but also crash instantly after reconnecting.

Re: [14.21] Crash after desync.

Posted: Thu Dec 22, 2016 11:59 pm
by Loewchen
MrDoomah wrote:Please note that not only I desync, but also crash instantly after reconnecting.
The crash is worth looking into, just a desync with mods would not be. We still need the mod-folder!

Re: [14.21] Crash after desync.

Posted: Fri Dec 23, 2016 1:03 pm
by MrDoomah
here are the mods.

Re: [Kovarex] [14.21] Crash after desync.

Posted: Fri Jan 13, 2017 6:55 pm
by MrDoomah
It happened again, same modpack.

Desyncs only seem to happen when updating the power grid, when plaing a power pole to power inserters to be exact, but that might just be my imagination.

desync report: https://www.dropbox.com/s/zo7r4cgxsa2nb ... 0.zip?dl=0

Re: [Kovarex] [14.21] Crash after desync.

Posted: Fri Jan 13, 2017 7:01 pm
by Rseding91
MrDoomah wrote:It happened again, same modpack.

Desyncs only seem to happen when updating the power grid, when plaing a power pole to power inserters to be exact, but that might just be my imagination.

desync report: https://www.dropbox.com/s/zo7r4cgxsa2nb ... 0.zip?dl=0
The desync is almost 100% caused by one of the mods you're using. The crash is still on our to-do to fix.

Re: [Kovarex] [14.21] Crash after desync.

Posted: Fri Jan 13, 2017 8:38 pm
by MrDoomah
So do I keep posting the desync reports and logfiles? I just happened again, but if these files don't help you then I won't bother to upload them.

Re: [Kovarex] [14.21] Crash after desync.

Posted: Thu May 04, 2017 1:30 pm
by kovarex
This should have been fixed in the 0.15