[quote]Shadows and reflections are very broken. Shadows look wrong and reflections only work on one eye (the left eye). [/quote]
These are VERY common problems when NVIDIA's drivers are left to fend for themselves. I strongly suspect the fix from CDProjekt was to simply stop trying to directly support 3D Vision and let the drivers do it.
The question is - is this permanent or just a stopgap to cover them while they fix up whatever is wrong? If it's a stopgap, they should say so. If it isn't, they should give us the option to turn off the shadows. Instead, we're told it's working fine even when it's perfectly obvious it isn't. That doesn't fit either option. Odd.
Shadows and reflections are very broken. Shadows look wrong and reflections only work on one eye (the left eye).
These are VERY common problems when NVIDIA's drivers are left to fend for themselves. I strongly suspect the fix from CDProjekt was to simply stop trying to directly support 3D Vision and let the drivers do it.
The question is - is this permanent or just a stopgap to cover them while they fix up whatever is wrong? If it's a stopgap, they should say so. If it isn't, they should give us the option to turn off the shadows. Instead, we're told it's working fine even when it's perfectly obvious it isn't. That doesn't fit either option. Odd.
This is so retarded. Shouldn't the question be who is NOT having problems with the Witcher 2. Please list your config. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
I'm pretty sure 100% of people are having problems /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
Does not even 1 SINGLE PERSON FEAKING PLAY THE GAME WITH THE PATCH TO MAKE SURE IT WORKS? Before coming on these forums and saying the patch is out. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
This is so retarded. Shouldn't the question be who is NOT having problems with the Witcher 2. Please list your config. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
I'm pretty sure 100% of people are having problems /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
Does not even 1 SINGLE PERSON FEAKING PLAY THE GAME WITH THE PATCH TO MAKE SURE IT WORKS? Before coming on these forums and saying the patch is out. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' /> /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
[quote name='pancake master' date='22 July 2011 - 03:30 AM' timestamp='1311301846' post='1268917']
AND JUST LIKE THAT...........ANDREW IS GONE
[/quote]
So true. Maybe anither nvidia employee will yet again drop by and ask why we are complaining as all are issue where apparently fixed with the 1.3 patch. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
So true. Maybe anither nvidia employee will yet again drop by and ask why we are complaining as all are issue where apparently fixed with the 1.3 patch. /wallbash.gif' class='bbc_emoticon' alt=':wallbash:' />
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
[quote name='Aladin' date='24 July 2011 - 07:42 AM' timestamp='1311507760' post='1269840']
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
[/quote]
I sincerely hope that Nvidia and CDProject can get this fixed, the "correct" stereo images posted here are stunning.
The Witcher 2 would be a real showpiece for 3DVision, and would revive our trust in the 3DVision Ready certification which until this point has been very reliable.
Until then I have instead purchased Alice Madness Returns, which is a very good game in stereo, also has great PhysX effects.
[size=1][color=#FFCC00]MOTHERBOARD: EVGA 780I SLI A2 P-06Bios
CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day
CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)
RAM: 2x2GB OCZ PC8000 SLI (Timing:5-5-5-15-2T@ 2.0V, FSB:DRAM Ratio=2:3)
GRAPHICS: 2X EVGA GTX 480sc(clocks: 769c/1007mem/1538shader, stock heatsink)
HDD1: 2X Western Digital Caviar SATA II 250GB 7200 rpm Raid 0
HDD2: Western Digital Caviar SATA II 500GB 7200 rpm
SOUND: On board
OS: Windows Vista Ultimate 64bit SP2
MONITOR: Dell 3008wfp 30" Native Res: 2560X1600 @ 60Hz, Acer235Hz120Hz-3D
PSU: Thermaltake Toughpower 1000W
CASE: Gigabyte 3D Mercury
3DMARK Vantage: 29,686p Current Display Driver:275.50[/color][/size]
[quote name='Aladin' date='24 July 2011 - 07:42 AM' timestamp='1311507760' post='1269840']
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
I sincerely hope that Nvidia and CDProject can get this fixed, the "correct" stereo images posted here are stunning.
The Witcher 2 would be a real showpiece for 3DVision, and would revive our trust in the 3DVision Ready certification which until this point has been very reliable.
Until then I have instead purchased Alice Madness Returns, which is a very good game in stereo, also has great PhysX effects.
MOTHERBOARD: EVGA 780I SLI A2 P-06Bios
CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day
CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)
I really don't think there is an NVIDIA driver bug at work here.
I changed the witcher2.exe file name to a few other 3D Vision ready titles (dukeforever.exe, metro233.exe, re5dx9.exe), and none of them worked. I also renamed it to foo.exe to test without profiles (that includes both driver level AND 3D vision profiles). Aside from wildly varying convergence settings, the shadows are always rendered at zero depth. That really does point to the game itself, rather than the driver.
Here's a hypothetical scenario:
A) In patch 1.1 & 1.2 CDPR is using the right API to create shadows, but invoking it improperly. This causes a massive performance hit. Disabling the service prior to launching the game, forces the game to use a different API as a fall back, thus improving performance, but rendering shadows in 2D.
B) In patch 1.3, CDPR switches to a different API to fix the performance issues (rather than overhaul the entire engine). The new API draws shadows in 2d, nice and quick. Now we get the behavior of the workaround from (A) by default.
A driver API is a driver API. It will do what its told. A developer has to use it correctly. If there was a driver issue, we would likely see one of the other profiles drawing the shadows correctly, or LOTS of other "[b]3D Vision ready[/b]" games with botched shadows. NVIDIA doesn't code their driver uniquely for every application - that would be crazy. They provide application profiles which contain optimizations (both driver level and 3D vision) which can effect things, but by changing the file name - we can rule these out.
Could it be a driver issue? There's a slim chance - but I really doubt it. I figure it's up to CDPR to fix it. And that's not good, because they have yet to even acknowledge it. I suspect they'll just remove the 3DVision Ready logo, and call it a day.
[b]Please, everyone, submit trouble tickets to CDPR[/b]. We must try. The game would be glorious in S3D. They will not allocate any R&D resources to an issue that has only a handful of trouble tickets against it. It just doesn't work like that.
Submit your ticket here:
http://www.en.thewitcher.com/support/ (at the bottom of the page)
And email it to them here:
tw2support@cdprojektred.com
You should include your dxdiag.exe output, and at least one screenshot.
I think at this point, I'd be happy if they simply let us turn off the shadows completely.
** Edited on July 27 to update the correct email address for support at CDPR.
I really don't think there is an NVIDIA driver bug at work here.
I changed the witcher2.exe file name to a few other 3D Vision ready titles (dukeforever.exe, metro233.exe, re5dx9.exe), and none of them worked. I also renamed it to foo.exe to test without profiles (that includes both driver level AND 3D vision profiles). Aside from wildly varying convergence settings, the shadows are always rendered at zero depth. That really does point to the game itself, rather than the driver.
Here's a hypothetical scenario:
A) In patch 1.1 & 1.2 CDPR is using the right API to create shadows, but invoking it improperly. This causes a massive performance hit. Disabling the service prior to launching the game, forces the game to use a different API as a fall back, thus improving performance, but rendering shadows in 2D.
B) In patch 1.3, CDPR switches to a different API to fix the performance issues (rather than overhaul the entire engine). The new API draws shadows in 2d, nice and quick. Now we get the behavior of the workaround from (A) by default.
A driver API is a driver API. It will do what its told. A developer has to use it correctly. If there was a driver issue, we would likely see one of the other profiles drawing the shadows correctly, or LOTS of other "3D Vision ready" games with botched shadows. NVIDIA doesn't code their driver uniquely for every application - that would be crazy. They provide application profiles which contain optimizations (both driver level and 3D vision) which can effect things, but by changing the file name - we can rule these out.
Could it be a driver issue? There's a slim chance - but I really doubt it. I figure it's up to CDPR to fix it. And that's not good, because they have yet to even acknowledge it. I suspect they'll just remove the 3DVision Ready logo, and call it a day.
Please, everyone, submit trouble tickets to CDPR. We must try. The game would be glorious in S3D. They will not allocate any R&D resources to an issue that has only a handful of trouble tickets against it. It just doesn't work like that.
[quote name='Corben' date='25 July 2011 - 04:31 PM' timestamp='1311625903' post='1270421']
@ encryptid
did you get an answer?
I didn't
[/quote]
Not yet from CDPR. NVIDIA answered my ticket and said they were looking into it.
When (or should I say IF) CDPR opens their Witcher 2 forum (supposedly by then end of July), it should be interesting.
If enough of us submit a ticket, maybe they'll answer someone ....
[quote name='encryptid' date='25 July 2011 - 10:15 PM' timestamp='1311628546' post='1270444']
If enough of us submit a ticket, maybe they'll answer someone ....
[/quote]
My bet: They say it has been thoroughly tested and confirmed that it worked at the time the patch was programmed, then start pointing fingers at Nvidia and leave us screwed.
Of course I can be wrong but I seriously doubt that anyone there is still working on a fix.
I mean when the first patch came out I still had hopes: But instead of fixing the issues at hand they thought it more important to add an alternate hairstyle to the character....HAIRSTYLE...I mean....they used internal resources and before actually fixing all the bugs they added the option to alter the gfx on the main characters head (Yes, i know they also fixed other things but c'mon)
And now the last patch where they apparently fixed 3D (according to what CDPR said) - well, you could always say third time is the charm but unfortunately reality isn't made of marshmellows and snugglebuns. IF they react to the complains at some point they most likely just start blaming someone else.
[quote name='encryptid' date='25 July 2011 - 10:15 PM' timestamp='1311628546' post='1270444']
If enough of us submit a ticket, maybe they'll answer someone ....
My bet: They say it has been thoroughly tested and confirmed that it worked at the time the patch was programmed, then start pointing fingers at Nvidia and leave us screwed.
Of course I can be wrong but I seriously doubt that anyone there is still working on a fix.
I mean when the first patch came out I still had hopes: But instead of fixing the issues at hand they thought it more important to add an alternate hairstyle to the character....HAIRSTYLE...I mean....they used internal resources and before actually fixing all the bugs they added the option to alter the gfx on the main characters head (Yes, i know they also fixed other things but c'mon)
And now the last patch where they apparently fixed 3D (according to what CDPR said) - well, you could always say third time is the charm but unfortunately reality isn't made of marshmellows and snugglebuns. IF they react to the complains at some point they most likely just start blaming someone else.
[quote]Anyway, we see the problem and are working on it.
Andrzej Kwiatkowski
CD Projekt RED[/quote]
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
Hmph. I had been sending it to the 'incorrect' address.
Maybe that's why they never answered.
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
Hmph. I had been sending it to the 'incorrect' address.
Maybe that's why they never answered.
I've already fired off another one.
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
[quote name='encryptid' date='27 July 2011 - 09:17 AM' timestamp='1311772673' post='1271162']
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
I've already fired off another one.
[/quote]
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
[quote name='encryptid' date='27 July 2011 - 09:17 AM' timestamp='1311772673' post='1271162']
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
I've already fired off another one.
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
[quote name='encryptid' date='27 July 2011 - 09:42 AM' timestamp='1311774125' post='1271169']
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
[/quote]
[quote]
Your problem is not related to tw2support mailbox. It's google antispam protection which activates when you send too many emails, like hundred within 24 hours.
Just sent an email to support mailbox from my home address. No problems.
[quote name='encryptid' date='27 July 2011 - 09:42 AM' timestamp='1311774125' post='1271169']
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
Your problem is not related to tw2support mailbox. It's google antispam protection which activates when you send too many emails, like hundred within 24 hours.
Just sent an email to support mailbox from my home address. No problems.
Andrzej Kwiatkowski
CD Projekt RED
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
These are VERY common problems when NVIDIA's drivers are left to fend for themselves. I strongly suspect the fix from CDProjekt was to simply stop trying to directly support 3D Vision and let the drivers do it.
The question is - is this permanent or just a stopgap to cover them while they fix up whatever is wrong? If it's a stopgap, they should say so. If it isn't, they should give us the option to turn off the shadows. Instead, we're told it's working fine even when it's perfectly obvious it isn't. That doesn't fit either option. Odd.
These are VERY common problems when NVIDIA's drivers are left to fend for themselves. I strongly suspect the fix from CDProjekt was to simply stop trying to directly support 3D Vision and let the drivers do it.
The question is - is this permanent or just a stopgap to cover them while they fix up whatever is wrong? If it's a stopgap, they should say so. If it isn't, they should give us the option to turn off the shadows. Instead, we're told it's working fine even when it's perfectly obvious it isn't. That doesn't fit either option. Odd.
I'm pretty sure 100% of people are having problems
Does not even 1 SINGLE PERSON FEAKING PLAY THE GAME WITH THE PATCH TO MAKE SURE IT WORKS? Before coming on these forums and saying the patch is out.
I'm pretty sure 100% of people are having problems
Does not even 1 SINGLE PERSON FEAKING PLAY THE GAME WITH THE PATCH TO MAKE SURE IT WORKS? Before coming on these forums and saying the patch is out.
1.3 patch (though I had the same issues before it too)
GTX 460 SLI
275.50
1.3 patch (though I had the same issues before it too)
GTX 460 SLI
275.50
Windows 7 64bit
450 GTS
450 GTS (SLI)
275.50 driver
1.3 patch
Windows 7 64bit
450 GTS
450 GTS (SLI)
275.50 driver
1.3 patch
|CPU: i7-2700k @ 4.5Ghz
|Cooler: Zalman 9900 Max
|MB: MSI Military Class II Z68 GD-80
|RAM: Corsair Vengence 16GB DDR3
|SSDs: Seagate 600 240GB; Crucial M4 128GB
|HDDs: Seagate Barracuda 1TB; Seagate Barracuda 500GB
|PS: OCZ ZX Series 1250watt
|Case: Antec 1200 V3
|Monitors: Asus 3D VG278HE; Asus 3D VG236H; Samsung 3D 51" Plasma;
|GPU:MSI 1080GTX "Duke"
|OS: Windows 10 Pro X64
AND JUST LIKE THAT...........ANDREW IS GONE
[/quote]
So true. Maybe anither nvidia employee will yet again drop by and ask why we are complaining as all are issue where apparently fixed with the 1.3 patch.
AND JUST LIKE THAT...........ANDREW IS GONE
So true. Maybe anither nvidia employee will yet again drop by and ask why we are complaining as all are issue where apparently fixed with the 1.3 patch.
Steam: https://steamcommunity.com/id/suntorytimes
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
[/quote]
I sincerely hope that Nvidia and CDProject can get this fixed, the "correct" stereo images posted here are stunning.
The Witcher 2 would be a real showpiece for 3DVision, and would revive our trust in the 3DVision Ready certification which until this point has been very reliable.
Until then I have instead purchased Alice Madness Returns, which is a very good game in stereo, also has great PhysX effects.
[size=1][color=#FFCC00]MOTHERBOARD: EVGA 780I SLI A2 P-06Bios
CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day
CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)
RAM: 2x2GB OCZ PC8000 SLI (Timing:5-5-5-15-2T@ 2.0V, FSB:DRAM Ratio=2:3)
GRAPHICS: 2X EVGA GTX 480sc(clocks: 769c/1007mem/1538shader, stock heatsink)
HDD1: 2X Western Digital Caviar SATA II 250GB 7200 rpm Raid 0
HDD2: Western Digital Caviar SATA II 500GB 7200 rpm
SOUND: On board
OS: Windows Vista Ultimate 64bit SP2
MONITOR: Dell 3008wfp 30" Native Res: 2560X1600 @ 60Hz, Acer235Hz120Hz-3D
PSU: Thermaltake Toughpower 1000W
CASE: Gigabyte 3D Mercury
3DMARK Vantage: 29,686p Current Display Driver:275.50[/color][/size]
If anyone is in doubt about the visual 3D Vision errors produced by patch 1.3, then I have captured 3 screenshots each with patch 1.2 and patch 1.3, so you can compare the difference and study the nature of the error. I have used the default high setting. The files named "correct" are from patch 1.2. The ones named "error" are from 1.3. You change the file format to .jps and use NVIDIA's 3D photo viewer.
I sincerely hope that Nvidia and CDProject can get this fixed, the "correct" stereo images posted here are stunning.
The Witcher 2 would be a real showpiece for 3DVision, and would revive our trust in the 3DVision Ready certification which until this point has been very reliable.
Until then I have instead purchased Alice Madness Returns, which is a very good game in stereo, also has great PhysX effects.
MOTHERBOARD: EVGA 780I SLI A2 P-06Bios
CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day
CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)
RAM: 2x2GB OCZ PC8000 SLI (Timing:5-5-5-15-2T@ 2.0V, FSB:DRAM Ratio=2:3)
GRAPHICS: 2X EVGA GTX 480sc(clocks: 769c/1007mem/1538shader, stock heatsink)
HDD1: 2X Western Digital Caviar SATA II 250GB 7200 rpm Raid 0
HDD2: Western Digital Caviar SATA II 500GB 7200 rpm
SOUND: On board
OS: Windows Vista Ultimate 64bit SP2
MONITOR: Dell 3008wfp 30" Native Res: 2560X1600 @ 60Hz, Acer235Hz120Hz-3D
PSU: Thermaltake Toughpower 1000W
CASE: Gigabyte 3D Mercury
3DMARK Vantage: 29,686p Current Display Driver:275.50
I changed the witcher2.exe file name to a few other 3D Vision ready titles (dukeforever.exe, metro233.exe, re5dx9.exe), and none of them worked. I also renamed it to foo.exe to test without profiles (that includes both driver level AND 3D vision profiles). Aside from wildly varying convergence settings, the shadows are always rendered at zero depth. That really does point to the game itself, rather than the driver.
Here's a hypothetical scenario:
A) In patch 1.1 & 1.2 CDPR is using the right API to create shadows, but invoking it improperly. This causes a massive performance hit. Disabling the service prior to launching the game, forces the game to use a different API as a fall back, thus improving performance, but rendering shadows in 2D.
B) In patch 1.3, CDPR switches to a different API to fix the performance issues (rather than overhaul the entire engine). The new API draws shadows in 2d, nice and quick. Now we get the behavior of the workaround from (A) by default.
A driver API is a driver API. It will do what its told. A developer has to use it correctly. If there was a driver issue, we would likely see one of the other profiles drawing the shadows correctly, or LOTS of other "[b]3D Vision ready[/b]" games with botched shadows. NVIDIA doesn't code their driver uniquely for every application - that would be crazy. They provide application profiles which contain optimizations (both driver level and 3D vision) which can effect things, but by changing the file name - we can rule these out.
Could it be a driver issue? There's a slim chance - but I really doubt it. I figure it's up to CDPR to fix it. And that's not good, because they have yet to even acknowledge it. I suspect they'll just remove the 3DVision Ready logo, and call it a day.
[b]Please, everyone, submit trouble tickets to CDPR[/b]. We must try. The game would be glorious in S3D. They will not allocate any R&D resources to an issue that has only a handful of trouble tickets against it. It just doesn't work like that.
Submit your ticket here:
http://www.en.thewitcher.com/support/ (at the bottom of the page)
And email it to them here:
tw2support@cdprojektred.com
You should include your dxdiag.exe output, and at least one screenshot.
I think at this point, I'd be happy if they simply let us turn off the shadows completely.
** Edited on July 27 to update the correct email address for support at CDPR.
I changed the witcher2.exe file name to a few other 3D Vision ready titles (dukeforever.exe, metro233.exe, re5dx9.exe), and none of them worked. I also renamed it to foo.exe to test without profiles (that includes both driver level AND 3D vision profiles). Aside from wildly varying convergence settings, the shadows are always rendered at zero depth. That really does point to the game itself, rather than the driver.
Here's a hypothetical scenario:
A) In patch 1.1 & 1.2 CDPR is using the right API to create shadows, but invoking it improperly. This causes a massive performance hit. Disabling the service prior to launching the game, forces the game to use a different API as a fall back, thus improving performance, but rendering shadows in 2D.
B) In patch 1.3, CDPR switches to a different API to fix the performance issues (rather than overhaul the entire engine). The new API draws shadows in 2d, nice and quick. Now we get the behavior of the workaround from (A) by default.
A driver API is a driver API. It will do what its told. A developer has to use it correctly. If there was a driver issue, we would likely see one of the other profiles drawing the shadows correctly, or LOTS of other "3D Vision ready" games with botched shadows. NVIDIA doesn't code their driver uniquely for every application - that would be crazy. They provide application profiles which contain optimizations (both driver level and 3D vision) which can effect things, but by changing the file name - we can rule these out.
Could it be a driver issue? There's a slim chance - but I really doubt it. I figure it's up to CDPR to fix it. And that's not good, because they have yet to even acknowledge it. I suspect they'll just remove the 3DVision Ready logo, and call it a day.
Please, everyone, submit trouble tickets to CDPR. We must try. The game would be glorious in S3D. They will not allocate any R&D resources to an issue that has only a handful of trouble tickets against it. It just doesn't work like that.
Submit your ticket here:
http://www.en.thewitcher.com/support/ (at the bottom of the page)
And email it to them here:
tw2support@cdprojektred.com
You should include your dxdiag.exe output, and at least one screenshot.
I think at this point, I'd be happy if they simply let us turn off the shadows completely.
** Edited on July 27 to update the correct email address for support at CDPR.
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
ASUS P5WDH Deluxe (BIOS 3001)
Intel Q9650 @ 3GHz
8 GB PC6400 RAM
Windows 7 Ultimate 64 bit
OCZ Vertex 2 128 GB Boot Drive (OS)
Alienware AW2310 1920x1080 120Hz (over DL-DVI)
did you get an answer?
I didn't
did you get an answer?
I didn't
@ encryptid
did you get an answer?
I didn't
[/quote]
Not yet from CDPR. NVIDIA answered my ticket and said they were looking into it.
When (or should I say IF) CDPR opens their Witcher 2 forum (supposedly by then end of July), it should be interesting.
If enough of us submit a ticket, maybe they'll answer someone ....
@ encryptid
did you get an answer?
I didn't
Not yet from CDPR. NVIDIA answered my ticket and said they were looking into it.
When (or should I say IF) CDPR opens their Witcher 2 forum (supposedly by then end of July), it should be interesting.
If enough of us submit a ticket, maybe they'll answer someone ....
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
ASUS P5WDH Deluxe (BIOS 3001)
Intel Q9650 @ 3GHz
8 GB PC6400 RAM
Windows 7 Ultimate 64 bit
OCZ Vertex 2 128 GB Boot Drive (OS)
Alienware AW2310 1920x1080 120Hz (over DL-DVI)
If enough of us submit a ticket, maybe they'll answer someone ....
[/quote]
My bet: They say it has been thoroughly tested and confirmed that it worked at the time the patch was programmed, then start pointing fingers at Nvidia and leave us screwed.
Of course I can be wrong but I seriously doubt that anyone there is still working on a fix.
I mean when the first patch came out I still had hopes: But instead of fixing the issues at hand they thought it more important to add an alternate hairstyle to the character....HAIRSTYLE...I mean....they used internal resources and before actually fixing all the bugs they added the option to alter the gfx on the main characters head (Yes, i know they also fixed other things but c'mon)
And now the last patch where they apparently fixed 3D (according to what CDPR said) - well, you could always say third time is the charm but unfortunately reality isn't made of marshmellows and snugglebuns. IF they react to the complains at some point they most likely just start blaming someone else.
If enough of us submit a ticket, maybe they'll answer someone ....
My bet: They say it has been thoroughly tested and confirmed that it worked at the time the patch was programmed, then start pointing fingers at Nvidia and leave us screwed.
Of course I can be wrong but I seriously doubt that anyone there is still working on a fix.
I mean when the first patch came out I still had hopes: But instead of fixing the issues at hand they thought it more important to add an alternate hairstyle to the character....HAIRSTYLE...I mean....they used internal resources and before actually fixing all the bugs they added the option to alter the gfx on the main characters head (Yes, i know they also fixed other things but c'mon)
And now the last patch where they apparently fixed 3D (according to what CDPR said) - well, you could always say third time is the charm but unfortunately reality isn't made of marshmellows and snugglebuns. IF they react to the complains at some point they most likely just start blaming someone else.
@ encryptid
did you get an answer?
I didn't
[/quote]
In another thread (kudos ShaderHacker for spotting it), CDPR has provided an update and an email address correction.
[url="http://www.gog.com/en/forum/the_witcher_2/the_3d_vision_errors_illustrated_with_screenshots"]http://www.gog.com/en/forum/the_witcher_2/the_3d_vision_errors_illustrated_with_screenshots[/url]
[quote]Anyway, we see the problem and are working on it.
Andrzej Kwiatkowski
CD Projekt RED[/quote]
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
Hmph. I had been sending it to the 'incorrect' address.
Maybe that's why they never answered.
I've already fired off another one.
@ encryptid
did you get an answer?
I didn't
In another thread (kudos ShaderHacker for spotting it), CDPR has provided an update and an email address correction.
http://www.gog.com/en/forum/the_witcher_2/the_3d_vision_errors_illustrated_with_screenshots
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
Hmph. I had been sending it to the 'incorrect' address.
Maybe that's why they never answered.
I've already fired off another one.
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
ASUS P5WDH Deluxe (BIOS 3001)
Intel Q9650 @ 3GHz
8 GB PC6400 RAM
Windows 7 Ultimate 64 bit
OCZ Vertex 2 128 GB Boot Drive (OS)
Alienware AW2310 1920x1080 120Hz (over DL-DVI)
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
I've already fired off another one.
[/quote]
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
In that same thread, Andrzej points out that the CORRECT email address to send in tech support requests is tw2support@cdprojektred.com (NOT tw2support@thewitcher.com).
I've already fired off another one.
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
ASUS P5WDH Deluxe (BIOS 3001)
Intel Q9650 @ 3GHz
8 GB PC6400 RAM
Windows 7 Ultimate 64 bit
OCZ Vertex 2 128 GB Boot Drive (OS)
Alienware AW2310 1920x1080 120Hz (over DL-DVI)
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
[/quote]
[quote]
Your problem is not related to tw2support mailbox. It's google antispam protection which activates when you send too many emails, like hundred within 24 hours.
Just sent an email to support mailbox from my home address. No problems.
Andrzej Kwiatkowski
CD Projekt RED[/quote]
Wow. That address rejects my mail as spam and then gmail disables my account forcing me to change my password due to 'suspicious activity'. I tried it twice - same result. Simply sending an email to the 'correct' address does not work. Nice.
The domain is owned by CDPR ...
MSI GEFORCE GTX 570 M2D12DS Single card (BIOS 70.10.17.00.03)
ASUS P5WDH Deluxe (BIOS 3001)
Intel Q9650 @ 3GHz
8 GB PC6400 RAM
Windows 7 Ultimate 64 bit
OCZ Vertex 2 128 GB Boot Drive (OS)
Alienware AW2310 1920x1080 120Hz (over DL-DVI)