Cannot interact with things after loading

[t-animal]

I run a Arch 64bit and built the game as of commit d3f5b3b .

When I load the game after dying, I cannot interact with things as TheCherry pointed out in issue #780 . This is fixed by restarting the game.

However even after restarting I still cannot interact with some switches and stuff that needs force power (e.g. the wall which has to be destroyed during the force power training in the beginning). This is NOT fixed by restarting the game but by restarting the mission. Thus some levels effectively become permadeath levels - you cannot finish them after you've died once.

[ensiform]

When was the last commit it worked. This commit just disables an unused variable on JK2 MODE which doesn't change any functionality.

[t-animal]

I don't know. I'm playing it for the first time. I could try and find out after I've finished it.

[t-animal]

During the mission where you have to race on the hoverbikes I noticed that the final cutscene was not triggered after loading, too. Therefore the level could not be finished. I guess that issue is related.

[ensiform]

Well the game runs good for me on mint 18 64 so that's strange.

[gabor-udvari]

I experience the same issue on Ubuntu 16.04 (64 bit) with the pre-built binaries. Happens with openjk-2016-11-21-39baf07d and openjk-2016-10-31-d3f5b3bd. I hit these issues so far:

• if you die on yavin1b, after reloading Rosh will not open the first gate
• if you die on t1_surprise, after reloading you cannot force pull down the escalator at the sandcrawler
• if you die on t1_rail, after reloading you cannot switch off the electricity between the two trams.

Closing the game and restarting fixes these.

[Razish]

Confirmed on xubuntu 16.10 x86_64:

1. Start new game (I picked Jedi Master)
2. Die to the howlers before triggering the cutscene
3. "Load Checkpoint"
4. The howlers do nothing, can't trigger the cutscene/checkpoint

[xycaleth]

Seems like a regression of #257 which I had fixed in e8fc63788. I recall bace05c9b potentially undid my fix but I couldn't remember what the visibility compile flag was for at the time.

[Razish]

Perhaps we need a comment around the compiler switch so people know not to remove it :P

[gabor-udvari]

I did some further testing and it seems that yavin1b is a special case. With the precompiled binary I can reproduce the bug on different maps. When I compile the binary from source the bug goes away on these maps (after dying and reloading checkpoint):

• t1_surprise: cannot force pull down the escalator at the sandcrawler
• t1_rail: cannot force pull down the escalator at the sandcrawler
• t3_rift: cannot force push the very first rock at the beginning

But the yavin1b issue still exists, even if all the above work. Putting the -fvisibility=hidden back to the CMakeLists.txt does not have any effect. The issue on yavin1b still exists while all the others are not. I compiled on Ubuntu 16.04, gcc version is 5.4.0 20160609.

[t-animal]

That is weird because I install from AUR and therefore always compile from source and I experienced all the described bugs. I've finished the game now and will take a closer look.

Am 27. Dezember 2016 23:35:09 schrieb Gábor Udvari notifications@github.com:

I did some further testing and it seems that yavin1b is a special case. With the precompiled binary I can reproduce the bug on different maps. When I compile the binary from source the bug goes away on these maps (after dying and reloading checkpoint):

• t1_surprise: cannot force pull down the escalator at the sandcrawler
• t1_rail: cannot force pull down the escalator at the sandcrawler
• t3_rift: cannot force push the very first rock at the beginning

But the yavin1b issue still exists, even if all the above work. Putting the -fvisibility=hidden back to the CMakeLists.txt does not have any effect. The issue on yavin1b still exists while all the others are not. I compiled on Ubuntu 16.04, gcc version is 5.4.0 20160609.

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/JACoders/OpenJK/issues/889#issuecomment-269392415

[smcv]

PR #905 was intended to fix #902, but might fix this as well (I tried yavin1b after a save/load cycle and it seems fine).

[t-animal]

With the current HEAD the bug is fixed for me, too.

[smcv]

Huh. Current master doesn't have my fix for #902 yet, so your bug must have been something different?

[gabor-udvari]

PR #905 was merged since then, pulled master and compiled it, all my bugs are now fixed on Ubuntu 16.04 64bit. Thanks @smcv !

[smcv]

Both people previously reporting problems here say they are now solved, so I think this issue can be closed?

[manuLlanos]

Hello, I'm running Debian stable 64 bits. And this issue keeps happening in singleplayer. Each time I load a save after playing, it seems like the map triggers ( levers, dialogs, elevators) cease to work until the game is reloaded. I have installed the latest Linux 64 bit version as of now (2017-03-20)