It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like:Chrome,Firefox,Internet Explorer orOpera

×
arrow-down2arrowcart2close4fat-arrow-leftfat-arrow-rightfeedbackfriends2happy-facelogo-gognotificationnotifications-emptyownedremove-menusad-facesearch2wishlist-menuwishlisted2own_thingsheartstartick
Hi all,

I picked this game up at the start of the sale and I've been having a great time with it. I'm using the 64bit version of OpenJK and I've run into a bug. Whenever I fail a mission in any way and reload any saved game. including checkpoints, (all?) triggers for the level cease to function, breaking the game. This may be worked around by quitting and launching the game again and then loading a save, but it's obviously not ideal.

To quickly test, start a new game and kill Rosh with your saber. if you reload and no one says or does anything and you can't cut down the tree, it affects you too.

Is anyone else using an OpenJK Linux version who either doesn't have this problem or who has managed to fix it? This seems to be a bug that comes and goes, as may be seen here:

https://jkhub.org/topic/7316-certain-events-not-loading-after-death-sp-openjk/

https://github.com/JACoders/OpenJK/issues/889

The second link is a closed bug where it seems to be fixed for others, but then someone commented that it's affecting them again.

I've tried using different releases from the last few months, including one made the day after it was said to be fixed in the Github bug report in January, as well as compiling it myself, but nothing seems to do the trick.

Any ideas? The game is still fun but having to relaunch the game because the mission-critical droid walks into your lightsaber is annoying.
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
pbnjoe: I've tried using different releases from the last few months, including one made the day after it was said to be fixed in the Github bug report in January, as well as compiling it myself, but nothing seems to do the trick.
I'm using Debian build from experimental, and I didn't notice this issue.
avatar
pbnjoe: I've tried using different releases from the last few months, including one made the day after it was said to be fixed in the Github bug report in January, as well as compiling it myself, but nothing seems to do the trick.
avatar
shmerl: I'm using Debian build from experimental, and I didn't notice this issue.
Hmm, alright, thanks, good to know. I'm using builds downloaded straight from the OpenJK site (builds.openjk.org) on Manjaro. I'll try the openjk-git AUR package and see if that helps.

EDIT: It actually works! I don't know what was different between me compiling it on my own and using the openjk-git PKGBUILD, but it must have been something I suppose. The only thing that I see is different is the file structure, which might be the issue.

May I ask, shmerl, do you have binaries away from the game folder, say somewhere in /opt/, and the .pk3 files in ~/.local/share/openjk/base/, or do you have the binaries in something like ~/Games/Jedi Academy/GameData/ and the .pk3 files in the base folder found there?

The latter is what I had before, which you get from following the instructions on the OpenJK site. Interesting.

In any case, seems like there's no more restarting for me!
Post edited May 06, 2017 by pbnjoe
avatar
pbnjoe: It actually works! I don't know what was different between me compiling it on my own and using the openjk-git PKGBUILD, but it must have been something I suppose. The only thing that I see is different is the file structure, which might be the issue.
One difference that I discovered is usage of different versions of libjpeg. See this bug for some context. I suppose it's possible that Manjaro build is using same libjpeg as Debian one. You can check it this way:

ldd rdsp-vanilla_x86_64.so

Debian build gives me:

libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x00007f4e61bb3000)

And OpenJK "official build" gives me:

libjpeg.so.8 => not found

I'm not sure if it's really related to the bug you experienced, but it's one difference. Anyway, it's always better to something built for your distro.
avatar
pbnjoe: May I ask, shmerl, do you have binaries away from the game folder, say somewhere in /opt/, and the .pk3 files in ~/.local/share/openjk/base/, or do you have the binaries in something like ~/Games/Jedi Academy/GameData/ and the .pk3 files in the base folder found there?

The latter is what I had before, which you get from following the instructions on the OpenJK site. Interesting.

In any case, seems like there's no more restarting for me!
I have binaries in /opt/games/jedi_academy and pk3 files in /opt/games/jedi_academy/base
Post edited May 07, 2017 by shmerl
avatar
shmerl: One difference that I discovered is usage of different versions of libjpeg. See this bug for some context. I suppose it's possible that Manjaro build is using same libjpeg as Debian one. You can check it this way:

ldd rdsp-vanilla_x86_64.so

[snip]

I'm not sure if it's really related to the bug you experienced, but it's one difference. Anyway, it's always better to something built for your distro.
With the AUR build I get

libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007faf434f6000)

So it could be the difference! And yes, I agree, normally that's what I do. Not sure why I went to the site first this time.
avatar
shmerl: I have binaries in /opt/games/jedi_academy and pk3 files in /opt/games/jedi_academy/base
Alright, so the files are in the same place relative to each other as the way the instructions tell you to have it. I suppose it doesn't matter then, as this AUR build has them different to that. It may well have been a library issue. Thanks for looking into it.