Navigation Menu

Skip to content

Commit

Permalink
fix a palette re-setting bug in the truecolor code
Browse files Browse the repository at this point in the history
  • Loading branch information
fabiangreffrath committed May 13, 2019
1 parent 9607e3e commit 533bc30
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/doom/st_stuff.c
Expand Up @@ -2232,7 +2232,7 @@ void ST_Stop (void)
#ifndef CRISPY_TRUECOLOR
I_SetPalette (W_CacheLumpNum (lu_palette, PU_CACHE));
#else
I_SetPalette (lu_palette);
I_SetPalette (0);
#endif

st_stopped = true;
Expand Down

4 comments on commit 533bc30

@JNechaevsky
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it fixes an issue with silent crash of TNT/Plutonia speed runs!

Something seems to be wrong with TNT speedrun from our table. It may randomly desync in MAP03 while -timedemo, in both Crispy and PrBoom. Really odd. Anyways, as you have said, better idea will be to have a both "as long as possible" and "as quick as possible" runs, I'll update our table soon.

@fabiangreffrath
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some Final Doom demos to work, you need to load TNT.WAD or PLUTONIA.WAD as PWADs with DOOM2.WAD as the IWAD.

@JNechaevsky
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I remember that. None of these approaches are working for current TNT run, though.

crispy-doom.exe -timedemo 30tn8336.lmp -file tnt.wad
crispy-doom.exe -timedemo 30tn8336.lmp -iwad doom2.wad -file tnt.wad

@JNechaevsky
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now it's oblivious, I'm using wrong IWAD, there are two of TNT. 😑

Please sign in to comment.