Jump to content

- - - - -

Gsync Not Working Right On Certain Maps

Help Me

7 replies to this topic

#1 Serpentine Shel Serpentine

    Member

  • PipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 187 posts

Posted 21 March 2018 - 06:55 AM

Hello: I have noticed on certain maps that Gsync fails at smoothing terrain rendering. On polar highlands and some others I notice that the ground does not evenly propagate as I move forward, such that there is stuttering and a wave effect as the terrain changes with a noticeable rippling or abrupt changes. I do not notice any artifacts on the mechs at all. I run an i7-6700 and GTX 1070 with a 144 Mhz Gsync monitor 2560x1440 with Gsync activated for windowed and full screen mode (Dell S2417DG). I had seen this with a 2009-era 1080 monitor but expected Gsync to smooth it out. But nothing changed with the new monitor. Is this a known issue? Any suggestions to fix it? Thanks - Serpentine

To add more details: I connect with Displayport which is required for GSync. Monitor and Nividia Control panel confirm Gsync is enabled. Max graphics settings for MWO at the native 1440 resolution for my monitor. Framerate is always good.

Edited by Serpentine Shel Serpentine, 21 March 2018 - 09:35 AM.


#2 Napoleon_Blownapart

    Member

  • PipPipPipPipPipPipPipPip
  • Shredder
  • Shredder
  • 1,173 posts

Posted 21 March 2018 - 09:06 AM

how do you connect the monitor to the comp?i have an AMD card with a freesync monitor and have read that i needed a displayport cable to use freesync (hdmi might work ) but not DVI.

#3 Serpentine Shel Serpentine

    Member

  • PipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 187 posts

Posted 21 March 2018 - 09:34 AM

View PostGorantir, on 21 March 2018 - 09:06 AM, said:

how do you connect the monitor to the comp?i have an AMD card with a freesync monitor and have read that i needed a displayport cable to use freesync (hdmi might work ) but not DVI.


Displayport. Monitor and Nividia Control panel confirm Gsync is enabled. Also max graphics settings for MWO at the native 1440 resolution for my monitor.

#4 Napoleon_Blownapart

    Member

  • PipPipPipPipPipPipPipPip
  • Shredder
  • Shredder
  • 1,173 posts

Posted 21 March 2018 - 11:40 AM

you might want to repost this in general discussion>archives>hardware and accessories where NARC BAIT might see it , he is very tech savvy and may know more. my card is old and has very little of the bells and whistles to go with my new freesync monitor.

try changing your in-game vsync setting maybe?

I do not claim to be knowledgeablePosted Image but I try to help Posted Image

#5 justcallme A S H

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • CS 2020 Referee
  • CS 2020 Referee
  • 8,987 posts
  • LocationMelbourne, AU

Posted 21 March 2018 - 05:27 PM

Just how the game is.

GTX1070 / gsync also. It's just terrain tear/rendering. Been a problem since, forever. Gsync can't fix a game rendering issue

Edited by justcallme A S H, 21 March 2018 - 05:27 PM.


#6 Squiggy McPew

    Member

  • PipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 755 posts

Posted 21 March 2018 - 06:07 PM

A gtx 960 with a dsub connection to a 1080p panel gets the same tearing. Its a game engine issue not hardware.

#7 Ruccus

    Member

  • PipPipPipPipPipPipPipPip
  • The Bloodlust
  • The Bloodlust
  • 1,136 posts
  • LocationAbbotsford, BC

Posted 21 March 2018 - 06:22 PM

All gsync/freesync does is eliminate screen tearing, just like v-sync. The difference is that freesync/gsync can do it at variable framerates instead of your graphics card having to sync with the monitor's refresh rate. This means on screen gameplay can look smoother and seamless well below a 60hz refresh rate so you can run higher graphics settings giving you lower framerates while still having the game be playable.

Maxing out the anisotrophic filtering settings might help with the terrain change, or at least give you higher detail at further distances. With regards to the 'stutter', if it's what I really think it is that's actually a sign the game engine gives you that there's an enemy nearby. When the game feeds in the enemy mech's information to be ready to render when the mech pops into your view you can get a stutter. This usually happens for your first encounter with the enemy; when you get that stutter be ready to start fighting and if you think you're still a distance from the enemy check behind you to see if an enemy light is scouting for your location.

#8 Squiggy McPew

    Member

  • PipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 755 posts

Posted 24 March 2018 - 12:17 PM

Yeah forgot that trick. Ingame settings don't allow for changing the af level so you have to go into the driver and set it to 8/16x so distant objects don't look like a pixelated mess.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users