• 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.
Windows 11 23H2
GPU: UHD 770 (integrated)
CPU: 13600K @ 5.2 & 4.1 GHz
RAM: 2x16GB DDR5 6800 CL34
SSD: yes

version 1.6.1 using 160 saves

medium preset no fps limit
1840: 1:00, 0:59 (1:06 in 1.5.12)
1900: 1:42, 1:43 (1:59 in 1.5.12)

low preset 60 fps limit
1840: 0:58, 0:57
1840.png
1900: 1:44, 1:43

low preset 30 fps limit
1840: 1:04, 1:04
1900: 1:28, 1:29
1900.png
Comparing to my best 1.5.12 times.
1840: 0:57 vs 0:59
There is hardly any difference in early game performance.
1900: 1:28 vs 1:46
Late game performance has some pretty large gains.
Windows 10 22H2
GPU: AMD Radeon R7 250
CPU: AMD FX-6300
RAM: 2x8GB DDR3
SSD: no

version 1.6.1 using 160 saves

medium preset no fps limit
1840: 4:00
Potato_1840.png
1900: 8:15
Potato_1900.png
 
Last edited:
  • 4
  • 1Like
Reactions:
Windows 11 23H2
GPU: UHD 770 (integrated)
CPU: 13600K @ 5.2 & 4.1 GHz
RAM: 2x16GB DDR5 6800 CL34
SSD: yes

version 1.6.1 using 160 saves

medium preset no fps limit
1840: 1:00, 0:59 (1:06 in 1.5.12)
1900: 1:42, 1:43 (1:59 in 1.5.12)

low preset 60 fps limit
1840: 0:58, 0:57
1900: 1:44, 1:43

low preset 30 fps limit
1840: 1:04, 1:04
1900: 1:28, 1:29
Comparing to my best 1.5.12 times.
1840: 0:57 vs 0:59
There is hardly any difference in early game performance.
1900: 1:28 vs 1:46
Late game performance has some pretty large gains.
Can you make cache and memory bechmark at aida?
 
GPU: NVIDIA Geforce RTX 4090
CPU: AMD Ryzen 9 7950X3D
RAM: 64GB
SSD: Yes
1840 time: 1 minutes 29 seconds
1840 Slow Tick Operations:
Vic1840.jpg


1900 time: 2 minutes 45 seconds
1900 Slow Tick Operations:
Vic1900.jpg
 
  • 5
Reactions:
1.6.1

GPU: Nvidia 1070 Ti
CPU: Ryzen 7 7800X3D
RAM: 32GB (2x16GB 6000Mhz Cl32)
SSD: Yes

1840 Time: 0:55 Minutes


Older Times: 1:07 Minutes in 1.5.7 and 1:00 Minute in 1.4.2

1709909255747.png



1900 Time: 1.55 Minutes

Older Times: 4:17 Minutes in 1.5.7 and 2:10 Minutes in 1.4.2

1709909513998.png
 
  • 5
Reactions:
GPU: NVIDIA GeForce GTX 1660
CPU: AMD Ryzen 5 3600 (6-Core) @ 3.593 GHz
RAM: 32GB (2x16)
SSD: yes

1.6.1 =

1840 time: 2:20
1840 Slow Tick Operations:
slowticks 1840 1.6.jpg
1900 time: 4:35
1900 Slow Tick Operations:
slowticks 1900 1.6.jpg




Comparison to 1.5.13 =

1840 time: 2:04
1840 Slow Tick Operations:
slowticks 1840 1.5.jpg
1900 time: 7:16
1900 Slow Tick Operations:
slowticks 1900 1.5.jpg

so definitely a HUGE improvement in late game speed. A slight degradation in early game speed.
 
  • 5
Reactions:
GPU: NVIDIA Geforce RTX 4090
CPU: AMD Ryzen 9 7950X3D
RAM: 64GB
SSD: Yes
1840 time: 1 minutes 29 seconds
1840 Slow Tick Operations:
View attachment 1090854

1900 time: 2 minutes 45 seconds
1900 Slow Tick Operations:
View attachment 1090855
This has to be an AMD issue then, if the person with the intel CPU just flat out has better times than people with stronger CPU's then his.
 
  • 1
Reactions:
This has to be an AMD issue then, if the person with the intel CPU just flat out has better times than people with stronger CPU's then his.
I don't think so... I have an Acer Predator Helios 300 (PH315-51-78NP) with an Intel i7-8750H and a GTX 1060. The game is definitely slower from the start. I see ticks taking seconds by 1850. It seems to be related to army calculations, since I noticed having more wars (including the never ending revolutions by vassals) would increase tick time.
 
  • 1
Reactions:
I don't think so... I have an Acer Predator Helios 300 (PH315-51-78NP) with an Intel i7-8750H and a GTX 1060. The game is definitely slower from the start. I see ticks taking seconds by 1850. It seems to be related to army calculations, since I noticed having more wars (including the never ending revolutions by vassals) would increase tick time.
I'm doing a Peru-Bolivia run and by the 1850's a week takes at least four second, it is so painfully slow I don't want to imagine how slow it'll be further down the road. I legit do not understand how a patch focused on optimization made things so much worse.
 
  • 2Like
  • 1
Reactions:
Patch 1.6.1

GPU: NVIDIA Geforce RTX 2070 Super
CPU: AMD Ryzen 7 5800X3D
RAM: 32GB
SSD: Yes

1840 time: 1:35
1840 Slow Tick Operations:
patch 1.6.1 1840 ticks.png



1900 time: 3:07
1900 Slow Tick Operations:
patch 1.6.1 1900 ticks.png
 
Last edited:
  • 2
Reactions:
Is there any demerit in running V3 in debug? Like, will the game be slower because of it? Or achievements will be unavailable?

I don't find this exact benchmark useful for trying to identify the problems I reckon are happening with 1.6.x. It is useful for the sake of repeatability, of course, but I felt big hangs in ticks in some specific situations and I would like to be able to see what was the game calculating at such times.
 
  • 1
Reactions:
I find the game runs so much faster on Linux.
 
Very interesting that despite my sepcs being better than yours, we have almost identical times. My CPU is almost an entire GHz faster than yours but that apparently doesn't matter much for early game speed. Something is artificially holding it back.
How does your cpu utilization look while playing at speed 5? From what I understanding the 7900X3D and 7950X3D processors can suffer from significant scheduling issues for some tasks because only 6 (7900X3D) and 8 (7950X3S) of the cores have access to the X3D cache, so if the game is scheduled to the non-X3D cores, performance could suffer a lot. If the Network/Session thread of the game is running on a non-X3D core on a 7900X3D it will (from what I understand) have half the L3 cache available compared to what the main thread will have for someone using a 7900X CPU, basically holding back all the threads used for the game.

The recommended checklist would be to make sure your AMD drivers (for the cpu) are up to date, make sure windows game mode is turned on, and make sure that windows recognizes Vic 3 as a game (this can be forced in the settings for windows game bar (windows key + G, then go to the settings cogwheel). Going to the graphics performance settings in windows and specifying Vic 3 to run in high performance mode probably won't hurt either, but I would expect that to only be GPU related. Some advanced users also turns to software which allows more control of the CPU core usage, but I have no idea how difficult or risky that is to do. It is also not a perfect solution. If you are interested you can look up infomration regardnig 7900/7950X3D and "Process Lasso".

@F4UST, you may also want to have a look at your settings, as you appear to be affected by the same issue.
 
Redoing the test on 1.6.2, which is supposed to fix some performance issues, I don't expect any major differences since it already seemed to run pretty fast for me in 1.6.1.

GPU: GTX 1080
CPU: i7-6700K CPU @ 4.00GHz
RAM: 16GB (2x8) 2133MHz DDR4
SSD: Yes
1840 time: 2 minutes 58 seconds
1840 Slow Tick Operations:
slowtickoperations184022.png


GPU: GTX 1080
CPU: i7-6700K CPU @ 4.00GHz
RAM: 16GB (2x8) 2133MHz DDR4
SSD: Yes
1900 time: 5 minutes 44 seconds
1900 Slow Tick Operations:
slowtickoperations190022.png


A little bit worse, not sure if that's just randomness (more wars?) or the fixed migration or something else. Still better than pre-1.6 for me.
 
  • 2
Reactions:
GPU: GTX 3060 laptop gpu
CPU Ryzen 7 5800h CPU @ 3.20GHz
RAM: 16GB (idk about the hz)
SSD: Yes

1.6.2 with the 1.6.0 saves

1840 time: 2 minutes 20 seconds
1840 Slow Tick Operations:

Screenshot 2024-03-23 022650.png

1900 time: 4 minutes 29 seconds
1900 Slow Tick Operations:

Screenshot 2024-03-23 023306.png


1.5.13 for comparasion with the 1.5.7 saves

1840 time: 2 minutes 5 seconds
1840 Slow Tick Operations:

Screenshot 2024-03-23 030110.png


1900 time: 4 minutes 31 seconds
1900 Slow Tick Operations:

Screenshot 2024-03-23 030751.png


EDIT: interestingly enough, there are less slow tick operations, but the time is still the same... Maybe something else is causing the slowdown which is not logged?
 

Attachments

  • 1711156768152.png
    1711156768152.png
    63,2 KB · Views: 0
Last edited:
  • 1
Reactions:
Slow tick operations seems only to log operations taking 10ms or more on at least one tick. Added operations or operations going from say, 2ms to 3ms would not show up there.
 
  • 1
Reactions:
Built a new rig after my laptop finished dying last week, enjoying a substantial performance increase.

GPU: 4070 Ti Super
CPU: Ryzen 9 7800x3d
RAM: 2x16GB 6000MT/s CL30
SSD: NVMe M.2
OS: WIndows 11
Version: 1.6.2

1840 Time: 1:18

1712675014687.png


1900 Time: 2:33

1712678563912.png


1840 Time (60 FPS cap): 1:07

1712679899560.png


1900 Time (60 FPS cap): 2:05

1712679589711.png


FPS cap helping significantly with the 1900 save, used nvidia control panel rather than ingame limiter, haven't tested yet if that matters.

EDIT: 1900 time of 2:11 using in game fps limiter instead of nvidia, probably a little too close to say with certainty that it matters.

EDIT 2: Capping fps to 20 (Lowest possible in nvidia settings) gave me a 1900 time of 1:49
 
Last edited:
  • 5
  • 2Like
Reactions:
Sounds like there is some sort of bug with graphics as capping FPS makes it run faster.
Devs did find out that outliner can make game run slow tho. Might be same bug that is present here.
 
  • 2
  • 1
Reactions:
Sounds like there is some sort of bug with graphics as capping FPS makes it run faster.
Devs did find out that outliner can make game run slow tho. Might be same bug that is present here.

Yeah It's probably the outliner and other UI elements being updated every frame.
 
  • 1
Reactions:
Yeah It's probably the outliner and other UI elements being updated every frame.
If you have trade center, or trade route list open, then game will slow down if you have like 100 trade routes too.
 
  • 1
Reactions:
Sounds like there is some sort of bug with graphics as capping FPS makes it run faster.
Devs did find out that outliner can make game run slow tho. Might be same bug that is present here.
Capping FPS making sim speed faster is not a bug. It is a result of how computers work. The CPU has to send instructions to the GPU for every frame being displayed. Fewer frames means less work and wait time for the CPU. As a result the simulation can run faster on the same CPU.
 
  • 3
Reactions: