Problems with Warp3DV4
----------------------

Permedia 2:

To use Warp3D in conjunction with Permedia2 based graphics boards
(CyberVisionPPC/BVisionPPC) you have to make sure to have the
latest CyberGrafics version installed. The following files
are the minimal versions that are reported to work with Warp3D:

CyberGfx V3 :

cgxsystem.library 41.21beta1
CVisionPPC 2.7 beta 3

CyberGfx V4 :

cgxsystem.library 42.0
CVisionPPC 4.0 beta 4 (CVisionPPC)
BVisionPPC 4.0 beta 4 (BVisionPPC)


It is also necessary to set some CyberGraphx tooltypes correctly.

DRAGGING=NO
BITMAPCACHE=YES

If you use a CyberVision3D and CGFX V3, then these tooltypes have
no effect on Warp3D. You have to set MULTIMEDIAMEM=YES for this.
It is recommended that you update your CGX V3 to V4, it's
much more stable and system compliant.


A lot of demos use V39 compliant multibuffering for displaying their
animation. Some ASL patches (like MagicASL) have a negative effect
on V39 multibuffering, therefore you should disable these patches
to see, if it solves the multibuffering problems.

Patches like MagicMenu have a negative effect on the menus, which
are displayed for V39-multibuffering-compliant demos, please disable
these patches to see, if the problems get solved.

In general, if you encounter problems, please temporarly remove any
patches and try the W3D software again.


To make the PPC version Warp3D/StormMesa working you need a perfectly
working WarpUp installation. Make sure to have the following env
variables set:

powerpc/gfxaddr $e0000000       (for CVisionPPC/BVisionPPC)
powerpc/force 1                 (for CVisionPPC/BVIsionPPC)
powerpc/terminator 2            (for BlizzardPPC boards)

Sometimes setting powerpc/memprot to 0 might also solve some problems.


It has been reported by some people that the Permedia2 chips sometimes
get very hot, and fail to work due to overheating. Installing a cooling
device, such as a fan, solved those problems. These crashes are mostly
random in nature, so if this happens frequently when using Warp3D, this
may be the cause.


Voodoo 3:

The Voodoo 3 driver is reported to work with the following revisions
of the graphics board drivers:

Picasso 96:     Picasso96API.library    2.300
		rtg.library             40.3992
		3dfxVoodoo.chip         6.375

		Prometheus.card         6.51

CyberGraphics4: soon

To use the PPC driver in conjunction with WarpUp software, the following
environment variables should be set:
PowerPC/force 1
PowerPC/gfxaddr $xxxxxxxx

The installer will try to figure out the gfxaddr setting. However, if that fails,
here's how to do it manually...

Prometheus
Run PrmScan, and find the Voodoo:

	Prmscan 1.2 © 2001 Matay.
	PCI cards listing:
	-------------------------------------------------
	Vendor: 3dfx Interactive Inc
	Device: Voodoo3 All Voodoo3 chips, 3000
	Revision: 1.
	Device class 03, subclass 00.
	Address range: 4E000000 - 4FFFFFFF.
    --> Address range: 4C000000 - 4DFFFFFF.
	Address range: 400EFF00 - 400EFFFF.
	64 kB of ROM at 4BFF0000 - 4BFFFFFF.
	-------------------------------------------------

gfxaddr needs to be set to this address, i.e.
setenv PowerPC/gfxaddr $4c000000