supererwin wrote on 2025-01-21, 19:21:

Ah! Now I got it moving. Please find my logs attached if you need them. I moved the window a little - don't know, if that's part of the info in the logs...

Anyway, here they are!

Thanks supererwin, and you're right, they're not in the logs.

Grafix wrote on 2025-01-21, 16:56:

Hi! […]
Show full quote

Hi!

I am running it from the launcher - and that is where I launch the staging version of dosbox too. Only the staging version works for me for some reason. I have uninstalled everything (including the .conf files in appdata) and started afresh but I get back to the same position. I can run it in staging dosbox (from the rendition launcher) but not the normal version. However it is running so I guess I'm not missing out on any functionality?

However - I have tried Ctrl-1 and remapping my controller in dosbox via the mapper about twenty different ways now (and with/without the joystick lines changed in the .conf file as you outlined). In dosbox it sees, recognises and and loads my xbox one controller and lets me remap the bindings after clearing all of them first - but in-game it doesn't recognise any input at all. I've tried 2axis, 4axis, 4axis2, auto, timed true, timed false, swap34 etc etc - but no luck!

It is driving me mad now (pun intended - as the one thing I can't do is drive the game!!)

I tried a second different controller with the same result - I can remap in dosbox no problem - but the game ignores it. No matter what joystick on the controllers I use or what I remap it to in dosbox the game can't pick it up in the calibration screen.

Any further ideas would be amazing!

All the best.

Are you using an alpha release? If you are, you could try an earlier release that should have all the earlier DLLs.

Also, run dosbox and when it crashes run Event Viewer, press [Start]->Eventvwr and navigate to "Windows Logs\Application" in the tree and see if there are any red exclamation mark entries there. Open them and see what the complaint is. I'll produce an updated Alpha release.

@Grafix

Could you try this build to see if vanilla Dosbox-Rendition runs?:

https://nirvtek.com/downloads/RReady.Alpha.20250122.007.7z
MD5: 481ef62c2c810ec2c405bc5169a847a0
- Alpha release should once again package all zips and DLL
- Both builds of dosbox should static link to their libraries
- Dosbox-Staging-Rendition now produces its own log file dosbox-staging-rendition.

Grafix wrote on 2025-01-21, 16:56:

Hi! […]
Show full quote

Hi!

I am running it from the launcher - and that is where I launch the staging version of dosbox too. Only the staging version works for me for some reason. I have uninstalled everything (including the .conf files in appdata) and started afresh but I get back to the same position. I can run it in staging dosbox (from the rendition launcher) but not the normal version. However it is running so I guess I'm not missing out on any functionality?

However - I have tried Ctrl-1 and remapping my controller in dosbox via the mapper about twenty different ways now (and with/without the joystick lines changed in the .conf file as you outlined). In dosbox it sees, recognises and and loads my xbox one controller and lets me remap the bindings after clearing all of them first - but in-game it doesn't recognise any input at all. I've tried 2axis, 4axis, 4axis2, auto, timed true, timed false, swap34 etc etc - but no luck!

It is driving me mad now (pun intended - as the one thing I can't do is drive the game!!)

I tried a second different controller with the same result - I can remap in dosbox no problem - but the game ignores it. No matter what joystick on the controllers I use or what I remap it to in dosbox the game can't pick it up in the calibration screen.

Any further ideas would be amazing!

All the best.

If you're using Windows Defender could you check its logs to see if any files have been zapped somehow? This can sometimes be a problem, Defender's a bit overzealous.

[EDIT] Also could you click "Zip Log Files" in Rlauncher and share or attach the zip files and the two conf files (dosbox-rendition.conf and dosbox-staging-rendition.conf) here as well? Thanks.

[EDIT2] You might want to email all these files and the specs to support@nirvtek.com, if you're worried about sharing your data publicly. There's no user identifiable data there other than perhaps your system specs.

[EDIT3] Your system specs would be useful as well.

sharangad wrote on 2025-01-21, 23:57:

@Grafix […]
Show full quote

@Grafix

Could you try this build to see if vanilla Dosbox-Rendition runs?:

https://nirvtek.com/downloads/RReady.Alpha.20250122.007.7z
MD5: 481ef62c2c810ec2c405bc5169a847a0
- Alpha release should once again package all zips and DLL
- Both builds of dosbox should static link to their libraries
- Dosbox-Staging-Rendition now produces its own log file dosbox-staging-rendition.

Thank you! I'll run this - and check the event viewer as you requested ☺️.

(I'll also check Defender and provide the log files)

The default key bindings for dosbox-staging-rendition is broken. It doesn't generate events for axes or buttons under some conditions. I'll fix it tomorow.

sharangad wrote on 2025-01-21, 23:57:

@Grafix […]
Show full quote

@Grafix

Could you try this build to see if vanilla Dosbox-Rendition runs?:

https://nirvtek.com/downloads/RReady.Alpha.20250122.007.7z
MD5: 481ef62c2c810ec2c405bc5169a847a0
- Alpha release should once again package all zips and DLL
- Both builds of dosbox should static link to their libraries
- Dosbox-Staging-Rendition now produces its own log file dosbox-staging-rendition.

I realise this might seem a daft question but how do I correctly install this update to my Microsoft Store bought app please?

I tried unzipping it and running the launcher but that just threw up 'cannot copy xxx to yyy' errors.

Sorry for the naive question.

All the best.

sharangad wrote on 2025-01-22, 12:54:

The default key bindings for dosbox-staging-rendition is broken. It doesn't generate events for axes or buttons under some conditions. I'll fix it tomorow.

Just to check - is this related to my not managing to map my controller in the staging variant of dosbox - or unrelated to that?

Grafix wrote on 2025-01-22, 18:42:

sharangad wrote on 2025-01-22, 12:54:

The default key bindings for dosbox-staging-rendition is broken. It doesn't generate events for axes or buttons under some conditions. I'll fix it tomorow.

Just to check - is this related to my not managing to map my controller in the staging variant of dosbox - or unrelated to that?

Yes.

Grafix wrote on 2025-01-22, 18:25:

I realise this might seem a daft question but how do I correctly install this update to my Microsoft Store bought app please? […]
Show full quote

sharangad wrote on 2025-01-21, 23:57:

@Grafix […]
Show full quote

@Grafix

Could you try this build to see if vanilla Dosbox-Rendition runs?:

https://nirvtek.com/downloads/RReady.Alpha.20250122.007.7z
MD5: 481ef62c2c810ec2c405bc5169a847a0
- Alpha release should once again package all zips and DLL
- Both builds of dosbox should static link to their libraries
- Dosbox-Staging-Rendition now produces its own log file dosbox-staging-rendition.

I realise this might seem a daft question but how do I correctly install this update to my Microsoft Store bought app please?

I tried unzipping it and running the launcher but that just threw up 'cannot copy xxx to yyy' errors.

Sorry for the naive question.

All the best.

This is a watermarked alpha release. Unzip the file somewhere and run rlauncher from the unzipped folder. You may get a malware warning with dosclient, you may have to allow that.

Run rlauncher and launch dosbox or dosbox-staging-rendition from there. See whether they start up.

To update the store based installation, run the RLauncher. Exe shortcut from the desktop and run dosbox and staging from there that should patch the dos execution folder. But you may have to update rlauncher. Exe from the Microsoft Store app first. Just run the store and goto the downloads tab bottom left icon on the left hand bar and press update.

Grafix wrote on 2025-01-22, 18:42:

sharangad wrote on 2025-01-22, 12:54:

The default key bindings for dosbox-staging-rendition is broken. It doesn't generate events for axes or buttons under some conditions. I'll fix it tomorow.

Just to check - is this related to my not managing to map my controller in the staging variant of dosbox - or unrelated to that?

Don't bother with the alpha. With a legacy cpu or an integrated gpu:

Try modifying these three lines in %localappdata%\Dosbox\dosbox-rendition.Conf and %localappdata%\Dosbox\dosbox-staging-rendition.conf

1)Set

1[rendition]
2threadsafe=true
3highperformance=false
4picdma=false

These settings should already be there, but you'll have to reverse them.

2) Disable Rendition Antialiasing and line rendering.

3) lower your upscaling resolution to default or something lower than the your panel's native res. You will have to experiment to find something that works.

You'll need to do all three of these things.

*******************************************************
RReady Alpha, January 23, 2025
*******************************************************
https://nirvtek.com/downloads/RReady.Alpha.20250123.007.7z
MD5: caaf34fc942b6848427112024a747e9a

- Both versions of dosbox allow selection of joystick devices. This is done with:
[joystick]
usejoystickids=true
joystickids= id1|[,id2]

id1 and id2 are numbers from 0 to the number of joysticks -1. The id2 and the preceding , can be omitted to use just a single joystick. This defaults to 0,1 when usejoystickids=false. The logfile %localappdata%\dosbox-staging-rendition lists all available devices along with joystick numbers.

On Windows 11 for some reason SDL2 (32 bit) seems to go bonkers and with dosbox-staging-rendition (which is currently a 32 bit app) returns garbage axis and button readings on Win11. The 64 bit version, which isn't part of RReady doesn't seem to be affected.

Dosbox-staging-Rendition has all the joystick changes from Dosbox-staging 0.82 incorporated, but my Logitech gamepad doesn't work in Dosbox-staging-Rendition. It would be nice if someone with a wheel could test this out and see if nothing's broken.

Grafix wrote on 2025-01-22, 18:42:

sharangad wrote on 2025-01-22, 12:54:

The default key bindings for dosbox-staging-rendition is broken. It doesn't generate events for axes or buttons under some conditions. I'll fix it tomorow.

Just to check - is this related to my not managing to map my controller in the staging variant of dosbox - or unrelated to that?

I f you have an integrated gpu

Dosbox-rendition.conf
In your [autoexec] section, set
Set SPEEDY3D_DMA=0

And try increasing your graphics memory VRAM in your machine's bios. Try setting it as high as it can go.

And no it's not related to your controller.

******************************************
RReady Alpha,January 24, 2024 (untested alpha build)
******************************************
https://nirvtek.com/downloads/RReady.Alpha.20250124.001.7z
MD5: 242a8a5a255d864026ae25a64bcd9ce3

- Joysticks should be fully functional in dosbox-staging-rendition. Dosclient being in focus causes Dosbox's SDL2 libraries to ignore joystick input.
- Screensaver and monitor idle is disabled while DOS/Speedy3D apps are running.

Hello again!

Success! 🤩

The latest build let me run it - and using 4axis in the joystick section of the conf file also auto-recognised my wheel and pedal set even... I then had a very happy time racing at Laguna Seca. Ahh the memories came flooding back.

Thank you so much for sticking with this and your specific help to me too! Chapeau!

All the best.

Oh - this also works perfectly now with my Xbox One controller (wired connection) - via the Dosbox Crtl-F1 mapper setting the bindings. It works beautifully and is such a blast to play - I can't thank you enough....

sharangad wrote on 2025-01-24, 11:17:

****************************************** RReady Alpha,January 24, 2024 (untested alpha build) ******************************** […]
Show full quote

******************************************
RReady Alpha,January 24, 2024 (untested alpha build)
******************************************
https://nirvtek.com/downloads/RReady.Alpha.20250124.001.7z
MD5: 242a8a5a255d864026ae25a64bcd9ce3

- Joysticks should be fully functional in dosbox-staging-rendition. Dosclient being in focus causes Dosbox's SDL2 libraries to ignore joystick input.
- Screensaver and monitor idle is disabled while DOS/Speedy3D apps are running.

Will this release be available via the microsoft store?

I'm sure this is a false alarm but my system has gone back to ending the dosbox process and it is throwing up this virus warning - is it just Defender making a mistake? (image attached).

Trojan Win32/Wacatac.B!ml

All the best.

yes this is false alarm, add to exclusions it please