[gl4java-usergroup] (no subject)

[<pat...@lm...>]

Microsoft Mail Internet Headers Version 2.0
Message-ID: <3E8...@lm...>
Date: Mon, 31 Mar 2003 13:30:04 -0500
From: Mark Montana <pat...@lm...>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: gl4...@li...
Subject: Capabilities of GL4Java state machine?
References: <200...@ml...>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Return-Path: pat...@lm...
X-OriginalArrivalTime: 31 Mar 2003 18:30:04.0838 (UTC) FILETIME=[8C82BC60:01C2F7B3]

I reduced the parameters in my GLCapabilities from:

Red: 8 bits
Green: 8 bits
Blue: 8 bits
Depth: 12 bits

down to:

Red: 2 bits
Green: 2 bits
Blue: 2 bits
Depth: 2 bits

And I still get a maximum supported texture size of 1024. (Granted, I don't need
any depth bits now, but I will be moving to a quasi-3D display soon). My guess is
that the card doesn't even offer a graphic that is so simplistic, and it is giving
me the nearest match, which has the same capabilities as before.

Here is something interesting that is related. The Java3D portion of our
application is reporting a version number (version of what...we have no idea) that
is 1.4 on the GeForce 2 Ultra machine, and 1.2 on the Wildcat III 6110 machine. Is
OpenGL 1.4 out yet? Could this be a OpenGL version number? (we are using Java3D
built on OpenGL). I do have the latest drivers for my Wildcat III, so I would
think it has the latest OpenGL. Of course, this version number feature is poorly
documented in Java3D, so it could be referring to something else.

"Kenneth B. Russell" wrote:

> > Should have included the following in my last posting... (again, I thank you
> > for any help you can provide)
> >
> > When Java3D queries the max-supported-texture-size on the Wildcat III 6110
> > machine (from within our application), it gets an answer of 2048. When
> > GL4Java queries this value with glGetIntegerv(GL_MAX_TEXTURE_SIZE, ...) from
> > within our same application on the same machine, it gets an answer of 1024.
> >
> > What is up with that? Could the GLCapabilities be used to increase the max
> > supported texture size when the GLContext (state machine) is being created?
> > Is GL4Java hardcoding this ceiling of 1024?
>
> There's nothing in GL4Java imposing this limit; the only thing I
> can think of is some difference in the capabilities of your GL
> context (color depth, depth buffer depth, etc.)
>
> -Ken