Payback white screen

[motorollin]

I've just downloaded the Payback demo from Aminet. I enabled hardware acceleration and chose 1024x768 on my Voodoo. When I ran the game, a screen opened with a title bar, which was then decorated with a VisualPrefs gadget in the top right hand corner, and the machine reset. I disabled VisualPrefs and tried again, and this time the game ran without crashing but all I got on the display was a white screen. The game was running because I could hear sound. I rebooted and tried it at 640x480, and the same thing happened. I then tried a PAL screenmode and the game ran (but performance was crap). I tested the 1024x768 screenmode in Picasso96Mode and it displayed the testcard fine.

Anyone else had this problem?

Cheers

--
moto

[kas1e]

Maybe wrong setting of envarc:mediator/mmu ? for ppc and 68k warp3d software, must be different settings.

[motorollin]

What should I set it to?

--
moto

[kas1e]

for 68k warp3d software, this env must be set to 'yes', for ppc warp3d stuff (like payback), env must be set to 'no'. btw, problems with 'white/black' screens - it is problem of this env usualy. hope this help.

[motorollin]

Ok I just checked and I didn't have ENVARC:Mediator/MMU. I created the file using ED and entered the word YES in the file, and saved it. I rebooted and the same thing happened :-( Did I do it right?

--
moto

[motorollin]

I don't know if Warp3D is installed. Do I need this?

--
moto

[nasty]

Yip it sure does! payback warp and answers

[humppa]

Does Payback also support Warp3D on 68k - or is it PPC-exclusive?

[motorollin]

Thanks Nasty. I just installed Warp3D from the Mediator CD and the same thing happened. I don't know if it's the version Apex are recommending though. I'll try their version in a bit. Do I also need the updated version of Payback to get it to work on a Mediator? Does that update require the full game or does it with with the demo?

--
moto

[nasty]

Yea the update is only for the full version. The warp 3d 4.2 on the mediator is better than the payback version as it doesnt included the a3000/a4000 warp files which sometimes cause problems on the a1200.  I'll try and located the post on this boards and ill dig out my mediator settings just now

@ Humppa
Both

[motorollin]

I did install the Warp3D version from the Apex web site and also the latest version of the demo. When I run any of the Warp3D demos, the same thing happens (just a white screen). So the problem would appear to be with the setup of the graphics card, not the game. A quick butchers at your Voodoo settings would probably help :-)

--
moto

[nasty]

Prefs/Env-Archive/mediator

mmu=no
nocache=no
voodooint=yes
patchint=no
emulation=no
voodoomem=15
warp3d=yes

Prefs/Env-Archive/powerpc

memprot=0
debug=0
earlyterm=0
force=1
gfxaddress=$200000
hidewarning=0
seginfo=100
teminator=2

Prefs/Env-Archive/powerpc

amigavid= 15khz
blackswitching=no
debug=no
directcolormask=no
disableamigablitter=no
donotsetmmu=no
enablebootvga=no
experimental=yes
planaronlydipfduf=no
planestofast=yes
showmodes=all

Devs/monitors/voodoo icon

boardtypr=voodoo
borderblank=yes
bigsprite=no
softsprite=no
ingoremask=yes
displaychain=no
fakenativemodes=no
fontfix=no
granddirectaccess=no
memoryclock=166
overclock=no

thinks thats all my settings, got to make an update to this post in a second!

[motorollin]

Is ENVARC:Mediator a directory or a file? On my system (68k) it's a directory, so I assumed the MMU=no has to go in a file called MMU with the word no in it? Or do I have to create a text file called Mediator with those settings in it?

--
moto

[nasty]

On my system (68k) it's a directory, so I assumed the MMU=no has to go in a file called MMU with the word no in it?

yip thats right, so all the bold writing is a directory and each name e.g is what the file is called and the bit after the equals sign is what is in the txt file.

You might have to delete some warp3d files as one of the warp3d adds 6 files for the A3000/A4000 to your A1200 which can cause problems with running warp3d on your 1200
files that arent needed:
 GFX drivers for A3/4000:      
W3D_Picasso96.library 4.2 02 Feb 2002 Libs:Warp3D/GFXdrivers
W3D_Picasso96_PPC.library 4.2 02 Feb 2002 Libs:Warp3D/GFXdrivers
HW drivers for A3/4000:      
W3D_AvengerBE.library 4.2 13 Jul 2001 Libs:Warp3D/HWdrivers
W3D_AvengerBE_PPC.library 4.2 13 Jul 2001 Libs:Warp3D/HWdrivers
W3D_AvengerLE.library 4.2 13 Jul 2001 Libs:Warp3D/HWdrivers
W3D_AvengerLE_PPC.library 4.2 13 Jul 2001 Libs:Warp3D/HWdrivers

so its safe to delete all these files on your 1200. and if you want you can download and run medconfig from elbox
 Medconfig  Elbox

[motorollin]

Thanks Nasty, MedConfig fixed it. I just told it what hardware I'm using then accepted their recommended settings, and the game now displays. Unforunately the performance is crap. The game itself runs at (literally) one frame per second. This happens even in the lowest res hardware accelerated screenmode available :-( Any idea why it's so slow?

--
moto