moroccupy.blogg.se

Generally, when debugging you want to narrow down the possible causes for a crash. Very useful for crashes during the loading process, to see when the game crashed. Prints the time it takes for the various loading steps to complete, and the tick interval. Prints the system information EU4 is loaded on. Prints errors in the /Europa Universalis IV/common/countries files. Very useful for discovering which file may be causing a crash. Prints the completion of setup loading for each part of the process. Prints the internal commands sent by the player in multiplayer. Prints the internal commands received by the player in multiplayer. Prints the profiling output if using the profiling. Prints the session info for the current session. Useful for crashes during the loading process, to see when the game crashed. Prints the graphical errors relating to positions. Useful when the crash is due to a specific action. Prints the actions taken by countries in game. Prints the internal commands uses by the player and AI. Currently only prints the hexadecimal address, making this file fairly useless. Prints the stacktrace when the game crashes to desktop.

The error.log from the second previous game launch. The error.log from the previous game launch. Many errors can be ignored, although almost all errors relating to files in the common folder should be fixed. Prints the country selection of the player and then the Starting AI line. To enable full error logging, add the -debug launch command via Set Launch Options in Steam. These are overwritten every time the game is started. The game stores various log files in your EU4 user folder: ( \\Documents\Paradox Interactive\Europa Universalis IV\logs\). When launching the game the following steps occur: By becoming an observer, you can let the game run without your input, making it easier to detect issues that occur irregularly. The observe is useful when you want to test the stability of your mod during gameplay. It also makes it very easy to setup test scenarios without introducing wayward code within the mod itself. The run command is very useful for testing effects without having to reload the game. Typically this is done via the in-game console with commands such as event, observe and run. Performing testing is vital to debugging a mod. These errors are almost always printed to the error.log. Non-fatal error occur when the game encountered invalid data or broken syntax. Typically these errors occur during the loading process or when a specific action is taken in game. When fatal errors occur, an exception will be printed to the exceptions.log. In general there are two kinds of errors: fatal and non-fatal.įatal errors occur when the game cannot load a vital piece of data and cannot operate without it present.