Monitor Tests Forum

Full Version: AMD/ATI Pixel Clock Patcher
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
When u said about V-sync issue with crossfire what exactly do u mean?
(02-19-2013 07:04 AM)ToastyX Wrote: [ -> ]
(02-18-2013 12:06 PM)y2kcamgameaross Wrote: [ -> ]Okay I found out what it's doing, whatever I set my refresh rate to in and then I've I set vsync in game, it halves the frame rate, so if I set the frame rate to 110 and enable vsync, it's 55 fps, I then tried 115 and it would bounce between 57 and 58 with vsync enabled, Is there anyway to fix that?
That's how vsync is supposed to work if the video cards aren't powerful enough for the frame rate to match the refresh rate. The frame rate with vsync can only be an evenly divisible fraction of the refresh rate like 1, 1/2, 1/3, 1/4, etc. For 120 Hz, that would be 120, 60, 40, 30, 24, 20, etc.

Check the frame rate without vsync. If the monitor is set to 110 Hz but the video cards can only pump out 90 FPS, then it will only show 55 FPS with vsync enabled.
I know how vsync works, what im saying is regardless of the game or settings the game will only lock at half of what the refresh rate is set to, without vync fit instance I can run cod4 @ 200+fps, with it will run@60 if set@120hz, 45 at 99hz, etc
Does the frame rate problem happen under the same conditions that the vsync crash did? By that I mean does it happen based on the pixel clock limit you encountered?

Maybe something else in the driver needs to be changed, but I don't have a CrossFire setup to test.

I have three patched files for you to test. I'd like to know if any of those help with the vsync crash as well.

If none of those help, there's probably nothing I can do about this, especially since you mentioned the vsync crash happening without the patched driver.
I'll try those when I get off work tonight, and I fixed the vsync crash by using 2 crossfire bridges instead of 1, odd I know, but I tried 5 different bridges individually on differnt crossfire fingersand they would all crash unless there was a second bridge connected
(02-19-2013 11:11 PM)ToastyX Wrote: [ -> ]Does the frame rate problem happen under the same conditions that the vsync crash did? By that I mean does it happen based on the pixel clock limit you encountered?

Maybe something else in the driver needs to be changed, but I don't have a CrossFire setup to test.

I have three patched files for you to test. I'd like to know if any of those help with the vsync crash as well.

If none of those help, there's probably nothing I can do about this, especially since you mentioned the vsync crash happening without the patched driver.

well good news and bad news, the Test 2 that you gave me fixed the vsync problem completley, the only problem was it looked like I was tripping on acid while playing, colors are completely distorted and what not, the other 2 didn't exhibit the same behaviors, but they also didnt fix the vsync problem

and some games seen to be crashing on startup and resetting my ati driver, but cs go and bf3 had perfect smooth vsync with psychedelic colors
That's weird. The third file includes the changes from the first two files, so I don't know why the second one would do that and not the third.
(02-22-2013 08:30 PM)ToastyX Wrote: [ -> ]That's weird. The third file includes the changes from the first two files, so I don't know why the second one would do that and not the third.

I want you to know I have fixed this problem, it all came down to Windows and how they were identifiying my monitors, evne though my catleap was hooked up first, whenever my secondary monitor was hooked up to my PC it would relabel my catleap as monitor 2 and my acer as monitor 1, as far as I know there is no way to change that in Windows 7/8, I do believe Vista had a registry hack where you could alter the way windows identified them, so what I did was go into my CCC/desktop management/creating and arranging desktops, and you can switch the identies around in there, although it doesnt actually switch them in the windows, it switches them enough for the graphics cards for it to work, then I enabled vsync and everything was perfect. Tried again by switching the monitors back to how they are in windows(Catleap monitor 2, acer identified as monitor 1) and once again, vsync is broken. I can't believe there is no way in Windows to switch the identities around, seems like a pretty big oversight
Yeah, I'm having issues with crossfire and vsync too. I use tri-fire so using two bridges isn't an option for me.
Hi Guys,

Since I've started using CRU-p4 and the driver patcher, I see the frame rate on the top left corner in bright yellow colour.

How can one get rid of it?

Also, I've tried OC my refresh rate to no avail. I get a message on my LCD after I reboot to have the changes take affect, that the timings are not correct. But I used the my own LCD timings.

I use DELL U2412M and ATI HD6950 with latest drivers.
Can someone help please?
(02-27-2013 11:04 PM)BababooeyHTJ Wrote: [ -> ]Yeah, I'm having issues with crossfire and vsync too. I use tri-fire so using two bridges isn't an option for me.


You using two monitors? If so, remove the non 1440p display and see how it goes
Reference URL's