Game spams /SaveEvents2 during Freelancer gameplay

[moonysolari]

Reported a few times. The game spams /SaveEvents2 during Freelancer gameplay. This is observed more often after exiting the level and before the mission end scene. This bug has happened before on v4 during normal gameplay but I don't know how it was resolved or by whom. I have not been able to reproduce this bug.

[RDIL]

Typically this is caused by the server failing to acknowledge an event has occurred, and as a result the client gets mad and keeps sending it until it does.

[LennardF1989]

I see this happen randomly at times. Perhaps we should introduce logic to make sure every event is always acknowledged, even if we don't use it. There is currently some logic in place to escape the event handler early on, and I'm pretty sure this causes this issue from time to time. Can't hurt to verify.

[moonysolari]

This has not happened to me at all. I think we should add more debug output around events so that we at least know what event the game is sending when it happens.

[moonysolari]

Closing this as completed by #190 and #191. Reopen if the problem reappears.

[Kronzky]

It's still happening fairly regularly, and in all kinds on game modes (Freelance, Exclusive Targets, etc.).
I don't see anything specific triggering it, but the error is always "The \"path\" argument must be of type string. Received undefined", after some time of playing (half an hour or so).
Sometimes it recovers, quite often it doesn't.

I've attached the logs of three crashes.
crashes.zip

[AnthonyFuller]

Close the Peacock server. Then open Tools.cmd, press enter, then send the DEBUG_PROFILE.zip found in the Peacock directory.

[moonysolari]

I've attached the logs of three crashes.

I think your problem was caused by a cracked version of Peacock.

[Kronzky]

I think your problem was caused by a cracked version of Peacock.

The thing is, I'm trying to run this on a machine that has no Internet at all.
The stock Peacock is still connecting to the official servers at startup, so that won't work.

And I guess this error is caused by subsequent connection attempts during the game (which isn't an issue if you're connected anyway, but for a real offline machine this is causing problems).

I understand if you don't want to do support for a "cracked" versions, but to me it seems that still needing online access for running the game sort-of contradicts the purpose of this tool...

[AnthonyFuller]

It needs it once on first connect. And to launch the game anyway, you need to be online for Epic (and possibly even Steam). We are not supporting cracked versions of Peacock as the issue doesn't even exist on "official" versions of Peacock.

I'm locking this to contributors only as it's just pointless trying to diagnose an issue, that in our eyes, doesn't exist.