It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Fellow GoG users,

I just want to pre-empt where this thread might go by saying that yes, I know that playing early 2000s/late 90s games on a G-Sync monitor isn't the best use of the technology, but I needed a new monitor anyway, and found that G-sync really helps reduce the headaches I got from screen usage.

So, basically, I have bought a G-sync monitor (AOC G2460PG) for my Windows 7x64 FX-8350 with GTX 660. For modern games, it is fantastic; a real reduction in screen judder and no more tearing at high FPS. Couldn't be happier with it - Shadow Warrior 2013 runs great, as does Saints Row 3.

However, I have found some issues with older games, and have been doing some searching on the net. However, because of the nature of the screens (not cheap and used a lot by online FPS kids) there isn't much on how the screens work with older games. I'll summarise what I've found so far below, but my question is really - do I have an issue with my screen's G-sync unit, do I have a driver issue, or were some game engines coded in such a way to be full on incompatible with G-sync?

The games I list below work perfectly if I turn off g-sync/create a custom profile in the graphics driver to not use g-sync.

Games which refuse to run (crash to desktop)
- Rogue Squadron
- Jedi Knight (menus work fine; when the 3d engine kicks in, the game crashes to desktop)
- Microsoft Starlancer (I know it's not a GoG and I should be thankful it works at all, but included here for completeness)

Games which have serious issues with G-Sync:
- F.E.A.R. (unplayable jerking even in menus)
- F.E.A.R. 2 (see above)


GoGs which run fine
- Costume Quest
- Daiktana
- Divinity 2 (note that there is some screen flicker where the FPS drops to zero)
- Quake III
- Shadow Warrior (2013)
- TOCA Race Driver 3 (although not sold anymore by GoG)




So - people of GoG - any thoughts?
Post edited January 05, 2016 by pds41
When I had a gsync monitor, there were a lot of games that did not work properly like Outlaws, but other games like Wizardry 8 worked great with it however. If a game did not start up, I knew to disable gsync for the game and go with regular vsync.
With some of the older games, it's possible there's an issue running them above 60fps. Not sure what FPS you're running them at, but try using RTSS or something to cap them to 60.

I haven't had issues with older games, but I haven't played too many on my G-Sync as of yet.
avatar
pds41: So - people of GoG - any thoughts?
Use AMD and Freesync instead. Problem solved. ( ͡° ͜ʖ ͡°)
Outlaws works fine with AMD + freesync without any changes.
avatar
qwixter: When I had a gsync monitor, there were a lot of games that did not work properly like Outlaws, but other games like Wizardry 8 worked great with it however. If a game did not start up, I knew to disable gsync for the game and go with regular vsync.
Yeah - that's the approach I've been going with. It's a little bit irritating to have to do, but at least I can play the games. I'm also glad I'm not the only person to be having these issues with a G-sync monitor!

It would be interesting to do a comparison between G-sync and freesync for old game compatibility; I'm tempted to turn this thread into a compatibility list for games and variable refresh monitors. At the weekend I'll see if outlaws has any issues on my machine with g-sync. It's possible that the glide wrapper might cause problems.

@Chacranajxy - I'd assume my GTX660 is throwing a lot of frames at Rogue Squadron, although it seems to work fine if I turn g-sync off (although the graphics drivers then by default chuck v-sync on - but it still might be trying to throw 144 frames at the game - unless it by default limits the refresh rate to 60). If any of that rambling makes sense!