• 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.
Status
Not open for further replies.

laywoman

Second Lieutenant
Paradox Staff
QA
Oct 4, 2022
109
414
V3_TOP_known_issues_1.png

Hello to all of you! I'm Jolanta, QA Lead for Victoria 3, and today I'm going to talk about an unavoidable reality of launching a complex new game: bugs.

Ever since our (very exciting!) launch 48 hours ago, we have been hard at work cataloging and addressing some of the issues you've discovered, big and small. What follows is a list of some issues that you can anticipate will be fixed in upcoming patches, the first of which you can expect sometime next week. Where applicable I have also added information about short-term workarounds you can employ until the bug has been patched.

We are also planning to share a roadmap with you next week, so you can take a sneak peek into upcoming game updates. Stay tuned!

Known Bugs:

  1. In some user configurations, the Paradox Launcher might fail to parse the settings file properly, making it impossible to change the language and other settings through the launcher.
    Most common solution: Uninstall all instances of the Paradox Launcher and run the game again.
    More information can be found in this dedicated post: https://forum.paradoxplaza.com/forum/threads/launcher-issues-troubleshooting.1550846/
    On Windows 10 OS it can be done via “Add or Remove Programs” utility.
    KI_1.png
  2. Game map is black when starting the game.
    Workaround: Ensure you don't have a controller plugged in while starting or playing the game. The controller may freely rotate the camera in a direction where no graphics exist.
  3. If the player participates in multiple wars at the same time, generals might prematurely abandon fronts and return to their HQs once one of the wars ends.
    Workaround: Check up on your Generals after you sign a peace treaty in one war while still involved in another.
  4. The game could crash if the player hovers the mouse cursor over Sell Orders after having a different country join their market.
    Workaround: After a country joins your market, run the game for at least a week of in-game time before digging into data in the Market panel.
  5. Out-of-sync errors when attempting to hotjoin a multiplayer game already in progress.
    Workaround: Try again! If this happens to you repeatedly, have the host save and rehost the game, ensuring everyone who wants to play is present in the lobby before starting the session.
  6. Travel time can be bypassed by issuing additional orders targeting the same Front.
    Workaround: Wait until the General has arrived at the Front before changing the order. Establish a house rule not to do this in multiplayer until fixed (soon!).
  7. Revolutions create empty country entries in several map lists (Markets, Global GDP, Cultures Overview and more).
    As long as you don't try to interact with these entries they won't cause anything but cosmetic harm.
    KI_2.png
  8. It might be possible to use the Investment Pool to construct any privately-owned building regardless of Economic System law.
    We are aware of this issue, it will be fixed soon!
  9. Some biomes don't emit ambient sound.
    The cause of this issue has been found and your soundscape will soon be more impressive!
  10. Successful secessions may retain their "civil war" status and name after the war, becoming untargetable for further Diplomatic Plays.
    We have this on our radars!
  11. Troops with low Morale may join battles despite there being plenty of troops with high Morale.
    Workaround: In particularly difficult wars you could set your Front to full defense until your troops have regained Morale, before switching back to Advance.
  12. American Civil War can be easily avoided, and if it triggers, the Union may contain slave states and vice versa.
    While civil wars and state selection for revolutionary countries are dynamically determined based on political support and radicalism, and may take different forms in different playthroughs, this particular outcome is not intended and will be addressed.
  13. Debt Enslavement and Slave Trade is too rapid.
    A number of economic and setup-related factors conspire to make it so more Pops are enslaved and moved around the world than intended. This will be addressed shortly.
  14. Players starting as Peru could become Puppeted without any say shortly after game start.
    Workaround: Until we can make sure that Peruvian independence is respected, you can run the game as another country for a few years and then switch over to Peru from the game menu.
  15. When a revolution starts in a Subject country, the Overlord country gets the option to switch sides and play as the revolution.
    Workaround: If you accidentally do this, you can manually switch the country you're playing as from the game menu.
  16. Newborn Rulers and Heirs may clip through their clothes. Japanese Shogunate Heirs do not wear clothes at all.
    Presence of unintentional Adamites in Victoria 3 is not intended, they will leave the game soon.
  17. Expedition Leaders may remain busy after the Expedition ends.
    Workarounds: send the commander on another expedition. And if you do several expeditions, sending the same commander on them whenever possible reduces the risk of this happening.
  18. Sometimes, expeditions may fail immediately in Africa.
    Workaround: to prevent this from happening, when you get the event “An Insolvent Business” during an expedition, don’t select the first option.
  19. Budget balance chart goes out of bounds after large shifts in Budget calculation
    Workaround: We will look into this. In the meantime these chart spikes will correct over time.
    KI_3.jpg
To sum up, these known issues are in progress and we are constantly scouting our communities for issues you raise. We are doing our best to fix them in the shortest amount of time so you can enjoy your playthroughs without any concerns.

If you notice anything else and have some spare time to spend submitting the issue you found in the game, please use our forum bug reporting page where you could easily file it using the link here.

This is not a complete list of known issues! If a bug you're experiencing isn't listed here, we may still be aware and working on it, especially if you have already submitted it on the bug reporting page.

Thank you for having time to read through and making our game better!

/Jolanta
 
  • 131Like
  • 32
  • 11Love
  • 10Haha
  • 2
Reactions:
Upvote 0
Newborn Rulers and Heirs may clip through their clothes. Japanese Shogunate Heirs do not wear clothes at all.
Presence of unintentional Adamites in Victoria 3 is not intended, they will leave the game soon.
Is this related to the fact that many male heirs seem to go bald before they're out of their teens?
 
will you also fix problem with AVX? Many users have the same issue: CPU without AVX support, not able to run Vic3. It will be great to know if we can expect fix or not, so we can ask for money refund or wait :cool:

The game was created with AVX in mind, which makes it a hard requirement (mentioned in the minimum system requirements). Unless you are playing on Mac, but the technological bar is set much higher there to facilitate that.

1666943587026.png
 
Last edited:
Interestingly, for some reason the beta worked better than the release version in terms of gameplay. The Civil War in the USA was more worked out, despite the bugs, Germany could have been formed more historically, when it was enough to include all the German-speaking principalities in the customs union, and it was not necessary to capture them all (I don't want to think that you did the right thing in beta to remove it in the release and then roll it out as a paid dlc). The military system worked just better. I played for Serbia, captured all the Balkans, Moldova came to the turn. I had 70 divisions, Moldova had 17. She defeated me twice and occupied my entire territory, because for some reason my generals sent 3-4 units into battle against 10 units of Moldova (both in defense and in attack). Not only is it unhistorical, it just shouldn't work that way. A state with 70 divisions and the best technology cannot lose to a small state with 17 divisions, no matter what morale they have, tactics on the battlefield do NOT work like that. Apparently, because of this problem, Mexico constantly defeats the United States, and Egypt defeats Turkey. Installations for auto-expansion and subsidies are constantly flying off in the structures. I came across this back in beta, but I thought it would be fixed in the release. What prevented you from fixing it? Also, I would like to be able to open the console just on ~, without having to run the game in developer mode, because in this case unnecessary information windows near the cursor are turned on, overlapping the entire map, which makes it unrealistic to play. The same problem was in ck3, but there the window near the cursor is not so big and does not interfere with the game so much. Even though I am an ordinary player, please think about these questions, because they will JUST make life better for players without having to change concepts. Just finalize the game with the next update, we believe in you. The game is really cool.
 
  • 8
  • 1
Reactions:
Formal tee m limits aren’t a thing in this time period so I can’t wait to see 99 year old president for life Lincoln.
Don't count on it. Winfield Scott became an opium addict and Henry Clay died in late 1836 for me, so Lincoln will probably fall down the stairs and die in 1850.
 
Any update on the issue of Macs crashing when trying to start a game after selecting a country? It is a game-breaking bug, that entirely prevents play, so I need to know whether to wait it out or get a refund while I can and try again in a few months.
We are looking into and fixing crashes, but did not mention all of them in the post. We are in need of more information to look at the Mac crash though. Replied in the forum thread!
 
  • 4Like
Reactions:
There is a weird bug, where sometimes when you want to mobilize all generals game just crashes - I realized that it always happens when game thinks that general X is occupied by smth (but is not).
 
  • 1
  • 1Like
Reactions:
Status
Not open for further replies.