Try running the game on minimum settings and recording FPS both for windowed and full screen.
(This save file was made legit without the use of CheatEngine for whatever it's worth to those who care) View mod page. Even stepping down from AA16 to AA4 will give the speed difference you're talking about. Enjoy starting a new game of Sleeping Dogs without worrying about the collectathon grind that distracts from the better parts of the game. Windowed Support - Some graphics cards disable FSAA and other features while windowed mode. Disable your built in GPU using BIOS, Fable could be using it as a default display adapter. OnBoard Confusion - Depends on your config. (Solved by closing a lot of useless crap that you'll have running all the time. When you're in windowed mode, I suspect, your computer uses a range of threads to handle all available tasks, allowing Fable to have more of the threads available to it. A mature, gritty undercover cop drama where a wrong decision can blow your cover at any time. FEATURES: -With all previously available content included and a wealth of new improvements, Hong Kong has never felt so alive. This is a modern gaming engineering fault, and they're only just starting to allow games 8/16 thread support. Sleeping Dogs Hong Kong is the ultimate playground. you can read about it here:Īdaptive vsync helped but did not completely eliminate the stuttering with my GTX 670 4gb SC card, the final solution was to download an tiny program called d3d antilag from here:Īffinity - If Fable 3, like most modern PC games, can only use a certain number (IE, 2) of your available CPU threads, and you are running it full screen, your computer will end up running at around 1/4 of it's total available speed. running it in fullscreen windowed makes a huge difference.
My question is, what is the real reason so many games have this problem with full screen in win 7? is it a problem with directx and win7 fullscreen mode, and could we inform microsoft of it so they patch it?ītw, this guy wrote a nice borderless window app here:Įdit: since I posted this, i bought sleeping dogs on steam sale, and this title definitely suffers from the same problem of fullscreen stuttering, even worse than darksiders 2. Lots of people reported doing this trick to fix stuttering in sleeping dogs and dark souls, also. Two examples are : 1) skyrim, the camera panning would not be perfectly smooth unless i ran it in windowed mode, and same thing happens with 2) darksiders 2, the game was extremely choppy until i ran it in windowed mode, using a borderless window app to make it look just as good as fullscreen mode and forcing vsync on, triple buffering off, with triple buffering on forced in nvidia control panel, By continuing to use this site, you are consenting to our use of cookies.
It seems like there must be something wrong with the way windows 7 handles fullscreen games, because so many games framerate drops and stuttering are fixed by using windowed mode and d3doverrider to force vsync? This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. The problem I'm describing looks like low fps even though a framerate indicator shows 60fps - for instance in darksiders 2, when i stand still and move the camera around, the scenery that is in motion sort of moves in a slightly jumpy/stuttery way, rather than perfectly smooth, as if frames are being skipped, resulting in a low fps look to the motion. Has anyone figured out exactly why borderless window fixes framerate stuttering/drops in so many games?
After that I tried disabling the f-sync with the Proton flag to check that was it, and it seems so.Figured out why borderless window fixes framerate stuttering in many games Then I saw a Youtube Video ( ) and thought the the main difference could be the f-sync kernel patch, so I got it for Fedora and tried again and the game was running incredibly well.
It was weird, because the game is not that impressive on the graphics side, the GPU usage was under 30% and the 16 CPU Threads were with a 75% usage.
The only difference there was using the PROTON_NO_FSYNC=1 for testing purposes. Notes: It required the mfplat patch to boot (Bacuse of the boot video sequences with companies logo). I would like for someone else to try by themselves, but this looks like a pretty huge improvement