vs and msys2 are two different compiling applications.
you use either one or the other not both.

i was thinking if it doesn't work in vs2022 then try vs2019 next 17, etc.
2005 is probably too old

robertmo3 wrote on 2025-07-16, 10:56:

i was thinking if it doesn't work in vs2022 then try vs2019 next 17, etc.
2005 is probably too old

When you try to build seabios it actually says some feature is deprecated after VS2005. I'll give that a shot later.

tested today
Rebel Moon
works perfectly.

probably dosbox usiues
game crashed once
music in game often turnoffs by itself , never happened on my retro pc.

RaVeN-05 wrote on 2025-07-16, 18:25:

tested today Rebel Moon works perfectly. […]
Show full quote

tested today
Rebel Moon
works perfectly.

probably dosbox usiues
game crashed once
music in game often turnoffs by itself , never happened on my retro pc.

Thanks Raven-05!

I've never tested the game beyond the first two levels. Once we get CGL going it'll be interesting to see if that still happens. I did once get a "division by zero" crash.

RaVeN-05 wrote on 2025-07-16, 18:25:

tested today Rebel Moon works perfectly. […]
Show full quote

tested today
Rebel Moon
works perfectly.

probably dosbox usiues
game crashed once
music in game often turnoffs by itself , never happened on my retro pc.

Does it use CD-Audio?

not audio cd, audio tracks stored at cd drive in music folder as wav files.

Edit

P.S. Best way to play rebel moon in wasd+mouse is to use novert
https://www.doomworld.com/idgames/utils/misc/novert

which will disable walking forward / backward by mouse movement up/down.

also reshade not compatible to dosclient.exe it crashes it , letting know , the lowest possible priority

RaVeN-05 wrote on 2025-07-17, 19:55:

also reshade not compatible to dosclient.exe it crashes it , letting know , the lowest possible priority

I think you mentioned this before, about reshade not working. Vertex data is mostly passed on to the shaders in rendition internal formats, the way it's passed to the wrapper, for two reasons :

1) converting each vertex to floar manually one vertex at a time is slow and is best done in parallel on the gpu,

2) for performance, the vertex data is passed as a massive blob to opengl/gpu. The floating point conversion would need a duplicate blob involving slow dynamic memory allocation.

So passing native data saves memory and improves performance.

The quake span shader (qspan) uses acompletely different format. Some shaders have a geometry shader stage and others do not. I could fork reshade to support all this or migrate some reshade functionality directly into rready.

One more Rendition Ready track: Toronto 2003 (not sure how I missed this in my earlier Toronto '95/'96  video):
https://youtu.be/fKmSAHWaVM0

and a few F1'96 (RRedline) demos:
https://youtu.be/89_0JEYV2lU

There's a strange bug here. A user over at icr2.net says [ALT+B] isn't toggling auto-brake. I tested this on real hardware and it works perfectly everytime.

I debugged this and Dosbox-Rendition seems to be getting the command but the game seems to be ignoring it OR Dosbox is swallowing it up.

Is [ALT+B] a super duper Dosbox 'do-nothing' keystroke? It doesn't look like it is.

left alt is certainly not working correctly in rready, in tomb raider if you hit left alt while running lara stops running.

robertmo3 wrote on Yesterday, 05:06:

left alt is certainly not working correctly in rready, in tomb raider if you hit left alt while running lara stops running.

OK. So there's definitely something wrong with Dosbox-Rendition with left alt.

RobertMo3, can see if Tomb Raider works with this? It appears to work for me.

I think I've fixed all the ALT issues, but [ALT+B] still doesn't work in ICR2. ALTW, ALTM, ALTX and ALTR work perfectly. ALT B is missing in action.

https://nirvtek.com/downloads/RReady.Alpha.20 … 0718.001.Alt.7z
MD5: 49198698be674f03cf4aac097218ba86

The previous build had unnecessary logging.
https://nirvtek.com/downloads/RReady.Alpha.20 … 0718.002.Alt.7z
MD5: 75e00f459fa53022de52362aff6e38db

This build also fixes a bug in ICR2 for slower dual core systems when using:
threadsafe=true
highperformance=false
picdma=false

Unfortunately for me my dual core laptop died a few weeks ago and my i7 2600 with HD2000 graphics also joined it in the microchip park in the sky. So my testing options at the moment are limited.
@Raven-05, if you've still got your core2 laptop it would be useful if you could give it a whirl.

Ok, [ALT+B] does work in ICR2, holding it down toggle it. I think on physical hardware even a slight keypress registers for a bit longer than on modern Windows. The evidence for that is that holding [ALT+B] down for a long while cycles auto-brake very quickly, whereas on physical hardware there's a delay. It doesn't switch 5-10 times a second.

Does dosbox have a key duration/repeat setting?

dosbox-x has:
MODE CON RATE=1 DELAY=4
RATE: Sets the repeat rate (characters per second). Valid values are 1-32, with higher numbers being faster.
DELAY: Sets the delay before repeating (in fractions of a second). Valid values are 1-4, representing 0.25, 0.50, 0.75, and 1 second respectively

Re: [resolved] cannot set keyboard delay rate

robertmo3 wrote on Yesterday, 19:19:

dosbox-x has: MODE CON RATE=1 DELAY=4 RATE: Sets the repeat rate (characters per second). Valid values are 1-32, with higher num […]
Show full quote

dosbox-x has:
MODE CON RATE=1 DELAY=4
RATE: Sets the repeat rate (characters per second). Valid values are 1-32, with higher numbers being faster.
DELAY: Sets the delay before repeating (in fractions of a second). Valid values are 1-4, representing 0.25, 0.50, 0.75, and 1 second respectively

Thanks!

It looks like [ALT+B] gets passed to every single running process before Dosbox-Rendition gets it including background processes. One of them seems to be taking a while to deal with it.