Caporegime
Cheers for that, good to see that about a single 780 too. Bsod issue on that server that time. Hopefully sorted with a boost on io/sa etc.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Its an odd one the high frame latency, as by all rights a high fluctuating frame time should feel quite poor, but it feels the complete opposite
The ROG swift needs to hurry up, I'm starting to realise what a waste a second 780 is at 1080 is.
Had a "driver not responding" error last night with the 337.50 beta drivers whilst playing FTL of all things!
Haven't had one of those in absolute yonks!
Must have been the high graphical demands of the game
...LoD biasing hasn't been working for a very long time in the Nvidia drivers...
I'm not sure. The article says that "no matter what you will set for this option, it will never be passed to your graphics card because the setting isn't actually read out". Whether that is referring to the Nvidia control panel or Nvidia inspector (or both) I don't know.I'm sure Nvidia are aware of this - it's listed as a known issue in driver release notes. Does forcing the setting via Inspector work?
Thanks Greg, I'm glad I finally joined up
Hi atomic I'm assuming Boston Lincolnshire? I swear we don't try and hog the sun down here in the west country Thanks for the warm welcomes guys I didn't intend to derail the thread so apologies Mr Boom sir! As a fellow west country man I hope you'll let this one slide Just to cover myself....Nvidia forever!! (but keep the pressure on AMD!)
http://techreport.com/review/26279/amd-radeon-r9-295-x2-graphics-card-reviewed/3Another problem that affects both AMD and Nvidia is a shortage of available resolutions. Any PC gamer worth his salt knows what to do when a game doesn't quite run well enough at the given resolution, especially if you have really high pixel densities at your command: just pop down to a lower res and let the video card or monitor scale things up to fill the screen. Dropping to 2560x1440 or 1920x1080 would seem like an obvious strategy with a display like this one. Yet too often, you're either stuck with 3840x2160 or bust. The video drivers from AMD and Nvidia don't consistently expose even these two obvious resolutions that are subsets of 3840x2160 or anything else remotely close. I'm not sure whether this issue will be worked out in the context of these dual-tile displays or not. Seems like they've been around quite a while already without the right thing happening. We may have to wait until the displays themselves get better scaler ASICs.