Wipeout 2097 at 800x600 - slow loading time

[Bamiga2002]

When i load Wipeout 2097 in 640x480 there's fast loading time, but if i change the resolution to 800x600 it loads nearly 2 mins. The game itself plays properly though.

I'm using A1200/PPC/128MB/Mediator+Voodoo3.

[Bamiga2002]

I have SCSI, it's not the drive's fault . Dunno what's causing the slowdown. Maybe some P96-variable, but i have tried many cfg's of those. Could it be a Mediator specific setting?

[Bamiga2002]

I have the newest 'pci.library' (6.5) and 'voodoo.card' (4.23) is from MM_CD_UP1.26 (everyone says the newest <4.26> causes graphical corruption).

Is there any chance the newest 'pci.library' causes incompatibility with the 'voodoo.card' 4.23?

[Bamiga2002]

Here you go:

MedReport.txt

I might add that i partially solved the problem: when the loading images are ehmm...loading :-), just press space and it will load on. Now i have a tiny scratching sound problem, but i think that's the monitors stereo output.

[Bamiga2002]

Medconfig (1.4) doesn't set MemSize-variable at all even if it says so. So i set it by hand to Envarc:Mediator/MemSize=15. Is this right?

EDIT:
Found out the MemSize-variable should go to Envarc:Warp3D/Mediator/MemSize right?

[Bamiga2002]

You seem to be right. Warp3d/Mediator/Memsize should be set to 8 and Mediator/VoodooMem to 15. That's with Voodoo3.

MemSize path is correct :-).

[Bamiga2002]

You don't have MemSize set my friend ;-). I think VoodooMem can be 8MB as you and i have, and MemSize can be 15. I read it somewhere (graphics card memory -1MB).

If VoodooInt=Yes you can't play WHDLoad games. What does Warp3D=Yes -variable do?

I also read that MMU-Warp3D -libraries could interfere even if you set the NOMMU-variable. :-?