Home Trending Latest threads New posts Developer diaries

Patch 1.04 Problems

Jump to latest Follow Reply
  • 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.
Crusader Kings II 69948 Bug Reports 19720 User Modifications 10606 Suggestions 5969 Tech Support 6376 After Action Reports
unmerged(432904)

unmerged(432904)

Private
6 Badges
Jan 9, 2012
22
0
  • Crusader Kings II
  • Europa Universalis III Complete
  • Divine Wind
  • Heir to the Throne
  • Rome Gold
  • Warlock: Master of the Arcane
Ok, I have the Steam version of the game and run it on Windows 7.

When I started loading the the game after the new patch the majority of the green on my terrain map is now white. Anybody else had this problem and if so how do I fix this? It makes looking at the terrain map pretty much unbearable for any length of time.

Another problem I have had is any time I try to load a game that I was playing from before the patch the game crashes. I thought I read somewhere here that the game saves would be compatible but maybe not. Even so, it seems like the game shouldn't completely crash just because I try to load a previous save.

One final thing, I always get this message when the game loads that I have to install a C++ library or something. I always click yes and it does it's thing and the game plays fine. I am not sure if that has anything to do with it or not.

Keep in mind, that prior to loading the 1.04 patch, this game was running great. The only thing that has changed is the patch install.

Any advise would be much appreciated.

Thanks :)
 
"When I started loading the the game after the new patch the majority of the green on my terrain map is now white. Anybody else had this problem and if so how do I fix this? It makes looking at the terrain map pretty much unbearable for any length of time."

Same problem for me (with gamergates version), except i can't play anymore (the game never start). I install/desinstall the game, it doesn't work. I try to update my graphic adaptater's pilots (hope it's the good english word) but it doesn't work better after.
 
I found the fix for the C++ message.

Now, however, I have been experiencing just flat out crashes on the menu screens in addition to the whited out terrain.
This patch turned a game that was working fine into a game that is rapidly becoming unplayable :-(
 
Move any valued save games elsewhere and uninstall the game. Manually delete the CK2 files under the Steam directory, and also those under MyDocuments. Now install it afresh, and make sure the checksum is MLDO.
 
AndrewT said:
Move any valued save games elsewhere and uninstall the game. Manually delete the CK2 files under the Steam directory, and also those under MyDocuments. Now install it afresh, and make sure the checksum is MLDO.
Click to expand...


Did all that.
With a freshly downloaded game (previous purged), the problem still exists.
The main menu screen does appear (as it did previously) but upon clicking a selection, the button remains highlighted... but nothing happens. Task Manager reports Crusader Kings II as "not responding".
 
Ok, I have reinstalled from scratch. My previous save games seem to be working fine. Although I was playing a game earlier on the new patch and the game crashed, which never happened with the previous versions.

It still did not get rid of that terrible terrain map problem though, which is a drag, because I love the terrain map. Does anyone know what is causing this map problem??

Thanks
 
Can EVERYONE still having the hanging/crashing problem that's new with 1.04 please post their dxdiag.txt files - only from the start of the file down to the end of the "Sound devices" section is necessary, for brevity's sake. Thank you.
 
Ok, Got it.


------------------
System Information
------------------
Time of this report: 3/12/2012, 17:59:34
Machine name: MIKE-PC
Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.111025-1501)
Language: English (Regional Setting: English)
System Manufacturer: Compaq-Presario
System Model: GC667AA-ABA SR5130NX
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (2 CPUs), ~2.0GHz
Memory: 4096MB RAM
Available OS Memory: 3582MB RAM
Page File: 1428MB used, 5736MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.

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

---------------
Display Devices
---------------
Card name: NVIDIA GeForce 7600 GS (Microsoft Corporation - WDDM)
Manufacturer: NVIDIA
Chip type: GeForce 7600 GS
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0392&SUBSYS_033C196E&REV_A1
Display Memory: 2024 MB
Dedicated Memory: 504 MB
Shared Memory: 1519 MB
Current Mode: 1680 x 1050 (32 bit) (59Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: AL2223W
Monitor Id: ACRAD84
Native Mode: 1680 x 1050(p) (59.954Hz)
Output Type: DVI
Driver Name: nvd3dum.dll,nvwgf2um.dll
Driver File Version: 8.15.0011.8593 (English)
Driver Version: 8.15.11.8593
DDI Version: 9Ex
Driver Model: WDDM 1.0
Driver Attributes: Final Retail
Driver Date/Size: 7/13/2009 21:16:11, 7592960 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-40D2-11CF-4F5B-372301C2C535}
Vendor ID: 0x10DE
Device ID: 0x0392
SubSys ID: 0x033C196E
Revision ID: 0x00A1
Driver Strong Name: nv_lh.inf:NVIDIA.Mfg.NTx86...1:nv_G7x:8.15.11.8593:pci\ven_10de&dev_0392
Rank Of Driver: 00F42001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeWMV9_B ModeVC1_A ModeWMV9_A
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
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{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,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) 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,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) 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
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{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
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Not Supported
DXVA-HD: Not Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
 
Thanks! I was able to get the terrain map back to normal doing the following

1. Try downloading this file and unrar it into the folder "gfx\FX", overwriting the file there.

pdxmap.rar

2. I also updated my driver per the above post

I did them both, so I am not sure which one got rid of the white glare on the terrain map but I am glad it's gone :laugh:

Now for some more play time to see if I have any further lock ups or crashes.

mike
 
I'd say updating the video driver resolved problems. Looking at your DXDiag file, the driver was THREE YEARS old! The original drivers that came on the disk with the card. Brother, you need to update video drivers often. Even fresh out of the box, the OEM packed driver is often already outdated. :)
 
Ronthors60 said:
I'd say updating the video driver resolved problems. Looking at your DXDiag file, the driver was THREE YEARS old! The original drivers that came on the disk with the card. Brother, you need to update video drivers often. Even fresh out of the box, the OEM packed driver is often already outdated. :)
Click to expand...

Hard to say... my graphics driver was only one month old (released Feb 9th, 2012), and I had the same white-out graphics problem until downloading Doomdark's pdxmap.rar gfx-fix file, mentioned in my own problem thread.
 
I bought the download version from Amazon and jumped though the hoops. The stream version keeps locking up as you start the game. So after a couple of hours of looking for the link to the patch,(I am not a PhD in computers, which seems to be the new requriement to play Paradox games) the patch here says, after doing the two "run" for the download, that I don't have a copy of the game installed on my computer!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I am angrey enough to delete the game and NEVER buy another Paradox game in my life. WHAT IS THE FRICKING PROBLEM WITh THIS PATCH?
 
Do you have the Steam or non-Steam version of the game (I don't know what one Amazon supply)? I think you have the Steam version, in which case it will update automatically, no need to manually apply the patch at all.
 
This game is still crashing after patch 1.04

It just doesn't make any sense why the additional patch would cause the game to crash like this. I was working fine with the earlier distributions. I did not have a single crash until the 1.04 patch.

While the video stuff is fixed and that is nice, it's a pretty big pain when the game locks-up most of the way into a year off the auto-save, because sometimes you've done a lot of stuff in 8-10 months, some good stuff happens that you might not even get on the 2nd play (like pregnancy or random event) through from the auto-save and then you're 10 minutes rebooting and reloading just to get back to the auto-save. Disappointing.

I've done a fresh install to see if that helps. Hasn't made any difference in regards to the crashes.
 
mike2323 said:
... It just doesn't make any sense why the additional patch would cause the game to crash like this. I was working fine with the earlier distributions. I did not have a single crash until the 1.04 patch...
Click to expand...

Any change made to a computer program always runs the risk of breaking something that was working fine earlier. This is especially true with patches that have a fast turn-around time, since it isn't possible to subject them, in only a few days or weeks, to the same stringent testing that the original game undergoes during Beta.

While Paradox is looking into the matter, I've simply rolled back my game to the 1.03b version. I always make a copy of my game folder before patching, so that if problems do come up I can play my game out of the (older, tested) copy while still maintaining another copy with the up-to-date patch version, in case Paradox has questions about exactly how the new problems behave.
 
mike2323 said:
Is there any way to go back to playing on the 1.03 patch with the Steam version? It seems to automatically include all the updates that have been put out.
Click to expand...

dont think so, ive tried to figure this out myself. frustrating is the word.
 
You must log in or register to reply here.
Top Bottom
Back