Dual Display Blinking
Maybe it has something to do with the screen refresh?
I use that resolution and run the game on 1 monitor and use a 2nd for everything else. It could be a couple of things. Windows 7 here, so I don’t think it’s completely a windows problem per say.
I’m wondering if it’s a power issue though. That your power supply isn’t able to keep up with the demand.
I’ve got a 250 watt power supply in the second display. The first one has a 212 watt supply. I don’t think it’s a power issue, because as I’ve said I changed the second one last week.
I only have had problems since the recent updates. Once all the screen refresh stuff is done, it finally settles down and I can use the second display as normal.
I’ve also tried repairing the clients on both Mac OS X and Windows 7.
(edited by Necromus.9276)
I’ve got a 250 watt power supply in the second display. The first one has a 212 watt supply. I don’t think it’s a power issue, because as I’ve said I changed the second one last week.
I only have had problems since the recent updates. Once all the screen refresh stuff is done, it finally settles down and I can use the second display as normal.
I’ve also tried repairing the clients on both Mac OS X and Windows 7.
I was more referring to your computers power supply to your video card. It was sounding it like can’t keep up.
I’ve got a 250 watt power supply in the second display. The first one has a 212 watt supply. I don’t think it’s a power issue, because as I’ve said I changed the second one last week.
I only have had problems since the recent updates. Once all the screen refresh stuff is done, it finally settles down and I can use the second display as normal.
I’ve also tried repairing the clients on both Mac OS X and Windows 7.
I was more referring to your computers power supply to your video card. It was sounding it like can’t keep up.
OP should look at this thread then:
http://www.tomshardware.com/forum/348043-33-graphics-card-power
MSI GTX 1080 Sea Hawk EK X 2xSLI 2025 / 11016 MHz, liquid cooling custom loop.
Samsung 850 Evo 500 GB. HTC Vive.
I don’t think it’s a graphic card problem. Like I said the only time it screws up is when I’m running the game itself.
I just noticed that when it happens something called DMProxy keeps running multiple times. Haven’t been able to find much info on what this is supposed to do, but it only shows up when the game keeps blinking the displays.
What kind of mac do you have, what kind of screen do you have, and what port are you using?
There are compatibility issues with some macs and HDMI screens that results in flickering. Could that be the issue?
(Also as to it being a graphics card issue, just because it’s only when you’re running the game doesn’t rule that out. The game puts a heavier load on your GPU, so combined with driving a second display that could be putting a strain on it) – what graphics card do you have?
I’m using an iMac 27" with the Apple 27" LED Cinema display. Uses the mini display port.
It has a Core i7 (2.93 Ghz) with an ATI Radeon HD 5750 (1 GB GDDR5), 16 GB RAM.
No HDMI at all.
I’m using an iMac 27" with the Apple 27" LED Cinema display. Uses the mini display port.
It has a Core i7 (2.93 Ghz) with an ATI Radeon HD 5750 (1 GB GDDR5), 16 GB RAM.
No HDMI at all.
Is it possible for you to update your graphics drivers? the AMD website should have them. I recommend using the 13.2 version instead of the newer 15.1 version (which doesn’t support your mac anyway).
It’s strange that it’s only a recent issue.
Have you tried changing the resolution in game to force it to recompile the settings? e.g. maybe try running the game in full screen for a minute and then go back to windowed mode. And make sure that you check which display is being registered as your primary display in windows.
(edited by FlamingFoxx.1305)
Well I tried your suggestion and it works to keep it from going nuts. The game still mucks with the second display until I make the game go full screen and then back to windowed mode. After that everything is happy. It stays that way until I run the client again.
At least this is a work-around, if not a bit clunky. Hopefully they can figure out what is causing the problem soon.