ViTi95 wrote on 2024-05-30, 20:20:

* New VGA 320x100 executable. Uses same direct rendering method as vanilla Doom, but with half height resolution. High detail resolution is 320x100, low detail 160x100 and potato detail 80x100. Recommended for slow 386 cpu's with VGA cards. 2D elements also have half height resolution, so text is pretty much unreadable (unless someone creates a WAD with optimized fonts for this mode)

looks... interesting :)

by the way, i think is is possible (but requires a fair number of effort) to simulate a raster interrupt which will switch to full 320x200 mode at the moment bottom HUD is displayed - I've experimented with that trick by polling for port 0x3DA, and toggling the doublescan bit in CRTC, and this seems to work on most VGA cards except NVidia.

I've done some font work and now I think FastDoom 320x100 modes are much more usable. What do you think?

It is actually legible. A lot more so than many handwritings I have to read daily.

So who has a Harris 25Mhz 286 with 8MB and wants to try it with a 386 emulator now? 🤣

(woe is me because I once had one and let it go)

I only have a 286-16 and I doubt that would be worth trying 😁

*cough* Doom8088 *cough*

crazii wrote on 2024-02-15, 04:34:

Sorry that I didn't know the incompatibility problem until recent days, I've created a PR so FastDoom can work with HDPMI, and maybe for win9x too.

Yes it is unfortunately. On E5800 (3.2GHz Core2 Duo) w/Audigy2ZS/Creative DOS drivers 5.00 w/8Mb GS bank under DOS 7.1 from W98SE (no GUI boot, clean MS-DOS startup) I have following observations:
1. with latest jemmex + hdmpi32 -r, starts ok, after several demo loops - crash
2. with stock himem/emm386 noems novcpi and hdpmi32 -r - not enough extended memory (the same for hdpmi32 -r -x)
The only solution to run fastdoom - via jemmex and following crash after several minutes.
Vanilla ultimate doom have no issues, the same for quake dos/q2dos w/SSE support/original quake1/Duke Nukem 3D - all of them w/hdpmi32 -r host (= mtrrlfb provides speedup for dos4gw and cwsdpmi games under hdpmi32 host).

vsharun wrote on 2024-06-17, 15:10:

Yes it is unfortunately. On E5800 (3.2GHz Core2 Duo)

Why would you need to run FastDoom on a 3.2GHz processor from the 2000s? Serious question, it seems absurd to me. Like, wouldn't regular Doom run very fast anyway?

7F20 wrote on 2024-06-17, 21:40:

vsharun wrote on 2024-06-17, 15:10:

Yes it is unfortunately. On E5800 (3.2GHz Core2 Duo)

Why would you need to run FastDoom on a 3.2GHz processor from the 2000s? Serious question, it seems absurd to me. Like, wouldn't regular Doom run very fast anyway?

The initial goal was to find a platform which will outperform everything in Phil's chart (Q1/Doom). Then the goal was shifted to narrower one - the fastest DOS gaming platform possible with Ensoniq (Creative then up to A2ZS) native sound.
So doom's, actually if you stick them together then the difference is apparent:
1. fastdoom (now) has working VESA support, which vanilla doesn't - 1024x768 looks fantastic
2. fastdoom - really fast, 800+ fps on athlonXP 2.2GHz/ti4200
3. fastdoom has broad sound and music cards support, which vanilla hasn't (Soundscape)

So my approach to the fastdoom is yet another discipline - run doom as fast as possible on as fast as possible hardware while maintaining some constraints (sound and music from A2ZS and/or Ensoniq's ES1370-1373).

@vsharun Is the crash happening on the 1024x768 modes? I think there is a bug somewhere that ends up crashing the game only in that mode, I still have to debug it. In that mode if you get close to a wall, the performance drops a lot, which shouldn't happen.

ViTi95 wrote on 2024-06-18, 09:25:

@vsharun Is the crash happening on the 1024x768 modes? I think there is a bug somewhere that ends up crashing the game only in that mode, I still have to debug it. In that mode if you get close to a wall, the performance drops a lot, which shouldn't happen.

Hi.
Any VESA modes affected (both r/d), the same for fdoom13h, the same for fdoom vanilla.
Last crash was related to memory allocation for Z_something with latest jemmex and ext memory limit to 59Megs.
EMM386 with NOVCPI - any fdoom binaries will refuse to run with "not enough extended memory", despite 1.7 gigs available.
jemmex with novcpi - fd768d - runs ok for a while (low fps), 768r - hang after startup. They all ultimately crash. And I suppose it is sound card related somehow.
hdpmi32 -r host in all cases.

Does it do it with music off? does it do it only using FM music? Thinking that MIDI timing loops are something that gets everything crashing sooner or later as CPU speed scales.

New release, FastDoom 0.9.9e!

Changelog:

* Fixed diminished lightning issues on high resolution VESA modes
* Fixed some 2D status bar and menus misalignements
* Fixed rendering corruption on VESA 386SX codepath
* Fixed MS-DOS 7 crash #187
* New fonts for 320x100 resultion modes (half height)
* Optimizations (C)

https://github.com/viti95/FastDoom/releases/d … Doom_0.9.9e.zip

vsharun wrote on 2024-06-18, 06:14:

The initial goal was to find a platform which will outperform everything in Phil's chart (Q1/Doom). Then the goal was shifted to […]
Show full quote

The initial goal was to find a platform which will outperform everything in Phil's chart (Q1/Doom). Then the goal was shifted to narrower one - the fastest DOS gaming platform possible with Ensoniq (Creative then up to A2ZS) native sound.
So doom's, actually if you stick them together then the difference is apparent:
1. fastdoom (now) has working VESA support, which vanilla doesn't - 1024x768 looks fantastic
2. fastdoom - really fast, 800+ fps on athlonXP 2.2GHz/ti4200
3. fastdoom has broad sound and music cards support, which vanilla hasn't (Soundscape)

So my approach to the fastdoom is yet another discipline - run doom as fast as possible on as fast as possible hardware while maintaining some constraints (sound and music from A2ZS and/or Ensoniq's ES1370-1373).

How does this approach compare to using ZDoom on a modern PC?

As in, what limitations are you trying to surmount with your current approach? Is it just the soundcard support for the specific, particular card you want to use, or are you just chasing framerates and FastDoom is able to pull ahead of ZDoom or something like that?

Yah 'coz if it's tryna train AIs to play doom at 2000fps so they can leverage the model to fly smart bullets through a keyhole, then we might have objections 🤣

BitWrangler wrote on 2024-06-18, 14:27:

Does it do it with music off? does it do it only using FM music? Thinking that MIDI timing loops are something that gets everything crashing sooner or later as CPU speed scales.

all combinations sfx and music crashes, including both set to none.

7F20 wrote on 2024-06-18, 17:35:

vsharun wrote on 2024-06-18, 06:14:

The initial goal was to find a platform which will outperform everything in Phil's chart (Q1/Doom). Then the goal was shifted to […]
Show full quote

The initial goal was to find a platform which will outperform everything in Phil's chart (Q1/Doom). Then the goal was shifted to narrower one - the fastest DOS gaming platform possible with Ensoniq (Creative then up to A2ZS) native sound.
So doom's, actually if you stick them together then the difference is apparent:
1. fastdoom (now) has working VESA support, which vanilla doesn't - 1024x768 looks fantastic
2. fastdoom - really fast, 800+ fps on athlonXP 2.2GHz/ti4200
3. fastdoom has broad sound and music cards support, which vanilla hasn't (Soundscape)

So my approach to the fastdoom is yet another discipline - run doom as fast as possible on as fast as possible hardware while maintaining some constraints (sound and music from A2ZS and/or Ensoniq's ES1370-1373).

How does this approach compare to using ZDoom on a modern PC?

As in, what limitations are you trying to surmount with your current approach? Is it just the soundcard support for the specific, particular card you want to use, or are you just chasing framerates and FastDoom is able to pull ahead of ZDoom or something like that?

Well, several constraints are involved:
1. only DOS
2. only PCI soundcards, Ensoniq/Creative with cleanest possible sound
3. maximum compatibility (Dune2 for example - jemmex with maxmem)
what platform will be the fastest one for doom/q1/q2/duke3d.

BitWrangler wrote on 2024-06-19, 04:02:

Yah 'coz if it's tryna train AIs to play doom at 2000fps so they can leverage the model to fly smart bullets through a keyhole, then we might have objections 🤣

Understand your scepticism. Take it from another angle: I'm from Bucha district, entire village was under occupation with executions etc, now I have friends and relatives on front line and would like to keep my sanity with me by chasing some technical goals and bringing back memories where life was somewhat easy.

Just wow @vsharun, I hope the situation gets better for you and Ukraine.

I'll test on faster / modern systems, there has been reports of FastDoom also crashing on Phenom machines, so maybe this is related. Maybe you can try latest release and see if it crashes in the same way.

ViTi95 wrote on 2024-06-18, 16:32:

* Fixed diminished lightning issues on high resolution VESA modes

This is sensational, thankyou to all involved. It looks and runs beautiful now - I love this port 👍

ViTi95 wrote on 2024-06-19, 20:45:

Just wow @vsharun, I hope the situation gets better for you and Ukraine.

I'll test on faster / modern systems, there has been reports of FastDoom also crashing on Phenom machines, so maybe this is related. Maybe you can try latest release and see if it crashes in the same way.

0.9.9e crashes:

1Sound Blaster DSP 4.01
2ADDR: 220, IRQ: 5, DMA LOW: 1, DMA HIGH: 5
3D_CheckNetGame: Checking network game status.
4S_Init: Setting up sound.
5HU_Init: Setting up heads up display.
6ST_Init: Init status bar.
7DOS/32A run-time (6001): exception 0Eh
8Identity: page fault at 0838:0041C279
9Unrelocated crash address 1:00034269, error code pushed on stack 00000000
10Module name: "C:\GAMES\FD099E\FDOOM13H.EXE", ProcessId=0000
11========================================================================APP/32=
12EFLAGS = 00010283 [00000010.10000011]  CS:[EIP] = 0F BF 03 C7 44 24 0C 00 00 00
13EAX = FFC0ED3C    ESI = 004D66E1       DR6 = FFFF0FF0    SS:[ESP+00] = FFFF9C13
14EBX = FFFFFFFF    EDI = FFC0894F       CR0 = 80000011    SS:[ESP+04] = 00000018
15ECX = 00000000    EBP = 004E66D4       CR2 = FFFFFFFF    SS:[ESP+08] = FFFFFFFF
16EDX = 00006500    ESP = 004E6658       CR3 = 00018000    SS:[ESP+0C] = 00000018
17CS: = 0838  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=CODE/32bit Type=5 Acc=DF9B
18DS: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
19ES: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
20SS: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
21FS: = 0840  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
22GS: = 0058  Base=00010980 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93

1Sound Blaster DSP 4.01
2ADDR: 220, IRQ: 5, DMA LOW: 1, DMA HIGH: 5
3D_CheckNetGame: Checking network game status.
4S_Init: Setting up sound.
5HU_Init: Setting up heads up display.
6ST_Init: Init status bar.
7DOS/32A run-time (6001): exception 0Eh
8Identity: page fault at 0838:0042FF97
9Unrelocated crash address 1:00047F87, error code pushed on stack 00000000
10Module name: "C:\GAMES\FD099E\FDM768R.EXE", ProcessId=0000
11========================================================================APP/32=
12EFLAGS = 00010286 [00000010.10000110]  CS:[EIP] = 8A 84 3D 00 24 FE FF 49 8A 00
13EAX = 004BD62F    ESI = FFE9BF68       DR6 = FFFF0FF0    SS:[ESP+00] = FFD5BF68
14EBX = 00000031    EDI = 00629EDC       CR0 = 80000011    SS:[ESP+04] = FFE9BF68
15ECX = FFFFFF69    EBP = 616D7800       CR2 = 61CE3ADC    SS:[ESP+08] = 0099D144
16EDX = 0048BD88    ESP = 00660E48       CR3 = 00018000    SS:[ESP+0C] = 0000024C
17CS: = 0838  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=CODE/32bit Type=5 Acc=DF9B
18DS: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
19ES: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
20SS: = 0830  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
21FS: = 0840  Base=00000000 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93
22GS: = 0058  Base=00010980 Limit=000FFFFF Gr=PAGE Seg=DATA/32bit Type=1 Acc=DF93

Can't reproduce crash with vanilla fdoom.exe 0.9.9e
Win98's himem/emm386 noems ram (with vcpi host)
audigy2zs creative 5.00 drivers as general MIDI (8M bank) and sound blaster as sfx.