Half-mip (smallest half dropped)

Cars2020: https://nirvtek.com/downloads/cars2020.HalfMi … nditionReady.7z
MD5: d19fa0742fae92c68904e99bd4e6952b
LOLA1995: https://nirvtek.com/downloads/LOLA1995.HalfMi … nditionReady.7z
MD5: 9219f4d3fda493008ff6886832f8ee66

Tracks (for these three, both the carset and the track need to shed a few mipmaps. Other tracks like Meadowlands and Nashville will work with just half-mipped carsets):
Denver: https://nirvtek.com/downloads/denver.HalfMip. … enditonReady.7z
MD5: ab20ac3af21ecdaabf038c3afb605e38
Indianpolis: https://nirvtek.com/downloads/Ims92.HalfMip.R … nditionReady.7z
MD5: 6600e746e7b2f727bbce798d92dcd456
Riverside: https://nirvtek.com/downloads/riversid.HalfMi … nditionReady.7z
MD5: 23de53c63fe034e1f6a7492e47ce1f86

[EDIT] These do work on origjnal hardware. I'll post a video tomrrow.

The 50% MIP tracks I uploaded in action:
https://youtu.be/Nf8xMa5Yui8

I will be trying these out but I'm away from home for at least three more days - so won't be able to report anything until after that - sorry!

Grafix wrote on 2025-03-21, 19:45:

I will be trying these out but I'm away from home for at least three more days - so won't be able to report anything until after that - sorry!

No worries, I can wait.

The 50% MIPS also work on original hardware:
Riverside https://youtu.be/U2XAtj-wyLY
Denver https://youtu.be/7Aq8CNh7ahA

Well - a little bit of feedback from me!

So far I've run the Lola 95 carset in races at IMS, Denver, Laguna Seca New and Riverside without any crashes. Well lots of crashes but all on the track 😉

However I have had weird black lines flickering across the Riverside track continuously (SOLVED - by turning 'no line rendering' on in RLauncher Rendition settings this issue went away).

The cars do now noticeably seem to float above the tracks as soon as they are any distance ahead. When they step down in level of detail they suddenly appear to be floating. (Like the original Canam71 carset for Grand Prix Legends before the increased detail/LOD set was released).

Perhaps new to me (As I've never had Riverside on ICR2 before) is the fact that on Riverside you see 'through' the track - cars appear visible when the are the other side of the rises in the track and are rendered 'under/in' the track so to speak - which looks very weird.

I'll keep testing 😀

Grafix wrote on 2025-03-23, 20:47:

Well - a little bit of feedback from me! […]
Show full quote

Well - a little bit of feedback from me!

So far I've run the Lola 95 carset in races at IMS, Denver, Laguna Seca New and Riverside without any crashes. Well lots of crashes but all on the track 😉

However I have had weird black lines flickering across the Riverside track continuously (SOLVED - by turning 'no line rendering' on in RLauncher Rendition settings this issue went away).

The cars do now noticeably seem to float above the tracks as soon as they are any distance ahead. When they step down in level of detail they suddenly appear to be floating. (Like the original Canam71 carset for Grand Prix Legends before the increased detail/LOD set was released).

Perhaps new to me (As I've never had Riverside on ICR2 before) is the fact that on Riverside you see 'through' the track - cars appear visible when the are the other side of the rises in the track and are rendered 'under/in' the track so to speak - which looks very weird.

I'll keep testing 😀

Thanks for the feedback!

I'm still working on this. I think its a number of mip map levels thing and no longer a texture size issue., but I could be wrong.

The game doesn't use z-buffering, which is why you can see cars through the track. Even the Rendition enhanced Laguna Seca had that issue in a section or two.

@sharangad ...I tried reducing track MIPs with TRedit.exe for an unpacked dat track (Pavel's lbeach96) but can't get a result yet.
I put TRedit.exe in .\ICR2 and made a dosbox_MIP.conf with [autoexec] to start tredit .\ICR2\TRACKS\lbeach96 - reduce -convert .\ICR2\TRACKS\_TEMP but nothing happened.

Not a power user - is my syntax wrong?

tincup wrote on 2025-03-24, 02:00:

@sharangad ...I tried reducing track MIPs with TRedit.exe for an unpacked dat track (Pavel's lbeach96) but can't get a result yet.
I put TRedit.exe in .\ICR2 and made a dosbox_MIP.conf with [autoexec] to start tredit .\ICR2\TRACKS\lbeach96 - reduce -convert .\ICR2\TRACKS\_TEMP but nothing happened.

Not a power user - is my syntax wrong?

Your syntax is fine.

Tredit is an X64 windows app and won't run inside dosbox. You need to hit [WIN+R] type CMD [ENTER] and run it from there using the machine native file paths and not the dosbox ones. Also if the track is packed into a dat file you'll have to unpack it (and replace the dat with the unpacked stuff in. \icr2 before copying in the mip reduced files.

tincup wrote on 2025-03-24, 02:00:

@sharangad ...I tried reducing track MIPs with TRedit.exe for an unpacked dat track (Pavel's lbeach96) but can't get a result yet.
I put TRedit.exe in .\ICR2 and made a dosbox_MIP.conf with [autoexec] to start tredit .\ICR2\TRACKS\lbeach96 - reduce -convert .\ICR2\TRACKS\_TEMP but nothing happened.

Not a power user - is my syntax wrong?

One thing to note is that some tracks will just work with just a mip reduced carset (surfers' paradise, Meadowlands and Nashville are three that I tested).

sharangad wrote on 2025-03-24, 03:15:

One thing to note is that some tracks will just work with just a mip reduced carset (surfers' paradise, Meadowlands and Nashville are three that I tested).

Cool - thanks. I'll give another shot tomorrow...

sharangad wrote on 2025-03-24, 01:20:

Thanks for the feedback! […]
Show full quote

Grafix wrote on 2025-03-23, 20:47:

Well - a little bit of feedback from me! […]
Show full quote

Well - a little bit of feedback from me!

So far I've run the Lola 95 carset in races at IMS, Denver, Laguna Seca New and Riverside without any crashes. Well lots of crashes but all on the track 😉

However I have had weird black lines flickering across the Riverside track continuously (SOLVED - by turning 'no line rendering' on in RLauncher Rendition settings this issue went away).

The cars do now noticeably seem to float above the tracks as soon as they are any distance ahead. When they step down in level of detail they suddenly appear to be floating. (Like the original Canam71 carset for Grand Prix Legends before the increased detail/LOD set was released).

Perhaps new to me (As I've never had Riverside on ICR2 before) is the fact that on Riverside you see 'through' the track - cars appear visible when the are the other side of the rises in the track and are rendered 'under/in' the track so to speak - which looks very weird.

I'll keep testing 😀

Thanks for the feedback!

I'm still working on this. I think its a number of mip map levels thing and no longer a texture size issue., but I could be wrong.

The game doesn't use z-buffering, which is why you can see cars through the track. Even the Rendition enhanced Laguna Seca had that issue in a section or two.

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's in your face on Riverside especially down the undulating straight towards turn 7.

From memory on that GPL Canam71 carset it was the number of mip map levels and eventually a carset with more levels was released which sorted it. I guess that's likely here too in that case?

Cheers!

Grafix wrote on 2025-03-24, 08:01:

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's i […]
Show full quote

sharangad wrote on 2025-03-24, 01:20:

Thanks for the feedback! […]
Show full quote

Grafix wrote on 2025-03-23, 20:47:

Well - a little bit of feedback from me! […]
Show full quote

Well - a little bit of feedback from me!

So far I've run the Lola 95 carset in races at IMS, Denver, Laguna Seca New and Riverside without any crashes. Well lots of crashes but all on the track 😉

However I have had weird black lines flickering across the Riverside track continuously (SOLVED - by turning 'no line rendering' on in RLauncher Rendition settings this issue went away).

The cars do now noticeably seem to float above the tracks as soon as they are any distance ahead. When they step down in level of detail they suddenly appear to be floating. (Like the original Canam71 carset for Grand Prix Legends before the increased detail/LOD set was released).

Perhaps new to me (As I've never had Riverside on ICR2 before) is the fact that on Riverside you see 'through' the track - cars appear visible when the are the other side of the rises in the track and are rendered 'under/in' the track so to speak - which looks very weird.

I'll keep testing 😀

Thanks for the feedback!

I'm still working on this. I think its a number of mip map levels thing and no longer a texture size issue., but I could be wrong.

The game doesn't use z-buffering, which is why you can see cars through the track. Even the Rendition enhanced Laguna Seca had that issue in a section or two.

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's in your face on Riverside especially down the undulating straight towards turn 7.

From memory on that GPL Canam71 carset it was the number of mip map levels and eventually a carset with more levels was released which sorted it. I guess that's likely here too in that case?

Cheers!

I have increased the texture buffer size, but there's still a limit somewhere. These carsets and tracks have their smallest (lowest detail) MIP maps removed, which is why they run. I'm still working on increasing these limits.

But yes, it is because there aren't enough MIP maps for low detail models.

sharangad wrote on 2025-03-24, 08:39:

Grafix wrote on 2025-03-24, 08:01:

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's i […]
Show full quote

sharangad wrote on 2025-03-24, 01:20:

Thanks for the feedback!

I'm still working on this. I think its a number of mip map levels thing and no longer a texture size issue., but I could be wrong.

The game doesn't use z-buffering, which is why you can see cars through the track. Even the Rendition enhanced Laguna Seca had that issue in a section or two.

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's in your face on Riverside especially down the undulating straight towards turn 7.

From memory on that GPL Canam71 carset it was the number of mip map levels and eventually a carset with more levels was released which sorted it. I guess that's likely here too in that case?

Cheers!

I have increased the texture buffer size, but there's still a limit somewhere. These carsets and tracks have their smallest (lowest detail) MIP maps removed, which is why they run. I'm still working on increasing these limits.

But yes, it is because there aren't enough MIP maps for low detail models.

Don't get me wrong - I think your work is amazing and I am enjoying ICR2 massively because of it!!

Grafix wrote on 2025-03-24, 12:39:

sharangad wrote on 2025-03-24, 08:39:

Grafix wrote on 2025-03-24, 08:01:

Ahh that Z buffer thing makes sense - thank you! I've never noticed it at Laguna Seca tbh but I'll go looking for it now. It's in your face on Riverside especially down the undulating straight towards turn 7.

From memory on that GPL Canam71 carset it was the number of mip map levels and eventually a carset with more levels was released which sorted it. I guess that's likely here too in that case?

Cheers!

I have increased the texture buffer size, but there's still a limit somewhere. These carsets and tracks have their smallest (lowest detail) MIP maps removed, which is why they run. I'm still working on increasing these limits.

But yes, it is because there aren't enough MIP maps for low detail models.

Don't get me wrong - I think your work is amazing and I am enjoying ICR2 massively because of it!!

Thank you, yet still I'm holding up the custom tracks.

sharangad wrote on 2025-03-24, 14:16:

Grafix wrote on 2025-03-24, 12:39:

sharangad wrote on 2025-03-24, 08:39:

I have increased the texture buffer size, but there's still a limit somewhere. These carsets and tracks have their smallest (lowest detail) MIP maps removed, which is why they run. I'm still working on increasing these limits.

But yes, it is because there aren't enough MIP maps for low detail models.

Don't get me wrong - I think your work is amazing and I am enjoying ICR2 massively because of it!!

Thank you, yet still I'm holding up the custom tracks.

You've done plenty already!! ☺️

Grafix wrote on 2025-03-23, 20:47:

Well - a little bit of feedback from me! […]
Show full quote

Well - a little bit of feedback from me!

So far I've run the Lola 95 carset in races at IMS, Denver, Laguna Seca New and Riverside without any crashes. Well lots of crashes but all on the track 😉

However I have had weird black lines flickering across the Riverside track continuously (SOLVED - by turning 'no line rendering' on in RLauncher Rendition settings this issue went away).

The cars do now noticeably seem to float above the tracks as soon as they are any distance ahead. When they step down in level of detail they suddenly appear to be floating. (Like the original Canam71 carset for Grand Prix Legends before the increased detail/LOD set was released).

Perhaps new to me (As I've never had Riverside on ICR2 before) is the fact that on Riverside you see 'through' the track - cars appear visible when the are the other side of the rises in the track and are rendered 'under/in' the track so to speak - which looks very weird.

I'll keep testing 😀

The tracks and carsets linked in my video are already modded and don't need to be MIP reduced. I think that's the problem you had with missing MIPS. I *forgot* to mention that in the video.

[EDIT] Half the low detail MIPs are in fact missing, but the high detail ones shouldn't make the cars floaty.[/EDIT]

A guide to MIP reduction for TREdit:
https://youtu.be/EIOizyyHDWg

[EDIT] DO NOT RUN THESE TWO MAPS, unless you're interested in building your own carset and tracks. They're just proof of concept demos. There is no extra detail, just the same texture padded out[/EDIT]

The texture limit appears to be already smashed. I can load MIPs (~122 MB) with a vertical resolution of ~16384, by replicating the texture vertically. The horizontal resolution has limits,
Rendition hardware supported horizonal resolutions of around 2048 in Windows (RRedline), but the limit may be lower in DOS. I'll dig up a list of valid horizontal resolutions. The vertical resolution can't be scaled higher than 16384 because modern OpenGL hardware doesn't support textures bigger than 16384x16384, the wrapper wouldn't be able to handle it. Original Rendition hardware doesn't have vertical limits, other than memory.

https://nirvtek.com/downloads/1982CART.x16384.7z
MD5: 75726862d06df3807f9932bd8845426e

Using this build of Dosbox-Rendition which supports 1.5 GB of RAM:
https://nirvtek.com/downloads/RReady.Alpha.20 … .1.5Gigs.001.7z
MD5: 0f9542b3008fb4fcd009c9527381f718

and these patched version of ICR2 (1200 MB) texture buffer:
https://nirvtek.com/downloads/ICR2.1200%20MB% … ure%20Buffer.7z
MD5: 37b018cb355a3e9800716cec17f86319

For good measure this version of Denver with 16384 textures (43MB) can be loaded along with the carset. Performance is horrible, but it loads:
https://nirvtek.com/downloads/denver.x16384.7z
MD5: b80e6f54b7a1df30f6df1f4a11cbf663

So tracks with higher resolution textures should be possible, but there's a limit to how many total MIP map levels can be loaded. That looks to be my next task.

The maximum number of mip map levels appear to top out at ~700 in total (carset+track):
Allowed horiziontal resolutions by RRedline are:
0;
256;
512;
1024;
4;
768;
16;
272;
528;
1040;
20;
784;
592;
1168;
32;
288;
544;
1056;
36;
800;
608;
1184;
64;
320;
576;
1088;
68;
832;
1216;
128;
384;
640;
1152;
132;
896;
704;
1280;
1536;
2048;
1028;
1792;
1600;
2176;
2048;
2304;
2560;
3072;
2052;
2816;
2624;
3200;
4096;
4352;
4608;
5120;
4100;
4864;
4672;
5248;
(Many thanks to @Raven-05 for supplying the list)
I don't know whether all of these are allowed in Speedy3D. I think in an earlier test x-resolutions higher than 1024 caused problems.