Thank you @BEEN_Nath_58! With this patched AYAPI.DLL the game (DD1, not 2) now works great using dgVoodoo on Windows 10 (it crashed before). It still requires some sort of exception handling, as the executable contains privileged instructions (I noped that instructions, instead).

davidmorom wrote on 2025-05-02, 07:49:

Thank you @BEEN_Nath_58! With this patched AYAPI.DLL the game (DD1, not 2) now works great using dgVoodoo on Windows 10 (it crashed before). It still requires some sort of exception handling, as the executable contains privileged instructions (I noped that instructions, instead).

DD1 yes. I have been calling it DD2 since yesterday for some reason.

Yes exception handling is necessary since it has CLI instructions that crashes the game

Reporting from cracyc, the version Re: S3d-to-software wrapper only works for them
The latest one on your site doesn't. Testing on Windows 11

Windows 11 with AMD graphics. It also only works with dxwnd and some compatibility options.

The Destruction Derby wrapper is for graphics only. If the game doesn't support your OS you need another compatibility layer.

vvbee wrote on 2025-05-10, 03:53:

The Destruction Derby wrapper is for graphics only. If the game doesn't support your OS you need another compatibility layer.

The game supports WIn11.

It runs fine on my Win11 with exception handling only, but doesn't on crazyc s computer. I am on NVIDIA, they are on AMD, if that makes a difference

Start with a supported 1990s system to eliminate other factors. If you're adventurous go with Windows 11 but I can't offer any support.

I now can successfully run DDerby1 in win10 with fixed exes, fixed ayapi, latest s3d2sw wrapper and latest dgvoodoo2.
However what do you mean with "exception handling"? My game is prone to random crashes to desktop here and there.

vvbee wrote on 2025-01-13, 09:17:

Thanks for the testing. The readme goes into some more detail, but yeah, you need a non-NT Windows for Destruction Derby to work […]
Show full quote

Thanks for the testing. The readme goes into some more detail, but yeah, you need a non-NT Windows for Destruction Derby to work. I'm on Linux and only have modern Windows in virtual machines so no idea how well it works there. Doesn't seem work on Linux in Wine , but the wrapper in general does.

The wrapper uses the same video mode as the game, so 16 bits. Strange colors means pixels are being rendered with the wrong bit masks. They seem to vary from one video card to another, although the wrapper makes an attempt to figure out the correct one on launch. Maybe the auto detection is failing and the default isn't good for such and such card.

The S3d SDK looks to be using DirectX 1, which is probably about what the games are using as well. I'm not sure how easy that is to translate into hardware acceleration. Maybe you can do offscreen rendering into the legact DirectDraw frame buffer, no idea, no experience in this. It seems likely you'd have to wrap DirectDraw itself as well.

Here's another alpha for Destruction Derby with performance and visual improvements, though a few things don't render properly still. Maybe one of the changes happens to fix the color modes as well. It's again tailored for DD, so other S3d games will likely have more trouble than before. There's an optional debug DLL (rename it to s3dtkw.dll) that outputs runtime info, so run the game with "game > output.txt" to get the log. Basically any game where the wrapper fails to hook DirectDraw (i.e. because the game doesn't use it) isn't likely to work as far as I know.

Great work on MSI wrapper for DD2, works as 60 fps and 1680x1050 (native to my mon res) under Windows 10

could be even much cooler if you also able to add ForceFilter=0 (1) into settings so i can force texture filtering as i saw on your screenshot and it looks neat.

also i tested with second MSI exclusive game
Monster_Trucks(ThunderTruckRally)_Mystique_OEMDEMO
and its semiworking.

mtrdemo.exe couldn't run (DirectDraw Init FAILED) not necessary as it just menu which choose tr1.exe or tr2.exe (error seems a game related)

tr1.exe works perfect.

tr2.exe couldn't run (Failed to set the DirectDraw video mode) after few seconds of waiting. (wrapper related, unimplemented i think)

No plans to support texture filtering or other MSI titles.

thought about sharing source with sharangad so he could try adding hardware acceleration and dos titles?

I think it's better you pay him to do the work you need done.

you mean its better if he doesn't use your code and starts from beginning himself his own another wrapper?
(or more probable the allusion to controversial financing method)
maybe some crowdfunding? or sponsors?
it's not i need that - i probably will never use it.
...just trying to help with ideas...
...sorry if stupid ideas...

I think it's you who's saying he needs to start from the beginning in order to deliver a freebie you don't need. I don't enter this equation and I recommend you look for ways to motivate him.

it is you who suggests a freebie 😀
i am fine with freebie with watermark 😀
of course i respect your decision 😀 as i understand your motivation
just had to ask to be sure 😀 don't blame me for that 😀
what i still wonder though is both codes are closed so i wonder why charging $for the watermark free version is something you don't like.
it would be a problem if you would like your share in profits - then there is problem how to share the $, but if you are fine with it being free so i guess that is not a problem.
what's wrong with few$ for removing the watermark
glidos had way worse unplayable watermark and nobody had nothing against it.
well i just think above idea is a good compromise. 😀
of course freebie would be nice too, but the reality is as it is, i cannot change that 😀

Why does the tone of the conversation seem a little off?

No plans to charge for the wrappers nor to share their code. Keep in mind the MSI wrapper has its own thread.