OpenMW 0.18.0

[scrawl]

The 0.18 binary linux release seems to be built against an older version of ogre, which causes this problem (I was able to reproduce it with the binary). I tested the 64 bit one but I assume the 32 bit has the same issue. The binaries are built against 1.8.0unstable while they should be built against 1.8.0 or 1.8.1. I'm a bit surprised this hasn't been noticed earlier. Looks like we haven't had enough testing.

[psi29a]

The 0.18 binary linux release seems to be built against an older version of ogre, which causes this problem (I was able to reproduce it with the binary). I tested the 64 bit one but I assume the 32 bit has the same issue. The binaries are built against 1.8.0unstable while they should be built against 1.8.0 or 1.8.1. I'm a bit surprised this hasn't been noticed earlier. Looks like we haven't had enough testing.

I don't believe it was tested, at least not by me. We will have to wait for k1ll's response since he rolled it.

We are sticking to 1.8.0 unless there is some DIRE reason as to why we need to upgrade. Moving targets are not fun.

[cdoublejj]

well basing something on a unstable releases usually doesn't sound like too good of an idea. i don't think any one wants this kind of stuff plaguing the game.

[psi29a]

well basing something on a unstable releases usually doesn't sound like too good of an idea. i don't think any one wants this kind of stuff plaguing the game.

I agree, but we've done it before by chasing 1.8 when it was still in beta with openmw >= 0.14 until 0.17 when ogre finally made it to real 1.8.0 release. The reason for that was because the terrain rendering would no work on < libogre 1.8 .

We know where the problem is, just waiting for k1ll to address it. Perhaps someone would be so kind as to remove the tgz until it is fixed, please?

edit: I do enjoy the fact that you still play UT.

[lgromanowski]

We know where the problem is, just waiting for k1ll to address it. Perhaps someone would be so kind as to remove the tgz until it is fixed, please?

Done.

[cdoublejj]

Seeing as it is an unstable version could other potential bugs pop up?

[K1ll]

Here are the new 0.18.0 targz packages. I've built them with ogre 1.8.1.

ftp://redfortune.de/openmw-0.18.0-Linux.tar.gz

ftp://redfortune.de/openmw-0.18.0-Linux-64Bit.tar.gz

I couldn't reproduce the problem with the old packages so someone else has to confirm that it's gone.

[psi29a]

k1ll, I do not think it has anything to do with 1.8.1, but rather a rc (or unstable?) version of 1.8.0 that was used. The Ubuntu debs apparently do not have this problem, only the tar balls. Some bad packages in your xen?

[sirherrbatka]

I will just lock this topic.