VBGamer |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
RE: Blue filter... The Gilb (10 replies, 0 views) (2000-May-27) Yeop - it certainly look as though all they've really done is alpha blend a blue surface over the top of the screen with varying opacity based on time.
I would definitely use the last method suggested by Rag On A Stick... True alpha blending through software, in my experience, is just simply too slow. Admittedly the D3D method would produce the requirement of a 3D card in a 2D game, but I personally am going to be using D3D hardware support more and more in my 2D apps.
The main push of the 3D industry at the moment is to blur the distinction between 2D and 3D (Thus 5D cards).
Software alpha blending is not fast enough. VB needs all the speed it can get - so use D3D alpha blending, mmkay? :-)
|