Check it out guys, as of now this, [url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_195.62.html"]http://www.nvidia.com/object/geforce_3D_vi...in7_195.62.html[/url], can be found on the nvidia homepage. Upon attepmting to download, however, I was greeted with a 'file not found' message. So I guess something's happening regarding new WHQL drivers... Yay!
Check it out guys, as of now this, http://www.nvidia.com/object/geforce_3D_vi...in7_195.62.html, can be found on the nvidia homepage. Upon attepmting to download, however, I was greeted with a 'file not found' message. So I guess something's happening regarding new WHQL drivers... Yay!
I only downloaded the 1.16 drivers yesterday, and now there apparently might be 1.17 already?
But yeah, I'm getting 'File not found' for the US drivers as well. However, the UK drivers seem to be up and they'll work fine on a US machine - you'll just have to see things spelled as 'colour' or 'honour.' ;)
I only downloaded the 1.16 drivers yesterday, and now there apparently might be 1.17 already?
But yeah, I'm getting 'File not found' for the US drivers as well. However, the UK drivers seem to be up and they'll work fine on a US machine - you'll just have to see things spelled as 'colour' or 'honour.' ;)
Updated my drivers to 1.17, but just like 1.16 it doesn't detect my ViewSonic projector. /shock.gif' class='bbc_emoticon' alt=':shock:' /> Anyone else having this problem?
Updated my drivers to 1.17, but just like 1.16 it doesn't detect my ViewSonic projector. /shock.gif' class='bbc_emoticon' alt=':shock:' /> Anyone else having this problem?
Downloading now - was not easy to get access to that file. Worked in the the end via UK (GBR) download (not beta drivers and archive, but regular). Now, let's see if Avatar will have proper framerates and Dragon Age character portraits are visible all the time again... Keeping fingers crossed.
Downloading now - was not easy to get access to that file. Worked in the the end via UK (GBR) download (not beta drivers and archive, but regular). Now, let's see if Avatar will have proper framerates and Dragon Age character portraits are visible all the time again... Keeping fingers crossed.
WOW.. so again my new driver same old prolem Avatar crashes when I try to turn off the 3d. I'm getting more disapointed now. back to 1.13 for me
Intel Core i9-9820x @ 3.30GHZ
32 gig Ram
2 EVGA RTX 2080 ti Gaming
3 X ASUS ROG SWIFT 27 144Hz G-SYNC Gaming 3D Monitor [PG278Q]
1 X ASUS VG278HE
Nvidia 3Dvision
Oculus Rift
HTC VIVE
Windows 10
Damn!!! Everyone has different issues with Avatar and new drivers. I was getting nothing but crashes with drivers 1.16 running Avatar demo.
Now I have installed the new 1.17 drivers WHQL and Avatar worked flawlessy. It's early to say cause I was in a hurry and only played the game for a 10 or 15 minutes I guess and didn't suffer any crashes. Anyway with 1.16 drivers I coudn't even play this game for more than 2 minutes without crashing, usually just hitting new game in options would make the game crash to desktop. At least these new drivers seen to be more stable, at least that was the first impression I had.
One thing I notice in Avatar options after I installed the new 1.17 drivers and I would like to share with you and find out if someone also notice that.
In the game's options I can not select directx10, all other options are selectable and ok, only the directx option is locked. I can't select Directx10, I'm stuck with Directx9 in this game.
Anyone notice that??
BTW, Convergence is now locked after I installed these new drivers. I think it auto adjusts according to the amount of depth used in the game. At least there's lots of pop out effects despite the locked convergence.
Damn!!! Everyone has different issues with Avatar and new drivers. I was getting nothing but crashes with drivers 1.16 running Avatar demo.
Now I have installed the new 1.17 drivers WHQL and Avatar worked flawlessy. It's early to say cause I was in a hurry and only played the game for a 10 or 15 minutes I guess and didn't suffer any crashes. Anyway with 1.16 drivers I coudn't even play this game for more than 2 minutes without crashing, usually just hitting new game in options would make the game crash to desktop. At least these new drivers seen to be more stable, at least that was the first impression I had.
One thing I notice in Avatar options after I installed the new 1.17 drivers and I would like to share with you and find out if someone also notice that.
In the game's options I can not select directx10, all other options are selectable and ok, only the directx option is locked. I can't select Directx10, I'm stuck with Directx9 in this game.
Anyone notice that??
BTW, Convergence is now locked after I installed these new drivers. I think it auto adjusts according to the amount of depth used in the game. At least there's lots of pop out effects despite the locked convergence.
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD
Avatar still drops to one third of its frame rate in 3d. Dragon Age still has wrong placed character icons.
When you try to download 1.17 right now, it's like a gamble. Most of the time the download site for 3d vision does not work at all, sometimes it leads you to 1.13 and if your lucky (or unlucky?) you find 1.17.
Now, user-to-user-with-dip-of-lucky-nvidia-pie-presence-sometimes-forum-moderators, ban me or whatever you like:
Fact 1: 3d vision is the greatest thing for me since invention of 3d cards or 3d engine at all. Love it.
Fact 2: Community support and especially COMMUNICATION is abyssmal. Official news in these forums or anywhere else on nvidia site about a new driver release? Nope, users have to find out by themselves. Official word of what's going on with the download trouble (perhaps accidental too early release - wouldn't be a shame, just tell about it, huh) in forum or anyhwere else on nvidia's site? Nothing. Let them users try in vain uncommented. Why do I care anymore? See Fact 1.
Avatar still drops to one third of its frame rate in 3d. Dragon Age still has wrong placed character icons.
When you try to download 1.17 right now, it's like a gamble. Most of the time the download site for 3d vision does not work at all, sometimes it leads you to 1.13 and if your lucky (or unlucky?) you find 1.17.
Now, user-to-user-with-dip-of-lucky-nvidia-pie-presence-sometimes-forum-moderators, ban me or whatever you like:
Fact 1: 3d vision is the greatest thing for me since invention of 3d cards or 3d engine at all. Love it.
Fact 2: Community support and especially COMMUNICATION is abyssmal. Official news in these forums or anywhere else on nvidia site about a new driver release? Nope, users have to find out by themselves. Official word of what's going on with the download trouble (perhaps accidental too early release - wouldn't be a shame, just tell about it, huh) in forum or anyhwere else on nvidia's site? Nothing. Let them users try in vain uncommented. Why do I care anymore? See Fact 1.
I always have better luck with the full CD. Seems to be missing at the moment: [url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_CD_1.17.html"]http://www.nvidia.com/object/geforce_3D_vi...n7_CD_1.17.html[/url]
Cause I care and accidentaly somebody at nvidia realises that COMMUNICATION might benefit user and company:
Avatar tries to use[b] two different 3d methods at the same time[/b]: [b]3d vision and split screen images [/b](two times the same image next to each other). This is why frame rate breaks in to one third to one quarter of 2d frame rate.
There is a nice experiment I can reproduce everytime with FRAPS on:
1. Start game with 3d mode selected and 3d vision as method selected from ingame menu. Game starts - Frame rate is one third to one quarter of the frame rate without 3d (check with strg + t: on and off).
2. Do many very fast switches with strg+t. You will notice in between the flickers that you see two side by side images - a method not needed for 3d vision.
3. Even clearer:
a ) Write down your 3d frame rate (16 fps in my example location)
b ) Press strg+t to enter 2d mode. Write down your frame rate again (47f fps here). Note: one cross hair in 2d, right?
c ) alt+ tab. alt+tab back again: low and behold: It's still 2d, but with only 30 fps and... 2 cross hairs. funny stuff. Gets better:
d ) press ecape to get to menu: That looks scrambled now, but note: with 3d glasses on you can read some of the letters perfectly good, 3d vision working. You also see the horizontal duplication, another method parallel.
e ) with strg+t you are back to your old 3d frames (16 in my case)
(note: during the tabbing process I reached even 67 frames in 2d - that's all rather strange)
If this helps? I don't know. Just a try to find out what's going on.
Cause I care and accidentaly somebody at nvidia realises that COMMUNICATION might benefit user and company:
Avatar tries to use two different 3d methods at the same time: 3d vision and split screen images (two times the same image next to each other). This is why frame rate breaks in to one third to one quarter of 2d frame rate.
There is a nice experiment I can reproduce everytime with FRAPS on:
1. Start game with 3d mode selected and 3d vision as method selected from ingame menu. Game starts - Frame rate is one third to one quarter of the frame rate without 3d (check with strg + t: on and off).
2. Do many very fast switches with strg+t. You will notice in between the flickers that you see two side by side images - a method not needed for 3d vision.
3. Even clearer:
a ) Write down your 3d frame rate (16 fps in my example location)
b ) Press strg+t to enter 2d mode. Write down your frame rate again (47f fps here). Note: one cross hair in 2d, right?
c ) alt+ tab. alt+tab back again: low and behold: It's still 2d, but with only 30 fps and... 2 cross hairs. funny stuff. Gets better:
d ) press ecape to get to menu: That looks scrambled now, but note: with 3d glasses on you can read some of the letters perfectly good, 3d vision working. You also see the horizontal duplication, another method parallel.
e ) with strg+t you are back to your old 3d frames (16 in my case)
(note: during the tabbing process I reached even 67 frames in 2d - that's all rather strange)
If this helps? I don't know. Just a try to find out what's going on.
Are you all able to select directx 9 and directx 10 in the game's options after installing drivers 1.17??? Please share that information with me. I don't understand why this option is locked in direcxt9 and why I can no longer select directx10? I don't understand that and I would like to know if I'm the only one with this bug.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
Are you all able to select directx 9 and directx 10 in the game's options after installing drivers 1.17??? Please share that information with me. I don't understand why this option is locked in direcxt9 and why I can no longer select directx10? I don't understand that and I would like to know if I'm the only one with this bug.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD
[quote name='francomg' post='956106' date='Nov 26 2009, 08:24 PM']Are you all able to select directx 9 and directx 10 in the game's options after installing drivers 1.17??? Please share that information with me. I don't understand why this option is locked in direcxt9 and why I can no longer select directx10. I don't understand that and I would like to know if I'm the only one with this bug.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.[/quote]
Hi francomg,
here is what has happend to me concerning your questions:
The easy one first: I can't change convergence via strg+f5/f6 either. It is tied, as you guessed yourself corrcetly, to monitor size and distance to monitor settings in ingame menu.
Now the difficult one: In fact with 1.17 for the first time I could choose dx10 in Avatar (at least that I noticed it). After I did however the game crashed. When I restarted dx10 was greyed out again and still is. I play in dx9 therefore.
[quote name='francomg' post='956106' date='Nov 26 2009, 08:24 PM']Are you all able to select directx 9 and directx 10 in the game's options after installing drivers 1.17??? Please share that information with me. I don't understand why this option is locked in direcxt9 and why I can no longer select directx10. I don't understand that and I would like to know if I'm the only one with this bug.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
Hi francomg,
here is what has happend to me concerning your questions:
The easy one first: I can't change convergence via strg+f5/f6 either. It is tied, as you guessed yourself corrcetly, to monitor size and distance to monitor settings in ingame menu.
Now the difficult one: In fact with 1.17 for the first time I could choose dx10 in Avatar (at least that I noticed it). After I did however the game crashed. When I restarted dx10 was greyed out again and still is. I play in dx9 therefore.
Bobarr, thank you very much for your feedback, it's always nice to share all 3D bugs we find out along the way with you guys. At least I'm not the only one.
I guess these drivers somehow works in misterious ways according to what hardware we own.
Ionic, a member of this forum, said he was playing Avatar demo flawlessy in directx10 after installing these new drivers. He also didn't have problems using drivers 1.16. I was getting nothing but crashes with drivers 1.16. 1.13 was doing a good job for me running this demo and I could select both types of directx. These different Avatar issues are so confusing.
I guess what matter is that we can at least play this demo with these new drivers. I don't think there's considerable graphic quality increase or better 3D effects using directx10, do you???
Bobarr, thank you very much for your feedback, it's always nice to share all 3D bugs we find out along the way with you guys. At least I'm not the only one.
I guess these drivers somehow works in misterious ways according to what hardware we own.
Ionic, a member of this forum, said he was playing Avatar demo flawlessy in directx10 after installing these new drivers. He also didn't have problems using drivers 1.16. I was getting nothing but crashes with drivers 1.16. 1.13 was doing a good job for me running this demo and I could select both types of directx. These different Avatar issues are so confusing.
I guess what matter is that we can at least play this demo with these new drivers. I don't think there's considerable graphic quality increase or better 3D effects using directx10, do you???
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD
But yeah, I'm getting 'File not found' for the US drivers as well. However, the UK drivers seem to be up and they'll work fine on a US machine - you'll just have to see things spelled as 'colour' or 'honour.' ;)
But yeah, I'm getting 'File not found' for the US drivers as well. However, the UK drivers seem to be up and they'll work fine on a US machine - you'll just have to see things spelled as 'colour' or 'honour.' ;)
http://estereomania.blogspot.com/
http://photos.3dvisionlive.com/Fguillotine/
Good to hear. I'll take the plunge then...
Good to hear. I'll take the plunge then...
Intel Core i9-9820x @ 3.30GHZ
32 gig Ram
2 EVGA RTX 2080 ti Gaming
3 X ASUS ROG SWIFT 27 144Hz G-SYNC Gaming 3D Monitor [PG278Q]
1 X ASUS VG278HE
Nvidia 3Dvision
Oculus Rift
HTC VIVE
Windows 10
I'm sorry to say I'm getting nothing but crashes in Avatar.. can't even change the settings in the display options without a crash.
What the hay?
Pretty ridiculous if you ask me.. the one game that could actually really show what
3d gaming is all about and.. we can't even play it..
sigh..
I'm sorry to say I'm getting nothing but crashes in Avatar.. can't even change the settings in the display options without a crash.
What the hay?
Pretty ridiculous if you ask me.. the one game that could actually really show what
3d gaming is all about and.. we can't even play it..
sigh..
Now I have installed the new 1.17 drivers WHQL and Avatar worked flawlessy. It's early to say cause I was in a hurry and only played the game for a 10 or 15 minutes I guess and didn't suffer any crashes. Anyway with 1.16 drivers I coudn't even play this game for more than 2 minutes without crashing, usually just hitting new game in options would make the game crash to desktop. At least these new drivers seen to be more stable, at least that was the first impression I had.
One thing I notice in Avatar options after I installed the new 1.17 drivers and I would like to share with you and find out if someone also notice that.
In the game's options I can not select directx10, all other options are selectable and ok, only the directx option is locked. I can't select Directx10, I'm stuck with Directx9 in this game.
Anyone notice that??
BTW, Convergence is now locked after I installed these new drivers. I think it auto adjusts according to the amount of depth used in the game. At least there's lots of pop out effects despite the locked convergence.
Now I have installed the new 1.17 drivers WHQL and Avatar worked flawlessy. It's early to say cause I was in a hurry and only played the game for a 10 or 15 minutes I guess and didn't suffer any crashes. Anyway with 1.16 drivers I coudn't even play this game for more than 2 minutes without crashing, usually just hitting new game in options would make the game crash to desktop. At least these new drivers seen to be more stable, at least that was the first impression I had.
One thing I notice in Avatar options after I installed the new 1.17 drivers and I would like to share with you and find out if someone also notice that.
In the game's options I can not select directx10, all other options are selectable and ok, only the directx option is locked. I can't select Directx10, I'm stuck with Directx9 in this game.
Anyone notice that??
BTW, Convergence is now locked after I installed these new drivers. I think it auto adjusts according to the amount of depth used in the game. At least there's lots of pop out effects despite the locked convergence.
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD
Avatar still drops to one third of its frame rate in 3d. Dragon Age still has wrong placed character icons.
When you try to download 1.17 right now, it's like a gamble. Most of the time the download site for 3d vision does not work at all, sometimes it leads you to 1.13 and if your lucky (or unlucky?) you find 1.17.
Now, user-to-user-with-dip-of-lucky-nvidia-pie-presence-sometimes-forum-moderators, ban me or whatever you like:
Fact 1: 3d vision is the greatest thing for me since invention of 3d cards or 3d engine at all. Love it.
Fact 2: Community support and especially COMMUNICATION is abyssmal. Official news in these forums or anywhere else on nvidia site about a new driver release? Nope, users have to find out by themselves. Official word of what's going on with the download trouble (perhaps accidental too early release - wouldn't be a shame, just tell about it, huh) in forum or anyhwere else on nvidia's site? Nothing. Let them users try in vain uncommented. Why do I care anymore? See Fact 1.
Avatar still drops to one third of its frame rate in 3d. Dragon Age still has wrong placed character icons.
When you try to download 1.17 right now, it's like a gamble. Most of the time the download site for 3d vision does not work at all, sometimes it leads you to 1.13 and if your lucky (or unlucky?) you find 1.17.
Now, user-to-user-with-dip-of-lucky-nvidia-pie-presence-sometimes-forum-moderators, ban me or whatever you like:
Fact 1: 3d vision is the greatest thing for me since invention of 3d cards or 3d engine at all. Love it.
Fact 2: Community support and especially COMMUNICATION is abyssmal. Official news in these forums or anywhere else on nvidia site about a new driver release? Nope, users have to find out by themselves. Official word of what's going on with the download trouble (perhaps accidental too early release - wouldn't be a shame, just tell about it, huh) in forum or anyhwere else on nvidia's site? Nothing. Let them users try in vain uncommented. Why do I care anymore? See Fact 1.
Avatar tries to use[b] two different 3d methods at the same time[/b]: [b]3d vision and split screen images [/b](two times the same image next to each other). This is why frame rate breaks in to one third to one quarter of 2d frame rate.
There is a nice experiment I can reproduce everytime with FRAPS on:
1. Start game with 3d mode selected and 3d vision as method selected from ingame menu. Game starts - Frame rate is one third to one quarter of the frame rate without 3d (check with strg + t: on and off).
2. Do many very fast switches with strg+t. You will notice in between the flickers that you see two side by side images - a method not needed for 3d vision.
3. Even clearer:
a ) Write down your 3d frame rate (16 fps in my example location)
b ) Press strg+t to enter 2d mode. Write down your frame rate again (47f fps here). Note: one cross hair in 2d, right?
c ) alt+ tab. alt+tab back again: low and behold: It's still 2d, but with only 30 fps and... 2 cross hairs. funny stuff. Gets better:
d ) press ecape to get to menu: That looks scrambled now, but note: with 3d glasses on you can read some of the letters perfectly good, 3d vision working. You also see the horizontal duplication, another method parallel.
e ) with strg+t you are back to your old 3d frames (16 in my case)
(note: during the tabbing process I reached even 67 frames in 2d - that's all rather strange)
If this helps? I don't know. Just a try to find out what's going on.
Avatar tries to use two different 3d methods at the same time: 3d vision and split screen images (two times the same image next to each other). This is why frame rate breaks in to one third to one quarter of 2d frame rate.
There is a nice experiment I can reproduce everytime with FRAPS on:
1. Start game with 3d mode selected and 3d vision as method selected from ingame menu. Game starts - Frame rate is one third to one quarter of the frame rate without 3d (check with strg + t: on and off).
2. Do many very fast switches with strg+t. You will notice in between the flickers that you see two side by side images - a method not needed for 3d vision.
3. Even clearer:
a ) Write down your 3d frame rate (16 fps in my example location)
b ) Press strg+t to enter 2d mode. Write down your frame rate again (47f fps here). Note: one cross hair in 2d, right?
c ) alt+ tab. alt+tab back again: low and behold: It's still 2d, but with only 30 fps and... 2 cross hairs. funny stuff. Gets better:
d ) press ecape to get to menu: That looks scrambled now, but note: with 3d glasses on you can read some of the letters perfectly good, 3d vision working. You also see the horizontal duplication, another method parallel.
e ) with strg+t you are back to your old 3d frames (16 in my case)
(note: during the tabbing process I reached even 67 frames in 2d - that's all rather strange)
If this helps? I don't know. Just a try to find out what's going on.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.[/quote]
Hi francomg,
here is what has happend to me concerning your questions:
The easy one first: I can't change convergence via strg+f5/f6 either. It is tied, as you guessed yourself corrcetly, to monitor size and distance to monitor settings in ingame menu.
Now the difficult one: In fact with 1.17 for the first time I could choose dx10 in Avatar (at least that I noticed it). After I did however the game crashed. When I restarted dx10 was greyed out again and still is. I play in dx9 therefore.
Hope that helps a little :)
With drivers 1.13 I could select directx 10 and 9 without problems, but directx10 was unplayable, I guess they fixed this issue with the new drivers but I can't figure out why I can't select directx10 anymore.
Is it normal not been able to adjust convergence by itself after installing these new drivers??? I can only adjust depth which auto adjust convergence, but not just the convergence.
Hi francomg,
here is what has happend to me concerning your questions:
The easy one first: I can't change convergence via strg+f5/f6 either. It is tied, as you guessed yourself corrcetly, to monitor size and distance to monitor settings in ingame menu.
Now the difficult one: In fact with 1.17 for the first time I could choose dx10 in Avatar (at least that I noticed it). After I did however the game crashed. When I restarted dx10 was greyed out again and still is. I play in dx9 therefore.
Hope that helps a little :)
I guess these drivers somehow works in misterious ways according to what hardware we own.
Ionic, a member of this forum, said he was playing Avatar demo flawlessy in directx10 after installing these new drivers. He also didn't have problems using drivers 1.16. I was getting nothing but crashes with drivers 1.16. 1.13 was doing a good job for me running this demo and I could select both types of directx. These different Avatar issues are so confusing.
I guess what matter is that we can at least play this demo with these new drivers. I don't think there's considerable graphic quality increase or better 3D effects using directx10, do you???
I guess these drivers somehow works in misterious ways according to what hardware we own.
Ionic, a member of this forum, said he was playing Avatar demo flawlessy in directx10 after installing these new drivers. He also didn't have problems using drivers 1.16. I was getting nothing but crashes with drivers 1.16. 1.13 was doing a good job for me running this demo and I could select both types of directx. These different Avatar issues are so confusing.
I guess what matter is that we can at least play this demo with these new drivers. I don't think there's considerable graphic quality increase or better 3D effects using directx10, do you???
Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD