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.
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?
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
Last edited by jirka642 on 15 Jun 2018, 01:32, edited 1 time in total.
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.
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!
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.