![]() ![]() Fixed an issue on slower video cards where terrain displayed in large quantities, or with rapid draws (like clicking rapidly around the mini-map), could cause the game to unload the terrain system, resulting in large amounts of checkerboards. Fixed an issue where the Workboat model exhibited graphical corruption. Fixed multiple issues with the pathfinder that was causing units to exhibit inefficient movement choices. Fixed an issue causing Denmarks trait (allows disembarked units to have an extra move after landing) to not function correctly. Could also cause modded saves to be corrupted or crash on load. Fixed an issue causing mods to constantly reload each time the user visited the mods area. Please see our note at the bottom of the change-list on how modders can correct this. NOTE: The cause of this could also exist in existing mods. Fixed an issue that was causing the pop-up queue to stop displaying in-game pop-ups until the game was reloaded. Fixed an issue where the DX9 version of the game could become unstable or crash if started multiple times in the same session. On certain video cards, after playing for a short amount of time (or across a number of short games), the game could exhibit strange graphical behavior (rapidly blinking graphics, terrain unloading, etc.), which could eventually lead to a driver failure or hang. A city-strike or ranged unit could cause the game to crash when playing in the DX9 version, mainly in full-screen, but could occur in windowed mode as well. There still may be a risk of crashes when changing modded resources/features/improvements/natural wonders.-ĝX9 Range-strike crash. The current test results are listed bellow.Īll test was made with default resources/features/improvements/natural wonders with Crash safe and Safe mode checkboxes turned on. So now I'm running long tests to find the functions which might cause the crashes. In general, it is pretty safe to make changes early in-game on the first turn (except the impassable-to-passable and water to lands and vice versa). It was not changed with the mod updates and if you start to get crashes after some mod update it does not related to this update in 99% of the cases it just your game went to the stage where the significant map updates are not safe anymore. The game was not designed to use these functions in mid-game after the players and AI appears on the map and this is the main reason for the crashes. ![]() These functions are used by the game on the map generation stage before the game starts. Mod uses game testing and map generation functions to make map changes. ![]() The only way is to load the save game made before the problematic change was done but the crash may happen 400+ turns later and you literally can lose all progress. The problem with crashes is that they happen on some turn later in-game and it is not possible to continue the game because it will repeat on that turn no matter what you do. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |