[Shallows-devel] Fwd: NVIDIA Updated Your Incident Report (187626)

[Johan S. <joh...@gm...>]

---------- Forwarded message ----------
From: nv...@nv... <nv...@nv...>
Date: Sep 6, 2005 6:41 PM
Subject: NVIDIA Updated Your Incident Report (187626)
To: jo...@st...

Please do not reply to this message
-------------------------------------------------------------------
The following items have been modified for this Bug:
- A new Comment has been added

-------------------------------------------------------------------
Bug Information
-------------------------------------------------------------------
Requester: Johan Simon Seland
Bug ID: 187626
Date: 9/6/2005 5:42:55 AM
Company/Division: Researcher
Severity: High
Synopsis: Programmer question: calling glReadBuffer(GL_NONE) without FBO.
Description: Calling glReadBuffer(GL_NONE) causes a gl error,=20
GL_INVALID_ENUM, when no framebuffer object is used.
The same statement called when a framebuffer object is attached causes no=
=20
error. As far as I have understood the spec (EXT_framebuffer_object) this i=
s=20
not the correct behaviour of the driver.


-------------------- Additional Information ------------------------
Computer Type: PC
System Model Type:
System Model Number:
CPU Type:
Video Memory Type:
Chipset Mfg:
Chipset Type:
Sound Card:
CPU Speed:
Network:
Modem:
North Bridge:
South Bridge:
TV Encoder:
Bus Type: AGP
OS Language:
Application: Shallows
(www.sf.net/projects/shallows(<http://www.sf.net/projects/shallows(>
Driver Version: 1.0-7676
System BIOS Version:
Video BIOS Mfg:
Video BIOS Version:
Direct X Version:
Monitor Type:
Monitor 1:
Monitor 2:
Monitor 3:
Video 1:
Video 2:
Video 3:
Resolution:
Color Depth:
Products: GeForce 6800 GT
Application Version: Pre-release
Application Setting:
Multithreaded Application: no
Other open applications:
Release: Beta
OS Details: Suse 9.2
Problem Category: Other
How often does problem occur:
Video Memory Size:
CPUs (single or multi):
RAM (amount & type):
AGP Aperture Size:

-------------------------------------------------------------------
Latest Comment update from NVIDIA (9/6/2005 9:41:38 AM):
Johan,
After review by development, we do not believe that this is a bug, as the=
=20
behavior that you are reporting is correct per the specification. The=20
following is cited from version #114 of EXT_framebuffer_object. (the latest=
=20
published version at the moment):

"The command:

void ReadBuffer( enum src );

takes a symbolic constant as argument. <src> must be one of the
..
Further, the acceptable values for <src> depend on
whether the GL is using the default window-system-provided
framebuffer (i.e., FRAMEBUFFER_BINDING_EXT is zero), or an
application-created framebuffer object (i.e.,
FRAMEBUFFER_BINDING_EXT is non-zero).
..

When the GL is using the default window-system-provided framebuffer,
<src> must be one of the values listed in table 4.4. ...

Here is table 4.4. Note that NONE is not listed in table 4.4.

symbolic front front back back aux
constant left right left right i
NONE
FRONT_LEFT X
FRONT_RIGHT X
BACK_LEFT X
BACK_RIGHT X
FRONT X X
BACK X X
LEFT X X
RIGHT X X
FRONT_AND_BACK X X X X
AUXi X
Table 4.4: Arguments to DrawBuffer and the buffers that they indicate.

Please let me know if you have any further questions.

Thanks,
Lonni


--=20
Help a man with his math problems and you get him off your back for a day.
Teach a man math, and you scare him off for the rest of your life.

Regards Johan Seland
PhD Student
Center of Mathematics for Applications
University of Oslo