robertmo3 wrote on 2024-05-19, 10:16:

using verite.dll and redline.dll from 12 makes tr look like 12
13, 15, 18 work just with dlls from 12
i don't have to change dosclient.exe for tr

Phew!
That's a relief.

https://1drv.ms/u/c/5277ef8d4f2a9dcf/ER6vSSAb … fXiAtQ?e=wJDYZr
MD5: 0c6a27cb92d5a31ece53501286d69287

@robertmo3: See if this fixes your tomb raider texture problem

Other fixes:
- Tomb Raider chroma keying now works
- Tomb Raider Eidos splash screen should be free from corruption.
- Whiplash performance is now back to normal
- Cart Racing high resolution mirrors. Part of the mirror isn't being chroma keyed out. This will be fixed later.
- CR textures in Rendition HQ levels should disappear less when high detail mirrors are in use ([ALT+M]). This appears to be a CPU load dependent switch to black. The Rebel Moon black texture also needs a fix.

doesn't fix tr

robertmo3 wrote on 2024-05-19, 13:31:

doesn't fix tr

With redline and verite from the new set?

robertmo3 wrote on 2024-05-19, 13:31:

doesn't fix tr

This is weird. I haven't committed any code for RReady in a long while and I'm not entirely sure which change causes your problem. But it works on a Sandy Bridge i7. I'll test it on my other Intel machines including a Haswell dual core.

how to find it should be very easy:
you have let's say 100 changes, so you try change 50th change first, and it either fixes or not
if it fixes than you try 75th change
if it doesn't fix than you try 25th change
every test throws away half of changes left,
just always check the middle change next (to save time)
that's how i do it when looking for regressions in the code
(and also testing any numeric changes in the code too, when trying to find the exact value that changes something)

it that is just one big change and you don't have the order of changes
then you just revert half of changes and they either fix or not
and then you just test half of the left ones like before

this way 100 changes are detected in only 7 tests

if you have twice more changes that will be just one test more 😀

Tomb raider runs perfectly on my Haswell dual core and the i3 uhd 620.

I'll test the Sandy Bridge machine in a bit.

Can you test it on integrated graphics to see if it makes a difference?

Also is your tomb raider exe called tombren.exe?

If it isn't then that's the problem.

The older version applied byte level change detection for all dos apps. The newer version does not.

all 5 versions of tomb.exe files provided by someone here in the thread were all called tomb.exe

here

robertmo3 wrote on 2024-05-19, 14:35:

all 5 versions of tomb.exe files provided by someone here in the thread were all called tomb.exe

The binary available on this site under rendition game updates is called tombren.exe. I'm guessing that's what it called in the final release.

I'll add support for tomb. Exe as well. Tomorrow...

robertmo3 wrote on 2024-05-19, 14:38:

here

I'll add tomb.exe as a supported name.

Under the downloads on this site there's a zip file of final game binaries for rendition.

robertmo3 wrote on 2024-05-19, 14:38:

here

Final releases available here.

http://vogonsdrivers.com/getfile.php?fileid=168&menustate=0

Did that work?

Rendition Enhanced tracks Michigan, Phoenix and Portland in Indy Car 2:

https://youtu.be/rBIY-MJOQ-M

robertmo3 wrote on 2024-05-19, 14:38:

here

When I tested this, I renamed tomb. Exe to tombren.exe.

I figured you'd done the same thing.

This release should be able to handle both tomb.exe and tombren.exe:

https://1drv.ms/u/c/5277ef8d4f2a9dcf/ESSqzIvA … uYdnyg?e=5hKHq7
MD5: 477f9af8286d04534a73087a377a9950

ICR2 appears to have picked up a strange stride issue with some textures.