RaVeN-05 wrote on 2024-04-21, 12:28:

[…]
Show full quote

Copy code to clipboard

1Buffer dims 640x480 stride 81 and linebytes 1280
2Buffer dims 800x600 stride 81 and linebytes 1280
3Buffer dims 1024x768 stride 81 and linebytes 1280
4Buffer dims 1280x1024 stride 81 and linebytes 1280

That can't be right.

Could you try this and see if it's any different:

https://1drv.ms/u/s!As-dKk-N73dSmG7UyjpNtIta3s3g?e=5ELl0L
MD5: e1cdd96b97729c5010605d7ab0abd4c8

I think the original buffer was being cached. This time around the session is recreated before creating the buffer.

RR.exe is almost 100%. The last part doesn't render correctly, the final logo.

Your source code dump explains how to handle V_FIFO_SYNC_AND_RESPOND.

Also could you post a video of the Michigan new track (two laps) if you've got the time and willpower to spare. This is the rendition enhanced track.

linebytes gives me same results
michigan video https://fex.net/s/mao03lx

RaVeN-05 wrote on 2024-04-21, 15:53:

linebytes gives me same results
michigan video https://fex.net/s/mao03lx

The linebytes result is weird.

How come your ICR2 videos have beautiful yet subtle fog and mine don't?

[Alt]+[X] Turbo mode works now, but the framerates are disappointing and the sky is purple.

https://youtu.be/PQ2F3MAcfuQ

sharangad wrote on 2024-04-21, 16:13:

RaVeN-05 wrote on 2024-04-21, 15:53:

linebytes gives me same results
michigan video https://fex.net/s/mao03lx

The linebytes result is weird.

How come your ICR2 videos have beautiful yet subtle fog and mine don't?

good question =) .

framerate is limited by dosbox itself, i mean not exactly framerate but inability to use high CPU clocks, i think dosbox can't go at 350mhz pII like mine? that's why i told way back to use dosbox-stages , as its probably only one dosbox fork managed to emulate higher CPU rates .

sky is purple , yes something odd , keep in mind ALT+X disables AA, disable mirrors, and turn on sky optimization which cutoff top part of it, and uses solid color instead, probably one that called by ClearColor function?

Please fix me if you know more, its way how i see it.

RaVeN-05 wrote on 2024-04-22, 12:08:

good question =) . […]
Show full quote

sharangad wrote on 2024-04-21, 16:13:

RaVeN-05 wrote on 2024-04-21, 15:53:

linebytes gives me same results
michigan video https://fex.net/s/mao03lx

The linebytes result is weird.

How come your ICR2 videos have beautiful yet subtle fog and mine don't?

good question =) .

framerate is limited by dosbox itself, i mean not exactly framerate but inability to use high CPU clocks, i think dosbox can't go at 350mhz pII like mine? that's why i told way back to use dosbox-stages , as its probably only one dosbox fork managed to emulate higher CPU rates .

sky is purple , yes something odd , keep in mind ALT+X disables AA, disable mirrors, and turn on sky optimization which cutoff top part of it, and uses solid color instead, probably one that called by ClearColor function?

Please fix me if you know more, its way how i see it.

The dosbox staging guys kicked up a fuss, I might port it to that as well. I think I have a solution for the licensing issue.

The DosClient which renders the games will be GPL 2.0, for which I, as the author grant a license exception to use a closed source library. DosClient talks to Dosbox via named pipe via a complex protocol, which is OK because I it's GPL 2.0. I think that's how the other closed sourced wrappers did it.

I'll port it to dosbox staging as well. Shouldn't be difficult now.

RaVeN-05 wrote on 2024-04-22, 12:08:

good question =) . […]
Show full quote

sharangad wrote on 2024-04-21, 16:13:

RaVeN-05 wrote on 2024-04-21, 15:53:

linebytes gives me same results
michigan video https://fex.net/s/mao03lx

The linebytes result is weird.

How come your ICR2 videos have beautiful yet subtle fog and mine don't?

good question =) .

framerate is limited by dosbox itself, i mean not exactly framerate but inability to use high CPU clocks, i think dosbox can't go at 350mhz pII like mine? that's why i told way back to use dosbox-stages , as its probably only one dosbox fork managed to emulate higher CPU rates .

sky is purple , yes something odd , keep in mind ALT+X disables AA, disable mirrors, and turn on sky optimization which cutoff top part of it, and uses solid color instead, probably one that called by ClearColor function?

Please fix me if you know more, its way how i see it.

Your post is spot on. I should be able to port it to dosbox staging without much of a hassle. The rights holders kicked up an almight fuss, but I'm sure making DosClient GPL 2.0 resolves the issue.

They were also extremely unhelpful.

dosbox's speed depends only on the speed of your computer's cpu speed. nothing is limiting dosbox.

if you want more speed you can use qemu which sends cpu messages directly to your real cpu, hence is many times faster

of course no cpu/emulator will speed up anything if game is limited to 30 fps 😉

robertmo3 wrote on 2024-04-22, 14:30:

dosbox's speed depends only on the speed of your computer's cpu speed. nothing is limiting dosbox.

if you want more speed you can use qemu which sends cpu messages directly to your real cpu, hence is many times faster

of course no cpu/emulator will speed up anything if game is limited to 30 fps 😉

In [Alt+X] mode the framerate should be uncapped. if you check out this video:
https://www.youtube.com/watch?v=CwQSQ63W50c&t=639s

Alt+X uncaps the framerate, though I'm not entirely sure how the board is running at 190 fps.

Got the rendering ported to dosbox staging. Get this:

Please do tests wisely, you will find it surprising that dosbox-staging has more cpu speed emulation comparing to dosbox original.
Try Chasm the rift or Quake or desperabis all those very cpu demand games and you will see that dosbox limited

RaVeN-05 wrote on 2024-04-22, 15:23:

Please do tests wisely, you will find it surprising that dosbox-staging has more cpu speed emulation comparing to dosbox original.
Try Chasm the rift or Quake or desperabis all those very cpu demand games and you will see that dosbox limited

I won't do anymore speed tests until I have dosbox-staging compatibility at 100%. I generally find staging quicker.

https://www.dosbox.com/wiki/Performance

used Note: Based on Speed Test 1.14
in dosbox 105% "û This computer 332117 parrots, 123.1 XT"
vs
dosbox staging 105% "û This computer 392241 parrots, 145.4 XT"

ok ok

If you've got power can you run good ole FIFO again:

https://1drv.ms/u/s!As-dKk-N73dSmG__kqJd7gQTP3Ey?e=cUhUmu
MD5: a0287c185d57c50079b5185d66fa37bc

Attach the FIFO.txt file here. What I really need is the Int21h call results at the end (EDI on entry and pre-exit):

1AllocDosMem returned 1
2*****************************************************************************
3SWI Before: (Int 21h)(Call 1) AX B101, BX 58B8, CX 3246, DX 00A7, ES 01D0, EDI 00000000, FLAGS 0246
4SWI After: (2) AX B100, BX 58B8, CX 3246, DX 00A7, ES 01D0, EDI 00000000, DS 0000, SI 0000, EDI 00000000, SP 0000, FLAGS 0212
5*****************************************************************************
6Int 21h succeeded
7FreeDosMem returned 1

I think the secret of vQuake support is in EDI, which should have the protected mode entry point for such calls. In the case of dosbox-rendition, this is set to NULL (0).

RaVeN-05 wrote on 2024-04-22, 15:47:

https://www.dosbox.com/wiki/Performance […]
Show full quote

https://www.dosbox.com/wiki/Performance

used Note: Based on Speed Test 1.14
in dosbox 105% "û This computer 332117 parrots, 123.1 XT"
vs
dosbox staging 105% "û This computer 392241 parrots, 145.4 XT"

ok ok

Now that's a lot of parrots! It's quite a bit faster.

After disabling logging, the performance mode framerate varies between 40-70 fps with occasional audio stutters.

This is with bog standard Dosbox, not elite dosbox-staging.

just wondering as latest dosbox staging is 64-bit only
are you using 64-bit rready or
using 32bit rready with older 32-bit dosbox staging

robertmo3 wrote on 2024-04-22, 17:46:

just wondering as latest dosbox staging is 64-bit only
are you using 64-bit rready or
using 32bit rready with older 32-bit dosbox staging

I built a 32 bit version from source. My code snapshot is from last year, so it still supports 32 bit.

It should still work with 64 bit Dosbox, since everything goes down a pipe. Dosclient is 32 bit.