Jump to content

is there a -hidden- fps Limiter?


Recommended Posts

Posted

Title.

 

should NOT be stuck at 29.9 - should be stuck at 59.9 (vsync stucking 59-60)

 

from initial start (title menu) on it's at 29.9 in enb-widget

 

FO4 for example runs at its intended stucked 59.9 and that game is newer, and "visually heavier"

 

Using Win 10 though, and we all know how in LOVE that is with dx9

 

edit: im in windowmode btw, (forcewindowborderless=true) to counteract gamefreezes (fullscreen freezes easily "hide" taskmanager on ctrl alt del)

Posted

Yes there is a limiter in the ENB optiions it probably set too that you can easily change in game or through your enblocal.ini.

Posted

I remember that enabling Vsync will effectively halve your framerates for Skyrim.  I can't remember which Vsync option though... there are 3 places.  Yes, three!  Why?  I dunno, just be glad there aren't four. 

 

Location 1:  iPresentInterval=1 or 0 in SkyrimPrefs.ini from Documents\My Games\Skyrim

Location 2:  Nvidia Control Panel under Program Settings tab select Elder Scrolls V: Skyrim and toggle Vertical Sync On or Off.

Location 3:  EnableVSync=true or false in enblocal.ini from game installation directory (Which you guys already talked about.)

 

I have all of mine turned off and have no screen tearing with greatly improved performance.  Funny thing is when I enabled Vertical Sync with Nvidia Control Panel there was a lot of screen tearing.

 

Posted

Oh?

 

Hmmm, Ima do this now then 

EnableVSync=false

and instead

EnableFPSLimit=true

FPSLimit=60.0
and see how it goes!
Posted

 

Oh?

 

Hmmm, Ima do this now then 

EnableVSync=false

and instead

EnableFPSLimit=true

FPSLimit=60.0
and see how it goes!

 

Honestly, you should just turn all Vsync options for Skyrim off, in my opinion.

Posted

It did work.

 

So apparently I had 2x vsync (enb and skyrim's ini file) and that halfd to 30 after downing to 60, so I'm only using 1x (iPresentInterval=1 in skyrimprefs) now

Posted

It did work.

 

So apparently I had 2x vsync (enb and skyrim's ini file) and that halfd to 30 after downing to 60, so I'm only using 1x (iPresentInterval=1 in skyrimprefs) now

Ha!  I knew it.  Please mark this as solved for anyone else who might have the same problem.

Posted

 

It did work.

 

So apparently I had 2x vsync (enb and skyrim's ini file) and that halfd to 30 after downing to 60, so I'm only using 1x (iPresentInterval=1 in skyrimprefs) now

Ha!  I knew it.  Please mark this as solved for anyone else who might have the same problem.

 

At least for me that's not true.

I have both vsync settings  activated (skyrimprefs.ini -> iPresentInterval=1 and enblocal.ini -> EnableVSync=true) and no framerate drops because of it. And the NVidia driver is set to application controlled.

 

But I also had framerate issues recently, solved them by switching from borderless fullscreen via ENB (also in the enblocal.ini) to the one provided by Onetweak. I just switched back and it seems the issue fixed itself somehow. Really don't know what caused that (framerate got cut in half or worse) but from what I've read in my online search about the issue it had something to do with the Windows driver that handles applications running in a window instead of fullscreen.

Posted

 

 

It did work.

 

So apparently I had 2x vsync (enb and skyrim's ini file) and that halfd to 30 after downing to 60, so I'm only using 1x (iPresentInterval=1 in skyrimprefs) now

Ha!  I knew it.  Please mark this as solved for anyone else who might have the same problem.

 

At least for me that's not true.

I have both vsync settings  activated (skyrimprefs.ini -> iPresentInterval=1 and enblocal.ini -> EnableVSync=true) and no framerate drops because of it. And the NVidia driver is set to application controlled.

 

But I also had framerate issues recently, solved them by switching from borderless fullscreen via ENB (also in the enblocal.ini) to the one provided by Onetweak. I just switched back and it seems the issue fixed itself somehow. Really don't know what caused that (framerate got cut in half or worse) but from what I've read in my online search about the issue it had something to do with the Windows driver that handles applications running in a window instead of fullscreen.

 

Cool story, bro.  

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...