Max. 3D texture size??

[maya3d]

Max. 3D texture size: is true??

RAGE 128 M4 x86/SSE 1024 x 1024 x 1024
ATI 8500 512 x 512 x 512
ATI 9700 2048 x 2048 x 2048
Matrox ICD for Parhelia 2048 x 2048 x 2048
GeForce3 TI 500 512 x 512 x 512
GeForce4 TI 4600 512 x 512 x 512
Intel 830M 128 x 128 x 128

[Robbo]

Probably - but if you have over 1gb of texture memory I would be *very* surprised (but wait a few years and of course you will have).

[ehart]

A couple corrections:

RAGE 128 M4 x86/SSE: No 3D texture in HW
ATI Radeon/7000/7500: 512 x 256 x 256
ATI 8500 512 x 512 x 256
ATI 9700 2048 x 2048 x 2048

I would expect the practical limitation on the latter to be less than 512 x 512 x 512 on most systems.

-Evan

[maya3d]

thanks ,
but http://www.delphi3d.net/hardware/listreports.php

[ehart]

I haven't looked into the GLinfo program yet, I am very certain the info I have posted is correct. (I may have the s and t dimensions flipped on one of the parts.)

It does look to me like the Rage128 is incorrectly exporting EXT_texture3D. This is only supported in SW on that chip. I am trying to get that fixed.

I believe elsewhere my information is simply more exact, that what is being examined to produce that table.

-Evan

[maya3d]

many thanks.

[Tom Nuydens]

Evan, the value reported by GLinfo is simply GL_MAX_3D_TEXTURE_SIZE as reported by the drivers.

I don't see how you can get something like 512x512x256, because GL_MAX_3D_TEXTURE_SIZE is specified as being a single value, not three of them. Developers must always be able to assume that the returned number applies to the width, height and depth of the texture. If this isn't the case for your HW or drivers, then your HW or drivers don't conform to the OpenGL specification.

As for the Rage128, I'm sure they don't support it in hardware, but if they have a GL 1.2 driver then they do support it in software. That's why GLinfo detects it and reports the maximum 3D texture size anyway.

-- Tom

[This message has been edited by Tom Nuydens (edited 12-05-2002).]

[MichaelK]

Originally posted by maya3d:
thanks ,
but http://www.delphi3d.net/hardware/listreports.php

this registry says that my gf2mx supports 64x64x64 3d textures. but the GL_EXT_texture3D string isnt exported. does it mean that on my system 3d textures are in software? am i right?

[Tom Nuydens]

Originally posted by MichaelK:
this registry says that my gf2mx supports 64x64x64 3d textures. but the GL_EXT_texture3D string isnt exported. does it mean that on my system 3d textures are in software? am i right?

Yes. The unofficial policy is not to expose GL_EXT_texture3D unless hardware 3D texture support is available. Unfortunately this still doesn't give you any real guarantees, e.g. in the case of the Rage128 mentioned above by Evan.

-- Tom

[ehart]

Tom,

Thanks for clearing up where the number comes from. I had suspected as much, but I had no way to know for certain.

Originally posted by Tom Nuydens:

I don't see how you can get something like 512x512x256, because GL_MAX_3D_TEXTURE_SIZE is specified as being a single value, not three of them. Developers must always be able to assume that the returned number applies to the width, height and depth of the texture. If this isn't the case for your HW or drivers, then your HW or drivers don't conform to the OpenGL specification.
[/B]

While it is true that the parameter is a single value, this is not what the GL spec says the reported max means. I have gone through the paragraph a couple times and it refers to the "maximum allowable width, height, or depth". The chapter for the 2D query seems to be written the other way. This means that those implementations are indeed reporting the correct value.

The way users should determine the largest size for indivual dimensions/formats is via the texture proxy mechanism.

-Evan

[Edit: UBB screw-up]


[This message has been edited by ehart (edited 12-05-2002).]

[This message has been edited by ehart (edited 12-05-2002).]