With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
Gigabyte x99 gaming 5p Intel 5930k 16gb Kingston Fury Sli Kfa Hof 980ti 500gb Samsung Evo Ssd Corsair hx v2 850w HafX Case + Full set of Demciflex filters Sony 8505 4k 3d
[quote name='mocca' date='02 February 2012 - 03:16 AM' timestamp='1328174183' post='1364044']
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
[/quote]
I actually do not have this problem, and Dirt3 still works in 3D. Only issue I noticed is that 3D does not automatically start like it should, and I have to manually press the pyramid button, or Ctrl-T. What settings are you using? What is your hardware? Mine is Phenom 2 X6, 8Gb ram, 2xGTX570 in SLI, win 7 64 bit.
[quote name='mocca' date='02 February 2012 - 03:16 AM' timestamp='1328174183' post='1364044']
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
I actually do not have this problem, and Dirt3 still works in 3D. Only issue I noticed is that 3D does not automatically start like it should, and I have to manually press the pyramid button, or Ctrl-T. What settings are you using? What is your hardware? Mine is Phenom 2 X6, 8Gb ram, 2xGTX570 in SLI, win 7 64 bit.
[quote name='mocca' date='02 February 2012 - 02:46 PM' timestamp='1328174183' post='1364044']
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
[/quote]
Nothing wrong with my system, game crashes at start of a race or at race loading screen, previous drivers work ok.
Last night crash pionted to a nvidia driver, but it's not so today?
Crash log is.
Problem Event Name: BEX
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: StackHash_4658
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00073a00
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 4658
Additional Information 2: 46583b407fe60adec22cbb356dfa81d6
Additional Information 3: 7e10
Additional Information 4: 7e1005a4353f9e3d4cd0221fc831c501
Nothing wrong with my system, game crashes at start of a race or at race loading screen, previous drivers work ok.
Last night crash pionted to a nvidia driver, but it's not so today?
Crash log is.
Problem Event Name: BEX
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: StackHash_4658
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00073a00
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 4658
Additional Information 2: 46583b407fe60adec22cbb356dfa81d6
Additional Information 3: 7e10
Additional Information 4: 7e1005a4353f9e3d4cd0221fc831c501
Gigabyte x99 gaming 5p Intel 5930k 16gb Kingston Fury Sli Kfa Hof 980ti 500gb Samsung Evo Ssd Corsair hx v2 850w HafX Case + Full set of Demciflex filters Sony 8505 4k 3d
OK, I did some more testing, and I can also confirm that I am (now) getting the same crashing. I have no idea why, but when I tried to launch from Steam tonight it said the game was not available, so I verified the game cache, started it and it did an 'installing for first time' thing, then I get the same problem with crashing:
Problem Event Name: APPCRASH
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: nvwgf2um.dll
Fault Module Version: 8.17.12.9551
Fault Module Timestamp: 4f212347
Exception Code: c0000005
Exception Offset: 000e9139
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Scenarios vary from crashing at the load screen, to starting a game, to crashing after playing for 3 minutes. Also, it does not *always* crash - I ran the benchmark a few times for example with no issues, but I did reduce quality levels a bit first.
I have not tried different game settings to see what it might be. I'm not going to try DX9 because 3D Vision does not work properly with that.
OK, I did some more testing, and I can also confirm that I am (now) getting the same crashing. I have no idea why, but when I tried to launch from Steam tonight it said the game was not available, so I verified the game cache, started it and it did an 'installing for first time' thing, then I get the same problem with crashing:
Problem Event Name: APPCRASH
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: nvwgf2um.dll
Fault Module Version: 8.17.12.9551
Fault Module Timestamp: 4f212347
Exception Code: c0000005
Exception Offset: 000e9139
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Scenarios vary from crashing at the load screen, to starting a game, to crashing after playing for 3 minutes. Also, it does not *always* crash - I ran the benchmark a few times for example with no issues, but I did reduce quality levels a bit first.
I have not tried different game settings to see what it might be. I'm not going to try DX9 because 3D Vision does not work properly with that.
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below: GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
[quote name='ManuelG' date='02 February 2012 - 09:12 PM' timestamp='1328235152' post='1364446']
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
[/quote]
playing Dirt 3 over Steam in 3D Vision @ 1024x768
it used to crash once in a while between races in R290.53 (!never within a race!) but it is now crashing all the time a few secs after starting a race (like monaco head2head for instance).
[quote name='ManuelG' date='02 February 2012 - 09:12 PM' timestamp='1328235152' post='1364446']
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
playing Dirt 3 over Steam in 3D Vision @ 1024x768
it used to crash once in a while between races in R290.53 (!never within a race!) but it is now crashing all the time a few secs after starting a race (like monaco head2head for instance).
Since the latest beta, My dirt3 is crashing aswell. But i run mine in 2d surround mode. I have a single 3d monitor for the centre screen, And notice when starting up dirt3 the 3d light on the usb controller lights up for a couple secs like 3dvision is being enabled then the light goes out. (checked the control panel and yep 3dvision is disabled so it should not do that)
Same as others in that it crashed at the very start of a race, or in-race.
Will revert back to the 290.53's to test again. (but from memory never had any crashes with that driver in 2d surround)
*******
UPDATE
Ok reverted back to 290.53 and dirt3 runs fine with no crashing in2d surround. SO something in the latest beta is causing it Manuel.
Since the latest beta, My dirt3 is crashing aswell. But i run mine in 2d surround mode. I have a single 3d monitor for the centre screen, And notice when starting up dirt3 the 3d light on the usb controller lights up for a couple secs like 3dvision is being enabled then the light goes out. (checked the control panel and yep 3dvision is disabled so it should not do that)
Same as others in that it crashed at the very start of a race, or in-race.
Will revert back to the 290.53's to test again. (but from memory never had any crashes with that driver in 2d surround)
*******
UPDATE
Ok reverted back to 290.53 and dirt3 runs fine with no crashing in2d surround. SO something in the latest beta is causing it Manuel.
i7 3820 | 16GB G.Skill F3-12800CL9Q-16GBZL | Gigabyte X79 UD3 | GTX 680 SLI | Intel 320-80gig, 120gig Corsair Force 3, 240gig Silicon Magic +4xHD | Coolermaster Silent Pro M1000 | CoolerMaster Haf-X | Asus 3d VH278H | X-Fi Titanium Fatal1ty Pro | SteelSeries 7H-USB | Coolermaster Hyper 212 EVO
hello
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
[quote name='kiss4luna' date='06 February 2012 - 02:40 AM' timestamp='1328514029' post='1365777']
hello
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
[/quote]
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
[quote name='kiss4luna' date='06 February 2012 - 02:40 AM' timestamp='1328514029' post='1365777']
hello
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
[quote name='mike_ar69' date='06 February 2012 - 09:46 PM' timestamp='1328535990' post='1365872']
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
[/quote]
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
[quote name='mike_ar69' date='06 February 2012 - 09:46 PM' timestamp='1328535990' post='1365872']
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
[quote name='kiss4luna' date='06 February 2012 - 09:27 PM' timestamp='1328581661' post='1366212']
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
[/quote]
3D Vision support (for the DX11 version, there is no support for DX9) requires the 1.02 game patch. I am not sure what problems gfwl has because I use Steam and I think I got the update there, but I will say that if you like driving games in stereo 3D then the 1.02 version of Dirt 3 is pretty awesome: all the dust, snow, lights (day and night), and shadows work perfectly. So take a chance, back up your files, and go for it. The only issues are that water reflections (on lakes) are a bit wrong (but who cares you only see them in cut scenes), and reflections on the car hood, while 'depth correct' from a stereo perspective, look 'painted on' the hood surface but it still looks good. Lens flare is annoying in any game, and this continues to be the case in Dirt 3.
[quote name='kiss4luna' date='06 February 2012 - 09:27 PM' timestamp='1328581661' post='1366212']
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
3D Vision support (for the DX11 version, there is no support for DX9) requires the 1.02 game patch. I am not sure what problems gfwl has because I use Steam and I think I got the update there, but I will say that if you like driving games in stereo 3D then the 1.02 version of Dirt 3 is pretty awesome: all the dust, snow, lights (day and night), and shadows work perfectly. So take a chance, back up your files, and go for it. The only issues are that water reflections (on lakes) are a bit wrong (but who cares you only see them in cut scenes), and reflections on the car hood, while 'depth correct' from a stereo perspective, look 'painted on' the hood surface but it still looks good. Lens flare is annoying in any game, and this continues to be the case in Dirt 3.
--------------------------------------------------------------------------------
[b]Found a solution/workaround for this issue on my system - using SLI and 3D-Vision for Dirt3 with the 295.51 drivers. I had to alter the [b]CUDA - GPUs[/b] setting for the dirt3.exe under 3D settings from standard using both to 1 of 2 or 2 of 2 (so only one card ).[/b]
Had a lot of other issues popping up with this new 295.51beta driver as well. One was a problem with the USB-Transmitter, solved by adding another USB-Card Transcend TS-PDU3 (connected to the PSU/ the IRQs of the GPUs are still the same) because with the new 195.51 driver the transmitter went offline from time to time. This changed unfortunately the 3d-vision setting automaticly to [b]3D-Vision Discover[/b] [b]without a notice[/b]. You might notice it when the MSN messenger changed its colours.
Now connected to the new USB 3.0 card it doesn´t do this anymore. I faced also the issue that the resulution changed after reboot again and again. I did study the Release Notes and found the hint NOT to uninstall the GPUs via the Windows device manager, always it has to be done using the Controlpanel / Software if you use W7. May be some stuff went wrong while installing the drivers. In total I spent more than 15 hours to solve all the problems. I had a spare 470GTX , so I started to swap cards and so on, but all 3 cards are O.K. At some point I couldn´t activate SLI, two minutes before the system told me to shut it down, add the SLI bridge and reboot ( I could reproduce this also after swapping or replacing the cards).
A workaround for the resolution change after reboot was to disable and enable the cards in the devicemanager. But you have to do the disable and enable very quick ( before the monitor wents black from the disable action). This always helped with the resolution.
But certainly I wasn´t happy with this and I tried more things. [b]Now all is good and works without any workaround [/b]like a charm
[b](with CUDA - GPUs setting for the dirt3.exe under 3D settings back to standard)[/b].
Within the last weeks I also faced random crashes in BF3( me always using the latest beta drivers), this problem is also solved now.
Also I do remember the message after reboot many times about the shortcuthandler to allow it doing changes to the system ( I used several restorepoints for investigation, certainly also one reason for this repetitions).
Benchmark 1920x1080 average ca. 80FPS all maxed out, just post processing on the lowest setting ( with 3D Vision enabled only average 40FPS )
a translation into German (just the most important stuff):
Bei einem [b]SLI-PC[/b] ([b]2x470GTX, W7x64, I7 no Virtu Software installed, Z68, 295.51, 16GB, 3D-Brille, no overclocking[/b]) war es notwendig unter [b]3D-Einstellungen verwalten für die Dirt3.exe den Standardwert CUDA - GPUs von beide auf 1 von 2[/b] anzupassen. Seither keine Abstürtze mehr. Läuft nun alles auf MAX, nur Nachbearbeitung auf den geringst möglichen Wert.
Hinweis: SLI läuft auch mit dieser geänderten Einstellung.
Benchmark 1920x1080 average ca. 80FPS ( mit 3D-Brille halbiert sich dieser Wert )
Found a solution/workaround for this issue on my system - using SLI and 3D-Vision for Dirt3 with the 295.51 drivers. I had to alter the CUDA - GPUs setting for the dirt3.exe under 3D settings from standard using both to 1 of 2 or 2 of 2 (so only one card ).
Had a lot of other issues popping up with this new 295.51beta driver as well. One was a problem with the USB-Transmitter, solved by adding another USB-Card Transcend TS-PDU3 (connected to the PSU/ the IRQs of the GPUs are still the same) because with the new 195.51 driver the transmitter went offline from time to time. This changed unfortunately the 3d-vision setting automaticly to 3D-Vision Discoverwithout a notice. You might notice it when the MSN messenger changed its colours.
Now connected to the new USB 3.0 card it doesn´t do this anymore. I faced also the issue that the resulution changed after reboot again and again. I did study the Release Notes and found the hint NOT to uninstall the GPUs via the Windows device manager, always it has to be done using the Controlpanel / Software if you use W7. May be some stuff went wrong while installing the drivers. In total I spent more than 15 hours to solve all the problems. I had a spare 470GTX , so I started to swap cards and so on, but all 3 cards are O.K. At some point I couldn´t activate SLI, two minutes before the system told me to shut it down, add the SLI bridge and reboot ( I could reproduce this also after swapping or replacing the cards).
A workaround for the resolution change after reboot was to disable and enable the cards in the devicemanager. But you have to do the disable and enable very quick ( before the monitor wents black from the disable action). This always helped with the resolution.
But certainly I wasn´t happy with this and I tried more things. Now all is good and works without any workaround like a charm
(with CUDA - GPUs setting for the dirt3.exe under 3D settings back to standard).
Within the last weeks I also faced random crashes in BF3( me always using the latest beta drivers), this problem is also solved now.
Also I do remember the message after reboot many times about the shortcuthandler to allow it doing changes to the system ( I used several restorepoints for investigation, certainly also one reason for this repetitions).
Benchmark 1920x1080 average ca. 80FPS all maxed out, just post processing on the lowest setting ( with 3D Vision enabled only average 40FPS )
a translation into German (just the most important stuff):
Bei einem SLI-PC (2x470GTX, W7x64, I7 no Virtu Software installed, Z68, 295.51, 16GB, 3D-Brille, no overclocking) war es notwendig unter 3D-Einstellungen verwalten für die Dirt3.exe den Standardwert CUDA - GPUs von beide auf 1 von 2 anzupassen. Seither keine Abstürtze mehr. Läuft nun alles auf MAX, nur Nachbearbeitung auf den geringst möglichen Wert.
Hinweis: SLI läuft auch mit dieser geänderten Einstellung.
Benchmark 1920x1080 average ca. 80FPS ( mit 3D-Brille halbiert sich dieser Wert )
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
Gigabyte x99 gaming 5p Intel 5930k 16gb Kingston Fury Sli Kfa Hof 980ti 500gb Samsung Evo Ssd Corsair hx v2 850w HafX Case + Full set of Demciflex filters Sony 8505 4k 3d
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
[/quote]
I actually do not have this problem, and Dirt3 still works in 3D. Only issue I noticed is that 3D does not automatically start like it should, and I have to manually press the pyramid button, or Ctrl-T. What settings are you using? What is your hardware? Mine is Phenom 2 X6, 8Gb ram, 2xGTX570 in SLI, win 7 64 bit.
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
I actually do not have this problem, and Dirt3 still works in 3D. Only issue I noticed is that 3D does not automatically start like it should, and I have to manually press the pyramid button, or Ctrl-T. What settings are you using? What is your hardware? Mine is Phenom 2 X6, 8Gb ram, 2xGTX570 in SLI, win 7 64 bit.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
[/quote]
System configuration?
Hi,
With latest beta Dirt 3 no longer works in 3d, crash pionts to nvidia drivers, plays fine in 2d.
System configuration?
NVIDIA Bug Report
NVIDIA newsletter
3D Vision System Requirements
3DTV System Requirements
sli gtx 570
Nothing wrong with my system, game crashes at start of a race or at race loading screen, previous drivers work ok.
Last night crash pionted to a nvidia driver, but it's not so today?
Crash log is.
Problem Event Name: BEX
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: StackHash_4658
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00073a00
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 4658
Additional Information 2: 46583b407fe60adec22cbb356dfa81d6
Additional Information 3: 7e10
Additional Information 4: 7e1005a4353f9e3d4cd0221fc831c501
sli gtx 570
Nothing wrong with my system, game crashes at start of a race or at race loading screen, previous drivers work ok.
Last night crash pionted to a nvidia driver, but it's not so today?
Crash log is.
Problem Event Name: BEX
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: StackHash_4658
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 00073a00
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: 4658
Additional Information 2: 46583b407fe60adec22cbb356dfa81d6
Additional Information 3: 7e10
Additional Information 4: 7e1005a4353f9e3d4cd0221fc831c501
Gigabyte x99 gaming 5p Intel 5930k 16gb Kingston Fury Sli Kfa Hof 980ti 500gb Samsung Evo Ssd Corsair hx v2 850w HafX Case + Full set of Demciflex filters Sony 8505 4k 3d
NVIDIA Display Driver Feedback-Form
Problem Event Name: APPCRASH
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: nvwgf2um.dll
Fault Module Version: 8.17.12.9551
Fault Module Timestamp: 4f212347
Exception Code: c0000005
Exception Offset: 000e9139
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Scenarios vary from crashing at the load screen, to starting a game, to crashing after playing for 3 minutes. Also, it does not *always* crash - I ran the benchmark a few times for example with no issues, but I did reduce quality levels a bit first.
I have not tried different game settings to see what it might be. I'm not going to try DX9 because 3D Vision does not work properly with that.
Problem Event Name: APPCRASH
Application Name: dirt3_game.exe
Application Version: 1.2.0.0
Application Timestamp: 4e2d973a
Fault Module Name: nvwgf2um.dll
Fault Module Version: 8.17.12.9551
Fault Module Timestamp: 4f212347
Exception Code: c0000005
Exception Offset: 000e9139
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Scenarios vary from crashing at the load screen, to starting a game, to crashing after playing for 3 minutes. Also, it does not *always* crash - I ran the benchmark a few times for example with no issues, but I did reduce quality levels a bit first.
I have not tried different game settings to see what it might be. I'm not going to try DX9 because 3D Vision does not work properly with that.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
We can't fix your bug if we can't reproduce it. Please provide as much details as possible including specs, steps to reproduce, graphics settings used, etc..
For GeForce driver issues, please leave feedback in driver feedback form: Driver Feedback
For GeForce Now PC issues, please fill out feedback form below:
GFN PC Feedback
For SHIELD Android TV issues/requests, please leave feedback in the SHIELD feedback form: SHIELD Feedback
I am also available on Twitter:
www.twitter.com/manuelguzman
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
[/quote]
playing Dirt 3 over Steam in 3D Vision @ 1024x768
it used to crash once in a while between races in R290.53 (!never within a race!) but it is now crashing all the time a few secs after starting a race (like monaco head2head for instance).
Thank you for the feedback. We will investigate this issue. Just to be clear, did anyone experience this same issue with R290.53 or does it only occur with R295.51 driver?
playing Dirt 3 over Steam in 3D Vision @ 1024x768
it used to crash once in a while between races in R290.53 (!never within a race!) but it is now crashing all the time a few secs after starting a race (like monaco head2head for instance).
DX58SO2 Intel Board | i7-970 | SLI 2x Gigabyte GTX 970 4GB stock OC @ 1033/1111 Mhz | 12GB Mem | Windows 10 64bit driver 368.22 | 3D Vision | PJ6221 Viewsonic Projector
Same as others in that it crashed at the very start of a race, or in-race.
Will revert back to the 290.53's to test again. (but from memory never had any crashes with that driver in 2d surround)
*******
UPDATE
Ok reverted back to 290.53 and dirt3 runs fine with no crashing in2d surround. SO something in the latest beta is causing it Manuel.
Same as others in that it crashed at the very start of a race, or in-race.
Will revert back to the 290.53's to test again. (but from memory never had any crashes with that driver in 2d surround)
*******
UPDATE
Ok reverted back to 290.53 and dirt3 runs fine with no crashing in2d surround. SO something in the latest beta is causing it Manuel.
i7 3820 | 16GB G.Skill F3-12800CL9Q-16GBZL | Gigabyte X79 UD3 | GTX 680 SLI | Intel 320-80gig, 120gig Corsair Force 3, 240gig Silicon Magic +4xHD | Coolermaster Silent Pro M1000 | CoolerMaster Haf-X | Asus 3d VH278H | X-Fi Titanium Fatal1ty Pro | SteelSeries 7H-USB | Coolermaster Hyper 212 EVO
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
hello
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
[/quote]
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
hello
my alienware m17x r3 with gtx 560m runs dirt3 nicely with 295.51 driver.
but the problem is there are some artiffacts in 3d vision mode, like incorrectly rendered shadows, ghost images, smoke errors.
i will try previous drivers to see if they are better.
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
[/quote]
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
This sounds like you are running in dx9 mode (all the rendering issues you note occur in dx9 mode still, despite being fixed for dx11 mode). Can you check the config file and see if "force dx9=true" or if it equals "false"?
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
[/quote]
3D Vision support (for the DX11 version, there is no support for DX9) requires the 1.02 game patch. I am not sure what problems gfwl has because I use Steam and I think I got the update there, but I will say that if you like driving games in stereo 3D then the 1.02 version of Dirt 3 is pretty awesome: all the dust, snow, lights (day and night), and shadows work perfectly. So take a chance, back up your files, and go for it. The only issues are that water reflections (on lakes) are a bit wrong (but who cares you only see them in cut scenes), and reflections on the car hood, while 'depth correct' from a stereo perspective, look 'painted on' the hood surface but it still looks good. Lens flare is annoying in any game, and this continues to be the case in Dirt 3.
yes they all set to correct mode
or is this caused by 1.01 version? cause i dont want that stupid gfwl update the game, it once ruined my bioshock 2 game files and put me waiting for an entire night to finish the update.
3D Vision support (for the DX11 version, there is no support for DX9) requires the 1.02 game patch. I am not sure what problems gfwl has because I use Steam and I think I got the update there, but I will say that if you like driving games in stereo 3D then the 1.02 version of Dirt 3 is pretty awesome: all the dust, snow, lights (day and night), and shadows work perfectly. So take a chance, back up your files, and go for it. The only issues are that water reflections (on lakes) are a bit wrong (but who cares you only see them in cut scenes), and reflections on the car hood, while 'depth correct' from a stereo perspective, look 'painted on' the hood surface but it still looks good. Lens flare is annoying in any game, and this continues to be the case in Dirt 3.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
DX58SO2 Intel Board | i7-970 | SLI 2x Gigabyte GTX 970 4GB stock OC @ 1033/1111 Mhz | 12GB Mem | Windows 10 64bit driver 368.22 | 3D Vision | PJ6221 Viewsonic Projector
--------------------------------------------------------------------------------
[b]Found a solution/workaround for this issue on my system - using SLI and 3D-Vision for Dirt3 with the 295.51 drivers. I had to alter the [b]CUDA - GPUs[/b] setting for the dirt3.exe under 3D settings from standard using both to 1 of 2 or 2 of 2 (so only one card ).[/b]
Had a lot of other issues popping up with this new 295.51beta driver as well. One was a problem with the USB-Transmitter, solved by adding another USB-Card Transcend TS-PDU3 (connected to the PSU/ the IRQs of the GPUs are still the same) because with the new 195.51 driver the transmitter went offline from time to time. This changed unfortunately the 3d-vision setting automaticly to [b]3D-Vision Discover[/b] [b]without a notice[/b]. You might notice it when the MSN messenger changed its colours.
Now connected to the new USB 3.0 card it doesn´t do this anymore. I faced also the issue that the resulution changed after reboot again and again. I did study the Release Notes and found the hint NOT to uninstall the GPUs via the Windows device manager, always it has to be done using the Controlpanel / Software if you use W7. May be some stuff went wrong while installing the drivers. In total I spent more than 15 hours to solve all the problems. I had a spare 470GTX , so I started to swap cards and so on, but all 3 cards are O.K. At some point I couldn´t activate SLI, two minutes before the system told me to shut it down, add the SLI bridge and reboot ( I could reproduce this also after swapping or replacing the cards).
A workaround for the resolution change after reboot was to disable and enable the cards in the devicemanager. But you have to do the disable and enable very quick ( before the monitor wents black from the disable action). This always helped with the resolution.
But certainly I wasn´t happy with this and I tried more things. [b]Now all is good and works without any workaround [/b]like a charm
[b](with CUDA - GPUs setting for the dirt3.exe under 3D settings back to standard)[/b].
Within the last weeks I also faced random crashes in BF3( me always using the latest beta drivers), this problem is also solved now.
Also I do remember the message after reboot many times about the shortcuthandler to allow it doing changes to the system ( I used several restorepoints for investigation, certainly also one reason for this repetitions).
Benchmark 1920x1080 average ca. 80FPS all maxed out, just post processing on the lowest setting ( with 3D Vision enabled only average 40FPS )
a translation into German (just the most important stuff):
Bei einem [b]SLI-PC[/b] ([b]2x470GTX, W7x64, I7 no Virtu Software installed, Z68, 295.51, 16GB, 3D-Brille, no overclocking[/b]) war es notwendig unter [b]3D-Einstellungen verwalten für die Dirt3.exe den Standardwert CUDA - GPUs von beide auf 1 von 2[/b] anzupassen. Seither keine Abstürtze mehr. Läuft nun alles auf MAX, nur Nachbearbeitung auf den geringst möglichen Wert.
Hinweis: SLI läuft auch mit dieser geänderten Einstellung.
Benchmark 1920x1080 average ca. 80FPS ( mit 3D-Brille halbiert sich dieser Wert )
--------------------------------------------------------------------------------
Found a solution/workaround for this issue on my system - using SLI and 3D-Vision for Dirt3 with the 295.51 drivers. I had to alter the CUDA - GPUs setting for the dirt3.exe under 3D settings from standard using both to 1 of 2 or 2 of 2 (so only one card ).
Had a lot of other issues popping up with this new 295.51beta driver as well. One was a problem with the USB-Transmitter, solved by adding another USB-Card Transcend TS-PDU3 (connected to the PSU/ the IRQs of the GPUs are still the same) because with the new 195.51 driver the transmitter went offline from time to time. This changed unfortunately the 3d-vision setting automaticly to 3D-Vision Discover without a notice. You might notice it when the MSN messenger changed its colours.
Now connected to the new USB 3.0 card it doesn´t do this anymore. I faced also the issue that the resulution changed after reboot again and again. I did study the Release Notes and found the hint NOT to uninstall the GPUs via the Windows device manager, always it has to be done using the Controlpanel / Software if you use W7. May be some stuff went wrong while installing the drivers. In total I spent more than 15 hours to solve all the problems. I had a spare 470GTX , so I started to swap cards and so on, but all 3 cards are O.K. At some point I couldn´t activate SLI, two minutes before the system told me to shut it down, add the SLI bridge and reboot ( I could reproduce this also after swapping or replacing the cards).
A workaround for the resolution change after reboot was to disable and enable the cards in the devicemanager. But you have to do the disable and enable very quick ( before the monitor wents black from the disable action). This always helped with the resolution.
But certainly I wasn´t happy with this and I tried more things. Now all is good and works without any workaround like a charm
(with CUDA - GPUs setting for the dirt3.exe under 3D settings back to standard).
Within the last weeks I also faced random crashes in BF3( me always using the latest beta drivers), this problem is also solved now.
Also I do remember the message after reboot many times about the shortcuthandler to allow it doing changes to the system ( I used several restorepoints for investigation, certainly also one reason for this repetitions).
Benchmark 1920x1080 average ca. 80FPS all maxed out, just post processing on the lowest setting ( with 3D Vision enabled only average 40FPS )
a translation into German (just the most important stuff):
Bei einem SLI-PC (2x470GTX, W7x64, I7 no Virtu Software installed, Z68, 295.51, 16GB, 3D-Brille, no overclocking) war es notwendig unter 3D-Einstellungen verwalten für die Dirt3.exe den Standardwert CUDA - GPUs von beide auf 1 von 2 anzupassen. Seither keine Abstürtze mehr. Läuft nun alles auf MAX, nur Nachbearbeitung auf den geringst möglichen Wert.
Hinweis: SLI läuft auch mit dieser geänderten Einstellung.
Benchmark 1920x1080 average ca. 80FPS ( mit 3D-Brille halbiert sich dieser Wert )