JACoders / OpenJK

Community effort to maintain and improve Jedi Academy (SP & MP) + Jedi Outcast (SP only) released by Raven Software
GNU General Public License v2.0
2.01k stars 612 forks source link

Events are not triggering upon reloading a level after death #257

Closed sjdowling closed 11 years ago

sjdowling commented 11 years ago

Compiled on Ubuntu 12.04 gcc 4.6.3

There are certain events, such as cutting down the trees in yavin.bsp, collecting the ship parts in danger.bsp and flicking a switch in rail.bsp where if you die and reload a checkpoint then these events don't trigger any more and you can't complete the level.

What is more, if you die and then select to load another mission instead no events will be triggered in that mission. For example if you die during danger and can no longer collect and attach the ship parts and then quit the mission and select to do rail instead then the first door switch will not trigger.

The only way out is to load a save from before the first death.

It has been suggested that this is related to issue 255.

shinyquagsire23 commented 11 years ago

I'll just go ahead and say that this is most likely a Linux only bug (testing from Arch Linux). In fact, I believe ioquake's JKA branch added this workaround, but I have yet to test if it works well or not.

eezstreet commented 11 years ago

Heard about this. This treats the symptom, not the underlying disease.

Sent from my Windows Phone


From: Max Thomasmailto:notifications@github.com Sent: ‎5/‎20/‎2013 12:00 PM To: Razish/OpenJKmailto:OpenJK@noreply.github.com Subject: Re: [OpenJK] Events are not triggering upon reloading a level after death (#257)

I'll just go ahead and say that this is most likely a Linux only bug (testing from Arch Linux). In fact, I believe ioquake's JKA branch added this workaround, but I have yet to test if it works well or not.


Reply to this email directly or view it on GitHub: https://github.com/Razish/OpenJK/issues/257#issuecomment-18155440

sjdowling commented 11 years ago

I tried using that workaround shinyquagsire23 but it didn't fix it for me.

xycaleth commented 11 years ago

I'm considering this as fixed now as there haven't been any more reports of broken behaviour. Please feel free to reopen if this is not the case!