Hansong Zhang (hzhang++at++torque.engr.sgi.com)
Thu, 27 Aug 1998 14:27:12 -0700 (PDT)
Texworm uses automatically generated texture coordinates (SPHERE_MAP).
You may want to modify the opengl/glut programs you wrote before to use
SPHERE_MAP, and see what happens.
On Thu, 27 Aug 1998, Andy Beall wrote:
> I've just found a curious behavior in which texture mapping seems to work
> differently on different machines that vary in hardware configuration. An a
> benchmark program, I'm using TEXWORM from the Optimizer NT distribution,
> that in turn accesses a texture file called TEX.RGB. All my machines are
> running NT 4.0.
>
> On two different Intergraph machines in our lab TEXWORM works fine. Both of
> these have hardware texture acceleration.
>
> On a PII/300, the textures appear but are not perspectively corrected (or at
> least I think that's what's going on). This machine has no OGL hardware
> acceleration.
>
> On a PI/180, the textures don't even appear--polygons are white shaded (the
> program does find the texture image file, however). This machine also has
> no OGL hardware acceleration.
>
> Both of these machines renders textures fine using OGL/glut programs that
> I've written in the past.
>
> I've tried adding the following program statement:
>
> ctx->setTexMode(csContext::PERSP_TEX);
>
> but that hasn't changed or corrected the behavior.
>
>
> Does anyone know if Cosmo/Optimizer chooses render parameters based on
> hardware configuration, and if so how do I reset them. Or is something else
> entirely going on?
>
> Thanks for any tips,
> Andy-
>
>
> +-----------------------------------------------------------------------+
> | Andy Beall MIT, Man Vehicle Lab |
> | http://web.mit.edu/beall/www/ 70 Vassar St., 37-151 |
> | Cambridge, MA 02139 |
> | 617/253-7758 |
> +-----------------------------------------------------------------------+
>
This archive was generated by hypermail 2.0b2 on Thu Aug 27 1998 - 14:27:15 PDT