From: Tim Gion (tcg3j++at++cs.virginia.edu)
Date: 02/23/2000 12:00:53
On Wed, 23 Feb 2000, Marcin Romaszewicz wrote:
> First, you don't need to call pfTexture::init. Performer automatically
> does this when you call pfInit(). The init function is a static
Understood.
> Secondly, if you're using the texture in a draw callback without putting
> it into a geostate, you should call pfTexture::format so the appropriate
> glTexImage calls get made
I've tried calling format() but it bombs out. It says that it's trying to
realloc() on 0 bytes. Naturally that returns NULL.
> In your example, what does the getImage function return for the value of
> comp? It should be a value 1-4, otherwise you get that error. The strange
.
.
> to mind. If the value of comp is indeed 0 after your call to loadFile,
> then that file is being loaded incorrectly or is corrupt. If the value of
> comp is not 0, then then odds are that you have a call to
> pfTexture::setImage somewhere that is sending the wrong number of
> components (this is the only way to change the value of comp without
> loading a file)
The value of comp is 3. I actually just moved all the texture
loading stuff before vgConfigSys() and now I no longer get the 0
components warning. The texture's size is intact now. However, it still
fails to display.
Guess I'm getting closer. :)
Tim
Tim Gion
tcg3j++at++cs.virginia.edu (fastest) or gion++at++cs.virginia.edu
http://www.cs.virginia.edu/~tcg3j
This archive was generated by hypermail 2b29 : Wed Feb 23 2000 - 12:01:24 PST