Victoria 3 | 1.7 - Known Issues

[PDX_Pelly]

Hello, Victorian players!

Update 1.7 releases on the 24th of June, as mentioned in the Changelog we have a list of Known issues occurring in the release version of 1.7 "Kahwah" listed below for your convenience, a number of fixes will come in subsequent hotfixes.

Updated: 1.7.1 any entry crossed through in this color has been fixed in this Hotfix

---

Known Issues:

1. All saves of a previous version of the game will not work and may crash due to the changes implemented in game.
2. Due to updated shaders, the game may load a bit longer the first time loading the game.
3. Some localization issues will roll out in subsequent hotfixes.
4. state_funding_for_campaigns_expenses modifier in election_neutral.7 does not apply money modifier.
5. We are aware of the performance issues in 3D map mode on Mac. For now, it is advised to use the paper map mode or low settings to improve gameplay.
6. Cursor flickers the windows cursor when moving the mouse at game start.
7. Agriculture buildings can be nationalized if the building is level 1 with Homesteading law.
8. Livestock Ranches can be fully nationalized with Homesteading law.
9. Military buildings appear in the Potential Buildings section of the Buildings panel.
10. Battalion/Fleets are not showing in Power Bloc tooltips, causing errors.
11. We are addressing the issues with tooltips on the 'failed to hire' icon for buildings.
12. Starting a DP against a country you are already in a war with.
13. Lobbies are not spawning when inviting/exiling agitators.
14. Pink face placeholder and NULL_STATE appear briefly after a building has finished construction in Foreign Queues.
15. Wrong icon for request knowledge sharing and demand state notification.
16. Events cluster in groups of 3-5 per yearly tick.
17. Power Bloc interactions do not show in the Power Bloc panel.
18. Private investment pool can be too eager to invest abroad.
19. Lobby opportunities can ask for impossible pacts.
20. Conscript battalions can be displayed as negative numbers.
21. Production Method tooltip for Power Bloc Statue shows TOOLTIP_UNLOCKED_BY_IDENTITY
22. It's possible to start a Ban Slavery diplomatic play against a subject.
23. Dutch East Indies breakup event can fire multiple times during the campaign.
24. Tibet Expedition events have a number of issues.
25. Rare CTD on opening Power Bloc Panel.
26. Popup on Foreign Investment Nationalization always claims that no compensation was given.
27. Subjugation toast missing subject text.
28. persia_events.1 targets claims on USA state Georgia.
29. Tooltip for "Request British Military Mission" button claims it only grants Russian Military Mission modifier in The Eastern Frontier JE.

---

For addressing the issue of CTDs (Crash to Desktop) related to building shaders, you can take the following steps to clear the shader cache and potentially improve game stability:
Delete Shader and Terrain Cache:

1. Navigate to Documents\Paradox Interactive\Victoria 3\.
2. Delete the shadercache and terraincache folders if they exist.

Verify Game Files:

1. Open Steam and go to your Library.
2. Right-click on Victoria 3 and select Properties.
3. Go to the Local Files tab and click on Verify Integrity of Game Files.

Clear DirectX Shader Cache (optional):

1. Open the Disk Cleanup tool by typing "cleanup" in the Start menu.
2. Select your C drive and uncheck all options except "DirectX Shader Cache."
3. Click OK to clear the cache.

Disable and Re-enable Shader Cache (NVIDIA Users optional):

1. Open the NVIDIA Control Panel.
2. Go to Manage 3D Settings and find Shader Cache Size.
3. Disable it, apply the changes, and then re-enable it after clearing the cache.

These steps should help manage and reduce the frequency of CTDs related to shader cache. Ensure that your GPU drivers are up-to-date and consider running the game with fewer mods to identify if any specific mod is causing additional issues


We are heavily invested in player feedback and look through as much as we humanly can, however people will encounter things we did not so please feel free to use the bug reporting.

Thank you to everyone who provides feedback and bug reports, they are really appreciated!

 

[Rabid]

Literally unplayable (for 4 more days)

 

[Cymsdale]

I kinda expected the changelog before the anti-changelog.

 

[Nitan17]

persia_events.1 targets claims on USA state Georgia.

 

[William-frost]

So how long will these known issues be resolved

 

[Nnorm]

In other words it needs more weeks to polish.

 

[Angrum877]

This one sounds funny: Political lobbies demanding impossible treaties. Care to elaborate?

 

[YonosTheManlyManner]

Thank you for the transparency. Greatest company in the world!

 

[SeekTruthFromFx]

Publishing a Known Issues list is proper and professional, so I'm happy we've got this post. But as someone who wants to see V3 thrive, I'm concerned that the Steam-review-writing masses (who haven't reached the Literacy threshold needed to read this post) are going to be unhappy when they encounter a release with this many visible bugs.

Also, commiserations to the dev team, who have no doubt worked hard on this and tried to avoid this situation by postponing the launch.

 

[SeekTruthFromFx]

So how long will these known issues be resolved

I don't know, but the Devs mentioned answered a question elsewhere by saying that something was fixed in 1.7.1, so it sounds like a bugfix patch is in the works as usual.

 

[TheBlahJ]

Was the mac bug present on previous patches, because I am experiencing performance issues now even.

 

[FranklyJustNess]

Seeing things mentioned, that would really only take a moment to an hour for one person to fix, three days before the actual release is not a good image.

 

[SeekTruthFromFx]

Seeing things mentioned, that would really only take a moment to an hour for one person to fix, three days before the actual release is not a good image.

I share the frustration, but the reality is that there is normally a 'freeze date' well before release. After that point, no more changes are allowed. If you allowed changes right up to the moment of release, the danger is that you accidentally botch the fix and introduce something even worse (e.g. you fix a bug playing as Prussia, but the game crashes on 1 January 1837 if you play any country except Prussia; releasing in that state would get bad headlines all over the gaming world). The fact that these issues are known means that they will be working on fixes already, which will go into 1.7.1 (at least one such fix has already been mentioned), which is probably going through QA right now and will be released very soon after 1.7 is launched. It's a sensible response to the fact that a release with moderately-sized known issues will get much better media coverage and Steam reviews than a major release with even one really bad bug.

 

[AlexGleb]

what a disrespect for the players. You know that the patch has a lot of bugs and you still sell it for money. Great policy. I want you to go to the store and buy yourself bread that is 60% ready. I wonder how you will feel after this? a shame. just a shame

 

[joseph_mcCarthy]

In 1.7, you can enforce religion on a nation after creating a power bloc and the appropriate prerequisites. I think this might have a flaw that if not fixed will affect the 1.7 launch.

Take my game playing as the Heavenly Kingdom (not in 1.7).

Let's say you've created the Heavenly Kingdom, and your goal for the game is to convert the entire country. Unfortunately, having zero Protestants means zero conversion. Even with an open borders policy, internal migration rarely fixes this issue. Some Protestants will move but at a shockingly slow pace. Most communities are restricted to a small number of provinces when migrating to increase performance, but the mass conversion of a nation should be an exception to this rule.

 

[jfinley12]

Some of these known issues sound like game breaking bugs. Why cant you give us a solid date on the first patch?
10,17, and 25 are major issues with power blocs. Is that not the new major feature? 25 being a rare ctd sounds like a big problem. So the major new feature of the expansion has tons of issues you know about not even counting the ones you don't know about and your launching anyhow? I want to play as much as the next person but this can seriously hurt your games image and just reinforce the idea about paradox expansions. Just my two cents.

 

[Ninking]

persia_events.1 targets claims on USA state Georgia.

I'm sorry, but isn't that a hotfix which takes 1 minute to change a three letter tag, requiring zero testing?

 

[SAS]

Regarding the cursor flickering at main menu issue, does anyone else besides also have that continue to happen in game, it is killing my eyes.

 

[nani the guard]

some mouse binding key like the front and back button(mouse 4 & 5 ) for some mouse doesn't work in 1.7, it works before but the update aaaaaaa

 

[Ker0]

I already notice the cursor flickering. Not SUPER dramatic but I hope it gets fixed quickly.