Slashdot Mirror
Multi-Display Gaming Artifacts Shown With AMD, 4K Affected Too
Vigile writes "Multi-display gaming has really found a niche in the world of high-end PC gaming, starting when AMD released Eyefinity in 2009 in three-panel configurations. AMD expanded out to six-screen options in 2010 and NVIDIA followed shortly thereafter with a similar multi-screen solution called Surround. Over the last 12 months or so, GPU performance testing has gone through a sort of revolution as the move from software measurement to hardware capture measurement has taken hold. PC Perspective has done testing with this new technology on AMD Eyefinity and NVIDIA Surround configurations at 5760x1080 resolution and found there were some substantial anomalies in the AMD captures. The AMD cards exhibited dropped frames, interleaved frames (jumping back and forth between buffers) and even stepped, non-horizontal vertical sync tearing. The result is a much lower observed frame rate than software like FRAPS would indicate and these problems will also be found when using the current top-end, dual-head 4K PC displays since they emulate Eyefinity and Surround for setup."
Yet, here you are posting, instead of over at wearetheworld.org. Just because people are starving doesn't mean that this isn't a problem worthy of mention for others. This is a tech site. If you want coverage of famine, there's a bevy of leftwing rags out there that talk about it every day. Go read one of those.
This 'first world problem' routine is little more than politically correct shaming language, meant to shame people focused on their own issues into caring only about whatever the speaker wants them to focus on (usually some identity politics 'crisis.').
I've got 5 monitors connected to 2 ATI cards (Linux + Xinerama).
The most interesting artefact I've seen is some apps can corrupt the cursor so the pointer is a little bit of random memory contents.
But only on some monitors. Move it to another monitor and it may come back, move it to the original monitor and it dies again.
There must be some really fun bugs in their drivers that rear their heads with massive setups.
I was playing flight sims on my Quadra 900 in the late 80s/early 90s with 4 displays. The resolutions and detail may be higher today, but I never had any issues or failures of the system. FA/18 Hornet was my favorite.
Article X: The powers not delegated... by the Constitution...are reserved...to the people
I've got 5 monitors connected to 2 ATI cards (Linux + Xinerama).
The most interesting artefact I've seen is some apps can corrupt the cursor so the pointer is a little bit of random memory contents. But only on some monitors. Move it to another monitor and it may come back, move it to the original monitor and it dies again.
There must be some really fun bugs in their drivers that rear their heads with massive setups.
I actually get this exact same problem on my Windows 7 desktop (3 monitors). The primary display cursor will sometimes have fragments of the cursor graphics or loading animation displayed but moving the cursor across each screens fast and back again can sometimes resolve it. Interesting that its a problem on both platforms.
Hmm...AMD is about to drop Hawaii and retake the single GPU crown and GUESS WHAT! Another round of FUD from the company that cancelled their next premium GPU in the name of funding also-ran ARM devices and niche handheld gaming devices. Fuck off, Jens. You played your hand now reap what you sow.
Note that the words "driver" and "version" don't occur on the page. There is a know issue that AMDs been working that sounds a lot like this issue. It's been known for months, they've got a "two phase" plan to attack it, the first of which is implemented in the current beta driver-set.
The timing of this article is very suspect. They're either reporting on a new problem (and totally failing at providing any relevant data on their configuration), or they're simpy regurgitating an already know issue, like doing a big splashy article about a bug report.
As a useful point, this has been an on-going issue with Nvidia drivers since about 290ish--and in the last three releases on 400,500 and some 600's where the drivers were so bad that they caused hardlocks across the board. Where either the drivers have been crap, or causing hardware lockups, or the various reports that can't be confirmed of them nuking hardware. In fact, it got so bad back 6mo ago that nvidia was looking for people in the continental US to send their entire rigs in to their hardware labs for testing. So, people thinking that this is a "flameware" or some other asinine thing, need to realize that there's driver issues on both sides. Sometimes however, the issues are more serious than reported for one side or the other. And between the two, nvidia has the more serious driver issue, and that's coming from someone who's last 6 cards have all been nvidia made by evga--three of which that had to be RMA'd because of a sudden hardware failure after a driver update.
Thinking on this a bit more, it reminds me of how nvidia was at one point blaming the driver reset issue only on "bad configurations" and "PSU power issues" until it was found that undervolting or overvolting(mainly) the cards solved this problem. Especially on the 500 series cards, this was of course after they had adjusted the voltage supplied to the cards downward, in order to make them run cooler.
Om, nomnomnom...