Treasury Display Problem

[jmberry]

So I don't know if this is a bug or something wrong with my display settings and preferences, but the treasury display comes off as too large and off-center for my screen. This means that a lot of times I can't even see some of the artifacts I have (since I can't move the display).

 

[AndrewT]

Please do a full **clean** re-install:

- move any valued save games elsewhere
- "uninstall" in Steam-CK2
- manually delete both the Steam/SteamApps/common/CK2 AND Documents/Paradox/CK2 folders
- re-install game in Steam, run a Steam Verify when done.
- start the game with no mods active and test

In particular make sure there are no files or folders left under either the Steam CK2 or Documents CK2 locations, before installing again.


IF that doesn't help, DXDIAG is a program you run from a command prompt or the Windows start menu 'run' dialog box (or 'search programs' in Windows 7 or later). After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

Please attach your Documents/Paradox/CK2/settings.txt.
From your Documents/Paradox/CK2/logs/ folder, attach system.log .

And can we see a screenshot of the problem, thanks.

 

[jmberry]

Alright, I'm in the process of re-installing the game now. Before I uninstalled it, though, I took a screenshot to show what the problem was.

As you can see, the treasury bleeds off the side of the screen.

 

[SchwarzKatze]

Um, is that 1024*768 resolution?

 

[jmberry]

Um, is that 1024*768 resolution?

You know, I don't know. The computer itself is set to be at 1440*900, but I also know that Steam changes the resolution when the game launches, and I don't know to what.

 

[jmberry]

In any event I followed the instructions and everything is fixed now (using the one guy I knew for a fact had an artifact as the test run).

Judging from how the character screen is also smaller, I'm guessing it was indeed a resolution problem. I don't know if it was the installation or verification that fixed it, but it's nice that everything is the way it should be.

Thanks for the help.