Page 1 of 2 12 LastLast
Results 1 to 10 of 18

  Click here to go to the first Developer post in this thread.  

Thread: TH2G problem with Patch 1.02 build 58134

  1. #1

    TH2G problem with Patch 1.02 build 58134

    yes. i am running newest patch build..
    v102_58134

    I CAN NOT PLAY PLAY ARMA2 with triplehead2go
    It will run at 1680x1050 on one monitor, but when i enable triplehead (4320x900)
    i get a message saying unable to create graphical engine error message.

    i am running Vista x64 SP2
    8 Gigs of Ram
    8800GTS 512 w/ v186.18 nvidia driver
    Powerdesk Version 2.05

    (i had better luck with nvidia v180.48 and powerdesk v2.04) but still gives me the error, if i start messing around with ther other graphics settings


    On top of the triplehead problem, i have graphic anomolies playing at 1680x1050 where cockpit windows look like static noise, and objects have a polygonish boxes that exist all over the game... (i think this is due to having 8Gigs of RAM or more..)

    BIS PLZ FIX....

  2.   This is the last Developer post in this thread.   #2
    seems like problem with 8GB RAM again, will be fixed in future

    please use commandline paramater -winxp

    e.g. arma2.exe -winxp

  3. #3
    OK, I will check that out.
    (for now i can run the game ok at single screen 1680x1050 and msconfig max memory set to 4Gigs -1 byte)

    for the triplehead problem, i tried V-Sync ON and OFF... no joy there...

  4. #4
    I am on Vista x64
    core2duo E8500
    6 Gig Ram
    8800GTS 512
    Powerdesk 2.05
    Nvidia 186.18
    PhysiX disabled

    I tired the command lines arguments,
    I AM STILL GET THE "Error creating Direct 3D 9 Gpahical engine
    when i try to run triplehead @ 4320x900

    in my shortcut, i set my target as:
    "C:\arma2.exe" -winxp -maxmem=2047 -cpuCount=2

    the game runs fine at single screen 1680x1050

    but NO Triplehead2go!!!!!!!!!
    (Note.. triplehead works after change settings from singlescreen to triplescreen BUT error appears when you start the game the next time around)
    force OFF V-sync does not help either...
    Last edited by hannibal636; Jun 29 2009 at 23:09.

  5. #5
    Triplehead2 Go Dosent work with beta 190.15 nvida either....

    PLZ FIX SOON!

  6. #6
    CWR² Developer Bushlurker's Avatar
    Join Date
    Aug 27 2004
    Location
    Under a bush, somewhere in Scotland...
    Posts
    1,807
    have you tried backtracking to an earlier driver version???

    Might be worth trying 182.50


  7. #7
    Quote Originally Posted by Bushlurker View Post
    have you tried backtracking to an earlier driver version???

    Might be worth trying 182.50

    I went back to 182.50 nvidia driver with powerdesk 2.04 (182.50 will not work PROPERLY with latest powerdesk 2.05)

    Triplehead2GO is BONKED WITH ARMA2 even with 182.50....!

    works fine for me with single screen.
    Last edited by hannibal636; Jul 1 2009 at 10:51.

  8. #8

    Another TH2G and Patch 102 build 58134 issue

    I had ArmA 2 in 1.01 nicely up and running with a Matrox TH2G in a 5040 x 1050 resolution.

    After applying Patch 1.02 build 58134 I got the infamous message "Error creating direct3d 9 graphical engine".

    I did the usual troubleshooting: -winxp parameter; removing config files; lowering memory in msconfig to 3070.
    To no avail.

    I did a rollback to version 1.01 and the ArmA 2 was running ok again.

    Looks like Patch 1.02 build 58134 doesn't like Matrox TripleHeads2Go.

    Also there might be a difference between the normal (<= 3840 x 1024) TH2G resolutions and the widescreen TH2G resolutions (up to 5040 x 1050, only with nVidia 200 series graphic cards, like the GTX 280 or 285).

    Is anybody out there with a TH2G who has it up and running with Patch 1.02 build 58134 ? And in what resolution ?

  9. #9
    Same issues.

    9800GTX+
    Q6600
    TH2G Digitial
    3x 1680x1050 screens
    Win7 RC 64bit
    6GB RAM

    Works fine on single 1680x1050. Dog's breakfast when trying to do triplehead modes, fullscreen or windowed. Latest drivers on everything as of yesterday when I rebuilt my rig.
    Last edited by vaaf_rup; Jul 8 2009 at 06:38.
    -- Before you criticise someone, walk a mile in their shoes. Then, when you criticise them, you&#39;re a mile away and you have their shoes.
    Virtual Australian Armed Forces: http://www.vaaf.net

  10. #10
    Quote Originally Posted by Gone Native View Post
    I had ArmA 2 in 1.01 nicely up and running with a Matrox TH2G in a 5040 x 1050 resolution.

    ...

    I did a rollback to version 1.01 and the ArmA 2 was running ok again.

    Looks like Patch 1.02 build 58134 doesn't like Matrox TripleHeads2Go.

    ...
    Yes I'm in the same boat. Was fine in 1.01, upgraded to 1.02 and it no longer works.

    Axek.

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
  •