supererwin wrote on 2025-01-10, 11:24:

Hi! […]
Show full quote

sharangad wrote on 2025-01-10, 02:57:

What's your screen resolution and how much vram have you got?

Hi!

Yes, I am testing with ICR2, got attention due to the awesome video of GPLaps. Always enjoying his content.

Here's my setup:

AMD Ryzen 5 5500 3,6 GHz
32 GB RAM
Windows 10 Pro 22H2
AMD Radeon RX 7900 XT
Fanatec Podium Wheel Base DD2
Fanatec Clubsport Steering Wheel F1 2019
Fanatec CSL Elite Pedals

I ran the program again in such a way that it flickers and does not show any picture but a white window in order to create the logfiles. The setup of your software can be seen in the screenshot attached. I hope, this helps.

BTW another question: I cannot seem to use the key mappings within ICR2. I can't locate the dosbox-mapper file after saving plus: I can use the mapped buttons on my wheel for shifting in the control config menu, but in game, hese buttons are just out of function. Any idea? This only happens in "your" ICR2. If I use my common ICR2 without Rendition, it works just fine...

Feel free to use me as beta tester. I am willing to support your work the best way I can (although time is a limiting factor here...).

All the best,
supererwin

Hi

Can you try this build and get me the logs, even if it works, I need the logs.:

https://nirvtek.com/downloads/RReady.Alpha.20 … .002.AMDTest.7z
MD5: 68d4cefebcc045a8d27f0b9e999997db

PS I don't think it'll work.

BEEN_Nath_58 wrote on 2025-01-10, 11:08:

sharangad wrote on 2025-01-10, 10:24:

***************************************** RReady Alpha, January 10, 2025 (Untested Store Release candidate) This will be undergo […]
Show full quote

*****************************************
RReady Alpha, January 10, 2025 (Untested Store Release candidate)
This will be undergoing testing shortly
*****************************************
https://nirvtek.com/downloads/RReady.Alpha.20250110.001.7z
MD5: 7a07f529eade3ed5aae43a6a5c0c8724

- Tomb Raider 1 video cutscenes should now render on Win11 24H2 with Nvidia hardware and possibly on most Intel integrated GPUs.
- ICR2 by default disables Rendition anti-aliasing which makes the game runnable on GPUs with less VRAM, such as Intel HD graphics. It also provides a significant performance boost on such systems.
- ICR2 – RLauncher now offers control over fogging, bilinear filtering and low res mirrors (original game resolution). Additionally options to disable line drawing and Rendition Anti-Aliasing are available. The latter two are turned off by default as custom carsets have issues with this, even on original hardware. They can be turned back on for purists.
- Whiplash original low res mirrors can be enabled.
- SDK Demo Ucube.exe should now once again render correctly in full screen mode.

Intel has issues running DOSBox videos as well?

Not dosbox, RReady videos. After updating my nvidia based machine to Win11 24H2 I noticed TR1 videos didn't render until Dosbox was visible. The moment I switched back to the background window with the video, it became black again.

After more testing it turned out that physically changing display modes when virtual Rendition modes are changed causes this. The reason RReady did this was because it supports different upscaling resolutions on a per Rendition mode basis.

So the fix turned out to be not changing the actual resolution on a Rendition VESA mode change for Tomb Raider 1. I haven't got time to test each and every app so I've gated the fix to TR1, but a general fix is coming soon, if it helps the other apps. Descent 2 is the other one, *I think*.

and maybe Scorched Planet also being affected? its has videos. and i remember i got problems with those once on real HW. and generally hard game to setup on rendition hardware. and it works best only on v1000.

tested amd build for fun, crashes for me.
tested latest build , icr2 has white screen if i turn on frameinterpolation. even at default low resolution / windowed.

RaVeN-05 wrote on 2025-01-10, 13:20:

and maybe Scorched Planet also being affected? its has videos. and i remember i got problems with those once on real HW. and generally hard game to setup on rendition hardware. and it works best only on v1000.

tested amd build for fun, crashes for me.
tested latest build , icr2 has white screen if i turn on frameinterpolation. even at default low resolution / windowed.

Logs please from both if possible. Also how much vram have you got?

You might be right about sp. Will look into at some point.

wait amd build works for me.
logs

sharangad wrote on 2025-01-10, 10:24:

***************************************** RReady Alpha, January 10, 2025 (Untested Store Release candidate) This will be undergo […]
Show full quote

*****************************************
RReady Alpha, January 10, 2025 (Untested Store Release candidate)
This will be undergoing testing shortly
*****************************************
https://nirvtek.com/downloads/RReady.Alpha.20250110.001.7z
MD5: 7a07f529eade3ed5aae43a6a5c0c8724

- Tomb Raider 1 video cutscenes should now render on Win11 24H2 with Nvidia hardware and possibly on most Intel integrated GPUs.
- ICR2 by default disables Rendition anti-aliasing which makes the game runnable on GPUs with less VRAM, such as Intel HD graphics. It also provides a significant performance boost on such systems.
- ICR2 – RLauncher now offers control over fogging, bilinear filtering and low res mirrors (original game resolution). Additionally options to disable line drawing and Rendition Anti-Aliasing are available. The latter two are turned off by default as custom carsets have issues with this, even on original hardware. They can be turned back on for purists.
- Whiplash original low res mirrors can be enabled.
- SDK Demo Ucube.exe should now once again render correctly in full screen mode.

I can confirm that this now works with my Intel UHD Graphics 630. Last night i bought the version from MS store but was unable to launch ICR2 (video artifacts at intro, very very slow and freezed before reaching the game menu). Now i can launch and race just fine.

Keep in mind that i had to add both the downloaded folder and the ICR2 folder in MS´s defender exclusion list.

Keep it up your great work! i´ve also created another report at Microsoft regarding false-positive of dosclient.exe

rfratelli wrote on 2025-01-10, 14:13:

I can confirm that this now works with my Intel UHD Graphics 630. Last night i bought the version from MS store but was unable t […]
Show full quote

sharangad wrote on 2025-01-10, 10:24:

***************************************** RReady Alpha, January 10, 2025 (Untested Store Release candidate) This will be undergo […]
Show full quote

*****************************************
RReady Alpha, January 10, 2025 (Untested Store Release candidate)
This will be undergoing testing shortly
*****************************************
https://nirvtek.com/downloads/RReady.Alpha.20250110.001.7z
MD5: 7a07f529eade3ed5aae43a6a5c0c8724

- Tomb Raider 1 video cutscenes should now render on Win11 24H2 with Nvidia hardware and possibly on most Intel integrated GPUs.
- ICR2 by default disables Rendition anti-aliasing which makes the game runnable on GPUs with less VRAM, such as Intel HD graphics. It also provides a significant performance boost on such systems.
- ICR2 – RLauncher now offers control over fogging, bilinear filtering and low res mirrors (original game resolution). Additionally options to disable line drawing and Rendition Anti-Aliasing are available. The latter two are turned off by default as custom carsets have issues with this, even on original hardware. They can be turned back on for purists.
- Whiplash original low res mirrors can be enabled.
- SDK Demo Ucube.exe should now once again render correctly in full screen mode.

I can confirm that this now works with my Intel UHD Graphics 630. Last night i bought the version from MS store but was unable to launch ICR2 (video artifacts at intro, very very slow and freezed before reaching the game menu). Now i can launch and race just fine.

Keep in mind that i had to add both the downloaded folder and the ICR2 folder in MS´s defender exclusion list.

Keep it up your great work! i´ve also created another report at Microsoft regarding false-positive of dosclient.exe

Good to know it works and thanks for the report!

sharangad wrote on 2025-01-10, 11:58:

@gplaps, could you reply to @michaelgott9524 (who commented on your video about being unable to buy the wrapper) to try it from the Microsoft Store app and search for RReady and make sure his region is set to the UK. I think the link is for the US store.

I posted a link in the comments section of the video and appear to be locked out of commenting.

I added a response. Youtube doesn't like when people post links in the comments, its not a setting i can change. I never even see your comment before it gets deleted.

gplaps wrote on 2025-01-10, 14:34:

sharangad wrote on 2025-01-10, 11:58:

@gplaps, could you reply to @michaelgott9524 (who commented on your video about being unable to buy the wrapper) to try it from the Microsoft Store app and search for RReady and make sure his region is set to the UK. I think the link is for the US store.

I posted a link in the comments section of the video and appear to be locked out of commenting.

I added a response. Youtube doesn't like when people post links in the comments, its not a setting i can change. I never even see your comment before it gets deleted.

Thanks @gplaps!

And now @Raven-05 and the @supererwin could you try this and see if frame generation works:
https://nirvtek.com/downloads/RReady.Alpha.20 … .003.AMDTest.7z
MD5: a1084601b77cc34a4640138899d5b74b

RaVeN-05 wrote on 2025-01-10, 13:40:

wait amd build works for me.

I did not read this. Aaargh!

RaVeN-05 wrote on 2025-01-10, 13:40:

wait amd build works for me.
logs

@Raven-05, the logs are confusing me.

1) could you delete all your RReadyLog files in %localappdata%\temp ,
2) run the AMD build with interpolation enabled,
3) Zip up the logs and post them here?

Thanks.

BTW Thanks @gplaps for the wonderful video. I didn't know the game meant so much to you and so many others.

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me.
got other idea. Maybe throw out idea of reverse engineering rendition specific AA , we have nowadays more advances AA techniques , just apply it everywhere or nowhere as option in RLauncher graphical settings.
vanilla vs modernity. lets it be modernity.
vanilla AA is probably handly for quake engine games in only case when you force resolution which bigger than internal, causes global AA (from nVidia panel) to not work.
it only works when internal and forced resolutions the same. well its for future.....
or you really want to realize AA that rendition offered back then?

RaVeN-05 wrote on 2025-01-10, 16:17:

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me. got other idea. Maybe throw out idea of reverse engineerin […]
Show full quote

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me.
got other idea. Maybe throw out idea of reverse engineering rendition specific AA , we have nowadays more advances AA techniques , just apply it everywhere or nowhere as option in RLauncher graphical settings.
vanilla vs modernity. lets it be modernity.
vanilla AA is probably handly for quake engine games in only case when you force resolution which bigger than internal, causes global AA (from nVidia panel) to not work.
it only works when internal and forced resolutions the same. well its for future.....
or you really want to realize AA that rendition offered back then?

In the interest of authenticity and correctness I would like to get proper edge aa working.

RaVeN-05 wrote on 2025-01-10, 16:17:

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me. got other idea. Maybe throw out idea of reverse engineerin […]
Show full quote

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me.
got other idea. Maybe throw out idea of reverse engineering rendition specific AA , we have nowadays more advances AA techniques , just apply it everywhere or nowhere as option in RLauncher graphical settings.
vanilla vs modernity. lets it be modernity.
vanilla AA is probably handly for quake engine games in only case when you force resolution which bigger than internal, causes global AA (from nVidia panel) to not work.
it only works when internal and forced resolutions the same. well its for future.....
or you really want to realize AA that rendition offered back then?

There's a serious bug there, I don't think the frame generation is working properly.

RReady calls glcopyteximage2d t to create a texture in gpu memory which is a copy of the framebuffer, either visible frame or back buffer. It doesn't appear to be working here.

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

RaVeN-05 wrote on 2025-01-10, 16:17:

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me. got other idea. Maybe throw out idea of reverse engineerin […]
Show full quote

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me.
got other idea. Maybe throw out idea of reverse engineering rendition specific AA , we have nowadays more advances AA techniques , just apply it everywhere or nowhere as option in RLauncher graphical settings.
vanilla vs modernity. lets it be modernity.
vanilla AA is probably handly for quake engine games in only case when you force resolution which bigger than internal, causes global AA (from nVidia panel) to not work.
it only works when internal and forced resolutions the same. well its for future.....
or you really want to realize AA that rendition offered back then?

There's a serious bug there, I don't think the frame generation is working properly.

RReady calls glcopyteximage2d t to create a texture in gpu memory which is a copy of the framebuffer, either visible frame or back buffer. It doesn't appear to be working here.

I need to do a few more builds, maybe I can figure it out from the code. Its working on more modern nvidia h/w but not on rx 7900 or a gt330m. Generally Amd's drivers are much more standards compliant. Nvidia let's you get away with a lot of things which, while being logical, are illegal in terms of the standard.

[EDIT] Not sure I can manage it tonight. But let's see.

RaVeN-05 wrote on 2025-01-10, 16:17:

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me. got other idea. Maybe throw out idea of reverse engineerin […]
Show full quote

RReady.Alpha.20250110.003.AMDTest - frame interpolation works for me.
got other idea. Maybe throw out idea of reverse engineering rendition specific AA , we have nowadays more advances AA techniques , just apply it everywhere or nowhere as option in RLauncher graphical settings.
vanilla vs modernity. lets it be modernity.
vanilla AA is probably handly for quake engine games in only case when you force resolution which bigger than internal, causes global AA (from nVidia panel) to not work.
it only works when internal and forced resolutions the same. well its for future.....
or you really want to realize AA that rendition offered back then?

Humus had a demo which carried out edge aa quite nicely a few years back.

I can't tell for certain from the AMD.003 logs whether it's working or not. IN some of them it is the other one, not.

So one final build #004:
https://nirvtek.com/downloads/RReady.Alpha.20 … .004.AMDTest.7z
MD5: 59bdf2555b20b287f8022fc403adaa95

I've added extra logging to tell me more.

Please find attached the logfiles I just generated from your last upload.

Sorry, I've been busy all day long and could not keep up with your posts here in the forum...

I suppose, you know the settings of your tool from the logfiles. If not, let me know, I will make a screenshot.

Sill, I got the problem of not being able to use accelleratrion or custom keymappings within dosbox - just to say this. 😀

All the best,
supererwin

Just a quick info, as I cannot edit my posting before - the keybindings have been adjusted. All my fault. Problem between monitor and chairback 😁

Plus: I also found the dosbox-mapper file: It's in C:\Users\USER\AppData\Local\DOSBox