New release! FastDoom 0.8.11:

Changelog:

- Optimized backbuffered video modes: Hercules, CGA B&W, Plantronics ColorPlus, EGA, ATI 640x200
- Small optimization on multiple modulo operations, sound code and gameplay code
- Fixed music initialization volume (@deat322)
- Fixed mouse move fordward button (@deat322)
- Include full FastDoom version number (issue #72, @SpitFire-666)

Download: https://github.com/viti95/FastDoom/releases/tag/0.8.11

Is the ATI 640x400 mode actually rendering in 640x400 or is it doubling 320x200?

A little mistake when I wrote the changelog, the optimized ATI Small Wonder mode has a resolution of 640x200 instead of 640x400. @AirIntake, the base resolution of the ATI mode is 320x200, but it's using scaling techniques to get more colors from the basic 16 ones (dithering 2x1).

Forgot to post when it came out: Raspberry Pi Pico standalone DOOM https://kilograham.github.io/rp2040-doom/
Good writeup with many optimizations, most trade speed for size (RP2040 has 264K of RAM), but there are some things (smaller data types) that could speed things up even on a 386/486 due to less cache pressure.

Getting messed up colors in fast doom, vanilla works perfectly. System is a 486DX33 16MB RAM and WD90C31 video card. Using latest version

Those colours perfect for Ancient Aliens, or for an outrun themed game. /jk

Does the same happen on older releases @maxtherabbit?? I've never seen that bug on the Mode Y executable. I'll add an issue and try to fix it, I guess the bug it's related to the change palette function, it's very optimized and maybe causes troubles with Western Digital videocards. Also, have you tried the fdoom13h.exe executable?

ViTi95 wrote on 2022-04-18, 08:39:

Does the same happen on older releases @maxtherabbit?? I've never seen that bug on the Mode Y executable. I'll add an issue and try to fix it, I guess the bug it's related to the change palette function, it's very optimized and maybe causes troubles with Western Digital videocards. Also, have you tried the fdoom13h.exe executable?

Same result on both FDOOM and FDOOM13H. Did not try older versions, is there a specific version I should try?

ETA I'm going to see if swapping the palette DAC changes anything

Try the 0.7 release, that was the last one with unoptimized palette set routines. Also what DOOM WAD and version are you using?

Seeing that palette garbage made me recall bad times with Tseng VLB cards on a M919...

ViTi95 wrote on 2022-04-18, 16:38:

Try the 0.7 release, that was the last one with unoptimized palette set routines. Also what DOOM WAD and version are you using?

1.9 shareware. I'll try the 0.7 fast doom and let you know

EDIT: 0.7 works just fine

Still planning to try the latest version again with different RAMDAC. Will post again when I know

The next release will include a fix for this issue (via command line parameter). Some video cards / DACs don't like setting the VGA palette via REP OUTS instruction. The REP OUTS instruction is faster but in some cases avoids checking if the port is ready to write more data, that's why it fails on some cases.

Wolf3D source code has a function called VL_TestPaletteSet to check if the palette can be set with outsb successfully or not. This could be adapted in FastDoom without requiring additional command line swtiches or another separate executable.

Thanks for the idea Gmlb256 !! I've updated the code to detect if the video card is compatible with the REP OUTSB palette set using the same method as Wolfenstein 3D, but I've mantained the command line parameter to force the use of the slower code in case the autodetection fails.

Tried a few different DACs with 0.8.11, the problem persisted. I'll look forward to the new version

https://www.youtube.com/watch?v=Op2tr2lGK6Y

IBM Monochrome Display Adapter

¯\_(ツ)_/¯

EDIT: FastDoom 0.8.12 released, please @maxtherabbit try it, I hope it fixes automatically the issue with the VGA card. If it still doesn't work fine, try the command line parameter "-fixDAC"

- New video mode: IBA MDA text mode (FDOOMMDA.EXE). Just for fun, quick'n'dirty
- Small optimization on gameplay code and melting screen functions
- Fixed corruption on VGA palettes (issue #75). Force fix if still doesn't work using the command line parameter "-fixDAC".

https://github.com/viti95/FastDoom/releases/tag/0.8.12

ViTi95 wrote on 2022-04-26, 16:10:

IBM Monochrome Display Adapter

¯\_(ツ)_/¯

I have every part of E1M1 memorized and I still can barely tell what the hell is going on. Nice.

It's hilarious, indeed- knowing the map, it really kinda works. 😁
Thank you for the continued insanity there - I love it! 😀

rasz_pl wrote on 2022-04-12, 09:50:

Forgot to post when it came out: Raspberry Pi Pico standalone DOOM https://kilograham.github.io/rp2040-doom/
Good writeup with many optimizations, most trade speed for size (RP2040 has 264K of RAM), but there are some things (smaller data types) that could speed things up even on a 386/486 due to less cache pressure.

Thanks for posting this, it was a fascinating read.

ViTi95 wrote on 2022-04-26, 16:10:

https://www.youtube.com/watch?v=Op2tr2lGK6Y […]
Show full quote

https://www.youtube.com/watch?v=Op2tr2lGK6Y

IBM Monochrome Display Adapter

¯\_(ツ)_/¯

EDIT: FastDoom 0.8.12 released, please @maxtherabbit try it, I hope it fixes automatically the issue with the VGA card. If it still doesn't work fine, try the command line parameter "-fixDAC"

- New video mode: IBA MDA text mode (FDOOMMDA.EXE). Just for fun, quick'n'dirty
- Small optimization on gameplay code and melting screen functions
- Fixed corruption on VGA palettes (issue #75). Force fix if still doesn't work using the command line parameter "-fixDAC".

https://github.com/viti95/FastDoom/releases/tag/0.8.12

I know that map like the back of my hand and I still had no idea WTF was going on 🤣