Tested: Nascar 1999 Edition:
cockpit view decrease fps a little bit, external view is faster. (set 39 cars behind and ahead of view in graphic settings)
Richmond raceway have bad clamping texture on grandstand.
Game crashes sometimes due to DMA bug, can't be reproduced (know)
Mouse cursor in main menu get copied over all screen (can be fixed by force screen refresh or draw tiny triangle somewhere) . Menu where we can see our car is being redrawn a lot and do not have that bug.

https://nirvtek.com/downloads/RReady.Alpha.20250905.003.7z
MD5: 31aafcd95b679fa450069709db37efb6
- Nascar 1999R texture clamping fix
- Whiplash coloured lines at edges of screen fix. V_FIFO_MEM_CLEAR_RECT was being called to erase these, but RReady wasn't filling the entire row and column.
- vQuake1/2/vHexen II should render correctly on AMD R7 250. V_FIFO_QSPAN wasn't working. This is a Rendition Quake specific function call.

ICR2: Colorado, Springs, Continental Divide, Daytona, Croix-en-Ternois and Crystal Palace
https://youtu.be/VlZWkwOvN2M

Super resolution:
https://youtu.be/CKQK_JeCjD4

[EDIT]
https://nirvtek.com/downloads/RReady.Alpha.20250907.003.7z
MD5: 650f01dfb146df313af5d2eb19a88677
- Frame gen should work correctly.
[/EDIT]

https://nirvtek.com/downloads/RReady.Alpha.20250907.002.7z
MD5: e054f5f5517c2d43420dda4a07ed2ad9

RLauncher has options for enabling and configuring super resolution. The resolution can be specified directly like 16384x16384 OR as a factor 8 (which for ICR2 would render at (640x8)x(480x8)). Using a factor would be better than using direct resolution as it would eliminate scaling artifacts.

- Extremely alpha Super Resolution support.
To Rendition.cfg add:
super=1 (set to 0 to disable)
superres=5200x3800

https://nirvtek.com/downloads/RReady.Alpha.20250907.001.7z
MD5: e476daff8bb34b1b1398a80514798c50

- Extremely alpha Super Resolution support.
To Rendition.cfg add:
rttp=1
rttpres=5200x3800

- to disable super resolution , set super=0
- This will internally render at 51200x2300 to a texture and downsample this to the screen resolution. This will allow artifacts in ICR2's rev counter to be corrected (this resolution is an integral multiple of 640 and 480, For vquake, a horizontal and vertical multiple of the in-game resolution would have to be used). The maximum super resolution is 16384x16384, GPU RAM and performance permitting.
- It has been tested to work with vQuakes 1 & 2 and ICR2. vHexen II is currently incompatlble. Other games probably won't work. For a win32 game click on the game in the "win apps" tab and click browse to get to the folder with rendition.cfg. For dos based apps, click on the relevant dosbox.exe in the "DOs apps" tab and click browse to get to the folder with rendition.cfg. For DOS apps, the setting is shared, for Windows apps, each app has its own setting.
- This code has been unused for a few years now, so YMMV.

This codepath isn't recommended for Intel HD graphics.

This is not Super Sampling AntiAliasing? or maybe i doing something wrong, i only see that watermark get more clearness or thinness . Rest scene aliased.

RaVeN-05 wrote on 2025-09-07, 08:14:

This is not Super Sampling AntiAliasing? or maybe i doing something wrong, i only see that watermark get more clearness or thinness . Rest oscene aliased.

It renders to a texture at a higher resolution and downscales it to the display res.

You can use a higher res like 16384x16384 to see if there's a difference. I'll post a video. Quake engine games have problems with the underwater resolution. Using a factor of 8 should render at 8 times the horizontal and vertical resolution of the game's internal resolution.

It fixes the icr2 rev counter aliasing.

RaVeN-05 wrote on 2025-09-07, 08:14:

This is not Super Sampling AntiAliasing? or maybe i doing something wrong, i only see that watermark get more clearness or thinness . Rest scene aliased.

It should fix the vquake polygon gaps/coloured edges or at least it should.

When downscaling it's resamples?
Like having 8 bigger resolution and downscaling back it's like nearest 8 pixels, those rgb values must be added in each own separate channels and then devide by 8 or other downscale factor, so this smoothes pixel makes them antialiased.
Maybe nVidia settings need to be dropped or I need some special settings.

I expect this should AA things especially noticeable at far distance objects

Super Resolution (render to texture):
https://youtu.be/CKQK_JeCjD4

120 fps frame interpolation (quad-rate interpolation)
https://nirvtek.com/downloads/RReady.Alpha.20 … 8.001.120fps.7z
MD5: 5ff504bfc1b7a42318964a7b53626966

RLauncher has options for enabling 60 fps (double rate) and 120 fps (quad-rate) frame generation/interpolation. It will currently only work with ICR2, the Nascar games, Die by the Sword and GPL (36 *4 fps=144 fps).

I can't test this because I only have 60 Hz displays, the video I've uploaded to youtube, which isn't available yet, has been captured with vsync disabled. OBS struggles to capture even 60 fps video with super resolution turned on.

RaVeN-05 wrote on 2025-09-07, 10:23:

When downscaling it's resamples? Like having 8 bigger resolution and downscaling back it's like nearest 8 pixels, those rgb valu […]
Show full quote

When downscaling it's resamples?
Like having 8 bigger resolution and downscaling back it's like nearest 8 pixels, those rgb values must be added in each own separate channels and then devide by 8 or other downscale factor, so this smoothes pixel makes them antialiased.
Maybe nVidia settings need to be dropped or I need some special settings.

I expect this should AA things especially noticeable at far distance objects

I render to a texture at a higher resolution and render to a lower res framebuffer. I'm not actually doing the downsampling, the videocard is.