openmw.org

Cell-relative coordinates are more reliable. Even if you don't end up running into precision issues, it can make batching easier if you just end up with a single merged mesh for each cell with only the cell's overall transformation matrix affecting it. It's probably what we're going to end up doing ...

Any support in OpenMW for MSYS/MINGW/CGYWIN/WSL is accidental and breaking it isn't a blocker for anything. It's nice to have if we can keep it, but it's not something we go out of our way to target.

I'm not 100% sure how configurable our control bindings are, but you might be able to unbind the mouse from controlling the camera. Playing with TES3MP Lua should give a reasonable idea of the kind of modding power you'll start to see in OpenMW around our 1.0 release, so I'd recommend experiementing...

Having detailed release notes somewhere is a good idea, even if they're not super tidy. If you've tried something in the past and it had a problem, Ctrl+F-ing the problem when the next release comes out and finding it's been solved can be greater motivation to actually try the new release rather tha...

An omwaddon file is basically just a renamed ESP without any compiled scripts. If you install it exactly like an ESP, OpenMW will use it just like an ESP. If you want to make it work in the original engine, though, you'll need to rename it to change the file extension to ESP and then open and resave...

It's been mentioned before, but the problem with the idea is that very little of what actually gets changed in the editor has any relation to what Blender can do already. The sculpting tools could be used for terrain (provided we could add extra constraints so they produced something that worked) an...

We don't need to add support for VSG, but if we do, we would need to add it as a second renderer.

It's much easier to work on something new than maintain legacy stuff. We need to keep compatibility with all the dumb decisions Bethesda made and loads of legacy bloat in OSG, but VSG doesn't need to copy anything.

It was going to be 'the thing' that tipped OSG from 3.x to 4.x, but that was before VSG was announced, so it may never happen. VSG is C++ 17, though, so potentially that'll make Robert passionately anti-pre-11 C++.

There are a few possible solutions, but they're complicated if we want to do them without introducing major problems.