• 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.

unmerged(26764)

General
Mar 14, 2004
1.833
5
So I have a game I started in 1066 that by the 1360s has become so laggy its hard to play. The game stutters every five or so game days, sometimes lagging out for ten seconds. It's become almost unplayable.

I thought the problem was the large history. So I tried deleting in the save game every dead character. (It's pretty easy to do because they're at the back of the character files). No fix.

I can't imagine what the problem is. There ought to be the same number of living characters in the game as there are in 1066. There are X number of counties and duchies in the game, and it doesn't really matter who holds them. Sure now most of them are my vassals but I'm not sure why that would matter. They're all warring and plotting and marrying the same whether they're my vassals or vassal of the King of France.

Does anyone have an idea what causes this? Is it something I can fix? I'd hate to give up so close to the end.
 
The game tends to bog down as it goes on. It is a common problem in Multiplayer games. You could always try deleting some of your older save games, that sometimes helps.
 
...now most of them are my vassals but I'm not sure why that would matter...
I wouldn't be so sure it doesn't matter. I experienced lags similar to what you described a few times. I'm not 100% sure what the causes are, but one of my suspicions is that too many direct vassals and/or courtiers is, indeed, problematic.

Are we talking hundreds, here?
 
Hardware?
I have a relatively new laptop (about a year) and i played through til finish with 0 lag...
The only annoying thing is the amount of spam messages holding a large kingdom that slowed it down.
 
I wouldn't be so sure it doesn't matter. I experienced lags similar to what you described a few times. I'm not 100% sure what the causes are, but one of my suspicions is that too many direct vassals and/or courtiers is, indeed, problematic.

Are we talking hundreds, here?

I'd already tried the save game delete trick too. I was aware of it from other Paradox games. The only save file left in my folder is this one. Didn't help.

Yeah, we're talking almost 200 dukes. A Frisian Empire encompassing most of Spain, France, Germany, Italy, Denmark, Poland, and great parts of North Africa -- with about half of it converted to Dutch culture. I was really looking forward to seeing how much more Dutch culture I could spread. I already had it from the outskirts of Paris to Prague, Vienna, Aqualiea, Dauphine, and Warsaw. Plus I was going to make Tech 5. It's tough to give up the game but I really can't play it anymore.

Not sure why the computer would lag out just because all those vassals are mine instead of someone elses. The game still has to process the same number of interactions. If anything, I've probably got the world a lot calmer than it otherwise would be.
 
Ah sorry to hear about late game lags. But it is just unavoidable computationally.

1) Given a fixed number of characters, having larger kingdoms is computationally more expensive.


▶ 2 kingdoms with 10 dukes each, each kingdom has 9*10/2 = 45 relationships to compute, for a total of 90 relationships in 2 kingdoms.

▶ 2 kingdoms, one with 19 dukes and the other with 1 duke, the large kingdom has 18*19/2 = 171 relationships to compute, for a total of 171 relationships in 2 kingdoms.


2) A game with larger number of characters is computationally more expensive.


▶ Game with 100 characters has 99*100/2 = 4950 relationships
▶ Game with 1000 characters will have 999*1000/2 = 499500 relationships
10x increase in characters roughly gives 100x increase in number of computations performed.


It may help if you severely curtail the chance of random courtiers appearing or make the random courtiers all low-borns, increase chance of people dying from disease, or drop the fertility once the court reaches size 20 instead of 30. But all that has the side effect of making dynasties die off more quickly, and affecting game play.
 
Also, let's see exactly what hardware you have: please post a dxdiag.txt down to include "Display devices" please.
 
It's an old rig low on RAM, so that's likely part of the problem:

------------------
System Information
------------------
Time of this report: 5/22/2012, 07:29:35
Machine name: FJD
Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.120411-1615)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell DM051
BIOS: Phoenix ROM BIOS PLUS Version 1.10 A07
Processor: Intel(R) Pentium(R) 4 CPU 3.00GHz (2 CPUs)
Memory: 3070MB RAM
Page File: 1058MB used, 3930MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode

------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: The file nv4_disp.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 1: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 8400 GS
Manufacturer: NVIDIA
Chip type: GeForce 8400 GS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_06E4&SUBSYS_0A9419F1&REV_A1
Display Memory: 512.0 MB
Current Mode: 1152 x 864 (32 bit) (60Hz)
Monitor: Mitsubishi DiamondPoint NX86LCD (Analog)
Monitor Max Res: 1280,1024
Driver Name: nv4_disp.dll
Driver Version: 6.14.0012.9053 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 12/17/2011 17:03:00, 4290816 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 12/17/2011 17:03:00, 13733696 bytes
Device Identifier: {D7B71E3E-45A4-11CF-1C59-982A00C2CB35}
Vendor ID: 0x10DE
Device ID: 0x06E4
SubSys ID: 0x0A9419F1
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
 
Actually your 3gb of Ram is fine, especially with XP which has quite a small footprint itself. Being on a 32bit OS and CPU you won't use any further Ram you put in this machine, around 3.25gb is the max that can be addressed.

Your hardware is on the slow side, especially your video card. You could try updating the driver though
http://www.geforce.com/drivers/results/44962
That aside all you can really do to help performance is make sure you have no other apps running at the time you are playing the game, reduce your resolution, and edit settings.txt to turn trees off.