robertmo3 wrote on 2025-01-30, 16:33:

sharangad wrote on 2025-01-29, 10:16:

At least that's what B* told me when I asked for permission.

you did what?? are you nuts?? i thought i have already explained you that in the past...

He asked for permission (now Nintendo and Take2 is probably after him)

robertmo3 wrote on 2025-01-30, 16:33:

sharangad wrote on 2025-01-29, 10:16:

At least that's what B* told me when I asked for permission.

you did what?? are you nuts?? i thought i have already explained you that in the past...

This was before you explained all that.

Just to say Sharangad - playing ICR2 now on your wrapper is ridiculously good. Thank you for all you've done to enable this and specifically for the help you've given me to nail down the controller input and fidelity!

Salut!

Grafix wrote on 2025-01-31, 18:43:

Just to say Sharangad - playing ICR2 now on your wrapper is ridiculously good. Thank you for all you've done to enable this and specifically for the help you've given me to nail down the controller input and fidelity!

Salut!

It was fun dude getting the wrapper going and I'm glad you're making good use of it! It's really nice to see it being put to use and thank you very much for the kind words.

[EDIT] If you really wanted to you could write a short review on the store page!

Thanks to whoever left that amazing review (@Grafix?) up on the store! It shows up in the developer console, but the rating I had previously and the review seem to have disappeared from the store page.

I should raise a ticket with Microsoft.

[EDIT] Thanks again![/EDIT]

***************************************************
RReady Alpha February 3, 2025 (Untested alpha release)
***************************************************
https://nirvtek.com/downloads/RReady.Alpha.20250203.007.7z
MD5: 21b44ad6ea5ed70f99a0bc416d72d651
- Dosbox-Rendition now supports up to 512 MB of RAM. This is forced to 512 MB when renditionEnabled=true in the [rendition] section of dosbox-renditoin.conf. Staging already supported 512 MB but even that now ups the limit when Rendition support is enabled. This currently has no effect on games and is designed to support possible future update to ICR2.
- ICR2 auto-patched. Unpatched versions of the game can now be automatically patched non-destructively (in-memory) by adding icr2unlock=true to dosbox-rendition.conf or dosbox-staging-rendition.conf. This is disabled by default and should not be used at this point.
- Joystick 2 deadzone controls:
[joystick]
deadzone2 = 0 ( This default to 0%)
circularinput2 = false

This release is going into testing and should, barring failures be live on the store before the end of the week.

sharangad wrote on 2025-02-03, 05:45:

Thanks to whoever left that amazing review (@Grafix?) up on the store! It shows up in the developer console, but the rating I had previously and the review seem to have disappeared from the store page.

I should raise a ticket with Microsoft.

[EDIT] Thanks again![/EDIT]

That wasn't me actually - but my (positive!) review is now on the store and live. ☺️ Still loving ICR2 with the wrapper!

Thanks for your review dude! Do you need the revised joystick deadzone adjustment pushed out to the store right away or can you hang on while I try to patch custom track support in?

My toolset for handling multi-gig disassembly files is ready and I've isolated some stuff related to icr2 memory handling already.

I probably should push out the update, it's just that it's relatively minor.

BEEN_Nath_58 wrote on 2025-01-29, 06:02:

Why is there an asterisk in game names in the Store?
Did you mean HD 4000 instead of HD400 in the store requirements?

That wasn't me. Microsoft edited what I entered and now the hardware requirements page can't be altered for some reason.

I've submitted a build for certification. I'll post an updated Alpha tomorrow.

DirectDraw Exclusive seems like a massive issue in DxWnd, it behaves uncertainly in many games. To improve the playability of games like POD or MechWarrior 2 it is possible that DxWnd defaults to not using exclusivity.

I wonder what that means for Interstate 76.

BEEN_Nath_58 wrote on 2025-02-05, 12:59:

DirectDraw Exclusive seems like a massive issue in DxWnd, it behaves uncertainly in many games. To improve the playability of games like POD or MechWarrior 2 it is possible that DxWnd defaults to not using exclusivity.

I wonder what that means for Interstate 76.

Interstate '76 works with dxwnd.
[EDIT]
I suppose you could make it an option?

RReady Alpha, February 05, 2025 (Fully tested Alpha Release)
https://nirvtek.com/downloads/RReady.Alpha.20250205.001.7z
MD5: db79e60cf9c50865450a60c14e663bec
- Setting ([Rendition]) icr2unlock=true now patches the cart.exe or indycar.exe destructively. This feature is disabled by default. The in-memory patching used previously could have had an impact on general CPU performance while in the game.
- Dosbox-Rendition memory ([dosbox] section memsize) is no longer forced to 512 MB for Rendition apps. This is true for Dosbox-Staging-Rendition as well.
- Adds deadzone adjustment for second stick:

1(for the second stick)
2[joystick]
3deadzone2 = 0 
4circularinput2 = false

This release should be live on the store (1.0.39) sometime within the next 3 days.

sharangad wrote on 2025-02-05, 02:33:

Thanks for your review dude! Do you need the revised joystick deadzone adjustment pushed out to the store right away or can you hang on while I try to patch custom track support in?

My toolset for handling multi-gig disassembly files is ready and I've isolated some stuff related to icr2 memory handling already.

I probably should push out the update, it's just that it's relatively minor.

No don't rush it please! Just release it as and when you are happy please!

Cheers!

Grafix wrote on 2025-02-05, 19:58:

sharangad wrote on 2025-02-05, 02:33:

Thanks for your review dude! Do you need the revised joystick deadzone adjustment pushed out to the store right away or can you hang on while I try to patch custom track support in?

My toolset for handling multi-gig disassembly files is ready and I've isolated some stuff related to icr2 memory handling already.

I probably should push out the update, it's just that it's relatively minor.

No don't rush it please! Just release it as and when you are happy please!

Cheers!

Too late, it should be live now! Every test passed except for "Team Apache" which appears to be a Win 11 24H2 problem.

The state of custom track with RReady (no progress yet):
ICR2's Pavel's Australia 2.0 is here with Cars95.
https://youtu.be/CBzcSvux0-Q

Simpler tracks work with the stock carset or something compatible with it. Riverside 82 works when textures are shrunk and a stock carset is used. The high detail tracks don't work.

[EDIT] Won't work[/EDIT]

A test for as many people as possible with Intel HD graphics (UHD6XX) or other older laptop GPUs (GT330M). A test on HD4000 would also be useful:

Backup your indycar.exe/cart.exe and all the *.DAT files in the folder (NB This is very important. Indycar.exe/Cart.exe will be modified)
https://nirvtek.com/downloads/RReady.A ... .UHD6XX.7z
MD5: 4052bce25da39c1b1e9e6e48b55df924

You'll need the following settings in Dosbox-rendition.conf (4 things to change):

[rendition]
threadsafe=false
highperformance=true
picdma=true
icr2unlock=true

In Rendition settings disable "Rendition AA" and "Line Rendering" (These should always be disabled for ICR2 with RReady). Rendition AA can now be disabled for everything and not just ICR2, RReady's Rendition edge AA didn't work particularly well. It's on my list of eternal "things to fix."


Run the game and select the 1982cart carset. Restart the game and run the intro/demo and a lap or two around any track with the 1982 cars. In the menus test rapid keypresses like [DOWN ARROW] rapidly to see if it locks up.

Thanks!

BEEN_Nath_58 wrote on 2025-02-05, 12:59:

DirectDraw Exclusive seems like a massive issue in DxWnd, it behaves uncertainly in many games. To improve the playability of games like POD or MechWarrior 2 it is possible that DxWnd defaults to not using exclusivity.

I wonder what that means for Interstate 76.

SODA Offroad doesn't crash anymore after the first 4 runs of the demo. It just keeps on running. So Microsoft do fix things. This is true on Win11 as well as Win10. Maybe they'll fix Team Apache as well at some point.

sharangad wrote on 2025-02-09, 02:07:

BEEN_Nath_58 wrote on 2025-02-05, 12:59:

DirectDraw Exclusive seems like a massive issue in DxWnd, it behaves uncertainly in many games. To improve the playability of games like POD or MechWarrior 2 it is possible that DxWnd defaults to not using exclusivity.

I wonder what that means for Interstate 76.

SODA Offroad doesn't crash anymore after the first 4 runs of the demo. It just keeps on running. So Microsoft do fix things. This is true on Win11 as well as Win10. Maybe they'll fix Team Apache as well at some point.

Didn't know this was an issue. Which Win11 had this issue?

BEEN_Nath_58 wrote on 2025-02-09, 05:45:

sharangad wrote on 2025-02-09, 02:07:

BEEN_Nath_58 wrote on 2025-02-05, 12:59:

DirectDraw Exclusive seems like a massive issue in DxWnd, it behaves uncertainly in many games. To improve the playability of games like POD or MechWarrior 2 it is possible that DxWnd defaults to not using exclusivity.

I wonder what that means for Interstate 76.

SODA Offroad doesn't crash anymore after the first 4 runs of the demo. It just keeps on running. So Microsoft do fix things. This is true on Win11 as well as Win10. Maybe they'll fix Team Apache as well at some point.

Didn't know this was an issue. Which Win11 had this issue?

If you left the demo running, it would crash after the 4th demo, even on Win 10 with both nvidia and Intel HD.

Actual gameplay worked fine. Replays also had random instability. I think you found that bug.

Largey's upcoming text file 'diffing' feature is proving useful for getting ICR2 to use 512 MB of RAM (ICR2 custom track support doesn't work yet. It will be a while yet before that works):

https://youtu.be/8QUgBUbmJwI