Ошибка hoi4 error log

Hoi 4 ошибка error log

you are right. my game was broken. but somehow it didn’t fixed by integrity check on steam.
manual deleting and re-installing solved the problem. thank you very much. :☺

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Bubbas,
Hi. Im having the same issue. I have done the following per Paradox’s support folks.
-Uninstalled via Steam and removed any other folders left for HOI4 or Paradox.
-Reinstalled the game and verified game integrity.
-Restarted the game via Steam. Launcher comes up. I did windowed view, and disabled all mods and still get an error.

System Log:
[19:02:28][systemsettings.cpp:71]: CPU Model: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
[19:02:28][systemsettings.cpp:72]: CPU Speed: 1800MHz
[19:02:28][systemsettings.cpp:73]: CPU Physical Cores: 4
[19:02:28][systemsettings.cpp:74]: CPU Logical Cores: 8
[19:02:28][systemsettings.cpp:75]: System Memory: 8116
[19:02:28][systemsettings.cpp:76]: OS: Windows 10 x86_64
[19:02:28][systemsettings.cpp:77]: OS Language: en

Here is my pdx_settings.txt

«Graphics»= <
«display_index»= <
version=0
value=»0″
>
«display_mode»= <
version=0
value=»windowed»
>
«fullscreen_resolution»= <
version=0
value=»2736×1824″
>
«vsync»= <
version=0
enabled=yes
>
«windowed_resolution»= <
version=0
value=»1920×1080″
>
>
«System»= <
«language»= <
version=0
value=»l_english»
>
>

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Bubbas,
Hi. Im having the same issue. I have done the following per Paradox’s support folks.
-Uninstalled via Steam and removed any other folders left for HOI4 or Paradox.
-Reinstalled the game and verified game integrity.
-Restarted the game via Steam. Launcher comes up. I did windowed view, and disabled all mods and still get an error.

System Log:
[19:02:28][systemsettings.cpp:71]: CPU Model: Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
[19:02:28][systemsettings.cpp:72]: CPU Speed: 1800MHz
[19:02:28][systemsettings.cpp:73]: CPU Physical Cores: 4
[19:02:28][systemsettings.cpp:74]: CPU Logical Cores: 8
[19:02:28][systemsettings.cpp:75]: System Memory: 8116
[19:02:28][systemsettings.cpp:76]: OS: Windows 10 x86_64
[19:02:28][systemsettings.cpp:77]: OS Language: en

Here is my pdx_settings.txt

«Graphics»= <
«display_index»= <
version=0
value=»0″
>
«display_mode»= <
version=0
value=»windowed»
>
«fullscreen_resolution»= <
version=0
value=»2736×1824″
>
«vsync»= <
version=0
enabled=yes
>
«windowed_resolution»= <
version=0
value=»1920×1080″
>
>
«System»= <
«language»= <
version=0
value=»l_english»
>
>

Источник

Hoi 4 ошибка error log

Hi
My Germany ironman save keeps crashing randomly like 2-6+ days after I load and it is really annoying as I was quite far into the game.
Can anyone help me understand the exception log below and if there is a solution? There was no error.log generated.
Any help much appreciated, thanks!

Application: HOI4
Version: Husky v1.9.0
Date/Time: 2020-03-06 23:55:21

Caught signal 11 (SIGSEGV)

Original Stack Trace:
2 . 0x0000000154114a00 0x0 + 5705386496
3 hoi4 0x00000001000e3d0b hoi4 + 933131
4 hoi4 0x00000001000e37b8 hoi4 + 931768
5 hoi4 0x00000001004783b0 hoi4 + 4686768
6 hoi4 0x0000000100478d72 hoi4 + 4689266
7 hoi4 0x0000000100582f48 hoi4 + 5779272
8 hoi4 0x000000010058393d hoi4 + 5781821
9 hoi4 0x00000001005872a0 hoi4 + 5796512
10 hoi4 0x00000001003a3181 hoi4 + 3813761
11 hoi4 0x00000001003a25d8 hoi4 + 3810776
12 hoi4 0x000000010062ac7e hoi4 + 6466686
13 hoi4 0x000000010110cb21 _ZN7luabind6detail19garbage_collector_sINS0_14class_registryEE5applyEP9lua_State + 456449
14 hoi4 0x000000010035c3a2 hoi4 + 3523490
15 hoi4 0x00000001003e1c5e hoi4 + 4070494
16 hoi4 0x00000001010a0528 _ZN7luabind6detail19garbage_collector_sINS0_14class_registryEE5applyEP9lua_State + 12552
17 hoi4 0x00000001010a0b91 _ZN7luabind6detail19garbage_collector_sINS0_14class_registryEE5applyEP9lua_State + 14193
18 hoi4 0x0000000100417ca4 hoi4 + 4291748
19 hoi4 0x0000000100007914 hoi4 + 30996
20 . 0x0000000000000003 0x0 + 3

Demangled Stack Trace:
2 . 0x0000000154114a00 0x0 + 5705386496
3 hoi4 0x00000001000e3d0b hoi4 + 933131
4 hoi4 0x00000001000e37b8 hoi4 + 931768
5 hoi4 0x00000001004783b0 hoi4 + 4686768
6 hoi4 0x0000000100478d72 hoi4 + 4689266
7 hoi4 0x0000000100582f48 hoi4 + 5779272
8 hoi4 0x000000010058393d hoi4 + 5781821
9 hoi4 0x00000001005872a0 hoi4 + 5796512
10 hoi4 0x00000001003a3181 hoi4 + 3813761
11 hoi4 0x00000001003a25d8 hoi4 + 3810776
12 hoi4 0x000000010062ac7e hoi4 + 6466686
13 hoi4 0x000000010110cb21 luabind::detail::garbage_collector_s ::apply(lua_State*) + 456449
14 hoi4 0x000000010035c3a2 hoi4 + 3523490
15 hoi4 0x00000001003e1c5e hoi4 + 4070494
16 hoi4 0x00000001010a0528 luabind::detail::garbage_collector_s ::apply(lua_State*) + 12552
17 hoi4 0x00000001010a0b91 luabind::detail::garbage_collector_s ::apply(lua_State*) + 14193
18 hoi4 0x0000000100417ca4 hoi4 + 4291748
19 hoi4 0x0000000100007914 hoi4 + 30996
20 . 0x0000000000000003 0x0 + 3

Источник

Troubleshooting

This is a community maintained wiki. If you spot a mistake then you are welcome to fix it.

Troubleshooting is the identification of the cause of crashes, bugs or other problems.

Содержание

Overview [ править | править код ]

In general, there are two kinds of errors: fatal and non-fatal.

Fatal errors occur when the game cannot load a vital piece of data and cannot operate without it present. This causes a crash to desktop (CTD). When fatal errors occur, an exception will be printed to the exceptions.log. Typically these errors occur during the loading process or when a specific action is taken in-game.

Non-fatal errors occur when the game encountered invalid data or broken syntax. These errors are almost always printed to the error.log.

Testing [ править | править код ]

Performing testing is vital to debugging a mod. Typically this is done via the in-game console with commands.

These are useful console commands for modders:

Log files [ править | править код ]

The game stores various log files in your HOI4 user folder: (Windows: \DocumentsParadox InteractiveHearts of Iron IVlogs , Linux: .local/share/Paradox Interactive/Hearts of Iron IV/logs ). These are overwritten every time the game is started.

To enable full error logging, add the -debug launch command via Set Launch Options in Steam.

Crash data log [ править | править код ]

When the game crashes, it provides information on system settings and what caused it to crash in the user directory’s /Hearts of Iron IV/crashes/ folder. Although most of the time this is not beneficial as to what caused it to crash, the error log could contain clues. However, one important logging mechanism can be additionally turned on:

Adding the -crash_data_log launch command via Launch Options in Steam will also cause the meta.yml file in that folder (Directly within, not in the /logs/ subfolder) to contain the last read line of code before crashing, as well as turning on the debug mode. This slows down the game by a significant amount, so it shouldn’t be used outside of crash debugging. If the last read line of the file given is the last line in the file, it’s rather likely the game crashed on the next read file instead, which is quite difficult to locate. In some cases, the game can grant a script instead of a file, such as a savefile or client_ping.
This can appear like LastRead: map/supply_nodes.txt (727) (Where the number represents the line of the file that was last read before the crash occurred) or LastRead: client_ping (1) .

Note that while -crash_data_log enables debug mode, not all benefits of the launch option get applied by default and require using both launch options. For example, edits to files indexed during the main menu loading will not get automatically loaded, requiring a console command usage to get reloaded instead. However, -crash_data_log’s debug does include the game loading into the main menu with map errors, the nudge being available for selection, and the debug information when hovering over a province or a country.

Common crash causes [ править | править код ]

A variety of crash types are caused by recklessly unloading folders with replace_path, leading to the game detecting there not being any database entries of a certain type. It’s best practice to port over generic files to the mod if overwriting a folder in entirety for this reason, as well as to avoid unintuitive errors.

In case of a different crash, note that if a file is completely empty, the game may skip reading it in entirety. As such, the same crash may display a different file if the one in this list is empty.
It’s best to completely clean the error log before trying to find a crash, as some errors may appear innocuous while still crashing the game.

If the last read file proves useless, it’s possible to temporarily remove files from the mod and slowly re-add them to find the exact cause; upon finding the cause folder, it should be adjusted accordingly. A sort of binary search can be used by adding/removing the files large chunks at the time. replace_paths can be removed aside from essential ones: history/states/ and map/strategicregions . Note that both *.mod files need to be edited for replace_paths to apply.

This list is non-exhaustive: There are more potential crashes, and any given file or script can have more causes that are not outlined in the list. This has been broken up into sections on when they happen for easier navigation. The file provided is the file marked as last read by the crash data log.

Main menu loading [ править | править код ]

• common/countries/cosmetic.txt – Caused by a complete overwriting of common/national_focus/ or common/continuous_focus/ .
• map/rocketsites.txt – Caused by a complete overwriting of history/states/ or common/unit_leader/ . As there are no «generic files» for states, one should be created manually instead.
• common/national_focus/*.txt – This crash, granted that it’s the last line of the last file in the folder, can be caused by a focus tree using a shared_focus = my_focus argument, specifying a shared focus that does not exist.
• gfx/models/supply/railroad.shader – Caused by the filesize of the provinces bitmap exceeding 40 MiB in size, which the engine cannot handle.
• history/general/*.txt / history/countries/*.txt / map/rocketsites.txt (In order in which they’d appear with replace_paths to the previous ones) — One of the states within the mod has a victory_points = < . >definition that attempts to assign victory points to a province that does not exist within the game.

During country selection [ править | править код ]

This also includes the loading after a country has been selected, but it’s not yet possible to play.

• set_controller – This crash typically happens when trying to select a country in a bookmark if the country doesn’t have a valid capital defined within its /Hearts of Iron IV/history/countries/TAG*.txt file. The game uses the capital in order to determine what portion of the map to zoom onto, and not getting one is unexpected.
• savegame.hoi4 (takes on the name of a savefile, not necessarily one that exists right now) – Caused by there being a large quantity of countries defined without there being any dynamic countries. The exact amount of countries that the game can handle is not a consistent number, usually falling in the range of 40–80. Typically caused by a reckless overwriting of common/country_tags .
• history/units/filename.txt – One of the naval orders of battle in the mod has a carrier defined with airwings directly inside, as was done in 1.11 and earlier. Adjust the orders of battle in the mod as needed. Note that the file shown as the last read one is not necessarily the one that crashes the game.
• history/units/filename.txt / map/railways.txt – Caused by a country having a division template, yet not finding any possible /Hearts of Iron IV/common/ai_templates entry to use to expand on the template. The exact file/script in question depends on when the country obtains the division template: an order of battle (which’ll be last read) or another history file (leading to railways).
• map/supply_nodes.txt or map/railways.txt – This crash is most commonly caused by the specified building types being placed on invalid provinces, such as those that are not located in states. This crash occurs both when trying to open the supply menu in nudge or when trying to start a single player game. This can be corrected by emptying the files in question and optionally creating a proper definition of the files, either manually or via nudge.
• tutorial/tutorial.txt – This crash is caused by the tutorial file being erroneous. This can be represented as a link to an invalid state ID within the file (such as if every base game was erased) or as the file lacking a tutorial = < . >definition of any kind entirely. Replacing the entire file’s contents with tutorial = < >works to solve the crash.

This is also the last file that gets read after the country selection process finishes. If a crash occurs directly afterwards and the game fails to write the file properly, it will land on this one.

Middle of the game [ править | править код ]

• client_ping or hourly_tick – This crash is caused by the in-game AI, which can be seen by turning off the AI using the console. There are several causes for this occurring, including but not limited to:
  • A country has a division template, yet couldn’t find any /Hearts of Iron IV/common/ai_templates entry to use to expand on the template.
  • Any state not having an owner defined in the history file. In general, such states always run unstably, with a lot of actions crashing them, such as right-clicking or attempting to transfer one to a country. One of such actions is attempting an air mission over that state. As the AI is able to use airplanes, they will try to attempt to at least evaluate the value of doing a mission over the state, which results in a crash to desktop.
  • An incomplete map/buildings.txt . The buildings file, alongside building models, is also used for determining into which sea province the naval bases and floating harbours will go out into. This information is necessary when attempting to use any naval base or floating harbour, as the game would have no idea via which province the province connects to the sea otherwise. The game also checks this information when attempting to build a naval base, and if the game attempts to evaluate an invalid naval base definition, the game gets stuck in an infinite loop of attempting to obtain the naval base information, resulting in a CPU/GPU overload and a game crash.

The game can fail to generate floating harbours when validating all states at the same time, so this may require validating each state individually. Comparing the amount of matches for naval_base (typically generated) and floating_harbor in the file can notify if an issue is present in the mod, however not telling where. There are several ways to find which states exactly need to be updated, if that issue is indeed present. For example, regular expression may be used, supported within any advanced text editor, such as Notepad++, Sublime Text, and Visual Studio Code. Turning on regular expression is a separate option within the search and replace menus, so it must be turned on manually. Copy the map/buildings.txt file and operate on that copy, since this process is destructive. First of all, every non-related line can be removed. This can be done by replacing ^d*;(?!(naval_base|floating_harbor)).*(rn|Z) with an empty string (or $1 if the text editor doesn’t support doing so). After this, replacing ^(d+;)naval_base(.*)rn(?s)(.*)(?-s)^1floating_harbor.*rn with $3 will remove a matching pair of floating harbours and naval bases within the same state, however this may only remove 2 lines at a time after the first few initial replacements. In order to speed up the line replacing, a macro can be recorded that does this replace request several times, and this macro would be played back itself. Notepad++ supports executing a macro several times in a row, which can be used here to instantly run it several hundred or thousand times. If, after doing this, pairs still remain, switching the order of naval bases and floating harbours with ^(d+;)floating_harbor(.*)rn(?s)(.*)(?-s)^1naval_base.*rn would detect any floating harbours that are followed by naval bases in the same state rather than the other way around. All lines that would remain after this are naval base definitions that do not have a matching definition within floating harbours or vise versa. For example, if there are 3 naval bases in state 123 and 2 floating harbours, 1 naval base definition in state 123 will remain. This can be used within the nudge to validate the states in question individually.

Additional details [ править | править код ]

A version tracking website, such as [Gitlab] or [Github], can be used to keep track of updates to the code. As such, it can be beneficial to use them and regularly push mod’s updates to them in order to limit the selection of possibly problematic files when trying to debug an issue.

When the game has a major update, it can be important to read the patch notes to fix the newly-appearing errors. For example, the 1.12’s patch notes provide an «Important modding notes» section, which also serves as a check-list of necessary things to fix in the mod in order to avoid a crash. It is also important to avoid overwriting most base game files when possible in order to ease compatibility, though this is not always possible. One folder where it’s incredibly important to do is defines, where an override file is essentially mandatory in order to avoid even minor game updates from introducing crashes.

In case the game crashes on startup, but there’s no obvious reason why in the error log and it’s unknown what was last changed since the last time, the mod could have folders strategically removed. As an example, it is almost always possible to remove the entire /Hearts of Iron IV/common/ folder from the mod without the game crashing, provided debug mode is turned on and there are no replace_paths to the folder.

Источник

• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

This is a community maintained wiki. If you spot a mistake then you are welcome to fix it.

Troubleshooting is the identification of the cause of crashes, bugs or other problems.

Overview[edit | edit source]

In general, there are two kinds of errors: fatal and non-fatal.

Fatal errors occur when the game cannot load a vital piece of data and cannot operate without it present. This causes a crash to desktop (CTD). When fatal errors occur, an exception will be printed to the exceptions.log. Typically these errors occur during the loading process or when a specific action is taken in-game.

Non-fatal errors occur when the game encountered invalid data or broken syntax. These errors are almost always printed to the error.log.

Testing[edit | edit source]

Performing testing is vital to debugging a mod. Typically this is done via the in-game console with commands.

These are useful console commands for modders:

Log files[edit | edit source]

The game stores various log files in your HOI4 user folder: (Windows: \DocumentsParadox InteractiveHearts of Iron IVlogs, Linux: .local/share/Paradox Interactive/Hearts of Iron IV/logs). These are overwritten every time the game is started.

To enable full error logging, add the -debug launch command via Set Launch Options in Steam.

Crash data log[edit | edit source]

When the game crashes, it provides information on system settings and what caused it to crash in the user directory’s /Hearts of Iron IV/crashes/ folder. Although most of the time this is not beneficial as to what caused it to crash, the error log could contain clues. However, one important logging mechanism can be additionally turned on:

Adding the -crash_data_log launch command via Launch Options in Steam will also cause the meta.yml file in that folder (Directly within, not in the /logs/ subfolder) to contain the last read line of code before crashing, as well as turning on the debug mode. This slows down the game by a significant amount, so it shouldn’t be used outside of crash debugging. If the last read line of the file given is the last line in the file, it’s rather likely the game crashed on the next read file instead, which is quite difficult to locate. In some cases, the game can grant a script instead of a file, such as a savefile or client_ping.
This can appear like LastRead: map/supply_nodes.txt (727) (Where the number represents the line of the file that was last read before the crash occurred) or LastRead: client_ping (1).

Note that while -crash_data_log enables debug mode, not all benefits of the launch option get applied by default and require using both launch options. For example, edits to files indexed during the main menu loading will not get automatically loaded, requiring a console command usage to get reloaded instead. However, -crash_data_log’s debug does include the game loading into the main menu with map errors, the nudge being available for selection, and the debug information when hovering over a province or a country.

Common crash causes[edit | edit source]

A variety of crash types are caused by recklessly unloading folders with replace_path, leading to the game detecting there not being any database entries of a certain type. It’s best practice to port over generic files to the mod if overwriting a folder in entirety for this reason, as well as to avoid unintuitive errors.

In case of a different crash, note that if a file is completely empty, the game may skip reading it in entirety. As such, the same crash may display a different file if the one in this list is empty.
It’s best to completely clean the error log before trying to find a crash, as some errors may appear innocuous while still crashing the game.

If the last read file proves useless, it’s possible to temporarily remove files from the mod and slowly re-add them to find the exact cause; upon finding the cause folder, it should be adjusted accordingly. A sort of binary search can be used by adding/removing the files large chunks at the time. replace_paths can be removed aside from essential ones: history/states/ and map/strategicregions. Note that both *.mod files need to be edited for replace_paths to apply.

This list is non-exhaustive: There are more potential crashes, and any given file or script can have more causes that are not outlined in the list. This has been broken up into sections on when they happen for easier navigation. The file provided is the file marked as last read by the crash data log.

Main menu loading[edit | edit source]

• common/countries/cosmetic.txt – Caused by a complete overwriting of common/national_focus/ or common/continuous_focus/.
• map/rocketsites.txt – Caused by a complete overwriting of history/states/ or common/unit_leader/. As there are no «generic files» for states, one should be created manually instead.
• common/national_focus/*.txt – This crash, granted that it’s the last line of the last file in the folder, can be caused by a focus tree using a shared_focus = my_focus argument, specifying a shared focus that does not exist.
• gfx/models/supply/railroad.shader – Caused by the filesize of the provinces bitmap exceeding 40 MiB in size, which the engine cannot handle.
• history/general/*.txt / history/countries/*.txt / map/rocketsites.txt (In order in which they’d appear with replace_paths to the previous ones) — One of the states within the mod has a victory_points = { ... } definition that attempts to assign victory points to a province that does not exist within the game.

During country selection[edit | edit source]

This also includes the loading after a country has been selected, but it’s not yet possible to play.

• set_controller – This crash typically happens when trying to select a country in a bookmark if the country doesn’t have a valid capital defined within its /Hearts of Iron IV/history/countries/TAG*.txt file. The game uses the capital in order to determine what portion of the map to zoom onto, and not getting one is unexpected.
• savegame.hoi4 (takes on the name of a savefile, not necessarily one that exists right now) – Caused by there being a large quantity of countries defined without there being any dynamic countries. The exact amount of countries that the game can handle is not a consistent number, usually falling in the range of 40–80. Typically caused by a reckless overwriting of common/country_tags.
• history/units/filename.txt – One of the naval orders of battle in the mod has a carrier defined with airwings directly inside, as was done in 1.11 and earlier. Adjust the orders of battle in the mod as needed. Note that the file shown as the last read one is not necessarily the one that crashes the game.
• history/units/filename.txt / map/railways.txt – Caused by a country having a division template, yet not finding any possible /Hearts of Iron IV/common/ai_templates entry to use to expand on the template. The exact file/script in question depends on when the country obtains the division template: an order of battle (which’ll be last read) or another history file (leading to railways).
• map/supply_nodes.txt or map/railways.txt – This crash is most commonly caused by the specified building types being placed on invalid provinces, such as those that are not located in states. This crash occurs both when trying to open the supply menu in nudge or when trying to start a single player game. This can be corrected by emptying the files in question and optionally creating a proper definition of the files, either manually or via nudge.
• tutorial/tutorial.txt – This crash is caused by the tutorial file being erroneous. This can be represented as a link to an invalid state ID within the file (such as if every base game was erased) or as the file lacking a tutorial = { ... } definition of any kind entirely. Replacing the entire file’s contents with tutorial = { } works to solve the crash.

This is also the last file that gets read after the country selection process finishes. If a crash occurs directly afterwards and the game fails to write the file properly, it will land on this one.

Middle of the game[edit | edit source]

• client_ping or hourly_tick – This crash is caused by the in-game AI, which can be seen by turning off the AI using the console. There are several causes for this occurring, including but not limited to:
  • A country has a division template, yet couldn’t find any /Hearts of Iron IV/common/ai_templates entry to use to expand on the template.
  • Any state not having an owner defined in the history file. In general, such states always run unstably, with a lot of actions crashing them, such as right-clicking or attempting to transfer one to a country. One of such actions is attempting an air mission over that state. As the AI is able to use airplanes, they will try to attempt to at least evaluate the value of doing a mission over the state, which results in a crash to desktop.
  • An incomplete map/buildings.txt. The buildings file, alongside building models, is also used for determining into which sea province the naval bases and floating harbours will go out into. This information is necessary when attempting to use any naval base or floating harbour, as the game would have no idea via which province the province connects to the sea otherwise. The game also checks this information when attempting to build a naval base, and if the game attempts to evaluate an invalid naval base definition, the game gets stuck in an infinite loop of attempting to obtain the naval base information, resulting in a CPU/GPU overload and a game crash.

The game can fail to generate floating harbours when validating all states at the same time, so this may require validating each state individually. Comparing the amount of matches for naval_base (typically generated) and floating_harbor in the file can notify if an issue is present in the mod, however not telling where. There are several ways to find which states exactly need to be updated, if that issue is indeed present. For example, regular expression may be used, supported within any advanced text editor, such as Notepad++, Sublime Text, and Visual Studio Code. Turning on regular expression is a separate option within the search and replace menus, so it must be turned on manually.

Copy the map/buildings.txt file and operate on that copy, since this process is destructive. First of all, every non-related line can be removed. This can be done by replacing ^d*;(?!(naval_base|floating_harbor)).*(rn|Z) with an empty string (or $1 if the text editor doesn’t support doing so). After this, replacing ^(d+;)naval_base(.*)rn(?s)(.*)(?-s)^1floating_harbor.*rn with $3 will remove a matching pair of floating harbours and naval bases within the same state, however this may only remove 2 lines at a time after the first few initial replacements. In order to speed up the line replacing, a macro can be recorded that does this replace request several times, and this macro would be played back itself. Notepad++ supports executing a macro several times in a row, which can be used here to instantly run it several hundred or thousand times. If, after doing this, pairs still remain, switching the order of naval bases and floating harbours with ^(d+;)floating_harbor(.*)rn(?s)(.*)(?-s)^1naval_base.*rn would detect any floating harbours that are followed by naval bases in the same state rather than the other way around. All lines that would remain after this are naval base definitions that do not have a matching definition within floating harbours or vise versa. For example, if there are 3 naval bases in state 123 and 2 floating harbours, 1 naval base definition in state 123 will remain. This can be used within the nudge to validate the states in question individually.

Additional details[edit | edit source]

A version tracking website, such as [Gitlab] or [Github], can be used to keep track of updates to the code. As such, it can be beneficial to use them and regularly push mod’s updates to them in order to limit the selection of possibly problematic files when trying to debug an issue.

When the game has a major update, it can be important to read the patch notes to fix the newly-appearing errors. For example, the 1.12’s patch notes provide an «Important modding notes» section, which also serves as a check-list of necessary things to fix in the mod in order to avoid a crash. It is also important to avoid overwriting most base game files when possible in order to ease compatibility, though this is not always possible. One folder where it’s incredibly important to do is defines, where an override file is essentially mandatory in order to avoid even minor game updates from introducing crashes.

In case the game crashes on startup, but there’s no obvious reason why in the error log and it’s unknown what was last changed since the last time, the mod could have folders strategically removed. As an example, it is almost always possible to remove the entire /Hearts of Iron IV/common/ folder from the mod without the game crashing, provided debug mode is turned on and there are no replace_paths to the folder.

[19:16:08][texturehandler.cpp:163]: Texture Handler encountered missing texture file: gfx/interface/geks_logo.dds

[19:16:08][texturehandler.cpp:303]: Couldn’t find texture file: gfx/interface/geks_logo.dds.

[19:16:08][texturehandler.cpp:163]: Texture Handler encountered missing texture file: gfx/interface/geks_inv.dds

[19:16:08][texturehandler.cpp:303]: Couldn’t find texture file: gfx/interface/geks_inv.dds.

[19:16:09][bitmapfont.cpp:537]: lineHeight (38) in ‘gfx/fonts/vic_36_cryllic.fnt’ does not match previous fontfiles in font ‘vic_36’

[19:16:09][bitmapfont.cpp:551]: base (28) in ‘gfx/fonts/vic_36_cryllic.fnt’ does not match previous fontfiles in font ‘vic_36’

[19:16:14][texturehandler.cpp:163]: Texture Handler encountered missing texture file: gfx//interface//button_421x34.dds

[19:16:14][texturehandler.cpp:303]: Couldn’t find texture file: gfx//interface//button_421x34.dds.

[19:16:35][pdx_achievements.cpp:640]: Failed to load global statistics, error no: 2

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: friend_in_need

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: time_is_on_our_side

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: canada_first

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: we_will_build_it_in_a_day

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: transport_tycoon

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: destroyer_of_worlds

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: wunderwaffen

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: united_netherlands

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: vive_la_france

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: master_of_war

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: mine_is_bigger_than_yours

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: no_country_for_old_men

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: poland_can_into_space

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: true_blitzkrieg

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: northern_light

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: nobody_expects

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: the_bell_tolls_for_us

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: the_revolution_triumphant

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: once_more_mate

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: forge_of_victory

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: sunset_invasion

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: duce_nukedem

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: operation_sealion

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: one_empire

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: party_like_its_1520

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: med_plutonium

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: montezumas_revenge

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: big_entente

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: new_world_order

[19:16:35][pdx_achievements.cpp:446]: Invalid achievement: vojtek_commander

[19:16:49][texturehandler.cpp:163]: Texture Handler encountered missing texture file: gfx//interface//generic_entry_bg_small_strategicair.dds

[19:16:49][texturehandler.cpp:303]: Couldn’t find texture file: gfx//interface//generic_entry_bg_small_strategicair.dds.

Продолжает вылетать после захода за какую либо страну

Hoi 4 ошибка error log

15 июл. 2020 в 9:39

game crash w/ eror log

https://ufile.io/f/qpb3n
my game were crashing. I did everything. but when I launch the game its crashing.
eror title: failed to load the map
text:some erors are present in the map defition and have been logged to error.log
you might want to disable your mods and try again ✔
if that fails, check the integrity of game files inside steam ✔
if tat fails, try clearing your user directory from launcher ✔
(✔ done)
but they didnt solve the problem I left a link of eror log and picture of eror.
I tried reinstalling hoi4 too (2 times) pls help

Автор сообщения: bubbas:

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

Paradox crash reporter hoi4

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Сообщения 1 – 6 из 6

Автор темы посчитал это сообщение ответом на свой вопрос.

15 июл. 2020 в 14:44

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

15 июл. 2020 в 17:22

thank you I will try

16 июл. 2020 в 4:51

you are right. my game was broken. but somehow it didn’t fixed by integrity check on steam.
manual deleting and re-installing solved the problem. thank you very much. :☺

Автор сообщения: bubbas

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

[HOI4/TNO] 런처 로딩 중 오류 해결 방법

19 июл. 2020 в 10:56

Автор сообщения: bubbas

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Bubbas,
Hi. Im having the same issue. I have done the following per Paradox’s support folks.
-Uninstalled via Steam and removed any other folders left for HOI4 or Paradox.
-Reinstalled the game and verified game integrity.
-Restarted the game via Steam. Launcher comes up. I did windowed view, and disabled all mods and still get an error.

Here is my pdx_settings.txt

«Graphics»= «display_index»= version=0
value=»0″
>
«display_mode»= version=0
value=»windowed»
>
«fullscreen_resolution»= version=0
value=»2736×1824″
>
«vsync»= version=0
enabled=yes
>
«windowed_resolution»= version=0
value=»1920×1080″
>
>
«System»= «language»= version=0
value=»l_english»
>
>

19 июл. 2020 в 14:55

20 июл. 2020 в 7:15

Автор сообщения: Hoot
Автор сообщения: bubbas

Going by the error.log fle you seem to have a corrupt installation, do a clean re-install to fix this.
http://steamcommunity.com/app/394360/discussions/2/1471966894885959849/
Follow the instructions that start with: Procedure to solve point 1º

The important part of the clean re-install is the order of which things are done. Also do not miss the last part about starting the game up and loading in to the main menu once before activating any mods after doing the clean re-install.

Bubbas,
Hi. Im having the same issue. I have done the following per Paradox’s support folks.
-Uninstalled via Steam and removed any other folders left for HOI4 or Paradox.
-Reinstalled the game and verified game integrity.
-Restarted the game via Steam. Launcher comes up. I did windowed view, and disabled all mods and still get an error.

Here is my pdx_settings.txt

«Graphics»= «display_index»= version=0
value=»0″
>
«display_mode»= version=0
value=»windowed»
>
«fullscreen_resolution»= version=0
value=»2736×1824″
>
«vsync»= version=0
enabled=yes
>
«windowed_resolution»= version=0
value=»1920×1080″
>
>
«System»= «language»= version=0
value=»l_english»
>
>
first you have to delete all mods. thats how I solved. if you couldnt find any solution try deleting mods first then uninstall from steam. after that delete remaining folders includes documentary

Источник: steamcommunity.com

Troubleshooting

In general, there are two kinds of errors: fatal and non-fatal.

Fatal errors occur when the game cannot load a vital piece of data and cannot operate without it present. This causes a crash to desktop (CTD). When fatal errors occur, an exception will be printed to the exceptions.log. Typically these errors occur during the loading process or when a specific action is taken in-game.

Non-fatal errors occur when the game encountered invalid data or broken syntax. These errors are almost always printed to the error.log.

Testing [ править | править код ]

Performing testing is vital to debugging a mod. Typically this is done via the in-game console with commands.

These are useful console commands for modders:

Command Usage

Log files [ править | править код ]

The game stores various log files in your HOI4 user folder: (Windows: DocumentsParadox InteractiveHearts of Iron IVlogs , Linux: .local/share/Paradox Interactive/Hearts of Iron IV/logs ). These are overwritten every time the game is started.

To enable full error logging, add the -debug launch command via Set Launch Options in Steam.

File Description Usefulness

Crash data log [ править | править код ]

When the game crashes, it provides information on system settings and what caused it to crash in the user directory’s /Hearts of Iron IV/crashes/ folder. Although most of the time this is not beneficial as to what caused it to crash, the error log could contain clues. However, one important logging mechanism can be additionally turned on:
Adding the -crash_data_log launch command via Launch Options in Steam, will also cause the meta.yml file in that folder to contain the last read line of code before crashing, as well as turning on the debug mode. This slows down the game by a significant amount so it shouldn’t be used outside of crash debugging. If the last read line of the file given is the last line in the file, it’s rather likely the game crashed on the next read file instead, which is quite difficult to locate. In some cases, the game can grant a script instead of a file, such as a savefile or client_ping.

Common crash causes [ править | править код ]

• client_ping or hourly_ping : This crash is caused by the in-game AI, which can be seen by turning off the AI using the console. There are several causes for this occurring, including but not limited to:

• An incomplete map/buildings.txt . The buildings file, alongside building models, is also used for determining into which sea province the naval bases and floating harbours will go out into. This information is necessary when attempting to use any naval base or floating harbour, as the game would have no idea via which province the province connects to the sea otherwise. The game also checks this information when attempting to build a naval base, and if the game attempts to evaluate an invalid naval base definition, the game gets stuck in an infinite loop of attempting to obtain the naval base information, resulting in a CPU/GPU overload and a game crash.
• Any state not having an owner defined in the history file. In general, such states always run unstably, with a lot of actions crashing them, such as right-clicking or attempting to transfer one to a country. One of such actions is attempting an air mission over that state. As the AI is able to use airplanes, they will try to attempt to at least evaluate the value of doing a mission over the state, which results in a crash to desktop.

Additional details [ править | править код ]

A version tracking website, such as [Gitlab] or [Github], can be used to keep track of updates to the code. As such, it can be beneficial to use them and regularly push mod’s updates to them in order to limit the selection of possibly problematic files when trying to debug an issue.

When the game has a major update, it can be important to read the patch notes to fix the newly-appearing errors. For example, the 1.12’s patch notes provide an «Important modding notes» section, which also serves as a check-list of necessary things to fix in the mod in order to avoid a crash. It is also important to avoid overwriting most base game files when possible in order to ease compatibility, though this is not always possible. One folder where it’s incredibly important to do is defines, where an override file is essentially mandatory in order to avoid even minor game updates from introducing crashes.

In case the game crashes on startup, but there’s no obvious reason why in the error log and it’s unknown what was last changed since the last time, the mod could have folders strategically removed. As an example, it is almost always possible to remove the entire /Hearts of Iron IV/common/ folder from the mod without the game crashing, provided debug mode is turned on and there are no replace_paths to the folder.

Источник: Дополнение:
Прописала в параметры запуска steam команду -debug чтоб получить возможности разработчика в игре, но ничего не изменилось кроме выскакивающего блокнота под названием «Error» и такая же надпись «Vanable only for developers». В прошлом вопросе, написать -debug надо было. И ошибка в виде комментария «Vanable only for developers»

3160 просмотров
больше 3 лет назад

Hearts of Iron 4

Может быть вы ввели не правильную команду? Вот тех. список:
-dev
Для включения мод для разработчиков.
-condebug
Для сохранения всех логов консоли в текстовом файле console.log
-nocrashdialog
Для отмены отображения некоторых ошибок(memory could not be read).
-zone #
Для выделения большего объема памяти файлам, таким как autoexec.cfg и т.д.

больше 3 лет назад

В прошлом вопросе, написать -debug надо было. И ошибка в виде комментария «Vanable only for developers» Paul Lera

больше 3 лет назадОтветить

Здравствуйте, поднял ваш вопрос на главной странице — не создавайте пожалуйста одинаковые темы, просто если что дополняйте данное обсуждение новой информацией.

больше 3 лет назад
#privet ya top Gamer in the World
больше 3 лет назадОтветить
Введите ваш ответ
Символов нужно 2
Похожие вопросы
Задать вопрос
Последние ответы
Добрый вечер,одним из самым прибыльным делом в gta
Посмотри в правом нижнем углу ! Там должен быть зн

И да я не умею нормально печатать!
Как убить паучиху с коричневыми сердцами
была такая проблема буквально 3 минуты назад,нашёл

• О нас
• Контакты

• Правила пользования
• Политика конфеденциальности

• Реклама
• Мобильная версия

• Добавить игру
• 160

• GameSubject � 2017 Вопросы и ответы для геймеров
  Игровое сообщество, помощь игрокам

Мы рады всем гостям которые любят провести свое время в онлайн или одиночных играх. У вас случилась беда, и вы не знаете как решить ту или иную ошибку? При заходе в любимую игрушку детства у вас появляется черный экран и вы уже не можете насладится теми ощущениями что испытывали раньше? Бывает такое что при попытке поиграть, любимая сага игры просто не запускается, тогда уже становится очень обидно. Не волнуйтесь, даже если вы думаете что это не поправимо, у нас вам помогут с этим справится.

Спецаильно для наших уважаемых посетителей, мы собираем лучшие советы и рекомендации которые помогут справится с той или иной проблемой. Как мы уже сказали раньше, даже если вы столкнулись с самыми редкими вылетами, даже если при запуске игры процесс находится в задачах но ничего не происходит, мы все равно найдем оптимальное решение которое подойдет каждому. Ах да, мы забыли упомянуть о самом главном, часто любители поиграть в 3D игры сталкиваются с такой ситуацией когда при попытке зайти в игровое приложение, у них просто происходит вылет или крэш на рабочий стол — с этим мы тоже знаем как боротся.

Вы думали что мы умеем только решать различные технические задачи? Нет это не правда, мы можем помочь каждому взрослому парню который решил найти или вспомнить название игры в которую он так любил поиграть в детстве, но забыл как она называется. Ведь наше игровое сообщество явлется прямой системой вопрос-ответ, вам нужно лишь обратится, и мы сразу же вам дадим ответ.

Источник: gamesubject.com

Консольные команды — Hearts of Iron 4

Читы

Автор Maxakow На чтение 7 мин

Что бы открыть окно для ввода консольных команд в Hearts of Iron 4 необходимо нажать: Shift+2, §, ~, `, или ALT+2+1, или Shift+3 — все зависит от раскладки вашей клавиатуры.

Источник: dmagame.ru

Консольные команды Hearts of Iron 4 — чит-коды к игре

И так, консольные команды не работают в онлайн-сессиях. Это сделано для того, чтобы не было преимуществ для игроков.

Скажем так, не все консольные команды работают на обычной версии. Чтобы
Использовать весь пак консольных команд, нам нужно сделать пару действий:

1. Перейти на — C:Program Files (x86)SteamsteamappscommonHearts of Iron IV (обычно здесь).
2. Затем, в данной папке ищем hoi4.exe .
3. Далее, правой кнопкой мыши на hoi4.exe — Отправить → Рабочий стол / Создать ярлык.
4. На рабочем столе, правой кнопкой мыши по ярлыку → Свойства → Ярлык → Объект.
5. В «Объект», в конце строки мы прописываем -debug . Самое главное ничего лишнего не удалить.

Если вы сделали все правильно, можете нажимать на ярлык (не через Steam), у вас откроется игра. В игре у вас не будет доступен онлайн режим.

После данных махинаций, у вас должно быть две игры:

1. Hearts Of Iron IV — Steam версия.
2. HOI4 — Версия для разработчиков / Debug Mode.

Далее, заходим в игру, нажимаем на (~) и все.

Основные консольные команды Hearts of Iron 4

• instantconstruction — мгновенное строительство.
• tdebug — узнать тег любой страны и другую информацию подробно (просто навести курсор на территорию).
• manpower [число] — добавляет указанное количество людских ресурсов (если не указывать количество, вам дадут ровно один миллион).
• pp [число] — добавляет политическую власть (если не указывать число, вам будут добавлять по 999).
• gain_xp — добавляет опыт выбранному лидеру / генералу.
• cp [число] — добавляет командные ресурсы (до 100 очков).
• st [число] — добавляет стабильность (до 100 очков).
• ws [число] — добавляет военную поддержку (до 100 очков).
• allowtraits — позволяет присваивать чужие черты.
• fow — отключает туман войны .
• delall / deleteallunits [тег страны] — удаляет войска выбранного государства.
• fronts — видимость вражеских фронтов.
• traderoutes — видимость торговых путей.
• adiplo / allowdiplo — дипломатические действия выполняются вне зависимости от ограничений.
• ai_accept — другие государства, не могут вам отказать в ваших желаниях.
• ai_invasion — выключает способность флотилий выполнять военно-морские вторжения.
• debug_nuking — позволяет совершать атомные атаки.
• research all — мгновенное изучение всех научно-исследовательских веток.
• annex [тег страны] — аннексирует выбранную страну.
• winwars — увеличивает очки войны.
• tag [тег страны] — переключает управление на любую страну в мире.
• add_opinion [тег страны] [число] — улучшает отношения с любой страной.
• add / remove_interest [тег страны] — добавляет / удаляет выбранное государство из списка ваших интересов.
• add / remove_core [ID провинции] — создает / отменяет претензии вашей страны на указанную территорию.
• xp [число] — добавляет указанное количество опыта вашим армиям и флотилиям.
• wp [тег страны] — позволяет заключить белый мир с указанным государством.
• threat [число] — добавляет выбранное количество угрозы для вашей страны (если не указывать число, вам будут добавлять по 999).
• nu [число] — добавляет указанное количество национального единства.
• nuke [число] — добавляет ядерное оружие (от 100 до 1000 очков).
• spawn [тип войск] [ID провинции] [число] — создание войск в выбранной провинции.
• occupationpaint [тег страны] — вы оккупируете выбранное государство, но не можете им полноценно владеть.
• setowner [код страны] [state id] — устанавливает владельца области.
• nocb — позволяет вам объявить войну абсолютно любому государству.
• setcontroller [тег страны] [id провинции] — устанавливает контроль страны над заданной провинцией.
• instant_prepare — позволяет высадкам флотилий происходить мгновенно.
• civilwar [тип войны] [тег страны] — начинает гражданскую войну в указанном государстве (гражданскую войну можно организовать только — fascism , communism , democratic ).
• add_party_popularity [идеология] [число] — повышает популярность какой-либо политической партии — f (фашизм), d (демократия), c (коммунизм), n (нейтральное).
• set_ruling_party [идеология] — устанавливает правящую партию в стране.
• event political.18 — Смена идеологии вашей страны на фашизм.
• event political.19 — Устанавливает коммунизм как идеологию государства.
• event political.20 — смена идеологии вашей страны на демократию.
• add_autonomy [тег] [число] — позволяет изменить автономию субъекта.
• pause_in_hours [число] — позволяет пропустить какое-либо кол-во часов.
• compliance [число] — изменение лояльности в провинции.

Фокусы

• Focus.AutoComplete — национальные фокусы открываются мгновенно.
• Focus.NoChecks — игнорирует требования фокусов.
• Focus.IgnorePrerequisites — игнорирует предварительные требования фокусов.

Дополнительные читы к Hearts of Iron 4

Для начала, скажу, что данные команды для людей, которые любят изменить игру так, чтобы им было эстетически удобно.

• rendertype — указывает тип используемого рендера.
• tweakergui — вызывает редактор GUI.
• time — показывает текущие время.
• reloadfx [Arguments: map/mapname/postfx or *.fx filename] — перезагружает шейдеры.
• particle_editor — открывает редактор частиц.
• testtool / test — инструмент для тестирования.
• analyzetheatres / anth — поиск ошибок в театрах военных действий.
• massconquer / massc — инструмент массового завоевания.
• nopausetext — включить / отключить значок паузы, чтобы получить более красивый скриншот (почему-бы и нет).
• nomapicons — включение / выключение значков на карте.
• reloadinterface — перезагрузка всего интерфейса.
• reloadtechnologies — перезагрузка базы данных технологий.
• updateequipments — обновление базы данных оборудования.
• updatesubunits — обновление базы данных субъединиц.
• reloadoob [тег страны] — перезагрузка приказов выбранного государства.
• update_loc [localization tag] — обновление тегов местоположения файлов локализации.
• poll — отображает доступные события.
• event [event id] [тег страны] — начинает выбранное событие.
• savegame — Сохраняет игру.
• savecheck — сохраняет игру (Test_01), загружает её, делает ещё одно сохранение (Test_02). Эти сохранения должны быть идентичны.
• ip — Показывает ваш IP адрес.
• requestgamestate — запрашивает состояние игры хоста.
• nudge — открывает инструмент nudge(редактор позиций на карте)
• mapmode [Mapmode type (int)] — изменить режим карты.
• fullscreen- включение / отключение полноэкранного режима.
• debug_smooth — включение / отключение сглаживания кадров.
• debug_nomouse — включение / отключение прокрутки колеса мыши.
• debug_terrain — включение / отключение местности.
• debug_cities — включение / отключение отображения городов.
• debug_water — включение / отключение воды.
• cameraclamp — включение / отключение стабилизации камеры.
• weather — включение / отключение моделирования погоды.
• browser [url] — открывает окно браузера.

Теги государств

Здесь находятся теги государств в Hearts Of Iron 4. Если вы не нашли какого-либо государства, можете написать в комментариях, добавлю.

Надстрочная звёздочка (*) — означает то, что данное государство вы сможете встретить по ходу игры. Данные государства появляются, либо от других стран — автоматически, либо от ваших решений.

Основные государства:

• Франция — FRA
• Третий Рейх (Германия) — GER / Западная Германия — WGR / Восточная Германия — DDR
• Италия — ITA
• Советский Союз — SOV
• Япония — ♥♥♥ (возможно, у вас не будет отображаться, поэтому — JAPan. Копируйте первые три буквы).
• Соединенное Королевство — ENG
• Соединённые Штаты Америки — USA

Европейские государства:

• Албания — ALB
• Австрия — AUS
• Бельгия — BEL
• Болгария — BUL
• Чехословакия — CZE
• Дания — DEN
• Эстония — EST
• Финляндия — FIN
• Греция — GRE
• Венгрия — HUN
• Ирландия — IRE
• Латвия — LAT
• Литва — LIT
• Люксембург — LUX
• Нидерланды — HOL
• Норвегия — NOR
• Польша — POL
• Португалия — POR
• Румыния — ROM
• Словакия* — SLO
• Испания — SPR
• Прусия* — PRE
• Швеция — SWE
• Швейцария — SWI
• Турция — TUR
• Югославия — YUG
• Украина* — UKR
• Каталония* — CAT
• Галисия* — GLC
• Исландия* — ICE
• Беларусь* — BLR

Северная Америка и Вест-Индия:

• Канада — CAN
• Коста-Рика — COS
• Куба — CUB
• Доминиканская республика — DOM
• Эль Сальвадор — ELS
• Гватемала — GUA
• Гаити — HAI
• Гондурас — HON
• Мексика — MEX
• Никарагуа — NIC
• Панама — PAN

Южная Америка:

• Аргентина — ARG
• Боливия — BOL
• Бразилия — BRA
• Чили — CHL
• Колумбия — COL
• Эквадор — ECU
• Парагвай — PAR
• Перу — PRU
• Уругвай — URG
• Венесуэла — VEN

Азия:

• Афганистан — AFG
• Бутан — BHU
• Британская Индия — RAJ
• Пакистан* — PAK
• Китайская Народная Республика / Коммунистический Китай — PRC
• Гуансийская клика — GXC
• Ирак — IRQ
• Иордания* — JOR
• Ливан* — LEB
• Мэнцзян — MEN
• Монголия — MON
• Китай — CHI
• Непал — NEP
• Оман — OMA
• Палестина* — PAL
• Иран — PER
• Вьетнам* — VIN
• Республика Лаос* — LAO
• Республика Камбоджа — CAM
• Саудовская Аравия — SAU
• Шаньси — SHX
• Синьцзян — SIK
• Сирия* — SYR
• Танну-Тува — TAN
• Манчжоу-го — MAN
• Тибет — TIB
• Сибэй Сань Ма — XSM
• Йемен — YEM
• Юньнань — YUN
• Корея* — KOR

Юго-Восточная Азия и Океания:

• Австралия — AST
• Новая Зеландия — NZL
• Филипины — PHI
• Голландская Ост.-Индия / Индонезия — INS
• Сиам (Тайланд) — SIA
• Малайзия — MAL

Африка:

Источник: showgamer.com