Ok, finally I managed to produce .lnk script file for "wlink" with right directives, linked all the object files into single DOS 32 bit DOS/4GW .exe, tried it in DOSbox and... it starts "DOS4GW.EXE" and then hangs. I'm giving up on this OW compiler and all this cross-compiling bullsh*t under Linux. Maybe another day I'll try old Watcom C/C++ for DOS/windows... or maybe not.

Sorry to hear that. At least you can use my working copy of the benchmark for testing old machines. 😀

I'm going to include it in all my future comparisons and if somebody else also wants to adopt it as a benchmark for their retro adventures... I'm happy to have given my little contribution.

I'm sure he'll give it another go after sleeping on it. Not much software would get done if people just gave up when it doesn't work.

Shameless plug: Super Trace VESA Benchmark

thp wrote on 2024-12-04, 19:49:

Shameless plug: Super Trace VESA Benchmark

😁
Interesting... I'll give it a try, although it's no raytracer. 😉 Thanks

I still can't find a way to make it work with 24bpp modes. That would open up the benchmark to older systems with cards that don't support 32bpp (ie. many ISA/VLB cards) I've never worked with vbe before so I'm really going blind in here. Any help would be appreciated 😀

MSxyz wrote on 2024-12-12, 17:36:

I still can't find a way to make it work with 24bpp modes. That would open up the benchmark to older systems with cards that don't support 32bpp (ie. many ISA/VLB cards) I've never worked with vbe before so I'm really going blind in here. Any help would be appreciated 😀

It should support 32bpp, 24bpp (RGB888 for both) and 16-bpp (RGB565) modes. It currently doesn't support 15bpp (RGB565) mode.

Can you run vesainfo from this thread on your card and post the output?

In some cases, for old cards, running UNIVBE might help expose more VESA modes. Oh, and the tracer only supports VESA 2.0, maybe that's the issue? (you having VESA 1.2 or something) In any case, a fallback to VGA should be offered with the latest version.

MSxyz wrote on 2024-12-12, 17:36:

I still can't find a way to make it work with 24bpp modes. That would open up the benchmark to older systems with cards that don't support 32bpp (ie. many ISA/VLB cards) I've never worked with vbe before so I'm really going blind in here. Any help would be appreciated 😀

Actually the current version is working somewhat in 24bpp modes but the colors are inverted (ie. red and blue color components are switched).
Here is a modified version that fixes this problem and allows to set 24bpp or 32bpp modes explicitly by adding '-b <bpp>' command line option.
The logic to automatically substitute 24bpp with 32bpp and vice versa is temporarily disabled for testing but can be re-enabled in the end (in GFX.C -> SAME_BPP macro).
Wrong video memory size display is also fixed.

@Edit:
Additional modifications:
After rendering the image the program waits for a keypress before switching back to text mode. It's not fair that you cannot see the beautifully rendered final image at all 😀.
The rendering time is still calculated properly regardless how long the program waits at the end. Moreover the rendering time is shown with millisecond precision.

Falcosoft wrote on 2024-12-13, 15:32:

Actually the current version is working somewhat in 24bpp modes but the colors are inverted (ie. red and blue color components a […]
Show full quote

MSxyz wrote on 2024-12-12, 17:36:

I still can't find a way to make it work with 24bpp modes. That would open up the benchmark to older systems with cards that don't support 32bpp (ie. many ISA/VLB cards) I've never worked with vbe before so I'm really going blind in here. Any help would be appreciated 😀

Actually the current version is working somewhat in 24bpp modes but the colors are inverted (ie. red and blue color components are switched).
Here is a modified version that fixes this problem and allows to set 24bpp or 32bpp modes explicitly by adding '-b <bpp>' command line option.
The logic to automatically substitute 24bpp with 32bpp and vice versa is temporarily disabled for testing but can be re-enabled in the end (in GFX.C -> SAME_BPP macro).
Wrong video memory size display is also fixed.

The attachment CRAY32_mod.zip is no longer available

@Edit:
Additional modifications:
After rendering the image the program waits for a keypress before switching back to text mode. It's not fair that you cannot see the beautifully rendered final image at all 😀.
The rendering time is still calculated properly regardless how long the program waits at the end. Moreover the rendering time is shown with millisecond precision.

Thanks! Trying it now...