Page 1 of 2 12 LastLast
Results 1 to 40 of 50

Thread: EU official support not responding

  1. #1
    Join Date
    Sep 2010
    Posts
    29

    EU official support not responding

    Hello to all CIV fanatics.

    Apart from the issues discussed in this forum, that are killing us all, I need to say that I am still waiting the official EU support response {ticket #216004} as of 25/09/10. Today is the 1st of October. Helloooooooooo?

    The automated response say that i will be having news from their side within max 72hours.

    Frankly speaking I DO NOT CARE if they are having too much work nowadays. Eventhough since the crashes / freezes issues are not a major problem for the CIV 5 - as some people say in this forum- CIV 5 support workload should have been normal and they should at least have responded to our help request.

    Value your loyal customers, cause you might end up with no customers in the near future. WE ARE NOT BETA TESTERS.

    Thanks in advance.

  2. #2
    Join Date
    Sep 2010
    Posts
    29
    5th of October and no response yet.

    Why the official EU support is not responding? 10days have only passed .

    Thank you 2k and Firaxis team.

    Really appreciate it .

    Will we manage to play the game before 2011?

  3. #3
    Join Date
    Oct 2010
    Posts
    17
    EU support page wants the EAN code of the Civ5 package.

    When entereing the code it says "Code not valid" :P

    So it is also *NOT* possible to use the Support-Formulars for Civ5 ^^

  4. #4
    ik25

    Your machine (depending on who you talk to) is below the minimum 7900GS nvidia card listed.

    That could be one reason no reply has come yet, if they are filtering by supprted vs non supported hardware.

    That bein said, if you want help, post a DXDIAG, and your issues

  5. #5
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by QuantumTarantino View Post
    ik25

    Your machine (depending on who you talk to) is below the minimum 7900GS nvidia card listed.

    That could be one reason no reply has come yet, if they are filtering by supprted vs non supported hardware.

    That bein said, if you want help, post a DXDIAG, and your issues
    I believe he lists himself has using a 8800 GTS which is above the minimum specification. I have attempted to contact steam, 2k, etc. and have no response other than post your DXDIAG or in Steam's email the windows system .nfo file.

    Tom's Hardware Video Card List

    7900GS
    7.2 GP/s 9 GT/s

    8800 GTS {640MB}
    10.26 GP/s 24.624 GT/s

  6. #6
    Join Date
    Sep 2010
    Posts
    29
    Mr. Quantin

    You recommend 8800GTS {640mb} is below 7900GS, {and below specs.}

    Because you write the code without taking into account a major nvidia card series. The specific card i am talking is still ranked 51st on the hi-end vga sections on the web. Search the web. And start doing some serious testing with a pc with some 8800 GT/GTS/GTX/ultra cards.

    Hello ? Wake up ..... You have just replied , just to reply.....

    There is an official ticket with all the tech details .

    Typical robot .

  7. #7
    Join Date
    Sep 2010
    Posts
    19
    If you're patient, you CAN get through on the phone (at least via the UK's technical support number)... it's the only way I've gotten any information at all about my issue... that said, I'm now waiting for a response from the operator who looked at my issue, but as I only spoke with him yesterday, it's probably unrealistic to expect a response the next day.

    But, yes, I agree with you... I waited six days and heard NOTHING from 2K support, so ended up holding in the phone queue until I -did- get through.

  8. #8
    Join Date
    Sep 2010
    Posts
    29
    My problem friend is not that i am expecting an immediate / magical solution to the crashes and freezes. It is not happening.

    I am just expecting people that are paid for, to care and do their jobs, ie respond. Not to rush into conclusion, and above all NOT TO start with the APPROACH your hardware is below specs {yes 8800GTS below specs}...... {just to get by, assuming that we are all that technologically uneducated}.

    Keep up with the great job you are doing.

    Mr. Quantum where did you get the conclusion my hardware is below specs? Did you read the crystral ball? Or is it easier this way?

    Wake up!!!!!!!!

    By the way is anyone having a working -"below spec"- machine with a 8800 GT/GTS/GTX/Ultras series card that actually can play the game with no freezes?

    How many dxdiag have been posted? Anyone with the above vga cards has found the solution and/or is enjoying crash free gaming?

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.


    Go public and admit that you did a crappy programming job...
    Last edited by ik25; 10-05-2010 at 12:22 AM.

  9. #9
    Join Date
    Sep 2010
    Posts
    21
    I haven't heard anything back either and I have 2 8800's in a sli which should be more than enough . My brother with his single 8800 card is the same. For us the game is still unplayable and no sight of any type of support. Appears this issue with the 8800 cards isn't that important.

    I will not call on the phone and deal with that mess and on top of that have to pay for it.

    Sucks
    Last edited by tr0lltek; 10-06-2010 at 12:13 AM.

  10. #10
    Quote Originally Posted by ik25 View Post
    My problem friend is not that i am expecting an immediate / magical solution to the crashes and freezes. It is not happening.

    I am just expecting people that are paid for, to care and do their jobs, ie respond. Not to rush into conclusion, and above all NOT TO start with the APPROACH your hardware is below specs {yes 8800GTS below specs}...... {just to get by, assuming that we are all that technologically uneducated}.

    Keep up with the great job you are doing.

    Mr. Quantum where did you get the conclusion my hardware is below specs? Did you read the crystral ball? Or is it easier this way?

    Wake up!!!!!!!!

    By the way is anyone having a working -"below spec"- machine with a 8800 GT/GTS/GTX/Ultras series card that actually can play the game with no freezes?

    How many dxdiag have been posted? Anyone with the above vga cards has found the solution and/or is enjoying crash free gaming?

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.


    Go public and admit that you did a crappy programming job...
    Quantum was just trying to help you out like some of us in the community tend to do. Like I was going to do till I saw the way you acted. Now I don't care if you ever get your game fixed, I hope you don't actually. I'm gonna go play mine now. Want me to copy and paste some nice screenshots in here for you?
    Last edited by dragoaskani; 10-06-2010 at 12:17 AM.

  11. #11
    Join Date
    Sep 2010
    Posts
    343
    The 8800GTS is actually below specs for direct x 10/11. If you own this card it does not physically have the hardware to run the game at 10.1 direct x. Sorry.

    To fix this problem you will need to run the game at direct x 9. Sorry. There is no work around, there is no patch for this, you can not patch hardware. Your card is physically missing pieces.

    I will repeat, the 8800gts/gtx/gt, does not have the hardware to run direct x 10.1. Only, direct x 10. There is no rendering path for civ 5 to use direct x 10.

    The current supported direct x rendering paths are: Direct x 9c. Direct x 10.1. Direct x 11.

  12. #12
    Join Date
    Sep 2010
    Posts
    29
    First of all thank you for your replies.

    Dear Dragoaskani allow me to dedicate you my Archive's favorite song.....

    Won't mention the title, but it was a big hit..... So go on....

    {Anyway do you have the mental capacity to read through and understand my point? Or you believe that quantum or anyone else need your assistance as their solicitor ? }



    Dear Draco, the games says DX 10/11 , it does not mention DX10.1 .....

    Still in my case it is running .... The problem is the crashes and freezes that occur eventually after time while playing.

    So if the case is the DX10.1 , I am sorry but they should have written it on the packaging, allowing me to read it. Still even in the main menu before loading the game {the recommended one} is DX 10/11 , not 10.1 / 11.

    Thanks
    Last edited by ik25; 10-06-2010 at 01:05 PM.

  13. #13
    Join Date
    Oct 2010
    Posts
    18
    Quote Originally Posted by dragoaskani View Post
    Quantum was just trying to help you out like some of us in the community tend to do. Like I was going to do till I saw the way you acted. Now I don't care if you ever get your game fixed, I hope you don't actually. I'm gonna go play mine now. Want me to copy and paste some nice screenshots in here for you?
    Why are you harsh on him ... he has the right to be angry, maybe not in that manner but still he is right.
    If 2k was fair to the buyer it wold have stated that there is a problem with cards that don't support DX10.1.

    OT: Try to run your game in DX9 or/and in windows mode and see if you get the crash again. I have a 9600GT, i can run it decent on DX9 ... funny thing is when i start the Launcher it recommends me DX 10/11, i can use the dx10/11 but at the first diplomatic screen all goes crazy and unplayable.

  14. #14
    Join Date
    Sep 2010
    Posts
    29
    Thanks edw.

    Still can play the game even on my wife's laptop @ DX10/11 with no major issues {minor bugs, but no major freezes/crashes}. The vga there is a 9600GT the mobile version.....

    Are you using the desktop version?

  15. #15
    Join Date
    Jul 2010
    Posts
    159
    Quote Originally Posted by Draco View Post
    The 8800GTS is actually below specs for direct x 10/11. If you own this card it does not physically have the hardware to run the game at 10.1 direct x. Sorry.

    To fix this problem you will need to run the game at direct x 9. Sorry. There is no work around, there is no patch for this, you can not patch hardware. Your card is physically missing pieces.

    I will repeat, the 8800gts/gtx/gt, does not have the hardware to run direct x 10.1. Only, direct x 10. There is no rendering path for civ 5 to use direct x 10.

    The current supported direct x rendering paths are: Direct x 9c. Direct x 10.1. Direct x 11.
    before bashing people, i suggest you to get your facts strait:

    Microsoft's Sam Glassenberg did however note that "DirectX 10.1 fully supports DirectX 10 hardware. No hardware support is being removed. It's strictly a superset. It's basically an update to DirectX 10 that extends the hardware functionality slightly." Glassenberg says DirectX 10.1 will be fully compatible with all graphics cards supporting DirectX 10.

    found here:
    http://www.neowin.net/news/directx-1...res-no-new-gpu

    so if there's problem using 8800 series in civ 5 in dx10.1, well we have to be looking at firaxis bad implementation, not a limitation with the card.

    i would add that i have a 8800 gtx, which is in term of performance slightly superior to the recommended 9800 series (just 8800 cheaper version to produce and rebranded) and when started in dx10/11 mode, works perfectly until some point where it freezes. i managed to make 50 turns one time, so the game CAN run in this mode, just there are bugs.

    on a side note, we can see the quality of code testing by the simple fact that the magellan achievement has a 0% completion rate. so it means the devs didn't even make the most MINIMAL, BASIC test of checking that this code works at least in ONE case. it speaks of how rushed in production the game was. heck, maybe they didn't even have implemented the code yet because it was non essential...
    Last edited by toasteur; 10-06-2010 at 02:23 PM.

  16. #16
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by Draco View Post
    The 8800GTS is actually below specs for direct x 10/11. If you own this card it does not physically have the hardware to run the game at 10.1 direct x. Sorry.

    To fix this problem you will need to run the game at direct x 9. Sorry. There is no work around, there is no patch for this, you can not patch hardware. Your card is physically missing pieces.

    I will repeat, the 8800gts/gtx/gt, does not have the hardware to run direct x 10.1. Only, direct x 10. There is no rendering path for civ 5 to use direct x 10.

    The current supported direct x rendering paths are: Direct x 9c. Direct x 10.1. Direct x 11.
    And you base this on what ? Direct3D 10.1 runtime can run on Direct3D 10.0 hardware . Keywords here "can run". . Look it up its in the white papers in msdn library. With an 8800 card / cards anyone should be able to still play dx10.1 / 11 although all the extra graphic options would not be available, e.g. shaders, cube arrys, whatever, but it should still be playable.

    We all know (or should) that you cannot _patch_ hardware (*edit actually you can with firmware updates , although you cant really get newwer functions if the extensions are not built into the chips*), that said please tell me why civ5 is so special here and not compatible, or freezes on 8800. I do not have this problem with other games using 10.1. and 10.1 has been around since vista sp1. So please enlighten me as to why

    FYI there are also 2 different builds of the 8800 series. The ones based on the g8 chip and the ones based on the g92 chip, depending although neither one should really be below spec.
    Last edited by tr0lltek; 10-06-2010 at 02:44 PM.

  17. #17
    Quote Originally Posted by ik25 View Post

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.

    WE ARE NOT BETA USERS.


    Go public and admit that you did a crappy programming job...
    Beta users?
    What are you talking about?.

    The A.I is in an alpha stage...
    So we are basicaly playing a late prototype of the game. At least when it comes down to the A.I

  18. #18
    Curious to what the exact problem is..and I would personally love to see a dxdiag.

  19. #19
    Join Date
    Sep 2010
    Posts
    21
    Posted already in other threads but ok here goes Problems general crash or freezes:

    Code:
    Faulting application name: CivilizationV_DX11.exe, version: 1.0.0.17, time stamp: 0x4c9b9292
    Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf
    Exception code: 0x0000087c
    Fault offset: 0x0000b727
    Faulting process id: 0x394
    Faulting application start time: 0x01cb5c250cace590
    Faulting application path: c:\program files (x86)\steam\steamapps\common\sid meier's civilization v\CivilizationV_DX11.exe
    Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
    Code:
    The program CivilizationV_DX11.exe version 1.0.0.17 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
     Process ID: 74c
     Start Time: 01cb5c119458c4a0
     Termination Time: 526
     Application Path: c:\program files (x86)\steam\steamapps\common\sid meier's civilization v\CivilizationV_DX11.exe
    Code:
    Faulting application name: CivilizationV_DX11.exe, version: 1.0.0.17, time stamp: 0x4c9b9292
    Faulting module name: d3d11.dll, version: 6.1.7600.16385, time stamp: 0x4a5bd9a6
    Exception code: 0xc0000005
    Fault offset: 0x0005aaa3
    Faulting process id: 0xce0
    Faulting application start time: 0x01cb5c1122262620
    Faulting application path: c:\program files (x86)\steam\steamapps\common\sid meier's civilization v\CivilizationV_DX11.exe
    Faulting module path: C:\Windows\system32\d3d11.dll
    DX: Shortened for post
    Code:
    ------------------
    System Information
    ------------------
    Time of this report: 9/28/2010, 00:52:04
           Machine name: BLACKMETAL
       Operating System: Windows 7 Enterprise 64-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)
               Language: English (Regional Setting: English)
    System Manufacturer: NVIDIA
           System Model: 132-CK-NF78
                   BIOS: Phoenix - AwardBIOS v6.00PG
              Processor: Intel(R) Core(TM)2 Quad CPU    Q9650  @ 3.00GHz (4 CPUs), ~3.0GHz
                 Memory: 4096MB RAM
    Available OS Memory: 4094MB RAM
              Page File: 1110MB used, 7076MB 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.7600.16385 64bit Unicode
    
    ------------
    DxDiag Notes
    ------------
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
            Sound Tab 2: No problems found.
            Sound Tab 3: 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 8800 GTS
           Manufacturer: NVIDIA
              Chip type: GeForce 8800 GTS
               DAC type: Integrated RAMDAC
             Device Key: Enum\PCI\VEN_10DE&DEV_0193&SUBSYS_E8273842&REV_A2
         Display Memory: 2404 MB
       Dedicated Memory: 613 MB
          Shared Memory: 1791 MB
           Current Mode: 1680 x 1050 (32 bit) (60Hz)
           Monitor Name: PnP-Monitor (Standard)
          Monitor Model: SyncMaster
             Monitor Id: SAM0304
            Native Mode: 1680 x 1050(p) (59.883Hz)
            Output Type: DVI
            Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 8.17.0012.5896 (English)
         Driver Version: 8.17.12.5896
            DDI Version: 10
           Driver Model: WDDM 1.1
      Driver Attributes: Final Retail
       Driver Date/Size: 7/10/2010 01:38:00, 12471400 bytes
            WHQL Logo'd: Yes
        WHQL Date Stamp: 
              Vendor ID: 0x10DE
              Device ID: 0x0193
              SubSys ID: 0xE8273842
            Revision ID: 0x00A2
     Driver Strong Name: oem20.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section003:8.17.12.5896:pci\ven_10de&dev_0193
         Rank Of Driver: 00E62001
            Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeWMV9_B ModeVC1_A ModeWMV9_A 
    <snip>
           D3D9 Overlay: Supported
                DXVA-HD: Supported
           DDraw Status: Enabled
             D3D Status: Enabled
             AGP Status: Enabled

  20. #20
    x87c is an invalid param code and 05 is a pretty standard "oops something went fooy" code.

    Your video drivers are out of date and could you include the audio section of your dxdiag? Also have you had any other error codes than the above 2 and have they referenced any file other than the dx11 executable for civ5?

  21. #21
    Join Date
    Sep 2010
    Posts
    21
    how are the drivers out of date they are back from beta 260 to 258.96 ? Ill post sound later

  22. #22
    Latest drivers are as follows:
    Version:
    260.63 BETA
    Release Date:
    2010.09.14
    Yours are a few months out of date for both WHQL and BETA versions. If they are not installing and updating properly it might take a wipe/restart/reinstall to get them properly functioning again.(Had that problem myself a few days ago).

  23. #23
    Join Date
    Sep 2010
    Posts
    21
    LOL yeah , I tried 260 and they didn't help . So I rolled back to a stable driver. Here is sound:

    Code:
    -------------
    Sound Devices
    -------------
                Description: Lautsprecher (Realtek High Definition Audio)
     Default Sound Playback: Yes
     Default Voice Playback: Yes
                Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001
            Manufacturer ID: 1
                 Product ID: 100
                       Type: WDM
                Driver Name: RTKVHD64.sys
             Driver Version: 6.00.0001.6151 (English)
          Driver Attributes: Final Retail
                WHQL Logo'd: Yes
              Date and Size: 7/6/2010 18:31:36, 2419176 bytes
                Other Files: 
            Driver Provider: Realtek Semiconductor Corp.
             HW Accel Level: Basic
                  Cap Flags: 0xF1F
        Min/Max Sample Rate: 100, 200000
    Static/Strm HW Mix Bufs: 1, 0
     Static/Strm HW 3D Bufs: 0, 0
                  HW Memory: 0
           Voice Management: No
     EAX(tm) 2.0 Listen/Src: No, No
       I3DL2(tm) Listen/Src: No, No
    Sensaura(tm) ZoomFX(tm): No
    
                Description: Realtek Digital Output (Realtek High Definition Audio)
     Default Sound Playback: No
     Default Voice Playback: No
                Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001
            Manufacturer ID: 1
                 Product ID: 100
                       Type: WDM
                Driver Name: RTKVHD64.sys
             Driver Version: 6.00.0001.6151 (English)
          Driver Attributes: Final Retail
                WHQL Logo'd: Yes
              Date and Size: 7/6/2010 18:31:36, 2419176 bytes
                Other Files: 
            Driver Provider: Realtek Semiconductor Corp.
             HW Accel Level: Basic
                  Cap Flags: 0xF1F
        Min/Max Sample Rate: 100, 200000
    Static/Strm HW Mix Bufs: 1, 0
     Static/Strm HW 3D Bufs: 0, 0
                  HW Memory: 0
           Voice Management: No
     EAX(tm) 2.0 Listen/Src: No, No
       I3DL2(tm) Listen/Src: No, No
    Sensaura(tm) ZoomFX(tm): No
    
                Description: Realtek HDMI Output (Realtek High Definition Audio)
     Default Sound Playback: No
     Default Voice Playback: No
                Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_0888&SUBSYS_10DE0175&REV_1001
            Manufacturer ID: 1
                 Product ID: 100
                       Type: WDM
                Driver Name: RTKVHD64.sys
             Driver Version: 6.00.0001.6151 (English)
          Driver Attributes: Final Retail
                WHQL Logo'd: Yes
              Date and Size: 7/6/2010 18:31:36, 2419176 bytes
                Other Files: 
            Driver Provider: Realtek Semiconductor Corp.
             HW Accel Level: Basic
                  Cap Flags: 0xF1F
        Min/Max Sample Rate: 100, 200000
    Static/Strm HW Mix Bufs: 1, 0
     Static/Strm HW 3D Bufs: 0, 0
                  HW Memory: 0
           Voice Management: No
     EAX(tm) 2.0 Listen/Src: No, No
       I3DL2(tm) Listen/Src: No, No
    Sensaura(tm) ZoomFX(tm): No

  24. #24
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by Nafensoriel View Post
    Latest drivers are as follows:
    Version:
    260.63 BETA
    Release Date:
    2010.09.14
    Yours are a few months out of date for both WHQL and BETA versions. If they are not installing and updating properly it might take a wipe/restart/reinstall to get them properly functioning again.(Had that problem myself a few days ago).
    Do actually know what you are talking about ? Or can properly read what I posted ? The WHQL is signed by driver date the last stable version of nvidia driver is 258, so of course it is signed on that date which was in July.

    I tried the recent 260 and had the same problem so I rolled back to the stable version since a beta did not fix it .

    The display driver is working fine and installed, deinstalled , updated properly.

  25. #25
    Join Date
    Sep 2010
    Posts
    29
    Just for reference, here is my dxdiag too. {shortened to fit here}
    If anyone can justify my crashes and freezes ,with some logical reasoning , is more than welcome to do so.



    ------------------
    System Information
    ------------------
    Time of this report: 10/6/2010, 21:25:14
    Machine name: MAINFRAME
    Operating System: Windows Vista™ Ultimate (6.0, Build 6002) Service Pack 2 (6002.vistasp2_gdr.100608-0458)
    Language: Greek (Regional Setting: Greek)
    System Manufacturer: System manufacturer
    System Model: System Product Name
    BIOS: Phoenix - AwardBIOS v6.00PG
    Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2 CPUs), ~2.4GHz
    Memory: 3070MB RAM
    Page File: 2036MB used, 4303MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    DxDiag Version: 7.00.6002.18107 32bit Unicode

    ------------
    DxDiag Notes
    ------------
    Display Tab 1: No problems found.
    Sound Tab 1: No problems found.
    Sound Tab 2: 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 8800 GTS
    Manufacturer: NVIDIA
    Chip type: GeForce 8800 GTS
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_10DE&DEV_0193&SUBSYS_22511682&REV_A2
    Display Memory: 1894 MB
    Dedicated Memory: 615 MB
    Shared Memory: 1279 MB
    Current Mode: 1280 x 1024 (32 bit) (60Hz)
    Monitor: Generic PnP Monitor
    Driver Name: nvd3dum.dll,nvwgf2um.dll,nvwgf2um.dll
    Driver Version: 8.17.0012.5896 (English)
    DDI Version: 10
    BGRA Supported: Yes
    Driver Attributes: Final Retail
    Driver Date/Size: 7/10/2010 01:37:00, 9818728 bytes
    WHQL Logo'd: Yes
    WHQL Date Stamp:
    Device Identifier: {D7B71E3E-42D3-11CF-3A62-5D021CC2C535}
    Vendor ID: 0x10DE
    Device ID: 0x0193
    SubSys ID: 0x22511682
    Revision ID: 0x00A2
    Revision ID: 0x00A2
    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=
    DDraw Status: Enabled
    D3D Status: Enabled
    AGP Status: Enabled

    -------------

  26. #26
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by ik25 View Post
    Just for reference, here is my dxdiag too. {shortened to fit here}
    If anyone can justify my crashes and freezes ,with some logical reasoning , is more than welcome to do so.
    Appears you have the exact same model of card as mine and same stable nvidia driver installed. Also I got a new freeze a few minutes ago. Funny how the binary dump says "unknown". PS. Still no word from the tickets on your end ?

    Code:
    Description:
      A problem caused this program to stop interacting with Windows.
    
    Problem signature:
      Problem Event Name:    AppHangB1
      Application Name:    CivilizationV_DX11.exe
      Application Version:    1.0.0.20
      Application Timestamp:    4ca37045
      Hang Signature:    260a
      Hang Type:    2048
      OS Version:    6.1.7600.2.0.0.256.4
      Locale ID:    1033
      Additional Hang Signature 1:    260a67857b12121fe6f196cf197bfe27
      Additional Hang Signature 2:    67dd
      Additional Hang Signature 3:    67ddce3120cebc9630abb4d55417f03c
      Additional Hang Signature 4:    260a
      Additional Hang Signature 5:    260a67857b12121fe6f196cf197bfe27
      Additional Hang Signature 6:    67dd
      Additional Hang Signature 7:    67ddce3120cebc9630abb4d55417f03c
    
    The program CivilizationV_DX11.exe version 1.0.0.20 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
     Process ID: 704
     Start Time: 01cb662b70895b60
     Termination Time: 554
     Application Path: c:\program files (x86)\steam\steamapps\common\sid meier's civilization v\CivilizationV_DX11.exe
     Report Id: 
    
    - System 
    
      - Provider 
    
       [ Name]  Application Hang 
     
      - EventID 1002 
    
       [ Qualifiers]  0 
     
       Level 2 
     
       Task 101 
     
       Keywords 0x80000000000000 
     
      - TimeCreated 
    
       [ SystemTime]  2010-10-07T14:33:01.000000000Z 
     
       EventRecordID 30116 
     
       Channel Application 
     
       Computer blackmetal 
     
       Security 
     
    
    - EventData 
    
       CivilizationV_DX11.exe 
       1.0.0.20 
       704 
       01cb662b70895b60 
       554 
       c:\program files (x86)\steam\steamapps\common\sid meier's civilization v\CivilizationV_DX11.exe 
        
       55006E006B006E006F0077006E0000000000 
    
    
    --------------------------------------------------------------------------------
    
    Binary data:
    
    
    In Words
    
    0000: 006E0055 006E006B 0077006F 0000006E 
    0008: 0000    
    
    
    In Bytes
    
    0000: 55 00 6E 00 6B 00 6E 00   U.n.k.n.
    0008: 6F 00 77 00 6E 00 00 00   o.w.n...
    0010: 00 00                     ..
    Last edited by tr0lltek; 10-06-2010 at 09:43 PM.

  27. #27
    The drivers should list differently for 258.96. However I checked with the installer and it seems to just like confusing folk like me. I don't have an 8800gts laying around at the moment but I'm going to borrow one from a coworker to see if I can reproduce this. If I remember correctly this card had a revision without actually changing the listed designation.

    Since I don't have the hardware in front of me do any of you have an older spare nvidia video card laying around you could pop in and do a quick test? It can even be DX9.. I just want to see if we can get SOMETHING working to build on. My gut tells me this one wont be fixed easily.. but the closer you get to isolating.. the faster the patch comes

  28. #28
    Join Date
    Sep 2010
    Posts
    29
    thanks tr0lltek.

    Unfortunately still no response yet for the ticket .

  29. #29
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by Nafensoriel View Post
    The drivers should list differently for 258.96. However I checked with the installer and it seems to just like confusing folk like me. I don't have an 8800gts laying around at the moment but I'm going to borrow one from a coworker to see if I can reproduce this. If I remember correctly this card had a revision without actually changing the listed designation.

    Since I don't have the hardware in front of me do any of you have an older spare nvidia video card laying around you could pop in and do a quick test? It can even be DX9.. I just want to see if we can get SOMETHING working to build on. My gut tells me this one wont be fixed easily.. but the closer you get to isolating.. the faster the patch comes
    Yes I know what you mean, sorry if I was somewhat snappy but I am getting really frustrated with this issue, been 2 weeks and still cannot play. The 258 is on the end somewhat confusing:

    Code:
    Driver File Version: 8.17.0012.5896 (English)
         Driver Version: 8.17.12.5896
    I do not have an older card than this to play around with unfortunately. I even took out 1 card from the sli and deactivated all things sli in hopes it was a sli issue . That did not help either. SLI wasn't really working for me on civ V anyways the second card was showing around 2 -5 % utilisation while the 1 card in the bundle was around 95 - 98 %.

    Just to clarify I have 2 older cards from the g8 series. My brother has a similar card but the g92 chip, which is also having similar issues. I think this maybe the revision you are talking about. Anyways it is not working on his card either. DX9 will play on my system but also freeze up and throw an app hang but a little bit longer into the game. Say maybe 150 - 200 turns instead of 20 - 30 on DX11.

    I really am not sure with these cards if it completely a civ 5 issue it may well be, but also in reference to something in the nvidia drivers or the current versions of dx11, and everything mixed together with the way civ engine wants to render the graphics through the drivers and direct3d. On the official nvidia forums other 8800 users have reported similar issues like mine and ik25. Also the loading screen on this card is always black until the ESRB comes, doesn't matter if I load from steam (DX 9 or 11) or if I just load the .exe from the steam folder in offline mode. Which tells me this issue is somewhat graphic related to civ.

    I am planning on upgrading my cards to 480's as holiday gift to myself anyways. But it would be really nice to play a game of civ 5 before that happens. If something doesn't happen soon I might just try and justify upgrading cards for the sake of being a civ junky.

    Thanks for helping .

  30. #30
    Join Date
    Sep 2010
    Posts
    343
    Quote Originally Posted by tr0lltek View Post
    And you base this on what ? Direct3D 10.1 runtime can run on Direct3D 10.0 hardware .
    Nope sorry, needs it own rendering path created by the game. It can not use the same path as 10.1 or 11. Just like 9 can not use a direct x 10 rendering path, hence why it is a different exe.

    But you want proof, ok. Easy enough.
    http://www.extremetech.com/article2/...2168429,00.asp
    DX 10.1 hardware will be backwards compatible with DirectX 10, but current DX10 hardware won't be forward compatible. So games looking to support DX 10.1 still need a DX 10 rendering path to support today's DX10 cards.
    From Microsoft themselves, admit, if you are creating a video game you need to render paths for 9c, 10, 10.1/11. Separate. Of course I do this for a living, so I kind of know what I am talking about.

  31. #31
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by Draco View Post
    Nope sorry, needs it own rendering path created by the game. It can not use the same path as 10.1 or 11. Just like 9 can not use a direct x 10 rendering path, hence why it is a different exe.

    But you want proof, ok. Easy enough.
    http://www.extremetech.com/article2/...2168429,00.asp


    From Microsoft themselves, admit, if you are creating a video game you need to render paths for 9c, 10, 10.1/11. Separate. Of course I do this for a living, so I kind of know what I am talking about.
    You do this for a living? Damn Ill quote the msdn from direct3d sdk library. Of course some calls will fail because the extensions are not in the chip but it is still compatible.

    http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx

    Quote Originally Posted by http://msdn.microsoft.com/en-us/library/bb694530%28VS.85%29.aspx
    These developers can use the Direct3D 10.1 headers and libraries exclusively, taking a dependency on the Direct3D 10.1 DLLs which support both 10.0 and 10.1 hardware (some calls may fail, however, on 10.0 devices where the new functionality is not supported).


    * The APIs exposed in the D3DX10.dll will accept both 10.0 and 10.1 devices, and will take advantage of 10.1 functionality when available.
    * D3D10SDKLayers.dll supports a 10.1 device and can output the appropriate debug spew for 10.1 features.
    * D3D10Ref.dll implements a 10.0 and 10.1 software device.
    * D3DX10 and FXC support the updated 10.1 shader model with the following targets: vs_4_1, gs_4_1, ps_4_1, and fx_4_1 which can be bound to a 10.1 device. A 10.1 device supports shader model 4.0 and 4.1 shaders.
    * The Direct3D 10.0 effect framework supports 10.0 and 10.1 devices, however, any technique that includes shader model 4.1 shaders or the new 10.1 features must use a 10.1 device.
    Last edited by tr0lltek; 10-07-2010 at 03:50 AM.

  32. #32
    Join Date
    Sep 2010
    Posts
    29
    Finally I got something today from the EU support.

    Got a response requesting the dxdiag.

    Will do that and see , what the "experts" will say, hopefully before Christmas.

  33. #33
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by ik25 View Post
    Finally I got something today from the EU support.

    Got a response requesting the dxdiag.

    Will do that and see , what the "experts" will say, hopefully before Christmas.
    hey good news , at least one step forward . I have not gotten anything yet hopefully soon then. If not Ill just start some new tickets.

  34. #34
    Join Date
    Sep 2010
    Posts
    343
    Quote Originally Posted by tr0lltek View Post
    You do this for a living? Damn no wonder so many problems these days
    LOL, just went for it didn't you, but you missed one little fact. Just one little thing.

    In Windows Vista Service Pack 1, Direct3D 10.0 and Direct3D 10.1 DLLs exist side-by-side on the system. To access 10.1 features, do either of the following:
    Comprehension is good.

    What you quoted simply states that if you use direct x 10 software, it will work on a 10.1 card, but you have to offer the rendering path to the 10 dll's. The direct x 10 card can not use the 10.1 dll's with out offering a path to the side by side functions of 10. You have to offer the rendering path, you still have to code for 10, but you can use SOME of the dll's from 10.1.

    (some calls may fail, however, on 10.0 devices where the new functionality is not supported).
    When a direct x call fails, it either locks up the game, crashes the game, runtime error, or blue screens the game. Which is happening with Civ 5.

    The default calls ask for only direct x 10.1 call at start up, do not offer a direct x 10 rendering path, making the game un-startable or crash prone.

    You see the problem? I do not think you still get it. So let me run it down.

    Game starts->rendering path 10.1->Card fails to call function->game locks up, bluescreens, runtime errors, or crashes.

    There is not way to turn off these functions, because the direct x 10.1 calls are defaulted into the game, at lowest setting. You can not run the game on direct x 10 card, using 10/11 exe. There is no option to use the 10 calls, they are not programed for.

    Now if the game went,

    Game starts-> check card-> Rendering path 10 or 10.1-> game would start.

    Because the failed call functions would not happen. You have to program the rendering path. Civ 5 is programed to use the functions that are not supported by 10.

  35. #35
    Join Date
    Sep 2010
    Posts
    21
    Quote Originally Posted by Draco View Post
    LOL, just went for it didn't you, but you missed one little fact. Just one little thing.



    Comprehension is good.

    What you quoted simply states that if you use direct x 10 software, it will work on a 10.1 card, but you have to offer the rendering path to the 10 dll's. The direct x 10 card can not use the 10.1 dll's with out offering a path to the side by side functions of 10. You have to offer the rendering path, you still have to code for 10, but you can use SOME of the dll's from 10.1.



    When a direct x call fails, it either locks up the game, crashes the game, runtime error, or blue screens the game. Which is happening with Civ 5.

    The default calls ask for only direct x 10.1 call at start up, do not offer a direct x 10 rendering path, making the game un-startable or crash prone.

    You see the problem? I do not think you still get it. So let me run it down.

    Game starts->rendering path 10.1->Card fails to call function->game locks up, bluescreens, runtime errors, or crashes.

    There is not way to turn off these functions, because the direct x 10.1 calls are defaulted into the game, at lowest setting. You can not run the game on direct x 10 card, using 10/11 exe. There is no option to use the 10 calls, they are not programed for.

    Now if the game went,

    Game starts-> check card-> Rendering path 10 or 10.1-> game would start.

    Because the failed call functions would not happen. You have to program the rendering path. Civ 5 is programed to use the functions that are not supported by 10.
    You dont need to dumb it down. If your statements are true , are you then official from 2k or firaxis ?

    Game starts-> check card-> Rendering path 10 or 10.1-> game would start.

    Isnt this how is was suppose to be ? Using createdevice function? looking for compatible hardware and creating the driver device. Also using the newer driver type enumeration /rasterizer. like here:

    http://msdn.microsoft.com/en-us/libr...=VS.85%29.aspx

    I do not know _a lot_ from dx but only a little from when I used to code with opengl and compare the api. Tbh I really don't care DX10 was also recommended by default for my system.

    Also why then do I get freezes playing in directx9 ? Not as soon but prolonged. This is my main concern because that should not be an issue.

    If V is missing the compatible calls for d3d10 then they should have stated as much in requirements 10.1 + cards or higher when playing dx10/11. Or completely separated all d3d versions, like you are saying.

    Other games I haven't had any problems with 10.1 running on the 8800 cards.
    Last edited by tr0lltek; 10-07-2010 at 04:23 AM.

  36. #36
    Join Date
    Sep 2010
    Posts
    21
    damn double post nothing to see here move along

    well just for the record: http://www.2kgames.com/civ5/support/#systemreqs

    Operating System: Windows® XP
    Processor: Intel Core 2 Duo 1.8 GHZ or AMD Athlon X2 64 2.0 GHZ
    Memory: 2 GB RAM
    Hard Disk Space: 8 GB Free
    DVD-ROM Drive: Required for disc-based installation
    Video: 256 MB ATI HD2600 XT or better, 256 MB nVidia 7900 GS or better, or Core i3 or better integrated graphics (see note)*
    Sound: DirectX 9.0c-compatible sound card
    DirectX®: DirectX® version 9.0c



    Recommended System Requirements

    Operating System: Windows® Vista/7
    Processor: 1.8 GHz Quad Core CPU
    Memory: 4 GB RAM
    Hard Disk Space: 8 GB Free
    DVD-ROM Drive: Required for disc-based installation
    Video: 512 MB ATI 4800 series or better, 512 MB nVidia 9800 series or better
    Sound: DirectX 9.0c-compatible sound ca
    Operating System: Windows® Vista/7
    Processor: 1.8 GHz Quad Core CPU
    Memory: 4 GB RAM
    Hard Disk Space: 8 GB Free
    DVD-ROM Drive: Required for disc-based installation
    Video: 512 MB ATI 4800 series or better, 512 MB nVidia 9800 series or better
    Sound: DirectX 9.0c-compatible sound card
    DirectX®: DirectX® version 11
    Last edited by tr0lltek; 10-07-2010 at 04:31 AM.

  37. #37
    Join Date
    Sep 2010
    Posts
    21
    actually F*** it ill just cancel payment on my credit card and not think twice. sick of having to look at an api just to fix a finished product I paid for. I Wish i2k luck with his problem.

  38. #38
    Join Date
    Jul 2010
    Posts
    159
    Quote Originally Posted by Draco View Post
    The default calls ask for only direct x 10.1 call at start up, do not offer a direct x 10 rendering path, making the game un-startable or crash prone.
    ok, let's say you are right and they programmed specifically for 10.1 (god knows why?)

    the problems here are:
    - shortcut says dx10/11, not dx10.1/11 so, their mistake, not ours.
    - this is only one exe for 2 versions of directx, i think that's because MS said that directx 11 will AUTOMATICALLY reverse to anterior version if detecting a none-dx11 card so dx10 card shouldn't stille be a problem.
    - in dx10/11 mode, i managed to make 40 turns and 65 turns straight with the game running PERFECTLY (much better and prettier than in dx9 mode) but other time it crashed directly after load, on the same setting (graphics, map, ia level...etc)
    so it means my card is perfectly fit to run this game with no degradation so a random lockup is most likely due to a lockup in the game engine maybe due to bad multithreading implementation in the dx10+ version (dx9 has not such builtin support i think)

    in the end, the lockups could very well be due to calls from missing functions, but even if it's the case, it's merely BAD implementation because at minima the code should only call available functions and ignoring useless features (while not crashing, all was very nice)

    i may add that in dx9 mode, the engine big memory leakings ultimately lead to ctd on a huge map, even if i managed to extend past 600 turns lowering details and playing merely in strategic view and pointing to a fog of war area between 2 turns (unit moving in a turn in the viewed area tend to crash the game)
    so, this game using like 2.5Gb is a joke, come on, anno 1404 is far prettier, has much more things going on in REAL TIME and (after patches) never got past 1.8Gb on a big map with high details.

    so the game going on very well for some time, and locking in the same situation other time is likely to have code problem, not hardware.

  39. #39
    Not quite true.

    Microsoft themselves, dont differentiate 10 and 10.1 in any meaningful way.

    It is Akin to the Blu-Ray profiles

    1.0 1.1 2.0 etc, theyre all blu-Ray's but its unfortuneately up to us as consumers, to know what we have

    And saying that it ran perfectly for 40 60 or even 500 turns, doesnt mean it will not crash, when running in a mode not supported by your hardware

    DX 10.1 is one of the most frustrating things microsoft has ever done to gamers, and another reason, why i exclusively console game now.

    Civ5 is the first PC game ive bought, since Civ4

  40. #40
    Join Date
    Sep 2010
    Posts
    343
    Quote Originally Posted by tr0lltek View Post
    You dont need to dumb it down. If your statements are true , are you then official from 2k or firaxis ?

    Game starts-> check card-> Rendering path 10 or 10.1-> game would start.

    Isnt this how is was suppose to be ?
    I have nothing, zip, zero, nada, to do with anyone that has anything to do with this game. Period. I would not have anything to do with them. Period.

    I know code.

    Microsoft told developers that the rendering path for 10 to 10.1 would be the same, they out and out lied. They told the rendering path to 10.1 to 11 would be the same. Which is a slight lie, but does work. But it defaults to 10.1, only allowing the user to change to 11. But it does not directly render to 11.

    Every time you start a directx 11 game, it renders path to 10.1, then only starts the dll's need for 11 after the game is booted. Looking at the code, in my completely unprofessional opinion, they coded it for consoles. The rendering path from direct x 9 to 11 means nothing to consoles. Only for windows.

    In the end, this game has some huge problems.

    Bottom line, they believed what everyone knows is a lie. They got suckered into rendering it for 10/11. Not 10/10.1 and 10.1/11.

    I will do this, I have a 8800gtx somewhere round here, I will go into the files, screw around until I get it to work.

    No promises.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •