Project Reality Forums

After the latest update i keep getting crash after like 30 minutes of game time, i reinstalled the whole game but it does not seem to help.

I was trying to find a reason but i always do something different in the game so i am not sure what is causing it exactly.

Running windows 10

This is the message that i get every single time.

COOP? What map and layer? if its custom map/layer, what factions are there? Did you mod something?

Suchar wrote:COOP? What map and layer? if its custom map/layer, what factions are there? Did you mod something?

No mods, coop.
It happened on pavlosk bay STD and omaha beach STD so far.
VG Coop server.

Ight i am running this bad boy for a while and seems like the bug just got scared ima keep eyes out because i am sure it will happen again.

Alright so i had the crash again with the program running in the background and there is no crashlog nothing.

There should be a .dmp file next to prodcump.exe.

Suchar wrote:There should be a .dmp file next to prodcump.exe.

Yeah i was reading the forums post but nothing, i just had the crash again and this time i checked if i was running it properly, the game crashes with getting the same error and the prodcump just exits without leaving and .dpm file in the folder.

What server are you getting this error on? Is it always VG? If so, could you try to reproduce it on another server?
We suspect it might be related to network issues between you and the server.

Mats391 wrote:What server are you getting this error on? Is it always VG? If so, could you try to reproduce it on another server?
We suspect it might be related to network issues between you and the server.

It may be possible, i could try a different server, VG is having some issues after the update i can tell the end screen is insanely long after the latest update, but they are working on it.

LangMaster wrote:It may be possible, i could try a different server, VG is having some issues after the update i can tell the end screen is insanely long after the latest update, but they are working on it.

If you need help with that, feel free to make a separate thread. Nothing in the update should have caused extended loading times

Mats391 wrote:If you need help with that, feel free to make a separate thread. Nothing in the update should have caused extended loading times

Yeah i don't think that is my job to do, i am not that up close to VG, Semler will definitely check it out though he is a bit sick lately, but i believe in him.

The end screen was usually long after we played around 60 maps already, now there is 8 in history and you can literally take a shower.

Though i still think this error is somewhat my problem, i was questioning players and i am not the only one who gets it, though some players who play alot does not even had this once.

SO it happened again and it happened to multiple people at once, some people stayed in the server some were kicked with a same error message.

now it happened on VG Coop Server Adak - Large

After lots of trying, Suchar managed to reproduce this crash and was able to generate a dump for it. On first look it seems to be some issue with path finding. We are still investigating the dump and will fix it as soon as possible.

Mats391 wrote:After lots of trying, Suchar managed to reproduce this crash and was able to generate a dump for it. On first look it seems to be some issue with path finding. We are still investigating the dump and will fix it as soon as possible.

Pathfinding was the server crash, I didn't check the new dump yet.

VG PR COOP will be able to turn on ProCdumps again once we get our new server box live. Dumps can pile up, can come back in a day to 5GB+ of files, and don't want to say how low our storage overhead is on our old server box... SSD's were brand new when we got it, a very small RAID-1 setup that is fairly at capacity. New server has plenty of space on a new NVMe RAID-1 setup, and will be up and running all our servers within a week.

This issue seems to be related to player entering vehicles on spawn. (objectTemplate.setEnterOnSpawn) We still have no real idea why this happens and especially why it just started happening recently. However we were able to fix the crash client side and it will be part of the next update.