Lastest driver literally breaks 3D for me
  3 / 3    
Registry locations changed maybe(?) Thats my guess at least since it doesnt effect any of Helix's stuff .At least I think so since I probably would of heard of it by now. Lets hope its fixed, they may of rushed this out since Batman AO/ Battlefield.
Registry locations changed maybe(?) Thats my guess at least since it doesnt effect any of Helix's stuff .At least I think so since I probably would of heard of it by now.

Lets hope its fixed, they may of rushed this out since Batman AO/ Battlefield.

Co-founder of helixmod.blog.com

If you like one of my helixmod patches and want to donate. Can send to me through paypal - eqzitara@yahoo.com

#31
Posted 10/23/2013 12:58 AM   
How does Chiri's fix work? Would there be an easy way to adjust it if we can track down where the registry keys have moved to?
How does Chiri's fix work? Would there be an easy way to adjust it if we can track down where the registry keys have moved to?

#32
Posted 10/23/2013 03:15 AM   
Edit: pretty sure I have no idea what I was talking about. :-> Sent a question to Chiri about it.
Edit: pretty sure I have no idea what I was talking about. :->

Sent a question to Chiri about it.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#33
Posted 10/23/2013 04:02 AM   
[quote="helifax"]Anyone tried in 3D Surround? I am curious as why they don't work for me....Going back to the previous beta or WHQL and is working properly...hmmm[/quote] Sorry took so long, 331.58 seems to work fine so far in 3d surround. I did the same install I always do. Rampage IV Extreme/bios 3010/3960K/Win7 64/Pro 16GB G.Skill F3-14900CL9D-8GBSR 3 X EVGA GTX 680/4GB, 04G-P4-2686-KR 3 X ASUS VG Series VG278H - Surround 3D 1 X EVGA GT 610 2 GB, 02G-P3-2617-KR 1 X Planar SA2311W whql 331.58 edit: just test Trine 2, more tomorrow.
helifax said:Anyone tried in 3D Surround? I am curious as why they don't work for me....Going back to the previous beta or WHQL and is working properly...hmmm


Sorry took so long, 331.58 seems to work fine so far in 3d surround. I did the same install I always do.

Rampage IV Extreme/bios 3010/3960K/Win7 64/Pro
16GB G.Skill F3-14900CL9D-8GBSR
3 X EVGA GTX 680/4GB, 04G-P4-2686-KR
3 X ASUS VG Series VG278H - Surround 3D
1 X EVGA GT 610 2 GB, 02G-P3-2617-KR
1 X Planar SA2311W
whql 331.58

edit: just test Trine 2, more tomorrow.

#34
Posted 10/25/2013 06:08 AM   
Small test- MetroLL with 320.49 (x64), non-SLI, still works with Chiri unlocker, even after all Metro updates.
Small test- MetroLL with 320.49 (x64), non-SLI, still works with Chiri unlocker, even after all Metro updates.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#35
Posted 10/25/2013 06:25 AM   
Same results as yours. Driver 331.58 (x64), non-SLI. MetroLL Fails with Chiri Unlocker. It looks to me like the unlocker is not being loaded at all anymore. Enabling logging, I didn't see any log files get created.
Same results as yours. Driver 331.58 (x64), non-SLI. MetroLL Fails with Chiri Unlocker.

It looks to me like the unlocker is not being loaded at all anymore. Enabling logging, I didn't see any log files get created.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#36
Posted 10/25/2013 07:17 AM   
Found a partial solution for unlocking MetroLL convergence. If you drop in the regular version of 3Dmigoto (non-Bioshock version), it doesn't have any shaders patched or other changes, but it [i]does [/i]unlock convergence. Might be overkill, but if you want or need the latest drivers with unlocked convergence, this sort of works. Unfortunately it's only a partial solution, because if you try to enable mouse or key specific changes to convergence for aiming, it doesn't work. Whatever is specified in the OverrideSettings becomes the always on variables.
Found a partial solution for unlocking MetroLL convergence.

If you drop in the regular version of 3Dmigoto (non-Bioshock version), it doesn't have any shaders patched or other changes, but it does unlock convergence. Might be overkill, but if you want or need the latest drivers with unlocked convergence, this sort of works.

Unfortunately it's only a partial solution, because if you try to enable mouse or key specific changes to convergence for aiming, it doesn't work. Whatever is specified in the OverrideSettings becomes the always on variables.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#37
Posted 10/25/2013 09:19 AM   
Hm. Does anyone even remotely understand how Chiri's unlocker works? Maybe there's a simple fix.
Hm. Does anyone even remotely understand how Chiri's unlocker works? Maybe there's a simple fix.

#38
Posted 10/25/2013 10:53 AM   
Well, I'm pretty sure I understand how this works. And I'm pretty sure that I even understand what went wrong now too. Not positive, I'm an expert programmer, but a true naif when it comes to Windows programming. [s]It looks to me like the IIDs for the NVAPI calls changed with the new driver, because it needed new calls to support G-Force. Since the API changed by adding 10 or so new functions, all the magic numbers changed. They are stable from driver to driver when the API is stable, but when the API changes, the numbers change. And this is the first change to the NVAPI in a looong time. [/s] [s]Assuming I'm right about what went wrong, I should be able to fix it. This is also something that new drivers will never fix, they'll never go back to the old IIDs. [/s] These aren't registry keys, in order to fix it, we need to compile a new version. Pretty sure I can do that, as Chiri generously provided the source code earlier. Chiri also kindly got back to me and said that the fix is easy, but that he won't be able to make a fix for awhile. So, we can definitely expect a fix. Not sure how long it will be. Until then, best bet is to use older drivers. Anything before 331.58 will work. 331.58 is the driver where they start supporting G-Sync. Edit: Well, that was a damn fine theory. Too bad it's just wrong. I did finally find the magic constants in the nvapi.lib, but they are the same for the calls in question. So, I don't know why it doesn't work. We'll just have to wait until Chiri gets an opportunity to take a look.
Well, I'm pretty sure I understand how this works. And I'm pretty sure that I even understand what went wrong now too. Not positive, I'm an expert programmer, but a true naif when it comes to Windows programming.

It looks to me like the IIDs for the NVAPI calls changed with the new driver, because it needed new calls to support G-Force. Since the API changed by adding 10 or so new functions, all the magic numbers changed. They are stable from driver to driver when the API is stable, but when the API changes, the numbers change. And this is the first change to the NVAPI in a looong time.


Assuming I'm right about what went wrong, I should be able to fix it. This is also something that new drivers will never fix, they'll never go back to the old IIDs. These aren't registry keys, in order to fix it, we need to compile a new version. Pretty sure I can do that, as Chiri generously provided the source code earlier.

Chiri also kindly got back to me and said that the fix is easy, but that he won't be able to make a fix for awhile.

So, we can definitely expect a fix. Not sure how long it will be. Until then, best bet is to use older drivers. Anything before 331.58 will work. 331.58 is the driver where they start supporting G-Sync.

Edit: Well, that was a damn fine theory. Too bad it's just wrong. I did finally find the magic constants in the nvapi.lib, but they are the same for the calls in question. So, I don't know why it doesn't work. We'll just have to wait until Chiri gets an opportunity to take a look.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#39
Posted 10/27/2013 12:04 AM   
Did you noticed that 3D Rating is back in latest drivers release note (331.65). 3D Vision Shadow Warrior – “Excellent” Call of Duty: Ghosts – “Fair” The Wolf Among Us – “Good” That is promising.
Did you noticed that 3D Rating is back in latest drivers release note (331.65).

3D Vision
Shadow Warrior – “Excellent”
Call of Duty: Ghosts – “Fair”
The Wolf Among Us – “Good”

That is promising.
[quote="djb"][quote="helifax"]Anyone tried in 3D Surround? I am curious as why they don't work for me....Going back to the previous beta or WHQL and is working properly...hmmm[/quote] Sorry took so long, 331.58 seems to work fine so far in 3d surround. I did the same install I always do. Rampage IV Extreme/bios 3010/3960K/Win7 64/Pro 16GB G.Skill F3-14900CL9D-8GBSR 3 X EVGA GTX 680/4GB, 04G-P4-2686-KR 3 X ASUS VG Series VG278H - Surround 3D 1 X EVGA GT 610 2 GB, 02G-P3-2617-KR 1 X Planar SA2311W whql 331.58 edit: just test Trine 2, more tomorrow.[/quote] Big thanks for the info. I am not sure why is not working for me.. The only difference I see is the GPU which mine is a Fermi (GTX590). Hmm I've sent them a bug in the first day when it was released. I tried installing the driver like 3 times. Everytime the same result...I wonder why (even went with driver sweep to remove everything) I'll try again...chances are very small to be a bad download... Thx again Edit: Apparently manually downloading the driver didn't work for me. However upgrading the driver through the Nvidia Geforce Experience installed it correctly...hmmmm Edit2: After playing some time in 3D Surround the driver kernel just crashes and tries to reboot (which fails...) bah... Going back to either the latest Betas or WHQL and I have no problem...-_- There is something wrong with these drivers and I expect is affecting only people with 500x or lower series...
djb said:
helifax said:Anyone tried in 3D Surround? I am curious as why they don't work for me....Going back to the previous beta or WHQL and is working properly...hmmm


Sorry took so long, 331.58 seems to work fine so far in 3d surround. I did the same install I always do.

Rampage IV Extreme/bios 3010/3960K/Win7 64/Pro
16GB G.Skill F3-14900CL9D-8GBSR
3 X EVGA GTX 680/4GB, 04G-P4-2686-KR
3 X ASUS VG Series VG278H - Surround 3D
1 X EVGA GT 610 2 GB, 02G-P3-2617-KR
1 X Planar SA2311W
whql 331.58

edit: just test Trine 2, more tomorrow.


Big thanks for the info.
I am not sure why is not working for me.. The only difference I see is the GPU which mine is a Fermi (GTX590).
Hmm I've sent them a bug in the first day when it was released. I tried installing the driver like 3 times. Everytime the same result...I wonder why (even went with driver sweep to remove everything)
I'll try again...chances are very small to be a bad download...

Thx again


Edit: Apparently manually downloading the driver didn't work for me. However upgrading the driver through the Nvidia Geforce Experience installed it correctly...hmmmm

Edit2: After playing some time in 3D Surround the driver kernel just crashes and tries to reboot (which fails...) bah... Going back to either the latest Betas or WHQL and I have no problem...-_-
There is something wrong with these drivers and I expect is affecting only people with 500x or lower series...

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#41
Posted 10/28/2013 05:25 PM   
For a data point, I'm running 331.58 with SLI GTX 580- pretty similar to a 590 of course. No problems for this combo in 3 days of use.
For a data point, I'm running 331.58 with SLI GTX 580- pretty similar to a 590 of course.
No problems for this combo in 3 days of use.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

#42
Posted 10/29/2013 03:23 AM   
[quote="bo3b"]For a data point, I'm running 331.58 with SLI GTX 580- pretty similar to a 590 of course. No problems for this combo in 3 days of use.[/quote] I would KILL to know what is happening on my system:)) I literally would kill:))) I have installed the drivers in any possible combination that I can think of...hmm Lately I have enabled the OnChip CPU - IGPu for some tests..and haven't disabled it yet... I wonder if that is what is causing the driver to behave like that...some researching needs to be done;))
bo3b said:For a data point, I'm running 331.58 with SLI GTX 580- pretty similar to a 590 of course.
No problems for this combo in 3 days of use.


I would KILL to know what is happening on my system:)) I literally would kill:))) I have installed the drivers in any possible combination that I can think of...hmm

Lately I have enabled the OnChip CPU - IGPu for some tests..and haven't disabled it yet... I wonder if that is what is causing the driver to behave like that...some researching needs to be done;))

1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc


My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com

(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)

#43
Posted 10/30/2013 12:59 AM   
  3 / 3    
Scroll To Top