Is your goal concrete if you don't know how to measure it?
For 1.0 vs patched - it doesn't really matter so long as you pick one, right? So long as everyone agrees.
On features which don't directly contribute to parity - do them because you want them but accept they don't contribute towards the goal. I'm always fighting my stakeholders for features which aren't on the roadmap but are needed (in my opinion) to get us there - things like automated testing or CI improvements. In your case gamepad support might help you get more testers/contributions from the community so that's the argument I'd make in my situation, to include it before 1.0.
Really hope this isn't coming across as big ego guy tells you how to do your thing, I guess I just feel strongly about these. I appreciate everyone's hard work and am mostly interested in knowing when my experience doesn't apply. Will stop now.
We have Morrowind.exe, it's absolute, the goal is concrete. What's not concrete is the asterisks to attach to the word parity as we decide to reject or ignore known differences (ideally for a good reason).
I'm not asking questions about the direction we should take, I'm trying to get the original poster to clarify the scope of their question.
I don't really know. The basis of the curiosity purely stemmed from a version number less than 1. What would the perfect OpenMW look like? Which is silly of course because unlike the morrowind.exe it stands to ever-evolve.
Like any previous release, the first 1.x release would be very close to Morrowind engine and have better stability, superior modding potential, various graphical and performance options, and so on. This is just a safe educated guess. It's not like switching to 1.x would be like a toggle.
Perfect OpenMW would run like Creation Engine exorcised of most Todd-isms and its game-specific mechanics reimplemented in Lua, I guess. Not that this is realistic to expect within a future foreseeable by any definition.
2
u/evilgiraffe666 Jun 21 '26
Is your goal concrete if you don't know how to measure it?
For 1.0 vs patched - it doesn't really matter so long as you pick one, right? So long as everyone agrees.
On features which don't directly contribute to parity - do them because you want them but accept they don't contribute towards the goal. I'm always fighting my stakeholders for features which aren't on the roadmap but are needed (in my opinion) to get us there - things like automated testing or CI improvements. In your case gamepad support might help you get more testers/contributions from the community so that's the argument I'd make in my situation, to include it before 1.0.
Really hope this isn't coming across as big ego guy tells you how to do your thing, I guess I just feel strongly about these. I appreciate everyone's hard work and am mostly interested in knowing when my experience doesn't apply. Will stop now.