Windows 10 or newer is required to run the Windows build.
If you're running an AMD GPU and get frequent freezes (driver timeouts), disable antialiasing in the launcher. AMD is aware of the issue and is working on fixing it.
If you're running an Intel GPU and the game's visuals often appear to freeze, try to check if it still happens with the latest available driver for your GPU and downgrade the driver if it does. This also appears to be a driver-side regression.
Finally, we received many reports on Nvidia Windows driver crashes with unclear reason or connection. This is also suspected to be a vendor-side regression associated with post-50 series drivers, but we do not currently have a recommendation on how to deal with those other than to provide us with more crash dumps and openmw.log files.
Changes since RC7:
- [#8165] OpenMW-Lua: For Lua-triggered object activation, Lua activation handler takes priority over mwscript activation inhibition
- [#8445] Launcher: Fixed a rare crash on exit due to start cell list reloading being interrupted
- [#8465] macOS: Hardware antialiasing no longer breaks rendering
- [#8469] OpenMW-Lua: Cell change events are no longer triggered when the player is teleported within a cell
- [#8478] Launcher: Various startup, content list loading and mass plugin toggling optimisations
- [#8503] OpenMW-Lua: To prevent rendering deadlocks, camera, time scale and animation speed bindings no longer accept infinities and NaN as input
- [#8514] AMD: Fixed broken shadows when they are enabled globally but need to be disabled (e.g. in interiors) on some hardware
- [#8516] OpenMW-Lua: Fixed the order of UI layer insertions if they happened during the same frame
- [#8532] Console search works properly and can no longer crash if the current marked occurrence includes the first character of the history
- [#8541] OpenMW-Lua:
util.color:asHexproperly converts color channel values lower than 16 - OpenMW-Lua: Animation API is no longer accessible in menu and global contexts
- OpenMW-Lua:
self:isActivebinding properly returns false is the object is inactive - Fixed undefined behaviour in the linear bloom shader that reportedly led to problems on Android
- Post-processing shaders can properly request a higher minimum GLSL version on systems that don't support UBO rendering, like macOS
- Weapon/shield attachment/detachment can once again happen at the very beginning of the (un)equipment animation