GalCiv2 and Windows 7

from GalCiv2 Forums

Anyone else playing GalCiv2 in Win7?

Just thought I would start a thread of the bugs and quirks in this new OS. Some may be worked out by MS in the beta process, but some may need addressing by the SD folks. (I am playing DL, by the way)

Here is what I have found so far:

1. I use a lot of add-in ships, mainly from the Star Trek mod. When I go into the shipbuilder I experience some strange behavior.

I'll click 'New' in the Shipbuilder, which loads the ship models. The memory usage increases to just over 1.3GB, then the screen goes black and the memory usage drops to around 400MB. The memory usage then gradually increases to about 1.1GB and the screen returns to normal.

It doesn't stop me from creating ships or effect the game play in any way. It is just strange that the screen goes black and that it unloads so much memory before returning to normal. Strange also, that the memory usage should be so much less once it does normalize.

 

2. I experience audio and video glitches with overlay windows open. Not stutters, but drop-outs for a fraction of a second. It might affect the audio, or the video, or both at the same time. Doesn't seem to have anything to do with relative CPU usage when it happens.

 

3. Screen updates take much longer - most notably in the Civ Manager - Timeline screen. (1/2 second vs. 1/10 second, or so)

Actual game play is comparable to playing in WinXP. Just these few quirks, which may have to do more with the beta DX11, or how W7 handles memory, than anything else.

 

15,449 views 18 replies
Reply #1 from GalCiv2 Forums Top

Wow.

5 days and not a single response.

I am very curious to know what causes GalCiv2 to unload so much memory when loading ship models. It is a repeatable thing - it happens every time I go to build a new ship.

 

Or, is no one else playing GalCiv2 in Win7?

Reply #2 from GalCiv2 Forums Top

I think DethAdder was, but I don't remember specifically.

I personally haven't loaded up 7 because I don't have a spare hard drive to test it on, and wouldn't want to screw up my current installation (of XP).  Granted, 7 is supposed to be better than Vista, but it's difficult to give someone the benefit of the doubt when they've screwed up before.  (In this instance I am speaking specifically of the issues that a large percentage of people ran into when running [admittedly early builds of] Vista on the same drive as their XP install, and not necessarily anything about Vista itself.)

Galactic Civilizations IV
Reply #3 from GalCiv2 Forums Top

My Report after about one week win7 rc x64 running...

7 is really running smooth and fast so far, quite cleaned up, can really compare to a ubuntu x64 speedwise.

Overall, I am the first time a bit impressed, that MS delivered finally, what the already promised for vista, get rid of some old win api.

TA delivers a 'dx not initialized error' or 'drivers too old' when starting, depending on compatibility settings. At least, I got the vid driver to work, which was impossible with beta build 7000.

My gfx is Geforce 9600M GT... no beta mobility drivers yet for win 7.... installed via vista copat mode the vista x64 drivers.

I'll post an update, if I got TA running with dx support o_O .

Reply #4 from GalCiv2 Forums Top

I haven't used the RC candidate yet. I had DA and TA running ok on Win7 after putting the Vista 64 Gfx drivers on it. With the initial Nvidia Win7 drivers DL would run ok, but both DA and TA would crash on the galaxy load screen.

My info is a little outdated because i got pushed back to using mainly XP for some of my older games and apps to run right.

Reply #5 from GalCiv2 Forums Top

Update: Latest win7 beta mobility driver also produces same error messages :(

Uhmm, I killed vista yesterday....

 

dxdiag from debug.err:

Debug Message:  *********DXDiag info follows.*********

DirectX Version: DirectX 11
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7100)
Languages: German (Regional Setting: German)                  
BIOS: Phoenix SecureCore(tm) NB Version 09LA.7027.20081209.JJC
Processor: Intel(R) Core(TM)2 Duo CPU     P8600  @ 2.40GHz (2 CPUs), ~2.4GHz
Physical Memory: 4096MB RAM
Page File: 1567MB used, 6611MB available
Windows Dir: C:\Windows

Display Info
Display device 1:
Device Name: \\.\DISPLAY1
Card Name: NVIDIA GeForce 9600M GT
Manufacturer: NVIDIA
Chip Type: GeForce 9600M GT
DAC Type: Integrated RAMDAC
Key Device: Enum\PCI\VEN_10DE&DEV_0649&SUBSYS_C03F144D&REV_A1
Display Memory: 2287 MB
Current Display Mode: 1680 x 1050 (32 bit) (60Hz)
Monitor Name:
Monitor Max Resolution:
Driver Name:
Driver Version:
Driver Date:
DirectX Acceleration Enabled: No

Sound info
Sound device 1:
Description: Lautsprecher (High Definition Audio-Gerät)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0262&SUBSYS_144DC03F&REV_1002
Manufacturer ID: 1
Product ID: 65535
Driver Name: HdAudio.sys
Provider: Microsoft
Driver Version: 6.01.7100.0000
Driver Date: 4/22/2009 06:15:37
Type: WDM
Other Drivers:
Acceleration Level: 1
Cap Flags: 0
Min/Max Sample Rate: 0, 0

Debug Message:  *********END dxdiag info.*********
Debug Message:  WARNING: DirectX Acceleration is not enabled.
Debug Message:  Entering WinMain

 

 

And now 32 bit dxdiag from system:

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

---------------
Display Devices
---------------
          Card name: NVIDIA GeForce 9600M GT
       Manufacturer: NVIDIA
          Chip type: GeForce 9600M GT
           DAC type: Integrated RAMDAC
         Device Key: Enum\PCI\VEN_10DE&DEV_0649&SUBSYS_C03F144D&REV_A1
     Display Memory: 2287 MB
   Dedicated Memory: 497 MB
      Shared Memory: 1789 MB
       Current Mode: 1680 x 1050 (32 bit) (60Hz)
       Monitor Name: PnP-Monitor (Standard)
      Monitor Model: unknown
         Monitor Id: SEC3646
        Native Mode: 1680 x 1050(p) (60.062Hz)
        Output Type: Internal
        Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.15.0011.8585 (English)
     Driver Version: 8.15.11.8585
        DDI Version: 10
       Driver Model: WDDM 1.1
  Driver Attributes: Final Retail
   Driver Date/Size: 4/30/2009 22:02:00, 9443840 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71E3E-4509-11CF-7456-34E001C2C535}
          Vendor ID: 0x10DE
          Device ID: 0x0649
          SubSys ID: 0xC03F144D
        Revision ID: 0x00A1
 Driver Strong Name: oem8.inf:NVIDIA.Mfg.NTamd64.6.0:Section001:8.15.11.8585:pci\ven_10de&dev_0649&subsys_c03f144d
     Rank Of Driver: 00E60001
        Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
   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: Supported
            DXVA-HD: Supported
       DDraw Status: Enabled
         D3D Status: Enabled
         AGP Status: Enabled

 

I also gave admin permission to ...\Programs(x86)\GalCiv2 directory.

Seems, that galciv2 does not handle and detect video driver properly in Win7.

Maybe MS changed their driver Model and signature?

I don't think, it is a DX11 issue.

Anyone any clue?

Reply #6 from Stardock Forums Top

There are several games that have this bug.

You have to repalce a file (dxdiag.dll??) with a version from vista to temporarily fix it.

Just google it, you should find more reports like that...

Reply #7 from GalCiv2 Forums Top

Thanks for the hint :)

well, here is the solution...

It seems, from what I googled, that the Galciv2 hardware acceleration check has gotten somehow buggy, with DX11 implemented in build 7100.

This will also affect Vista users, upgrading to DX11 soon!

For x86:

1. Take ownership, grant your user full permissions, and make a backup from dxdiagn.dll located in ..\windows\system32

2. download (or copy from vista/XP 32bit) dx redisributable 32bit

3. copy dxdiagn.dll from 2. to ..\windows\system32

 

For x64:

do step 1-3

4. do 1-3 for ..\windows\sysWOW64

Reply #8 from GalCiv2 Forums Top

Can you please share where you got the DLL from, i cannot find the right one on google, i have this same problem with the Windows 7 RC. Its quite annnoying.

Or if you didnt download it and got it from a previous windows, whihc i do no thave the luxury of, could you perhaps email me the file at [email protected]

Reply #9 from GalCiv2 Forums Top

I copied the dll from my "old" vista x86 box, since I wiped vista off my laptop, as soon as 7 got RC.

I'll email you the dll.

Reply #10 from GalCiv2 Forums Top

Thanks for the file but i cant replace it, it wont let me, i've tried taking ownership of the folder and giving myself full control but it wont let me says access denied when i try to change the settings.

 

EDIT: Its ok, after much trial and error with the permissions system, i was able to replace the file, game works perfectly now no "you dont have up to date drivers"  stuff, says im running with DX acceleration on, so thank you for your assitance

Reply #11 from GalCiv2 Forums Top

Folder?! You just need to take ownership of the dll, in order to grant full permission. By default, your user is not listed, and the add button greyed out.

Click in properties of dll-->security--> advanced--> owner and change from trustedinstalled to your user. Your are now ableto add your user to the security list ;)

Reply #12 from GalCiv2 Forums Top

Could I get a copy of that file as well? I found a file called dxdiagn.dll, not dxdiag.dll, on both my Vista and Win7 machines (both x64). I copied the Vista version over, which cased TA to say that it required Directx 9.0c installed. As it is, with the default dxdiagn file, it will start up, tell me dx mode is disabled, play the first second of audio (no video) from the opening cutscene, and then crash.

Reply #13 from GalCiv2 Forums Top

The dll needs to be 32 bit.

Reply #14 from GalCiv2 Forums Top

can i get the x64 one, can't seem to find one that matches the same size as the one i have on my computer

Reply #15 from GalCiv2 Forums Top

Can I get an email of that DLL too? I don't have vista.

Reply #16 from GalCiv2 Forums Top

Please guys, read the thread.

The dll needs to be 32bit, despite of running a x64 win7.

The dll is also part of the mentioned x86 dx redistributable package.

 

@Kryo

You could sticky the thread, since threads regarding the DX issues are growing.

Just add a use at own risk comment, for this ugly temorary workaround, and edit the title to something more describing.

I suspect a lot of vista userers also complaining, after upgrading to dx11, in case MS don't fix it.

Just a thought, keeping things win7 calm here *_*

Reply #17 from GalCiv2 Forums Top

I am using Windows 7 RC 64-bit, on a GeForce 9800 GTX+, with 190.38 GeForce drivers.

I got this error as well. I didn't bother trying to actually play the game as I assumed it would be terrible, or wouldn't work at all. So I did the workaround, and the game launched without issue and played fine.

Here's the wrinkle though guys: I had to run dxdiag to submit a report for a beta testing application. So I removed the work-around DLLs and replaced them with the originals that I had backed up. But the game still ran. It gave the error, but when I was actually playing everything worked fine. 1920x1200, 8x anti-aliasing, everything set to max, and not so much as a hiccup, and everything looked just the same as I remember.

I'm thinking the error is a toothless tiger. Can anyone confirm that the error in fact breaks the game, or if its just an annoying popup? I'm 100% certain I'm running the stock DLLs that come with Win7 RC 64-bit, and I do get the error, but everything runs fine.

It might not be necessary to bother.

Reply #18 from GalCiv2 Forums Top

Now that we have the final RTM Win7 code, we've checked into this and it does not appear to be an issue with the release.

http://windowsfixup.com/2009/05/windows-7-build-7122-fixes-game-issues/ suggests it was an issue with the RC builds and they include the workaround steps posted above.

I am going to be republishing new revisions of the Twilight/Endless Universe/Ultimate installs on Impulse either today or Monday. These do not change the game, but work around some issue Win7 RTM has with one of the files used by the editors causing a crash prompt during install (though the game works afterwards).

Kris