Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've had this type of crash many times, to the point its pretty much guaranteed to occur on any given play-thru, along with the Time Roll-Back you described. I notice the time resets to whatever the sandbox starting time is. And this means all the loot, corpses, and anything you did after the last save point is gone.
There's quite a few crash reports on TIS forums pertaining to the AMD issues... Not sure if this is part of that issue or not. Or whether is its more connected to Gamepad use, which I am using along with the B42.x W.I.P. aiming system.
car locations seem to get updated when you park?
zed status may be updated on killed?
Protip: quit to menu occasionally to save the game state. Especially when staying in one spot for a long time, doing *important stuffz*
Yep.. im on an AMD as well... and getting the crashes on 0.2 starting pop... maybe a few dozen but definitely less than 100 which should be like nothing for this game. Odd thing is, these hard crashes sometimes indicate nothing in the console log except the last thing you did... (ie, No Stack Trace) Other times it will point to the PZBullet64.dll... and other times another dll (cant remember atm)
B41 in comparison was very forgiving... I can't say that it ever Forcibly Ejected you from the game with a Time Reset Penalty... at least not that I can remember. It basically kept running, and gave you the lua error (redbox).... Which in most cases, one could troubleshoot. Difference here is, sometimes it just Ejects you with nothing in the log... and all you have to go off of is the last thing you did... which in my case for the most recent pair of crashes was "Aim and Pan"