Canadair wrote on 2025-01-15, 00:12:

I don' NEED anything, actually thank you. What is possible I would like
I have to report also severe fps drop with addon car sets, (for example your indy2020) but only at the beginning in the pit lane

At the pit lanes the issue is there. That's being looked at, it's most probably a texture loading issue. It's already on my list.

[EDIT] The replays also suffer from the same problem when all the cars are there in one scene.[/EDIT]

Integer Scaling for RReady:
https://youtu.be/ZDgl9zrlhg8

sharangad wrote on 2025-01-15, 00:20:

Canadair wrote on 2025-01-15, 00:12:

I don' NEED anything, actually thank you. What is possible I would like
I have to report also severe fps drop with addon car sets, (for example your indy2020) but only at the beginning in the pit lane

At the pit lanes the issue is there. That's being looked at, it's most probably a texture loading issue. It's already on my list.

[EDIT] The replays also suffer from the same problem when all the cars are there in one scene.[/EDIT]

Actually could be my pc: if I reduce the number of opponent in front and behind to 10 or less it is okei and keeps 60fps

Canadair wrote on 2025-01-15, 01:31:

sharangad wrote on 2025-01-15, 00:20:

Canadair wrote on 2025-01-15, 00:12:

I don' NEED anything, actually thank you. What is possible I would like
I have to report also severe fps drop with addon car sets, (for example your indy2020) but only at the beginning in the pit lane

At the pit lanes the issue is there. That's being looked at, it's most probably a texture loading issue. It's already on my list.

[EDIT] The replays also suffer from the same problem when all the cars are there in one scene.[/EDIT]

Actually could be my pc: if I reduce the number of opponent in front and behind to 10 or less it is okei and keeps 60fps

I don't think it's your pc. I think it's common to all pcs, but I may be wrong. Since my sample set size is pretty small.

What're the specs of your machine?

Hi Sharangad,
have you seen that the latest version of DOSBox-X can handle 4 GB of ram and beyond?
https://github.com/joncampbell123/dosbox-x/re … x-x-v2025.01.01
I hope it can be useful to you for your good work.
Thank you!

Makus wrote on 2025-01-15, 07:42:

Hi Sharangad, have you seen that the latest version of DOSBox-X can handle 4 GB of ram and beyond? https://github.com/joncampbel […]
Show full quote

Hi Sharangad,
have you seen that the latest version of DOSBox-X can handle 4 GB of ram and beyond?
https://github.com/joncampbell123/dosbox-x/re … x-x-v2025.01.01
I hope it can be useful to you for your good work.
Thank you!

Thanks for that! At the moment I'm using a 32 bit version of staging which can't handle so much ram, max 3gb. The wrapper is 32 bit only at the moment because the RRedline apps (Rendition on Windows) are 32 bit only. I'll be looking at a 64 bit build of dosbox, but not anytime soon.

***************************************************
RReady Alpha, January 17, 2025 Build #002 (Fully tested build)
*****************************************************
https://nirvtek.com/downloads/RReady.Alpha.20250114.002.7z
MD5: 48d1e0041a6c803bdffab34cea656d07
- Corrects lockup when resuming a race/season in ICR2.
- All OEM keys on keyboards are now handled correctly depending on locale, should work correctly for all keyboard language settings.
Identical to previous untested alpha.
(This should be live on the store.)
******************************************************

Upcoming update (Alpha hopefully today): Intege scaling and Moveable Window.

https://youtu.be/JUJlwvtavXk

RReady Alpha, January 20, 2025

https://nirvtek.com/downloads/RReady.Alpha.20 … ent2VideoFix.7z
MD5: a2a172df9b128577260b34ea9e55c757

- Integer scaling
- moveable window
- Descent II video should render better on weaker h/w. The game still doesn't work properly.

Does anyone have any experience with using dosbox with a logitech g25 wheel?

Im new to this - lured in to your wrapper to run ICR2?! ☺️

I've followed the set up as laid out by @GPLaps but when I hit launch I only get as far as the first DOS window opening - with a line saying memory size has been set to 63 as the nearest number and then it all just closes down and CTD.

I understand there could be many causes but are there some obvious checks I could make first?

I'll attach the . conf file as it is currently on my laptop in case that helps?

All the best.

How to move the window?

Attached my latest log. Working fine!

Greetings from Germany!

Grafix wrote on 2025-01-20, 18:18:

Im new to this - lured in to your wrapper to run ICR2?! ☺️ […]
Show full quote

Im new to this - lured in to your wrapper to run ICR2?! ☺️

I've followed the set up as laid out by @GPLaps but when I hit launch I only get as far as the first DOS window opening - with a line saying memory size has been set to 63 as the nearest number and then it all just closes down and CTD.

I understand there could be many causes but are there some obvious checks I could make first?

I'll attach the . conf file as it is currently on my laptop in case that helps?

All the best.

Try changing the commands [EDIT-spelling] in dosbox-rendition.conf under the autoexec section to this:

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D_DMA=1
5set SPEEDY3D_MEMSIZE=16
6INDYCAR

Report back what you see in the console.
[EDIT] Also make sure your IndyCar.Exe (and the rest of the subfolder live in c:\DOS\ICR2REND and not another subfolder.[/EDIT]

instead of this:

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D=C:\ICR2REND
5set SPEEDY3D_DMA=1
6set SPEEDY3D_MEMSIZE=16
7if exist INDYCAR.DMP del INDYCAR.DMP
8INDYCAR > INDYCAR.DMP
9

supererwin wrote on 2025-01-20, 19:46:

How to move the window?

Attached my latest log. Working fine!

Greetings from Germany!

You'll need the latest alpha from here:
Re: RReady (Rendition Verite wrapper) Test Build (Alpha 1)

From RLauncher, enable windowed mode and tick the "Moveable" checkbox near the top.
[EDIT]
You'll have to [ALT +Tab] out of the window and then drag the window by its title bar.

sharangad wrote on 2025-01-20, 23:04:

Try changing the commands [EDIT-spelling] in dosbox-rendition.conf under the autoexec section to this: […]
Show full quote

Grafix wrote on 2025-01-20, 18:18:

Im new to this - lured in to your wrapper to run ICR2?! ☺️ […]
Show full quote

Im new to this - lured in to your wrapper to run ICR2?! ☺️

I've followed the set up as laid out by @GPLaps but when I hit launch I only get as far as the first DOS window opening - with a line saying memory size has been set to 63 as the nearest number and then it all just closes down and CTD.

I understand there could be many causes but are there some obvious checks I could make first?

I'll attach the . conf file as it is currently on my laptop in case that helps?

All the best.

Try changing the commands [EDIT-spelling] in dosbox-rendition.conf under the autoexec section to this:

Copy code to clipboard

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D_DMA=1
5set SPEEDY3D_MEMSIZE=16
6INDYCAR

Report back what you see in the console.
[EDIT] Also make sure your IndyCar.Exe (and the rest of the subfolder live in c:\DOS\ICR2REND and not another subfolder.[/EDIT]

instead of this:

Copy code to clipboard

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D=C:\ICR2REND
5set SPEEDY3D_DMA=1
6set SPEEDY3D_MEMSIZE=16
7if exist INDYCAR.DMP del INDYCAR.DMP
8INDYCAR > INDYCAR.DMP
9

Firstly - Thank you for the help!

Unfortunately I seem to get exactly the same sequence and CTD - It doesn't appear to get as far as a console? (I tried to attach a quick video of the sequence but the site here won't allow it to upload). I did double check that the folder structure and contents are all correct.

It's basically a flash of a DOS window, a flash of the DOSBOX logo Dos window over it and then both windows disappear and that's it.

All the best.

Grafix wrote on 2025-01-21, 08:15:

Firstly - Thank you for the help! […]
Show full quote

sharangad wrote on 2025-01-20, 23:04:

Try changing the commands [EDIT-spelling] in dosbox-rendition.conf under the autoexec section to this: […]
Show full quote

Grafix wrote on 2025-01-20, 18:18:

Im new to this - lured in to your wrapper to run ICR2?! ☺️ […]
Show full quote

Im new to this - lured in to your wrapper to run ICR2?! ☺️

I've followed the set up as laid out by @GPLaps but when I hit launch I only get as far as the first DOS window opening - with a line saying memory size has been set to 63 as the nearest number and then it all just closes down and CTD.

I understand there could be many causes but are there some obvious checks I could make first?

I'll attach the . conf file as it is currently on my laptop in case that helps?

All the best.

Try changing the commands [EDIT-spelling] in dosbox-rendition.conf under the autoexec section to this:

Copy code to clipboard

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D_DMA=1
5set SPEEDY3D_MEMSIZE=16
6INDYCAR

Report back what you see in the console.
[EDIT] Also make sure your IndyCar.Exe (and the rest of the subfolder live in c:\DOS\ICR2REND and not another subfolder.[/EDIT]

instead of this:

Copy code to clipboard

1mount c c:\DOS
2c:
3cd ICR2REND
4set SPEEDY3D=C:\ICR2REND
5set SPEEDY3D_DMA=1
6set SPEEDY3D_MEMSIZE=16
7if exist INDYCAR.DMP del INDYCAR.DMP
8INDYCAR > INDYCAR.DMP
9

Firstly - Thank you for the help!

Unfortunately I seem to get exactly the same sequence and CTD - It doesn't appear to get as far as a console? (I tried to attach a quick video of the sequence but the site here won't allow it to upload). I did double check that the folder structure and contents are all correct.

It's basically a flash of a DOS window, a flash of the DOSBOX logo Dos window over it and then both windows disappear and that's it.

All the best.

Try installing the Visual C++ Runtime from here:
(for 64 bit systems)
https://aka.ms/vs/17/release/vc_redist.x64.exe
and (for 32 bit systems)
https://aka.ms/vs/17/release/vc_redist.x86.exe

This should fix it, I think.

Hi again!

Soo - that Visual C++ runtime didn't fix it unfortunately - but - just on a whim - I tried launching with the staging dosbox version instead - with the same autoexec lines added - and it worked!?

I don't understand why that worked - but it does appear to be running fine. Unless I am missing some functionality by not running the std dosbox.exe?

Now - I just need to understand if I can map/use an xbox type controller with ICR2 as that is now my stumbling block - but it is running fine using the keyboard.

All the best.

Grafix wrote on 2025-01-21, 12:42:

Hi again! […]
Show full quote

Hi again!

Soo - that Visual C++ runtime didn't fix it unfortunately - but - just on a whim - I tried launching with the staging dosbox version instead - with the same autoexec lines added - and it worked!?

I don't understand why that worked - but it does appear to be running fine. Unless I am missing some functionality by not running the std dosbox.exe?

Now - I just need to understand if I can map/use an xbox type controller with ICR2 as that is now my stumbling block - but it is running fine using the keyboard.

All the best.

How're you running it? The preferred method is to run from RLauncher.

You might be missing a dll. Is this the alpha release or the store based version? [edit2] I have on a few occasions accidentally forgotten to zip up the odd dll or two in the alpha releases. [/EDIT2]

To map a controller, just hit [ctrl +F1] while in dosbox without the last IndyCar command in the config and click on the axes and controller buttons and then remove existing bindings and click bind. Then move your sticks/wheels pedals or press your buttons.

For the dosbox problem, try updating the app from the store and then run through rlauncher. It should just work.

[edit] you might need to enable the following options in dosbox-rendition.conf and dosbox-staging-rendition.conf:

joysticktype=auto
timed=false
autofire=false
swap34=true
buttonwrap=false

More info here:
https://www.icr2.net/forum/showthread.php?tid=1383&pid=10741

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.

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!