collapse

* Notice

Important notice (31 July): We have recently recovered from a nearly two day downtime due to an attack. No data was lost or stolen but the server has been reinstalled as a precaution. Please let us know if you encounter any issues. We apologise for the unacceptable inconvenience. Please read here for more information.

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Crash After Finishing Park Quest/Meeting Jack  (Read 3248 times)

Offline GlassDeviant

  • Neonate
  • **
  • Posts: 78
  • Reputation: +1/-3
Re: Crash After Finishing Park Quest/Meeting Jack
« Reply #15 on: December 28, 2013, 06:47:24 pm »
I have a funny feeling that this comes back to the crappy autosave feature (a problem in a lot of games, not just VtMB). Autosave often interrupts other scripts in various games, especially older ones running on newer multicore computers, causing all sorts of odd things to happen. Have you tried disabling autosave completely in the config files? You can also try setting processor affinity for the VtMB executable file so that it runs on only one CPU core. Of course neither option will fix corrupted saves.

 

SimplePortal 2.3.7 © 2008-2020, SimplePortal