[vtkusers] Huge textures? round 2

[Jim Moore]

Hi John (and vtkusers),

Did you ever get an answer on this?   I am facing exactly the same issue...
It is DEFINITELY
a pain to break up images to satisfy this apparently artificial limitation.
If I figure it out, I'll be sure and let you know what I find.

Jim




John Biddiscombe wrote:

> On all machines I've tested so far (NT) the max texture size has never
> exceeded 1024 (most are 512) (as returned by glGet...MAX_TEX...or whatever
> it is).
>
> Is there any way around breaking a large (e.g. terrain mesh) into small
> pieces and stuffing each piece into a seperate actor and assigning each
> actor a different "piece" of texture.
>
> There are a number of reasons why I don't want to break up data
> a) It's a pain breaking the data up
> b) I want the data in one piece for getCell reasons and don't want n copies
> of bits of it lying around
> c) performance (display lists as mentioned in previous post)
> d) It's a less elegant way of doing the job.
>
> How about more complex texture coordinates? texture arrays and subID's ???
>
> John B
>
> --------------------------------------------------------------------
> This is the private VTK discussion list. Please keep messages on-topic.
> Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
> To UNSUBSCRIBE, send message body containing "unsubscribe vtkusers" to
> <majordomo at public.kitware.com>. For help, send message body containing
> "info vtkusers" to the same address.
> --------------------------------------------------------------------

--
  ------------------------------------------------------------------------
James C Moore, Ph.D.
ph: 614-267-8429 jmoore at qn.net
direct linux consulting