Releases: Erimelowo/OpenVR-Dynamic-Resolution
v1.1.0
v1.0.0
Changelog since v0.4.1:
- Add a GUI through Dear ImGui
- Add a way to change settings at runtime
- Add a button to pause resolution adjustment
- Add a tray icon
- Improve default settings
- Use OpenVR's framebuffer
- Use a simpler and better way to calculate FPS
- Cleanup on exit (it didn't before...)
- Lots of bugfixes
- Rebrand to OVR because "OpenVR" is owned by Valve
v1.0.0-rc.1
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.4.1:
- Rewrite a LOT of code
- Add a GUI
- Add a way to change settings at runtime
- Use OpenVR's framebuffer, which should make the resolution adjustment a whole lot more stable and smooth
- Use another simpler/better way to calculate FPS
- Cleanup on exit (it didn't before lol)
- Lots of fixes
- Partially rebrand to OVR because "OpenVR" is owned by Valve
v1.0.0-rc.2
Second release candidate with minor fixes and changes
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.4.1:
- Rewrite a LOT of code
- Add a GUI
- Add a way to change settings at runtime
- Use OpenVR's framebuffer, which should make the resolution adjustment a whole lot more stable and smooth
- Use another simpler/better way to calculate FPS
- Cleanup on exit (it didn't before lol)
- Lots of fixes
- Partially rebrand to OVR because "OpenVR" is owned by Valve
v0.4.1
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.4.0:
- Add config option for disabling specific applications by @williammck
This adds a new setting,disabledApps
, that allows for people to exclude specific applications from resolution adjustment.
The setting expects a space-delimited list of OpenVR application keys, e.g.steam.app.438100
for VRChat,steam.app.620980
for Beat Saber, etc.
v0.4.0
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.3.2:
-
Added CPU Frametime support!
It is enabled by default (you can set ignoreCpuTime to 1 to disable it).
This will double your Adjusted target frametime when your CPU frametime is 2x the HMD Hz target frametime.
You can make it so the Adjusted target frametime is doubled whenever the CPU frametime goes over the HMD Hz target frametime by whatever amount by setting preferReprojection to 1. -
Added a VRAM-only mode.
Enable it by setting vramOnlyMode to 1 in the settings.
This will completely ignore your GPU and CPU frametimes and aim to keep the resolution around the initialRes while keeping VRAM usage in check. -
minGpuTimeThreshold is now minCpuTimeThreshold.
The CPU is now used to figure out if the user is in the SteamVR void/VRChat loading screen.
This will work even if ignoreCpuTime is 0. -
More information on the UI, yay!
CPU time (raw and adjusted for reprojection) are shown as well as the adjusted target frametime and VRAM target.
v0.3.2
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.3.1:
- Fix missing nvml.dll for AMD GPU users.
v0.3.1
v0.3.0
Do not use, this has a big memory leak when using GPU monitoring. Fixed in https://github.com/Louka3000/OpenVR-Dynamic-Resolution/releases/tag/v0.3.1
Dynamically adjusts the HMD resolution to the GPU frametime.
Changelog since v0.2.2:
- Implemented vram limit. Thanks @kruemmelbande! (#23)
v0.3.0-rc.1
Dynamically adjusts the HMD resolution to the GPU frametime.
This is a release candidate. Please report any bug to me on discord (erimel) or by email (loukalemire@gmail.com)
Changelog since v0.2.2:
- Implemented vram limit. Thanks @kruemmelbande! (#23)