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
GenericFurry
Posts: 5
Joined: 25 Sep 2022, 22:59

Re: OpenMW 0.48.0

Post by GenericFurry »

Installing over 0.47 works?
User avatar
AnyOldName3
Posts: 2668
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

Usually, probably, but we recommend against it. Just delete the 0.47 folder first to be on the safe side.
acatlady
Posts: 8
Joined: 28 Jun 2021, 22:18

Re: OpenMW 0.48.0

Post by acatlady »

After release, will there be a standard way to install postprocessing shaders with e.g. Flatpak?

e.g. putting them in

Code: Select all

~/.config/openmw/resources
instead of

Code: Select all

/usr/share/openmw/resources
or equivalent, which would be read-only in a flatpak?
User avatar
AnyOldName3
Posts: 2668
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

Post-processing shaders don't go in the resources directory. They go in a data directory like normal mods.
elsid
Posts: 20
Joined: 01 Aug 2017, 08:20

Re: OpenMW 0.48.0

Post by elsid »

Linux RC2 is built with wrong LuaJIT version. It doesn't match the version we provide with windows builds. This can cause problems in general. But also there is a specific problem that GC64 is not enabled by default in 2.0.5 (the version we provide with Linux RC2) but enabled in 2.1.0. With some set of mods users can't use Lua mods because 2GB is not enough for them (default GC). GC64 provides 128 TB limit.
User avatar
psi29a
Posts: 5356
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: OpenMW 0.48.0

Post by psi29a »

The fact that Lua can chew through 2GiB is alarming. This sounds like a mod problem. I'm fine with the 2GiB limit exactly for this reason.
elsid
Posts: 20
Joined: 01 Aug 2017, 08:20

Re: OpenMW 0.48.0

Post by elsid »

psi29a wrote: 30 Sep 2022, 12:47 The fact that Lua can chew through 2GiB is alarming. This sounds like a mod problem. I'm fine with the 2GiB limit exactly for this reason.
The problem might be Lua interpreter related and how OpenMW uses it.

Anyway, it doesn't matter which version we use but it has to be the same everywhere. If flatpack authors want to have it different they has to change CI in upstream first and probably Linux packages. We should not repeat OpenSceneGraph fiasco on Ubuntu where users install openmw from main repo and get crashes because we allowed unsupported version and can't change it anymore due to Ubuntu rules.
scandal
Posts: 2
Joined: 05 Oct 2022, 21:01

Re: OpenMW 0.48.0

Post by scandal »

I am trying to build/package the 0.48 branch for Android but I ran into this error. Any suggestions?

Code: Select all

src/openmw/apps/openmw/mwworld/scene.cpp:262:42: error: invalid operands to binary expression ('ESM::RefNum' and 'const ESM::RefNum')
        if (it == pagedRefs.end() || *it != refNum)
                                     ~~~ ^  ~~~~~~
User avatar
AnyOldName3
Posts: 2668
Joined: 26 Nov 2015, 03:25

Re: OpenMW 0.48.0

Post by AnyOldName3 »

That sounds like a too-old compiler, so try upgrading your NDK.
scandal
Posts: 2
Joined: 05 Oct 2022, 21:01

Re: OpenMW 0.48.0

Post by scandal »

Thanks - I have updated the compiler and got most of it to build. I'm using the OpenMW fork of OSG but that fails with REQUIRED PACKAGE NOT FOUND, specifically the PNG plugin.

It seems to recognise that LibPNG is installed and lists it under PNG_LIBRARY, but it shows OSGPlugins_osgdb_png_LIBRARY=<not found> and I didn't find any CMake errors in the osg-build/CMakeFiles directory.

I'm building on Ubuntu if that helps?
Last edited by scandal on 07 Oct 2022, 11:21, edited 1 time in total.
Post Reply