Currently only the Windows build is available due to limitations in GOG's platform support, but that should hopefully improve in the not-too-distant future.

Well-lit, traveller! This is a rare development blog post sighting. We haven't had one of those in a while... While version 0.52.0 of our open-source engine is still baking in the oven and will take some time to finish, we'd like to talk about some of the exciting changes coming with it.

Lighting

One of the annoying limitations of Morrowind's original rendering engine is the light limit: every object can only be lit by up to 8 light sources. What happens if there are more? Any extra lights are simply ignored for that object. This can lead to flickering or harsh lighting seams in particularly well-lit areas. Level designers traditionally had to work around this limit, carefully designing areas so players wouldn't notice, but even the most meticulous layout can't account for every scenario in a game as dynamic as Morrowind and its myriad of mods, and for our optimisations, like active grid object paging, merging objects on the fly.

OpenMW has included a setting to raise the light limit to an arbitrary value for a while now. But there has always been a catch: a performance hit. What if we told you that doesn't have to be the case?

The next release introduces an implementation of volume-tiled forward shading, nicknamed "Project Magnus" and referred to in-game as clustered lighting. Supported by any hardware that can run OpenGL 4.3 or higher, it completely removes the per-object light limit by dividing the screen into small tiles and assigning lights to them. The best part is that it has a dramatically lower performance impact than raising the limit to Aetherius. In fact, the performance can in some cases be better than with the regular light limit, like in the below scene.

Light limit: 8

Clustered

This lays the groundwork for an eventual implementation of **bindless rendering **(not binding rendering states like materials, textures, and lights to individual objects at all), which will offer major performance gains, even surpassing full texture atlasing.

Also, don't tell anyone, but a secret, rad feature of clustered lighting is that it makes water reflect point lighting!

Light limit: 8

Clustered

Hardware: Nvidia GeForce GTX 1050 and Intel Pentium G4560

Mod: Balmora Underworld. Impact on more standard scenes may not necessarily be as dramatic.

Billboards

We have another important graphical update: up until now, our implementation of billboards (sprite-like geometry) has effectively been a stub, offering only partial functionality compared to the original engine.

In Morrowind, billboards are used for Reflect and Spell Absorption visual effects, which look noticeably incorrect in OpenMW 0.51.0.

https://youtu.be/9x_-JazAIPM

The upcoming release properly reimplements the three original billboard modes. Two of them allow billboards to rotate fully toward the camera, while the third keeps them aligned with the vertical axis (a mode frequently used in modded assets). What's significant is that they now support rotations applied by animations, allowing the visual effects to look as designed.

https://youtu.be/DH4H1J16MCI

...Well, mostly. Full disclosure: multiple instances of these effects currently overlap. We'll fix that some day, pinky promise!

Spellcasting

"What if I don't care about billboards? Give me gameplay! Give me Lua!"

While the previous release gave modders the ability to create custom spell effects, the ongoing effort to dehardcode spellcasting will revolutionise magic modding. The goal is to move effect application, projectile movement, and casting-related animations into built-in Lua scripts.

Once complete, modders will be able to override these mechanics to implement things like swift casting, dual casting, homing projectiles, custom projectile trajectories, and much more.

So far, most of the temporary magic effect application has been dehardcoded, and we are currently polishing magic projectile hit application before moving on to the rest of the subsystem. While not every single part might make it into 0.52.0, rest assured that the upcoming release will still be a massive leap forward.

Combat

You might be wondering: "Wait, what about 1.0 and Morrowind parity? Are you working on anything that isn't billboards (which I still don't care about)?" Absolutely!

Spellcasting is often used in combat, and 0.52.0 will contain AI accuracy fixes for melee encounters. NPCs and creatures will feel slightly more responsive: they'll follow you closer when you backpedal and face you and attack you quicker.

https://youtu.be/zZ8J5kyvmys

Custom records

Back to Lua! The load context system introduced in 0.51.0 is being expanded further. In the latest development builds, modders can inject custom classes, factions, levelled lists, lockpicks, races, and repair items as game records directly through Lua, with support for additional object types on the way. Beyond that, work is in progress to allow custom skills and attributes to be injected.

That wraps it up for now. This is non-exhaustive! You can test these features (and many more) right now in our latest development builds. Expect more to read or watch about 0.52.0 as we get closer to its release. Until next time!

It’s been nearly half a year since 0.50.0 landed back in early November, but we’ve almost reached Area 51, and we’re ready to share the first release candidate (RC) builds of the next release of our open-source engine! Grab one from our GitHub releases page.

0.51.0 introduces a new script context to our Lua scripting API, the Load context. Fabulous secret powers bestowed on Load scripts allow them to inject and modify game data right after it is loaded. Most notably, this includes spell effects—which allows mods to add spells that don’t rely on the built-in effects.

0.51.0 also fixes game-breaking dialogue issues in Russian and Polish Morrowind, introduces BC7 texture compression support for DDS files, adds terrain vertex painting to our editor, and more.

As usual, our intention for the RC period is to have you try to break it — run into any uncaught crashes, freezes, regressions, or other unexpected issues, and report them to us on our issue tracker. If you don’t run into any issues, tell us too!

The RC1 prerelease description includes a preliminary list of changes. Do give it a read.

A few things to keep in mind before you jump in:

• The saved game format has changed since 0.50.0. Your existing 0.50.0 saves will load in 0.51.0, but once you save in 0.51.0, you cannot go back to 0.50.0 and load that newer save there. Consider keeping a “pre-RC” save around.
• The scripting API hasn’t had meaningful breaking changes, but asterisks apply: mods with a UI that were written in a suboptimal way may be an annoyance for the new widget validation. Double-check that all of those are up-to-date.
• Shader mods, including some post-processing shaders and those that replace the built-in forward pass shaders, must be updated due to certain texture handling changes.
• Please read the known issues section in the RC notes. Some issues you don’t, in fact, have to report, assuming you’re 100% sure it’s an issue listed there.

You install it like you would install a stable release: run the installer or unpack the archive into a new directory. If you were using a portable install, remember to set that up again for the new build; your configuration and saves are otherwise stored in their normal location.

If you’re not curious or brave, the current stable release 0.50.0 is, of course, still available from our Downloads page.

To join in on the forum discussion, head over to the release topic.

We’ll see you later—hopefully, on release day!