Another thing to note about this is that even loading a save file via the 'Continue' option crashed while loading.this happened to me twice thus far, and it will most likely happen again soon. This has been happening to me in ACT IV several times (I'd say it's my 7th SAVE CRASH now in Arx alone). THE CRASHING chance becomes evident when saving has been initiated.the tell-tale sign is the slowdown that occurs during the saving process 2 or 3 seconds later, the software will crash completely, resulting in nothing saved. The game frequently crashes (65% chance to crash each attempt) during the saving process (this absolutely includes auto-saving), which results in all unsaved progress lost, and this REALLY HURTS the player especially after long difficult battles that you've barely won by the skin of your teeth or after taking a long time customizing character builds. PLEASE USE THIS LINK TO SEE AN IMAGE OF MY DETAILED ORIGINAL POST BEFORE I REALIZED UBBCode was DISABLED HERE -> <- (Zoom in 100% with magnifying glass for full clarity)ĪCT I - Overall smooth experience in Fort Joy, no crashing.ĪCT II - Some significant slowdown in bustling areas as well as longer game load times in Reaper's Coast game only crashed maybe once here.ĪCT III - Smoother experience and faster game load times in Nameless Isle than in Reaper's Coast game only crashed maybe once here.ĪCT IV - The longest game load times in this version, especially in Arx, slowdown (both visual and audio) is even more prevalent than ever, and saving your game takes much longer than ever before, and with that comes a SERIOUS risk: I have been playing for well over 100 hours (despite my save file time data being stuck at "Fort Joy Beach - 4h59m" ) and I'm currently close to the end of ACT IV. I would first and foremost like to thank everyone involved the great feat of bringing Divinity: Original Sin 2 to the Nintendo Switch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |