Jump to content

Recommended Posts

Posted
32 minutes ago, TechAngel85 said:

I set all my menus to 60, as well, and noticed some smoother effects on the loading screens when I did so (used to flicker a bit). Granted, think I have vsync off due to dev and testing.

Same XP for me

  • Replies 41
  • Created
  • Last Reply

Top Posters In This Topic

  • 3 weeks later...
Posted

Mod updated on Nexus.

  • Version 0.4.16

    • Fixed an issue where the OSD would not initialize if the d3d device creation call returned a non-fatal status code.
    • Inform the user with a message box popup if device initialization fails.
Posted

Mod updated on Nexus. With beta support for AE 1.6.318 !

  • Version 0.5.0b

    • Anniversary Edition support (beta)
    • Added VerticalLookSensitivityFix and SlowTimeCameraMovementFix (EngineFixes)
Posted
4 hours ago, Mercury71 said:

Mod updated on Nexus. With beta support for AE 1.6.318 !

  • Version 0.5.0b

    • Anniversary Edition support (beta)
    • Added VerticalLookSensitivityFix and SlowTimeCameraMovementFix (EngineFixes)

Nice

Posted

Mod updated on Nexus.

  • Version 0.5.1b

    • Version independance - updated to use AE address library
    • Changed MaxFrameLatency setting to 0 (bethesda default value is used). This was done because the default was changed from 2 (SE) to 1 (AE). AE users who maintain their own plugin configuration should make sure that MaxFrameLatency is set to either 0 or 1.
Posted

Mod updated on Nexus. Will it never end!

  • Version 0.5.2b

    • Fixed DialogueLookSmoothEdge (off by default) taking effect outside of the dialogue menu. This caused slowed mouse movement if the player exited a menu and the cursor was near the edge of the screen.
Posted

Updated again on Nexus

  • Version 0.4.5b
    • Previous version had all controls fixes turned off by default in the .ini (optional conf. file not affected)
    • Fixed an error reporting message box having swapped caption and text.
  • Version 0.5.5b
    • AE: fixed crash caused by SetExpressionOverride patch
  • 2 weeks later...
  • 2 weeks later...
Posted

Now im going to post this here, even though it relates to v2.0.0, but for some reason Shift+Ins is not bringing up OSD - yes ive double check the INI and been over the TL:DR for setting up the testing custom ini etc....hence why im now asking what it could be, as ive been at this for some days now, and it worked previously.

Disregard; INI overwrite issue that i only just came across.

Buuuuut, COC Tamriel 40 -24 does not function either....and substituting COC for COW will briefly transport one too Riften Docks on the ship but then warp back to the cell in ASLAL...

Posted
34 minutes ago, NuroDragonfly said:

Now im going to post this here, even though it relates to v2.0.0, but for some reason Shift+Ins is not bringing up OSD - yes ive double check the INI and been over the TL:DR for setting up the testing custom ini etc....hence why im now asking what it could be, as ive been at this for some days now, and it worked previously.

Are you sure the OSD is enabled in your SSEDisplayTweaks.ini? It's off by default.

[OSD]

## Enable the on-screen display.
#
Enable=false

And the default keyboard shortcut uses the left Shift key, in case you have 2 and may be using the right side one.

38 minutes ago, NuroDragonfly said:

Also, COC Tamriel 40 -24 does not function either....and substituting COC for COW will briefly transport one too Riften Docks on the ship but then warp back to the cell in ASLAL...

Right. It's a typo, should be cow. You need to sleep in the ASLAL bed and wait until you are teleported to your spawn point, then you can cow to Riften docks.

Another good spot for testing FPS is the Riverwood bridge - overlooking the river towards Lake Ilinalta.

Posted

It was my custom INI that overwrote the main one (as i added a few more options for ease of finding the options to turn on/off - the reading of those pages is hell for my eyes in the font and contrast RE my dyslexia)

And copy, didnt notice the wording meant sleep then teleport...

Posted
1 hour ago, NuroDragonfly said:

And copy, didnt notice the wording meant sleep then teleport...

Yes it's confusing. I don't think you need to wait 3 hours before or after landing at your spawn point. Simply going through the ASLAL quest normally, choosing to spawn in an interior, and landing there may be good enough.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.