Page 14 of 28

Re: OpenMW 0.44.0

Posted: 13 Jun 2018, 22:40
by Lagahan
NullCascade wrote:
08 Jun 2018, 21:59
This isn't really a regression for me, but my rendering freezes have gotten worse in the 0.44 RC above. I can trigger it every time when loading a save in 0.44, but only about 50% of the time in 0.43.

More information here: https://bugs.openmw.org/issues/4445
Can't reproduce this personally, though I never had crashes with OpenMW 0.43 or earlier either. Is there any mods in particular that I could install to see if I can induce it?

Is there anything else anyone would like tested on Windows?

Re: OpenMW 0.44.0

Posted: 14 Jun 2018, 04:53
by lysol
Windows x64 builds work as they should. Sorry, was too busy yesterday it seems.

Re: OpenMW 0.44.0

Posted: 14 Jun 2018, 16:16
by Starsheep
No issues from my side running the 0.44 RC1 x64 on Win10
Haven't encountered the rendering freeze issue at all

Re: OpenMW 0.44.0

Posted: 14 Jun 2018, 19:55
by jirka642
K1ll wrote:
11 Jun 2018, 21:53
RC1s have been rebuild:
(same links as before)
32 Bit
64 Bit
I am getting this on Linux Mint 18.3:
./openmw.x86_64: error while loading shared libraries: libx264.so.152: cannot open shared object file: No such file or directory
Works after I created symbolic link to my version of library.
ln -s /usr/lib/x86_64-linux-gnu/libx264.so.148 libx264.so.152
EDIT:
Also got this in logs:
Warning: dynamic library '/home/jirka642/bin/openmw-0.44.0-Linux-64BitRC1/lib/osgPlugins-3.4.1/osgdb_jpeg.so' exists, but an error occurred while trying to open it:
libjpeg.so.62: cannot open shared object file: No such file or directory
Error: Can't open savegame screenshot, no jpg readerwriter found

Re: OpenMW 0.44.0

Posted: 14 Jun 2018, 20:15
by akortunov
jirka642 wrote:
14 Jun 2018, 19:55
Works after I created symbolic link to my version of library.
A common error on Linux. Compiler links executables with installed version of libraries.
That's why you often need to download package for your distro or build software from source.

Re: OpenMW 0.44.0

Posted: 15 Jun 2018, 03:52
by Ravenwing
Sounds like we've already got a few testers for Windows 10 but I've played through a few hours in 0.44 RC and haven't had any problems. But praise be to whoever fixed the graphical artifacts with shaders on, that is a much appreciated improvement!

Re: OpenMW 0.44.0

Posted: 15 Jun 2018, 08:36
by psi29a
@NullCascade: is your freezing problem still there in 0.44?

Re: OpenMW 0.44.0

Posted: 15 Jun 2018, 08:43
by NullCascade
psi29a wrote:
15 Jun 2018, 08:36
@NullCascade: is your freezing problem still there in 0.44?
Yes, though I conveniently can't reproduce it when I build the project myself, which makes it super awesome to try to debug.

Re: OpenMW 0.44.0

Posted: 15 Jun 2018, 08:45
by psi29a
NullCascade wrote:
15 Jun 2018, 08:43
psi29a wrote:
15 Jun 2018, 08:36
@NullCascade: is your freezing problem still there in 0.44?
Yes, though I conveniently can't reproduce it when I build the project myself, which makes it super awesome to try to debug.
Fuck... I hate heisenbugs.

Might there be a difference between debug, release and relwithdebinfo builds?

Things to also check, is it compiler specific? MSVC15 vs MSVC17 for example?

Re: OpenMW 0.44.0

Posted: 15 Jun 2018, 08:48
by NullCascade
psi29a wrote:
15 Jun 2018, 08:45
NullCascade wrote:
15 Jun 2018, 08:43
psi29a wrote:
15 Jun 2018, 08:36
@NullCascade: is your freezing problem still there in 0.44?
Yes, though I conveniently can't reproduce it when I build the project myself, which makes it super awesome to try to debug.
Fuck... I hate heisenbugs.

Might there be a difference between debug, release and relwithdebinfo builds?

Things to also check, is it compiler specific? MSVC15 vs MSVC17 for example?
I've tried debug and release (though not RelWithDebInfo) locally without being able to reproduce it when building myself in the latest clean clone. My environment is using the latest version of MSVC2017.