OpenMW 0.48.0

Anything related to PR, release planning and any other non-technical idea how to move the project forward should be discussed here.
User avatar
AnyOldName3
Posts: 2252
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

ANGLE already does GLES3 to Metal translation, and native GLES support is ludicrously more feasible than having two backends (which, if one of them was Vulkan, would still require MoltenVK to translate from Vulkan to Metal). Whether or not it eventually becomes a good idea, Vulkan won't be the only answer at any point for a couple of decades at least, i.e. way too far in the future to even guarantee it'd still be Vulkan we'd be discussing supporting.
AnyOldName3, Master of Shadows
User avatar
psi29a
Posts: 5149
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: OpenMW 0.48.0

Post by psi29a »

Then perhaps shooting for native GLESv3 support should be a stretch-goal for 0.48 as it would resolve some long standing issues Android as well.
User avatar
FiftyTifty
Posts: 62
Joined: 15 Oct 2014, 21:02

Re: OpenMW 0.48.0

Post by FiftyTifty »

It's a pretty unknown engine, but NeoAxis makes use of BGFX, which has support for all manner of rendering APIs: https://github.com/bkaradzic/bgfx

It has it all, including GLES 3.1, Vulkan, and Direct3D 12. I imagine it would be a massive change from an OSG-based renderer, to the point of being a complete rewrite, unfortunately.
CPU - i7 6700k @ 4.0Ghz
GPU - Vega 56
RAM - 2x16GB DDR4 3000MHz
Mobo - Asus Z170 Pro Gaming
Soundcard - Creative Soundblaster X-Fi Titanium Fatal1ty Pro
OS - Win. 10 LTSC 2019 x64
Post Reply