• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Another Pascal bug? (THW)

3

3DVagabond

Lifer
Nvidia GeForce GTX 1080 Doesn’t Boost In VR With The Latest Game Ready Driver

Last week we reported that there is a compatibility issue between the HTC Vive and Nvidia’s Pascal-based graphics cards. Nvidia said that a solution is coming this week, but we’ve now discovered another problem.
Nvidia released GeForce Game Ready Driver 368.69 on July 6 in preparation for the impending release of Codemasters’ Dirt Rally VR update. Though this driver is meant to prepare your system for a VR game, the update (rather ironically) broke the ability for the GTX 1080 to put its impressive boost clock to work. We tested the driver to see if the Vive display port issue was corrected, but we had no reason to monitor boost clocks at the time.
Click to expand...

Seems Maxwell is fine.
We can’t say for sure if this will happen with the GTX 1070, because we don’t have one at the lab where our VR equipment is. However, we can verify that this does not happen with Maxwell-based cards.
Click to expand...
 
I am sure they will fix it quickly, but hopefully these issues help dispel the illusion that AMD is the only one that has issues in their drivers. I have maintained for a while that both parties have issues. You are going to end up with drivers from either camp that have quirks especially if you use a fringe technology. Both manufacturers will fix it.
 
This happens with new toys.. a driver update away i am sure... wish we could dial the doom and gloom down thou' .. (not op)
 
digitaldurandal said:
I am sure they will fix it quickly, but hopefully these issues help dispel the illusion that AMD is the only one that has issues in their drivers. I have maintained for a while that both parties have issues. You are going to end up with drivers from either camp that have quirks especially if you use a fringe technology. Both manufacturers will fix it.
Click to expand...

Big difference between a new card\architecture driver bug & broken CF drivers lasting almost 18 mths.
 
SolMiester said:
Big difference between a new card\architecture driver bug & broken CF drivers lasting almost 18 mths.
Click to expand...

Right because Nvidia doesn't have any known issues...

http://us.download.nvidia.com/Windows/368.69/368.69-win10-win8-win7-desktop-release-notes.pdf

Just copying the SLI related ones but there are pages of them in total...


  • [SLI] Street Fighter V performance drop (pause and play) observed when the game is played at 4K resolution with SLI enabled. [200172046]
  • [SLI] Blank display is observed on disabling SLI with two displays connected.
  • [200168702]
  • [SLI, UEFI] Event Viewer error 14 points to nvlddmkm when the system is rebooted.
  • [1309257]
  • [SLI] Mirrors Edge: Catalyst crashes with DirectX error on launch. [1773411]
  • [SLI, GeForce 500 series, DirectX 11, Dragon Age II] Shadows flicker in the cutscene
  • when SLI is enabled. [849235]
  • [SLI, Company of Heroes: Tales of Valor] With SLI enabled, there is heavy flickering in the game after switching from windowed mode to full-screen mode. [892264]

This one cracks me up though, COH shut down years ago:

  • City of Heroes–The mouse cursor does not display. [259256]
    This is an application issue that can be worked around in full-screen mode by adding
    “compatible cursors 1” to the City of Heroes desktop shortcut.
    NVIDIA is pursuing a fix with the application developer.
 
Update, 7/11/16, 9:50pm PT: We received a reply from Nvidia's Senior PR Manager, Brian Del Rizzo, about the issue. Nvidia was aware of the problem and already has a solution. Del Rizzo said that the new driver that is due later this week will solve the Boost clock issue as well as the Display Port to Vive incompatibility.
Click to expand...

I was assured by certain people that this was an unfixable hardware flaw.
 
^Yeah that's nonsense. NV could not be so incompetent as to design simultaneous multi-projection for Pascal, yet overlook unfixable hardware issues that make it basically incompatible with VR...
 
3DVagabond said:
Who? Especially the subject of this thread since I haven't seen anyone say it.
Click to expand...

Look at the thread list. Some people are gleefully running "design flaw" watchlists.

Not saying that the green camp was any better with the RX 480 power issues and their speculation that it couldn't be fixed by re-balancing the VRM load.

That said, these bugs are pretty embarrassing for Nvidia when they're selling halo cards. Maybe the guy doing 90% of the work in driver validation finally rage quit after years of carrying the team.
 
jj109 said:
Look at the thread list. Some people are gleefully running "design flaw" watchlists.

Not saying that the green camp was any better with the RX 480 power issues and their speculation that it couldn't be fixed by re-balancing the VRM load.

That said, these bugs are pretty embarrassing for Nvidia when they're selling halo cards. Maybe the guy doing 90% of the work in driver validation finally rage quit after years of carrying the team.
Click to expand...

Pretty bad to miss this on what they call a "game ready driver" release. Personally I've thought for a while now that game ready drivers are nothing but hype and marketing. This lends to that belief.
 
Bacon1 said:
Right because Nvidia doesn't have any known issues...

http://us.download.nvidia.com/Windows/368.69/368.69-win10-win8-win7-desktop-release-notes.pdf

Just copying the SLI related ones but there are pages of them in total...


  • [SLI] Street Fighter V performance drop (pause and play) observed when the game is played at 4K resolution with SLI enabled. [200172046]
  • [SLI] Blank display is observed on disabling SLI with two displays connected.
  • [200168702]
  • [SLI, UEFI] Event Viewer error 14 points to nvlddmkm when the system is rebooted.
  • [1309257]
  • [SLI] Mirrors Edge: Catalyst crashes with DirectX error on launch. [1773411]
  • [SLI, GeForce 500 series, DirectX 11, Dragon Age II] Shadows flicker in the cutscene
  • when SLI is enabled. [849235]
  • [SLI, Company of Heroes: Tales of Valor] With SLI enabled, there is heavy flickering in the game after switching from windowed mode to full-screen mode. [892264]

This one cracks me up though, COH shut down years ago:

  • City of Heroes–The mouse cursor does not display. [259256]
    This is an application issue that can be worked around in full-screen mode by adding
    “compatible cursors 1” to the City of Heroes desktop shortcut.
    NVIDIA is pursuing a fix with the application developer.
Click to expand...

Oh dear, another reading comprehension failure. No one said NV dont have 'issues', I think its great they actually list them for customers.

I was pointing out that a bug is a long way from broken drivers....do you understand that?
 
Most bugs are just that, bugs that can get squashed. Its hard for some to realize that a problem they have is not a projection of a huge audience on the internet. If someone has a problem with a VR headset not working on a 1080, its still less than ...0001% of total users.
 
SolMiester said:
Oh dear, another reading comprehension failure. No one said NV dont have 'issues', I think its great they actually list them for customers.

I was pointing out that a bug is a long way from broken drivers....do you understand that?
Click to expand...

No, you specifically called out AMD having known CF driver issues (flickering), so I specifically mentioned that Nvidia has the same issues.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top