Difference between revisions of "DEPTHBUFFER"

From QB64 Wiki
Jump to navigation Jump to search
imported>Clippy
m
imported>Clippy
m
Line 16: Line 16:
''Photo:''
''Photo:''
Here's another screenshot which shows rending to 2d images then rendering to the screen. The difference is that QB64 is adding a hardware depth-buffer to the destination images on demand when and if it requires one. Note which image is not using a depth-buffer. In QB64 a depth-buffer is implied unless you specifically state not to use one.
Here's another screenshot which shows rending to 2d images then rendering to the screen. The difference is that QB64 is adding a hardware depth-buffer to the destination images on demand when and if it requires one. Note which image is not using a depth-buffer. In QB64 a depth-buffer is implied unless you specifically state not to use one.
http://i301.photobucket.com/albums/nn53/burger2227/YUNEEEDaDEPTHBUFFER.png
 
[http://i301.photobucket.com/albums/nn53/burger2227/YUNEEEDaDEPTHBUFFER.png You need a _DEPTHBUFFER]





Revision as of 19:33, 10 August 2014

The _DEPTHBUFFER statement turns depth buffering ON or OFF, LOCKs or _CLEARS buffering


Syntax

_DEPTHBUFFER {ON|OFF|LOCK|_CLEAR}[,handle]


Description

  • Buffering can be turned ON or OFF, LOCKed or _CLEARed. Default is ON, so ON should only be used if OFF was previously used.
  • An image handle is optional. _DEST could also be used.


Photo: Here's another screenshot which shows rending to 2d images then rendering to the screen. The difference is that QB64 is adding a hardware depth-buffer to the destination images on demand when and if it requires one. Note which image is not using a depth-buffer. In QB64 a depth-buffer is implied unless you specifically state not to use one.

You need a _DEPTHBUFFER


See also:



Navigation:
Keyword Reference - Alphabetical
Keyword Reference - By Usage
Main Wiki Page