
BETRAYAL AT KRONDOR PRINT PC
Windows 7 64-bit PC with NVIDIA 650 GTX graphics card: Game crashed during the intro, despite trying several different compatibility modes and setting the CPU affinity to a single core (you can avoid this by skipping the intro by pressing "Esc" twice after clicking "NEW" in the main menu). Windows 7 64-bit laptop with Intel HD3000 integrated graphics: Tested with various saves from different chapters, and ran several of the chapter intros and conclusions - everything appeared to work fine. Windows XP laptop with ATI Radion Express integrated graphics: Game worked fine from start to finish and all chapter intros and conclusions ran without a problem. this is with GOG version "setup_betrayal_in_antara_2.1.0.19.exe") I can only provide evidence from playing the game on the following PCs: "F5" alters the level of darkness at night - if the scenery turns pink at nighttime, keep pressing F5 until the pink disappears. The day/night cycle runs correctly in the gog version of the game. The game includes a day/night cycle, which ran too fast when I first tried to play it years ago using a non-gog version. However, if you want to, you can successfully add it to your game by using the following workaround:

The temple south of Ligano is part of one unimportant side-quest and I completed the game without ever visiting it. Repeat this process as you make more saves, that way you can always return to any point in the game if you need to by swapping the current save folder with an older version. When you have filled the 20 or so save slots, copy and paste the entire folder to another location. Locate the save folder (in Windows 7 this was "User/AppData/Roaming/Sierra/Betrayal in Antara").
BETRAYAL AT KRONDOR PRINT PATCH
Getting trapped in one patch of swamp and being unable to get out.Īs with all games with limited save slots, my advice is to save regularly as follows: One random crash to desk-top in the entire 57 hours. No, my play-through was remarkably bug-free and the only small issues I encountered were: It took approximately 57 hours, including probably the majority of side-quests. Yes, I've just successfully completed the game.


There appears to be some uncertainty concerning the state of this game, so I thought I'd try to answer some of those queries.
