AOC G2460PF

coreupted · 1 Dec 2015 at 12:05

Tried PCM2's driver and it's saying in AMD crimson from 30 to 144 where as before from 48 to 144.
I've never had any of the problems others have on this monitor, but thanks to PMC2, this monitor is now as it should be.
In monitor asset Manager for vertical it is still saying 48 to 146

PCM2 · 1 Dec 2015 at 12:15

coreupted said:
Tried PCM2's driver and it's saying in AMD crimson from 30 to 144 where as before from 48 to 144.
I've never had any of the problems others have on this monitor, but thanks to PMC2, this monitor is now as it should be.
In monitor asset Manager for vertical it is still saying 48 to 146

Are you sure you're viewing the active entry with the new driver, not one of the previous entries for 'G2460P' (or whatever it's called there)?

coreupted · 1 Dec 2015 at 12:21

Definitely saying 2460G4 48 to 146

henson0115 · 1 Dec 2015 at 12:26

you will need to reboot after installing the driver, else monitor info, will not update. i noticed this whilst testing a while ago.

coreupted · 1 Dec 2015 at 12:26

Checked freesync demo and 35fps is there as before it wasn't.

PCM2 · 1 Dec 2015 at 12:27

coreupted said:
Definitely saying 2460G4 48 to 146

But didn't you have the 'official non-WHQL' installed previously? I'd recommend removing the monitor completely from device manager and allowing it to display as a 'Plug and Play' monitor. Then disabling driver enforcement as required to correctly install the beta driver given on my link.

Maybe somehow the new 'Crimson' drivers are changing how this is reported, although that seems a bit odd if so.

coreupted · 1 Dec 2015 at 12:30

PCM2 said:
But didn't you have the 'official non-WHQL' installed previously? I'd recommend removing the monitor completely from device manager and allowing it to display as a 'Plug and Play' monitor. Then disabling driver enforcement as required to correctly install the beta driver given on my link.

Maybe somehow the new 'Crimson' drivers are changing how this is reported, although that seems a bit odd if so.

Already done this and checked mam then rebooted and still same.

coreupted · 1 Dec 2015 at 12:30

henson0115 said:
you will need to reboot after installing the driver, else monitor info, will not update. i noticed this whilst testing a while ago.

Done this also

henson0115 · 1 Dec 2015 at 13:04

coreupted said:
Done this also

only other thing is, in the top left corner of the software, you may notice multiple entrys for the monitor. have you clicked them all if you do have more than one?

if the amd freesync app is working, then i suppose thats confirmation enough. also crimson tells you in the display section the freesync value now.

Barnacles · 1 Dec 2015 at 13:14

henson0115 said:
hopefully, freesync will go from strength to strength as it is still in early stages.

i hope they also fix the annoying issue of display corruption with freesync enabled and launching games in fullscreeen mode occasionally.(alt tabbing a few times normally fixes this)

the flickering at 144hz, was it because you were jumping outside of the freesync range? have you tested this recently with crimson? i run mine at 120 as at 144 the memory clocks do not down clock when idle at 144, i do however run games at 144 where the game allows an override and cant say i have noticed any flickering i do however use a frame limiter.

perhaps you are jumping in and out of the range and that is causing the flicker.

yes, I should try the frame-limiter idea - actually I'm using that with rivatuner to cap at 58 with my current setting of 60 hz, as I noticed a kind of slow pulse / stutter (I mean like every second or so) at 60fps sometimes.

I know what you mean about the display corruption thing - a right pain, particularly with morrowind, which doesn't allow alt-tabbing without tweaks!

coreupted · 1 Dec 2015 at 13:18

henson0115 said:
only other thing is, in the top left corner of the software, you may notice multiple entrys for the monitor. have you clicked them all if you do have more than one?

if the amd freesync app is working, then i suppose thats confirmation enough. also crimson tells you in the display section the freesync value now.

The demo says 35 as before it was 50, crimson says 30 as before said 48.
The only thing that hasn't changed is MAM.

coreupted · 1 Dec 2015 at 13:24

Just updated crimson driver and now when i look at mam it says 30 to 146 yeeha..
So everything seems sorted now.

Maybe needed to reboot more than once.

humbugmx · 1 Dec 2015 at 13:34

Barnacles said:
yes, I should try the frame-limiter idea - actually I'm using that with rivatuner to cap at 58 with my current setting of 60 hz, as I noticed a kind of slow pulse / stutter (I mean like every second or so) at 60fps sometimes.

I know what you mean about the display corruption thing - a right pain, particularly with morrowind, which doesn't allow alt-tabbing without tweaks!

Just a quick question regarding the 'proper' use of freesync. It's meant to be run with vsync always on in the driver, freesync doing its thing and vsync kicking in again, when the frames get out of the freesync range, isn't it?

henson0115 · 1 Dec 2015 at 13:34

the demo will allow you to test freesync 5hz higher than your limit, so if you can do 30hz with freesync enabled, then it will allow you to test 35fps, if you can do 55hz, then it will let you test 60fps etc.

I know what you mean about the display corruption thing - a right pain, particularly with morrowind, which doesn't allow alt-tabbing without tweaks!
Just a quick question regarding the 'proper' use of freesync. It's meant to be run with vsync always on in the driver, freesync doing its thing and vsync kicking in again, when the frames get out of the freesync range, isn't it?
Last edited by humbugmx; 1st Dec 2015 at 13:37.

if you are not able to produce a constant freesync framerate, then ideally you would have vsync enabled. however it does introduce mouse lag.

henson0115 · 1 Dec 2015 at 20:10

PCM2 said:
Right.... I'm really not sure what's going on with these drivers, but I am going to be in contact with AOC about this. In the meantime I have uploaded the drivers I was provided for the review. These worked properly for the FreeSync range and can be found in the review itself or on my Twitter - https://twitter.com/pcmonitors/status/671606049569447936.

they work perfect for me pcm, 30hz-146hz freesync range. thank you

PCM2 · 1 Dec 2015 at 20:19

Glad the beta drivers are working for you guys! :cool:

I'll let AOC know so hopefully it can kick something into gear. Whatever that something is, I'm not sure.

jbnitro · 1 Dec 2015 at 21:00

with your beta driver for me MyInfo always displays 48 / 146hz but on amd freesync demo I can check 35Hz for tests

humbugmx · 1 Dec 2015 at 21:47

Good news, everyone! Beta driver is also working on my side.

One strange observation and maybe an explanation for a WHQL delay:
Flickering at 144Hz/Freesync is now gone but only for windmill demo, still there in games.
On the other hand now some games that had been flicker-free with 120Hz are now flickering.

PCM2 · 1 Dec 2015 at 22:13

jbnitro said:
with your beta driver for me MyInfo always displays 48 / 146hz but on amd freesync demo I can check 35Hz for tests

coreupted had the same issue and it was fixed when he reinstalled/updated the graphics driver. But it will be running with the 30Hz floor anyway regardless of what is being reported on the monitor asset manager.

jbnitro · 1 Dec 2015 at 22:29

PCM2 said:
coreupted had the same issue and it was fixed when he reinstalled/updated the graphics driver. But it will be running with the 30Hz floor anyway regardless of what is being reported on the monitor asset manager.

ok I'll redo the update then, but thank you for the review, the optimal parameters OSD settings and your icc are perfect

edit : after update drivers always 48/146 on mam :/