WipeOut 2097

CountRaven · 04 June 2012, 19:23

Hello to everyone!

I have been trying to run WipeOut 2097 on my A1200 PPC Setup.

I am installing the game from the CD, I am installing the latest Warp3D from Aminet.

I have already installed WarpOS -warp.library- ver 5.1

I am using CyberGraphX 4 plus updates. I have a BVision Gfx card. I have made a new 320x200 8 bit mode to try with FullScreen WipeOUT.

I run the game but it would not run. On the launcher Window the Play button is deactivated and I can not select any ModeID, if I choose to play it on Window mode the Play button gets active but the game hangs.

Have also tried to play it under AmigaOS 4.1 same symptoms, however the game runs in Window mode but VERY SLOW.

I remember I have make it to run on my other 1200PPC some eyars ago but I can not remember how. And this machine is not here right now. -parents house-.

I think that this could be a variable for the ModeID or something that should be set, but I am loosing track in here

any tips?

zipper · 04 June 2012, 19:35

15/16bit screenmode?

CountRaven · 04 June 2012, 22:24

Not actually the screenmode I run my miggy at is 24bit, should I make any 16 bit modes?

I make a 320x200 16bit mode and now I am able to select. But when I do the game would go full screen and then crash

Mad-Matt · 04 June 2012, 22:48

you need a 640x480 x16 mode if you want to play it hardware accelerated.

CountRaven · 04 June 2012, 23:06

Actually the HardWare selection is de activated, same on 640x480 mode selection.

Michael · 12 January 2013, 19:38

Try the older v4.0 warp.library not the warp.library ver 5.1
In fact a lot of things work with 4.0 and fail with later version on my machine.
It's funny but with a some combinations of libs you can get even FusionPPC to load on A1200 which is supposed to be impossible (sadly it was never fixed for A1200 and there is graphics corruption)

One more thing to note on WipeOut, is you have to use a older version of Warp3D if you would like to see the game without tail graphics problems.

Was there ever an update to fix comparability issue with later Warp3D releases ?
(some texture rendering mode was changed)

Bamiga2002 · 12 January 2013, 19:47

The tail problem AFAIK is with BVision only, using older warp.library v4 should correct the problem. With Mediator + Voodoo there is no tail problem.

Michael · 13 January 2013, 15:51

In fact, I am using the 4.0 warp.library, since 5.1 is buggy .
And if I remember correctly, this does not effect the tails, but the WARP3D library does.
V4.0 comes with the games and works nicely, but 4.2 update has the problem ;-(

Hoping to see a patch! I guess now = never :-(

But it's a great for hardware demonstration and FPS benchmark too.

640x480x16b mode gives ~15 FPS average (10-30 FPS during play) in full detail
and 320x240 rolls silky smooth above 30 FPS all the time.

Triple buffering and 16bit modes seems to be 2 FPS better then then same in 15 bit or DoubleBuffer, or window.

04 June 2012, 19:23	#1
CountRaven Registered User Join Date: Jun 2012 Location: Rethymno, Crete, GREECE Posts: 32	WipeOut 2097 Hello to everyone! I have been trying to run WipeOut 2097 on my A1200 PPC Setup. I am installing the game from the CD, I am installing the latest Warp3D from Aminet. I have already installed WarpOS -warp.library- ver 5.1 I am using CyberGraphX 4 plus updates. I have a BVision Gfx card. I have made a new 320x200 8 bit mode to try with FullScreen WipeOUT. I run the game but it would not run. On the launcher Window the Play button is deactivated and I can not select any ModeID, if I choose to play it on Window mode the Play button gets active but the game hangs. Have also tried to play it under AmigaOS 4.1 same symptoms, however the game runs in Window mode but VERY SLOW. I remember I have make it to run on my other 1200PPC some eyars ago but I can not remember how. And this machine is not here right now. -parents house-. I think that this could be a variable for the ModeID or something that should be set, but I am loosing track in here any tips? Last edited by CountRaven; 05 June 2012 at 15:40.

04 June 2012, 22:24	#3
CountRaven Registered User Join Date: Jun 2012 Location: Rethymno, Crete, GREECE Posts: 32	Not actually the screenmode I run my miggy at is 24bit, should I make any 16 bit modes? I make a 320x200 16bit mode and now I am able to select. But when I do the game would go full screen and then crash Last edited by CountRaven; 04 June 2012 at 22:40.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Will we ever be playing Wipeout 2097 on WinUAE as smooth as a Sega Saturn?	ImmortalA1000	Amiga scene	31	09 June 2021 02:02
Wipeout 2097	Dreamcast270mhz	request.Old Rare Games	8	12 January 2013 20:09
Amiga WipeOut 2097 and Quake II Available	amigakit.com	MarketPlace	18	21 April 2009 14:32
WipeOut XL (2097)	Frog	Retrogaming General Discussion	29	01 December 2007 16:08
Wipeout 2097	^^Snoop^^	request.Old Rare Games	6	03 December 2002 05:00

04 June 2012, 19:35	#2
zipper Registered User Join Date: Mar 2004 Location: finland Posts: 1,838	15/16bit screenmode?

04 June 2012, 22:48	#4
Mad-Matt Longplayer Join Date: Jan 2005 Location: Lincoln / UK Age: 44 Posts: 1,848	you need a 640x480 x16 mode if you want to play it hardware accelerated.

04 June 2012, 23:06	#5
CountRaven Registered User Join Date: Jun 2012 Location: Rethymno, Crete, GREECE Posts: 32	Actually the HardWare selection is de activated, same on 640x480 mode selection.

12 January 2013, 19:38	#6
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 840	Try the older v4.0 warp.library not the warp.library ver 5.1 In fact a lot of things work with 4.0 and fail with later version on my machine. It's funny but with a some combinations of libs you can get even FusionPPC to load on A1200 which is supposed to be impossible (sadly it was never fixed for A1200 and there is graphics corruption) One more thing to note on WipeOut, is you have to use a older version of Warp3D if you would like to see the game without tail graphics problems. Was there ever an update to fix comparability issue with later Warp3D releases ? (some texture rendering mode was changed)

12 January 2013, 19:47	#7
Bamiga2002 BlizzardPPC'less Join Date: May 2004 Location: Finland Age: 46 Posts: 3,210	The tail problem AFAIK is with BVision only, using older warp.library v4 should correct the problem. With Mediator + Voodoo there is no tail problem.

13 January 2013, 15:51	#8
Michael A1260T/PPC/BV/SCSI/NET Join Date: Jan 2013 Location: Moscow / Russia Posts: 840	In fact, I am using the 4.0 warp.library, since 5.1 is buggy . And if I remember correctly, this does not effect the tails, but the WARP3D library does. V4.0 comes with the games and works nicely, but 4.2 update has the problem ;-( Hoping to see a patch! I guess now = never :-( But it's a great for hardware demonstration and FPS benchmark too. 640x480x16b mode gives ~15 FPS average (10-30 FPS during play) in full detail and 320x240 rolls silky smooth above 30 FPS all the time. Triple buffering and 16bit modes seems to be 2 FPS better then then same in 15 bit or DoubleBuffer, or window.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)