| [AD] [ alleg-Bugs-2665155 ] ALLEGRO_DEPTH_BUFFER |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Bugs item #2665155, was opened at 2009-03-05 13:33
Message generated for change (Comment added) made by elias
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2665155&group_id=5665
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 4.9
>Status: Closed
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Elias Pschernig (elias)
Assigned to: Nobody/Anonymous (nobody)
Summary: ALLEGRO_DEPTH_BUFFER
Initial Comment:
When you want a depth-buffer, you usually don't care about the resolution (as long as it is HW accelerated, only 16 bits are better than 32 or floating point). Right now this is not possible with Allegro, we likely need a new ALLEGRO_DEPTH_BUFFER option which can be set to ALLEGRO_REQUIRE to require a display to have a depth buffer (but not care about the depth).
----------------------------------------------------------------------
>Comment By: Elias Pschernig (elias)
Date: 2010-06-10 10:56
Message:
Yes, just using SUGGEST with 16 should work in my example... if will give
you the first available of 16, 24, 32. No need for even more fine control
really.
----------------------------------------------------------------------
Comment By: Milan Mimica (mmimica)
Date: 2009-03-05 19:55
Message:
Not strictly necessary once we have the ability to retrieve supported
values, but it would still be convenient.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105665&aid=2665155&group_id=5665