Display mode options are no longer overriden by default, fullscreen/borderless/windowed options can now be configured in the launcher/BethINI/etc.. You can still use "Fullscreen" and "Borderless" in SSEDisplayTweaks.ini if you want, just remove the comments (number signs) in front of the options.
Borderless V-Sync-off feature (EnableTearing) is now disabled by default - For whatever reason DirectX only allows V-Sync to be turned off in exclusive fullscreen, if you want to be able to turn it off in borderless/windowed mode EnableTearing must be set to true. For ENB users: ForceVSync is incompatible with this feature, if you enable it ForceVSync must also be disabled in enblocal.ini. While it's all the same driver-powered V-Sync (ForceVSync is there just for convenience), ENB currently ignores certain flags which have to be set in order to make this feature work properly - this results in the game freezing before the main menu shows (when the first frame is rendered).
PSA: Stop turning V-Sync off with G-Sync, you're just shooting yourself in the foot
Seems there's a lot of confusion about G-Sync + V-Sync, hopefully this will help clear it up.
Since its inception, G-Sync was designed to work in conjunction with V-Sync. In the beginning it was impossible to use G-Sync without V-Sync, NVIDIA later decided to give users the option to turn it off.
Here's why it should be kept enabled:
1.) VRR monitors have a fixed operating frequency range. For instance a 144hz G-Sync monitor with a range of 48-144 hz will produce tearing if framerate drops below 48 or goes above 144 FPS unless V-Sync is enabled.
2.) G-Sync does not eliminate all tearing even inside its operating range. With V-Sync off you might see tearing at the bottom of the screen in the upper FPS range and full tearing in the lower range. This is caused by frametime variances (see linked article below).
3.) There's practically no additional input lag from G-Sync + V-Sync. In fact the only time you'd get an advantage is in cases where you'd also see tearing (see 1. and 2.), which defeats the whole purpose. In G-Sync + V-Sync mode, V-Sync fills the gaps left behind by G-Sync and does so without negating its benefits.
There's a gang of tech geniuses running around reddit and various forums making all sorts of baseless claims on why V-Sync needs to be off with G-Sync. As usual, they're wrong. Blurbusters blame NVIDIA for the confusion for allowing V-Sync to be turned off in the first place. While it's true that there's no good practical reason to turn it off (if you're playing competitive first person shooters both G-Sync and V-Sync should be off anyway since G-Sync itself introduces some input lag), people spreading misinformation are just as much to blame.
Always refer to trusted sources when researching this stuff and whenever possible, run your own tests.
I've already installed the latest Address Library for 1.6.1179 and repaired Microsoft Visual C++ Redistributable 2022 X64. Is there something wrong my setup or do I need to downgrade?
Sorry for the really noob question: My game is not going over 60fps - I know this mod sets to 240 - where else do I need to change settings to get a higher frame rate? (Nvidia 4070 8gb card, so I know it can handle higher....)
mine works but only up to 120. I ran this like 2 weeks ago and it was going to 240 but reinstalled everything and now its only going to 120. So weird. You have address library installed correct?
mine was fixed after i got rid of the dlss mod, no idea why or how, but i was going through mod by mod. and it was the dlss one i deleted and boom fps back. so if you have that mod try that
I had the same problem--turns out, it was caused by using PureDark's latest Skyrim Upscaler from Patreon. Going back to Version 12 allowed me to get FPS above 60 again.
Go into Nvidia Control Panel > Manage 3D settings > Program Settings > (Select 'ESV: Skyrim Special Edition') > Scroll down to Max Frame Rate > turn off. I hope that helped, if you have an AMD card then I cant help you friend. I was just having the same issue until I did what's listed above.,
I was under the impression that fps and refresh rate are different things. That even if the refresh was below the computer would still render at the be rendering them.
How do I configure the INI so that the FPS limit is 144? I removed VSync but I can't get the limit to be 144. I've already changed it to the following values but without success: EnableVSync=false EnableTearing=true MaximumRefreshRate=144 FramerateLimit=144
I also changed it in enblocal.ini: [ENGINE] ForceVSync=false VSyncSkipNumFrames=0
While using BethINI to address what OP was asking is not relevant, ignore the bad advice, they have no idea what they are talking about. BethINI works fine.
Question for the mod author and the community as a whole:
How would I configure the mod to enable the bugfixes only? I.e: only enable the options in the Bugfixes section in the description page? I ask because I'd rather use DXVK to limit my framerate and enable my vsync, for they have the most consistent frametimes over other options. Do I just comment out everything except the bugfixes?
Give Feedback
2938 comments
Seems there's a lot of confusion about G-Sync + V-Sync, hopefully this will help clear it up.
Since its inception, G-Sync was designed to work in conjunction with V-Sync. In the beginning it was impossible to use G-Sync without V-Sync, NVIDIA later decided to give users the option to turn it off.
Here's why it should be kept enabled:
1.) VRR monitors have a fixed operating frequency range. For instance a 144hz G-Sync monitor with a range of 48-144 hz will produce tearing if framerate drops below 48 or goes above 144 FPS unless V-Sync is enabled.
2.) G-Sync does not eliminate all tearing even inside its operating range. With V-Sync off you might see tearing at the bottom of the screen in the upper FPS range and full tearing in the lower range. This is caused by frametime variances (see linked article below).
3.) There's practically no additional input lag from G-Sync + V-Sync. In fact the only time you'd get an advantage is in cases where you'd also see tearing (see 1. and 2.), which defeats the whole purpose. In G-Sync + V-Sync mode, V-Sync fills the gaps left behind by G-Sync and does so without negating its benefits.
Read this FAQ (second answer) for a detailed explanation: https://blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/15
There's a gang of tech geniuses running around reddit and various forums making all sorts of baseless claims on why V-Sync needs to be off with G-Sync. As usual, they're wrong. Blurbusters blame NVIDIA for the confusion for allowing V-Sync to be turned off in the first place. While it's true that there's no good practical reason to turn it off (if you're playing competitive first person shooters both G-Sync and V-Sync should be off anyway since G-Sync itself introduces some input lag), people spreading misinformation are just as much to blame.
Always refer to trusted sources when researching this stuff and whenever possible, run your own tests.
Please check skse64.log and SSEDisplayTweaks.log for errors or warnings before posting issues here.
I checked the log and saw this:
<ERROR> [Window] GetClientRect hook failed, upscaling disabled
I've already installed the latest Address Library for 1.6.1179 and repaired Microsoft Visual C++ Redistributable 2022 X64.
Is there something wrong my setup or do I need to downgrade?
An I9, 32g, rtx4070 laptop would be considered a high end device?
I am assuming there is a setting somewhere I need to adjust, but I have no idea what it would be.
But thank you for the suggestion! I hope it helps others with this issue.
EnableVSync=false
Just started trying Community Shaders, no enb.
Thank you for the help!
Thank you!
EnableVSync=false
EnableTearing=true
MaximumRefreshRate=144
FramerateLimit=144
I also changed it in enblocal.ini:
[ENGINE]
ForceVSync=false
VSyncSkipNumFrames=0
[LIMIT]
EnableFPSLimit=false
FPSLimit=144.0
Hopefully that's what you're looking for. 👌
How would I configure the mod to enable the bugfixes only? I.e: only enable the options in the Bugfixes section in the description page? I ask because I'd rather use DXVK to limit my framerate and enable my vsync, for they have the most consistent frametimes over other options. Do I just comment out everything except the bugfixes?
main takeaway is that most mods will work. ENB is a little tricky though.