1D Textures

[andyc]

Hi,

I was about to put in a feature request ticket for 1D textures but saw
that this has already been rejected/deleted twice (see:
https://sourceforge.net/tracker/index.php?func=detail&aid=1748565&group_id=76879&atid=548565).
Using a k by 1 2d texture in place of a k-long 1D one feels ugly.
Would it be objectionable if I raise the issue again or would the
ticket just be closed?

A.

[zybx]

I'm also having these two problems:

1. 3D textures are not necessarily power of two but G3D prevents me to
create NPOT 3D textures. (this should be a bug)

2. 1D textures are often used in volume rendering as transfer
functions. (G3D does not provide 1D texture dimensions)

On Oct 18, 9:18 am, andyc <ah...@btinternet.com> wrote:
> Hi,
>
> I was about to put in a feature request ticket for 1D textures but saw

> that this has already been rejected/deleted twice (see:https://sourceforge.net/tracker/index.php?func=detail&aid=1748565&gro...).

[Andrew Cox]

There is a third to complete the list:

On Thu, 2009-10-22 at 17:11 -0700, zybx wrote:
> I'm also having these two problems:
>
> 1. 3D textures are not necessarily power of two but G3D prevents me to
> create NPOT 3D textures. (this should be a bug)
>
> 2. 1D textures are often used in volume rendering as transfer
> functions. (G3D does not provide 1D texture dimensions)
>

3. Array Textures. These are different from the more general uniform
array issues as there are distinct new sampler types for each kind
of array texture rather than just using the subscript syntax. They
are also bundled into one texture object rather each level/element
being bound to a distinct texture_unit->texture_object chain as
orthogonality with other array types would suggest.

I could do some work on these things but I'm still new to the project
and to open source development in general (to my shame).

Best,
Andrew

[zybx]

I hope these features will be supported in the future. But I didn't
see them in 8.00 beta2.

> > > A.- 隐藏被引用文字 -
>
> - 显示引用的文字 -