mirror of
https://github.com/ZDoom/raze-gles.git
synced 2025-01-27 01:10:51 +00:00
- block opening of the menu in the fade out phase of a screenjob and in Exhumed's map/intermission screens.
At these places there's some inteference that can bring the engine into an unstable state. This is not a real fix, just a quick workaround. The actual problem requires closer examination why these are the only places where this happens.
This commit is contained in:
parent
68b7628f56
commit
58fb938aa7
2 changed files with 3 additions and 0 deletions
|
@ -189,6 +189,7 @@ static void GameTicker()
|
|||
case ga_newgame:
|
||||
FX_StopAllSounds();
|
||||
case ga_newgamenostopsound:
|
||||
DeleteScreenJob();
|
||||
newGameStarted = true;
|
||||
FX_SetReverb(0);
|
||||
gi->FreeLevelData();
|
||||
|
|
|
@ -915,6 +915,7 @@ public:
|
|||
startTime = -1;
|
||||
clock = 0;
|
||||
jobs[index].job->fadestate = DScreenJob::fadeout;
|
||||
gamestate = GS_INTRO; // block menu and console during fadeout - this can cause timing problems.
|
||||
actionState = State_Fadeout;
|
||||
}
|
||||
else
|
||||
|
@ -959,6 +960,7 @@ void DeleteScreenJob()
|
|||
delete runner;
|
||||
runner = nullptr;
|
||||
}
|
||||
twod->SetScreenFade(1);
|
||||
}
|
||||
|
||||
void RunScreenJobFrame()
|
||||
|
|
Loading…
Reference in a new issue