BEEN_Nath_58 wrote on 2025-03-04, 06:27:

Somehow I never managed to notice this.

It's new.

BEEN_Nath_58 wrote on 2025-03-04, 06:27:

The "Failed run 3D hardware acceleration" is coming from RReady itself. I let RReady use the Launch function to play, in which case the game most times (ran 3 out of 20 Launches).

Edit: Not to mention the game will crash anyways on Windows 11 even if RReady init is successful, since EmulateHeap is pulling it from behind... the motive here is to let the init happen correctly and to let the game crash automatically, not at the Redline error

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls [ddraw] in the i76 folder AND dxwnd running to run the game.

[EDIT]
The errors in the RReady log files are how older rredline games allocated memory. They ask for insane amounts of vram and exponentially shrink down the amount they ask for. Later on Rendition added an extension to get the largest amount possible in one fell swoop.

The "failed to initialise 3d hardware" error message pops up when ddraw doesn't work.
[/EDIT]

sharangad wrote on 2025-03-04, 06:51:

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in th […]
Show full quote

BEEN_Nath_58 wrote on 2025-03-04, 06:27:

The "Failed run 3D hardware acceleration" is coming from RReady itself. I let RReady use the Launch function to play, in which case the game most times (ran 3 out of 20 Launches).

Edit: Not to mention the game will crash anyways on Windows 11 even if RReady init is successful, since EmulateHeap is pulling it from behind... the motive here is to let the init happen correctly and to let the game crash automatically, not at the Redline error

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in the i76 folder AND dxwnd running to run the game.
[edit]
The errors in the RReady log files are how older rredline games allocated memory. They ask for insane amounts of vram and exponentially shrink down the amount they ask for. Later on Rendition added an extension to get the largest amount possible in one fell swoop.

The "failed to initialise 3d hardware" error message pops up when ddraw doesn't work.
[/EDIT]

Let me try dgVoodoo2. I never needed it for the game, but let's see.

BEEN_Nath_58 wrote on 2025-03-04, 06:58:

sharangad wrote on 2025-03-04, 06:51:

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in th […]
Show full quote

BEEN_Nath_58 wrote on 2025-03-04, 06:27:

The "Failed run 3D hardware acceleration" is coming from RReady itself. I let RReady use the Launch function to play, in which case the game most times (ran 3 out of 20 Launches).

Edit: Not to mention the game will crash anyways on Windows 11 even if RReady init is successful, since EmulateHeap is pulling it from behind... the motive here is to let the init happen correctly and to let the game crash automatically, not at the Redline error

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in the i76 folder AND dxwnd running to run the game.
[edit]
The errors in the RReady log files are how older rredline games allocated memory. They ask for insane amounts of vram and exponentially shrink down the amount they ask for. Later on Rendition added an extension to get the largest amount possible in one fell swoop.

The "failed to initialise 3d hardware" error message pops up when ddraw doesn't work.
[/EDIT]

Let me try dgVoodoo2. I never needed it for the game, but let's see.

Already seems to be working better so far. Interesting, didn't expect it...

BEEN_Nath_58 wrote on 2025-03-04, 06:58:

sharangad wrote on 2025-03-04, 06:51:

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in th […]
Show full quote

BEEN_Nath_58 wrote on 2025-03-04, 06:27:

The "Failed run 3D hardware acceleration" is coming from RReady itself. I let RReady use the Launch function to play, in which case the game most times (ran 3 out of 20 Launches).

Edit: Not to mention the game will crash anyways on Windows 11 even if RReady init is successful, since EmulateHeap is pulling it from behind... the motive here is to let the init happen correctly and to let the game crash automatically, not at the Redline error

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in the i76 folder AND dxwnd running to run the game.
[edit]
The errors in the RReady log files are how older rredline games allocated memory. They ask for insane amounts of vram and exponentially shrink down the amount they ask for. Later on Rendition added an extension to get the largest amount possible in one fell swoop.

The "failed to initialise 3d hardware" error message pops up when ddraw doesn't work.
[/EDIT]

Let me try dgVoodoo2. I never needed it for the game, but let's see.

The ddraw related dlls from the ms(I think) subfolder.

sharangad wrote on 2025-03-04, 07:01:

BEEN_Nath_58 wrote on 2025-03-04, 06:58:

sharangad wrote on 2025-03-04, 06:51:

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in th […]
Show full quote

I get that error without dxwnd always and didn't use to after using DxWnd. After windows 11 24h2, I need the dgvooodo dlls in the i76 folder AND dxwnd running to run the game.
[edit]
The errors in the RReady log files are how older rredline games allocated memory. They ask for insane amounts of vram and exponentially shrink down the amount they ask for. Later on Rendition added an extension to get the largest amount possible in one fell swoop.

The "failed to initialise 3d hardware" error message pops up when ddraw doesn't work.
[/EDIT]

Let me try dgVoodoo2. I never needed it for the game, but let's see.

The ddraw related dlls from the ms(I think) subfolder.

The game seems to be working fine now regardless. Probably I could've (been asked) to use dgVoodoo2 earlier 😀

BEEN_Nath_58 wrote on 2025-03-04, 07:02:

sharangad wrote on 2025-03-04, 07:01:

BEEN_Nath_58 wrote on 2025-03-04, 06:58:

Let me try dgVoodoo2. I never needed it for the game, but let's see.

The ddraw related dlls from the ms(I think) subfolder.

The game seems to be working fine now regardless. Probably I could've (been asked) to use dgVoodoo2 earlier 😀

I only ran it like this after win11 24h2. Before that DxWnd worked fine. Dxwnd might work if its ddraw dll is copied into the game folder, but I've never tested it.

BEEN_Nath_58 wrote on 2025-03-04, 07:02:

sharangad wrote on 2025-03-04, 07:01:

BEEN_Nath_58 wrote on 2025-03-04, 06:58:

Let me try dgVoodoo2. I never needed it for the game, but let's see.

The ddraw related dlls from the ms(I think) subfolder.

The game seems to be working fine now regardless. Probably I could've (been asked) to use dgVoodoo2 earlier 😀

The ddraw support in DxWnd isn't working properly on some systems and never on win11 24h2. Not entirely sure why.

sharangad wrote on 2025-03-04, 07:24:

BEEN_Nath_58 wrote on 2025-03-04, 07:02:

sharangad wrote on 2025-03-04, 07:01:

The ddraw related dlls from the ms(I think) subfolder.

The game seems to be working fine now regardless. Probably I could've (been asked) to use dgVoodoo2 earlier 😀

The ddraw support in DxWnd isn't working properly on some systems and never on win11 24h2. Not entirely sure why.

Maybe whatever problematic in system DDraw was never fixed, dgVoodoo2 is a full implementation and translation of DirectDraw and Direct3D, DxWnd is not

BEEN_Nath_58 wrote on 2025-03-04, 08:04:

sharangad wrote on 2025-03-04, 07:24:

BEEN_Nath_58 wrote on 2025-03-04, 07:02:

The game seems to be working fine now regardless. Probably I could've (been asked) to use dgVoodoo2 earlier 😀

The ddraw support in DxWnd isn't working properly on some systems and never on win11 24h2. Not entirely sure why.

Maybe whatever problematic in system DDraw was never fixed, dgVoodoo2 is a full implementation and translation of DirectDraw and Direct3D, DxWnd is not

Didn't know that. I just assumed DxWnd offered a full implementation. It still doesn't work on my problem UHD620 laptop with dgvoodoo2 and dxwnd.

I only figured this out in January, when I was offered the 24H2 update.

Cart.exe:

Base "MZ", extended , start 00000000, size 0000F474
Base "BW", extended , start 0000F474, size 008FB400

The second exec is a PE/COFF or whatever but there's no sign of an LX, LC or LE in there.

Does this mean Dos4gw is statically linked?

The second exe is a BW (watcom exp) that for some weird reason doesn't work when stripped. It should work because dos/4g can run them, but in this case it isn't. It isn't a pe/coff as I thought, that was a bug in my header parser.

Does anyone know if there's any documentation for watcom exp binary formats. I seem to be struggling to find anything. I'd like to try converting it to an mz/LE if possible .

i think you should post also in the other tread Replacing DOS/4GW with DOS32A

robertmo3 wrote on 2025-03-07, 06:20:

i think you should post also in the other tread Replacing DOS/4GW with DOS32A

Thanks @robertmo3, I didn't think of that.

Here's a DOS32A bound version of Cart.exe (Non-Rendition/Software rendered):

https://nirvtek.com/downloads/CART32.7z
MD5: 24cf46597d851bbac619b2212e1aa6c4

ICR2 (Rendition and non-Rendition) use DOS/4G and not DOS/4GW which is why sb (from DOS32A can't unbind and bind to it).

To unbind the existing exe, (easy way), you need to use DOS/4G's 4GWBIND.EXE /U command before binding to DOS32A.

The Rendition edition (DOS32A) has had its limits increased, but the custom tracks don't seem to be working, ... yet. It does accept and report the higher limits now.

Lazy Sunday and back to Scorched Planet.

Scorched planet menus and HUD at 100% (almost):

https://youtu.be/aS85ScBkJ2w

There'll be an alpha release with the following bugfixes and it will go into testing for release to the store before the end of the week:

1) ICR2 brake balance not working for Windows keyboard layouts other than US-English and UK-English.
2) RReady not defaulting to upscaling at maximum resolution when a rendition.cfg file is missing (stock Rendition Dosbox setting, unconfigured). This was broken by windowed mode support.
3) Scorched planet almost 100% (videos, menus and HUD now correctly rendering)
4) Dosbox RAM limits increased, should support up to 1 GB of RAM.

*******************************************
RReady Alpha, March 09 2025
(Untested Alpha release, undergoing testing for store release)
*******************************************
https://nirvtek.com/downloads/RReady.Alpha.20250309.001.7z
MD5: 11f908fe29f2c1bbe181e9929c076e19

1) ICR2 brake balance not working for Windows keyboard layouts other than US-English and UK-English.
2) RReady not defaulting to upscaling at maximum resolution when a rendition.cfg file is missing (stock Rendition Dosbox setting, unconfigured). This was broken by windowed mode support.
3) Scorched planet almost 100% (videos, menus and HUD now correctly rendering) with Dosbox-Rendition (non-functional in Dosbox-Staging-Rendition)
4) Dosbox RAM limits increased, should support up to 1 GB of RAM.

********************************************
RReady Alpha, 12 March 2025 (full tested Alpha Build)
Store Release 1.0.40 (Live on MS Store)
********************************************

https://nirvtek.com/downloads/RReady.Alpha.20250312.001.7z
MD5: 22d7c73617524cbfb5f55d42d3cf8112

- ICR2 brake balance not working for Windows keyboard layouts other than US-English and UK-English.
- RReady not defaulting to upscaling at maximum resolution when a rendition.cfg file is missing (stock Rendition Dosbox setting, unconfigured). This was broken by windowed mode support.
- Scorched Planet almost 100% (videos, menus and HUD now correctly rendering) with Dosbox-Rendition (non-functional in Dosbox-Staging-Rendition)
- Dosbox-Rendition RAM limits increased, should support up to 1 GB of RAM. Currently forced to 512 MB. The next release will restore memsize selection.
- Rendition AA can be disabled only for apps that whose image quality is badly impacted by RReady’s implementation (ICR2, vQuake 1 & 2 and vHexen II). It will default to disabled in these games unless overridden.

Hi all,

I have a sound problem I cannot seem to crack. With RR Indycar Racing II everything works, except that the game sound is only audible when the little dosbox window has focus, not when the game itself has focus. It doesn't matter if the game is run fullscreen or windowed.

Would anyone have suggestions for this dosbox newb?

Cheers

- RReady Rendition Verite wrapper is freakin' brilliant for Indycar Racing II by the way! Love it.

wowbaggr wrote on 2025-03-14, 11:57:

Hi all, […]
Show full quote

Hi all,

I have a sound problem I cannot seem to crack. With RR Indycar Racing II everything works, except that the game sound is only audible when the little dosbox window has focus, not when the game itself has focus. It doesn't matter if the game is run fullscreen or windowed.

Would anyone have suggestions for this dosbox newb?

Cheers

- RReady Rendition Verite wrapper is freakin' brilliant for Indycar Racing II by the way! Love it.

Could you zip up your logs and attach them in your reply? Also which version of Windows is this running on.

wowbaggr wrote on 2025-03-14, 11:57:

Hi all, […]
Show full quote

Hi all,

I have a sound problem I cannot seem to crack. With RR Indycar Racing II everything works, except that the game sound is only audible when the little dosbox window has focus, not when the game itself has focus. It doesn't matter if the game is run fullscreen or windowed.

Would anyone have suggestions for this dosbox newb?

Cheers

- RReady Rendition Verite wrapper is freakin' brilliant for Indycar Racing II by the way! Love it.

Also do you have any audio plugins or audio/video capture software of any sort running? Dosbox should have audio all the time.