Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Set launch options within Steam (for JC3) to "/borderless /windowed"
Then turn the ingame vsync OFF and the ingame fullscreen OFF.
I then have no tearing, and the FPS doesn't dip (running Win10). It still appears to be fullscreen due to the borderless window.
Only problem is that the FPS for me anyway goes up to about 400 FPS when in the menu, which makes my GPU scream with awful coil whine. Maybe I should use a frame limiter. Apart from that, it solved the issue.
Radeon Pro works, but the framerate still gets cut in half sub 60fps
Yeah, that's my solution for now. Not preffered since screen tearing happens whenever the game drops below 60 fps.
Borderless windowed launch command however alongside in game vsync gives the best experience; as it will cap the framerate and Windows vsync used in borderless mode will be triple buffered and avoid the 30/60 fluctuations by overriding the ingame double buffered solution.
So....use the launch command, dont get the problem. Budget cards will struggle regardless as they lack the power to display a fluid framerate but the better vsync option above will still make it seem smoother as it will sync the frames they can achieve to the refresh rate of the monitor.
They should add a better vsync solution in a patch, but ill bet that never happens. If you read this devs....double buffered vsync in 2015/2016 is not really good enough. This sort of thing makes a massive difference to gameplay smoothness. Getting it wrong is a bad move.
Ill also add that afaik Just cause 2 used double buffering too.