mesa3d-users

[Mesa3d-users] (no subject)

[david b. <sup...@ho...>]

I want to know if it is possible to use a image in the format jpg or bmp
for texturing .
if it is possible how can I do this


________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

[Mesa3d-users] Importing modelled objects

[Simon L. <lem...@ya...>]

Hi,
	I was wondering if there were any utility capable of translating any 3D format
(I don't know them very much, but the ones 3DStudio could output for example..)
into GL C code?
glBegin(GL_POLYGON);
glVertex3f(...);
etc...

Is this possible?

Thanks,
	Simon

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [Mesa3d-users] Mesa 3.1 & 3.2 with 3dfx Voodoo2 library notworking.

[Bill M. <Bil...@wc...>]

Well here's the ldd for my app and the fire demo out of the demos (3.2)
folder.  Both don't use the 3d hardware but the fire one actually draws into
the window.  I'm guessing its defaulting to SW.  I included my environment
variables I have.  Is there a change I missed?  Also is listed the packages
to get my 3d hardware to work.

Anyone else out there using Mesa3.2 & Voodoo2 I can bounce questions off
of??
Bill.


ENVIRONMENT VARIABLES...
[bmcclint@bm0054 glcarspin]$ set
...
FX_GLIDE_SWAPINTERVAL=1
MESA_GLX_FX=fullscreen
...

INSTALLED PACKAGES...
Device3Dfx-2.3-1.src.rpm
Glide_V2-2_53-1_i386_glibc.rpm
Glide2x_SDK-2.1-3.i386.rpm
Mesa*-3.*.tar.gz  (3.0 working, 3.1&2 not)


LDD...
[bmcclint@bm0054 glcarspin]$ ldd glcarspin
 libm.so.6 => /lib/libm.so.6 (0x4001b000)
 libglut.so.3 => /usr/X11R6/lib/libglut.so.3 (0x40038000)
 libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x4006a000)
 libGLU.so.1 => /usr/X11R6/lib/libGLU.so.1 (0x401d2000)
 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x401ef000)
 libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40293000)
 libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x4029f000)
 libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x402b2000)
 libc.so.6 => /lib/libc.so.6 (0x402ba000)
 libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x403af000)
 libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x403ba000)
 libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x403d1000)
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


[bmcclint@bm0054 demos]$ ldd fire
 libglut.so.3 => /usr/X11R6/lib/libglut.so.3 (0x4001b000)
 libGLU.so.1 => /usr/X11R6/lib/libGLU.so.1 (0x4004d000)
 libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0x40069000)
 libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x401d1000)
 libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x4021c000)
 libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x40224000)
 libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40237000)
 libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40243000)
 libm.so.6 => /lib/libm.so.6 (0x402e7000)
 libc.so.6 => /lib/libc.so.6 (0x40304000)
 libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x403fa000)
 libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x40404000)
 /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


Brian Paul wrote:

> Bill McClintock wrote:
> >
> > I've been fighting this for some time now but I have given up.
> >
> > I have written several GL apps using Mesa 3.0 and a 3dfx Voodoo2 card
> > and all has been going well.  When 3.1 & 3.2 came out I decided to
> > upgrade.  Well all builds ok but I don't get any output when linking to
> > the new libraries.
> >
> > DETAILS:
> >  Using Mesa 3.0...make linux-glide or linux-386-glide.
> >   Build successful.
> >      Makes libMesaGL, libMesaGLU and libglut.
> >   Write and make app...All works well.  Hardware support and a great
> > frame rate.
> >
> >  Using Mesa 3.1...make linux-glide or linux-386-glide.
> >   Build successful.
> >      Makes libGL, libGLU and libglut.
> >   Rebuild app with the new libraries.  Seems to run but no output.  I
> > get an X frame and CPU pegs.  At exit app reports a slow but not
> > incredibly slow frame rate.  I am guessing that the hardware is setup
> > and call are being accepted.  HMMM.  Relink with old libs...works like
> > before.
> >
> >  Using Mesa 3.2...make linux-glide or linux-386-glide.
> >   Build successful.
> >      Makes libGL, libGLU and libglut.
> >   Same results as 3.1.
> >
> > I would like to use 3.2 and future releases but I just can't figure out
> > what is up.  My code is all to the OpenGL 1.1 standard so did something
> > change in the init calls to Mesa?
> >
> > Anyone have any ideas?  Please!!!
>
> Use ldd to be absolutely sure what you're linking with.  Other than
> that I don't know what to say.  No one else has reported a problem
> like this.
>
> -Brian

--
Bill McClintock - EDMS App/Web Development
   MCIWorldcom - Colorado Springs (GOG)
   VNet:622-0054   Local:(719)265-0054
     Pager:1-800-PAGEMCI PIN#1686599
     EMail:Bil...@wc...
              AOLIM:bm0054

Re: [Mesa3d-users] Mesa 3.1 & 3.2 with 3dfx Voodoo2 library not working.

[Brian P. <br...@pr...>]

Bill McClintock wrote:
> 
> I've been fighting this for some time now but I have given up.
> 
> I have written several GL apps using Mesa 3.0 and a 3dfx Voodoo2 card
> and all has been going well.  When 3.1 & 3.2 came out I decided to
> upgrade.  Well all builds ok but I don't get any output when linking to
> the new libraries.
> 
> DETAILS:
>  Using Mesa 3.0...make linux-glide or linux-386-glide.
>   Build successful.
>      Makes libMesaGL, libMesaGLU and libglut.
>   Write and make app...All works well.  Hardware support and a great
> frame rate.
> 
>  Using Mesa 3.1...make linux-glide or linux-386-glide.
>   Build successful.
>      Makes libGL, libGLU and libglut.
>   Rebuild app with the new libraries.  Seems to run but no output.  I
> get an X frame and CPU pegs.  At exit app reports a slow but not
> incredibly slow frame rate.  I am guessing that the hardware is setup
> and call are being accepted.  HMMM.  Relink with old libs...works like
> before.
> 
>  Using Mesa 3.2...make linux-glide or linux-386-glide.
>   Build successful.
>      Makes libGL, libGLU and libglut.
>   Same results as 3.1.
> 
> I would like to use 3.2 and future releases but I just can't figure out
> what is up.  My code is all to the OpenGL 1.1 standard so did something
> change in the init calls to Mesa?
> 
> Anyone have any ideas?  Please!!!

Use ldd to be absolutely sure what you're linking with.  Other than
that I don't know what to say.  No one else has reported a problem
like this.

-Brian

Re: [Mesa3d-users] GLU 1.2 tesselator bugs ?

[Olivier M. <Oli...@cy...>]

Stephen J Baker wrote:
> 
> On Wed, 14 Jun 2000, Olivier Michel wrote:
> 
> > I recently moved from Mesa-3.0 to Mesa-3.2 and I had to update the GLU
> > tesselator from 1.0 to 1.2. Although I followed the guidelines explained
> > in the Red Book, the results weren't good at all:
> > Some faces were reversed (wong side) and I got many crashes in glu
> > library (apparently memory leaks) when the vertices of a non-convex
> > polygon didn't lie exactly in the same plane.
> >
> > I could identify more precisely one bug:
> >
> > The gluTessNormal is ignored for re-orienting vertices whereas it should
> > be used (as described in the OpenGL Reference and User manuals). This
> > makes some faces appear on the wrong side. I found a workaround for this
> > bug by calling glCullFace(GL_FRONT) just before drawing a face for which
> > the normal direction is negative (and should reverse the vertice order).
> > But this is an ugly workaround (as often).
> >
> > I am now trying to identify better the crash problems.
> 
> Have you tried the same code using the GLU from the SGI OpenGL Reference
> Implementation?    It would certainly be interesting to discover if it
> exhibits the same problem...and might give you a reasonable work-around
> in the short term.

I didn't know that existed! I finally found it on http://oss.sgi.com,
installed and ran.
I only installed the /usr/include/glu.h and /usr/lib/libGLU.so and it
worked fine together with the Mesa libGL.so. So, I think now that it's a
bug in Mesa GLU since unlike with Mesa GLU, the behavior observed with
the ogl-sample GLU was correct (the vertice order is good, it takes into
account the gluTessNormal direction as expected). Moreover, the
ogl-sample GLU never crashes or enter endless loops while the Mesa-3.2
GLU does it too often... I found the Mesa-3.0 tesselator (based on GLU
1.0) much more stable.

However, I don't feel like I would able to fix such bugs in Mesa-3.2
since I didn't write the original code and don't know anything about
tesselation algorithms. I will anyhow subscribe to the Mesa-devel
mailing list and try to find out some help to fix this...

Maybe it would be more easy to use the GLU from ogl-sample (one problem
is that it currently need libstdc++, which I don't know why). I didn't
read the license from SGI about their ogl-sample, but would it be
legally possible and useful to copy/paste the SGI ogl-sample GLU to Mesa
GLU since the Mesa GLU appear to be really buggy ?

-Olivier

[Mesa3d-users] Mesa 3.1 & 3.2 with 3dfx Voodoo2 library not working.

[Bill M. <Bil...@wc...>]

I've been fighting this for some time now but I have given up.

I have written several GL apps using Mesa 3.0 and a 3dfx Voodoo2 card
and all has been going well.  When 3.1 & 3.2 came out I decided to
upgrade.  Well all builds ok but I don't get any output when linking to
the new libraries.

DETAILS:
 Using Mesa 3.0...make linux-glide or linux-386-glide.
  Build successful.
     Makes libMesaGL, libMesaGLU and libglut.
  Write and make app...All works well.  Hardware support and a great
frame rate.

 Using Mesa 3.1...make linux-glide or linux-386-glide.
  Build successful.
     Makes libGL, libGLU and libglut.
  Rebuild app with the new libraries.  Seems to run but no output.  I
get an X frame and CPU pegs.  At exit app reports a slow but not
incredibly slow frame rate.  I am guessing that the hardware is setup
and call are being accepted.  HMMM.  Relink with old libs...works like
before.

 Using Mesa 3.2...make linux-glide or linux-386-glide.
  Build successful.
     Makes libGL, libGLU and libglut.
  Same results as 3.1.

I would like to use 3.2 and future releases but I just can't figure out
what is up.  My code is all to the OpenGL 1.1 standard so did something
change in the init calls to Mesa?

Anyone have any ideas?  Please!!!

Thanks in advance,

--
Bill McClintock - EDMS App/Web Development
   MCIWorldcom - Colorado Springs (GOG)
   VNet:622-0054   Local:(719)265-0054
     Pager:1-800-PAGEMCI PIN#1686599
     EMail:Bil...@wc...
              AOLIM:bm0054

Re: [Mesa3d-users] GLU 1.2 tesselator bugs ?

[Stephen J B. <sj...@li...>]

On Wed, 14 Jun 2000, Olivier Michel wrote:

> I recently moved from Mesa-3.0 to Mesa-3.2 and I had to update the GLU
> tesselator from 1.0 to 1.2. Although I followed the guidelines explained
> in the Red Book, the results weren't good at all:
> Some faces were reversed (wong side) and I got many crashes in glu
> library (apparently memory leaks) when the vertices of a non-convex
> polygon didn't lie exactly in the same plane.
> 
> I could identify more precisely one bug:
> 
> The gluTessNormal is ignored for re-orienting vertices whereas it should
> be used (as described in the OpenGL Reference and User manuals). This
> makes some faces appear on the wrong side. I found a workaround for this
> bug by calling glCullFace(GL_FRONT) just before drawing a face for which
> the normal direction is negative (and should reverse the vertice order).
> But this is an ugly workaround (as often).
> 
> I am now trying to identify better the crash problems.
 
Have you tried the same code using the GLU from the SGI OpenGL Reference
Implementation?    It would certainly be interesting to discover if it
exhibits the same problem...and might give you a reasonable work-around
in the short term.

Steve Baker                      (817)619-2657 (Vox/Vox-Mail)
L3Com/Link Simulation & Training (817)619-2466 (Fax)
Work: sj...@li...           http://www.link.com
Home: sjb...@ai...       http://web2.airmail.net/sjbaker1

[Mesa3d-users] GLU 1.2 tesselator bugs ?

[Olivier M. <Oli...@cy...>]

Hello,

I recently moved from Mesa-3.0 to Mesa-3.2 and I had to update the GLU
tesselator from 1.0 to 1.2. Although I followed the guidelines explained
in the Red Book, the results weren't good at all:
Some faces were reversed (wong side) and I got many crashes in glu
library (apparently memory leaks) when the vertices of a non-convex
polygon didn't lie exactly in the same plane.

I could identify more precisely one bug:

The gluTessNormal is ignored for re-orienting vertices whereas it should
be used (as described in the OpenGL Reference and User manuals). This
makes some faces appear on the wrong side. I found a workaround for this
bug by calling glCullFace(GL_FRONT) just before drawing a face for which
the normal direction is negative (and should reverse the vertice order).
But this is an ugly workaround (as often).

I am now trying to identify better the crash problems.

Anyone else experienced such problems ? Could fix them easily ?
Who is the main maintainer of GLU ?
Would you like I submit some source code exhibiting the problems ?

Thanks,

-Olivier

[Mesa3d-users] slow 3dfx

[<lk...@in...>]

This is probably a very dumb question but I couldn't figure it out reading
the docs: I've got a voodoo3 card and compiled Mesa-3.2, than tested it
with Mesa/3Dfx/demos/tunnel. However it's soo slow, (1 frame every 3-5
seconds) My X-Server 3.3.5 doesn't seems to have a GLX extension but..?

This is the output from tunnel:
> export MESA_GLX_FX=fullscreen
> ./tunnel

Tunnel V1.5
Written by David Bucciarelli (tec...@pl...)
MMX cpu detected.
3Dnow cpu detected.
video memory unprotecting
grSstWinOpen( win 0 res 7 ref 3 fmt 1
              org 1 ncol 2 naux 1 )
 ==> 0
voodoo 0, wid 640 height 480 hack: usable 0 active 0
	       
Do I need a X server with GLX extension (and where can I get a .rpm of it?)
or what's wrong? What can I do to enhance/tune the performance of OpenGL
stuff especially for 3Dfx cards and quake2? 

thanks lothar

[Mesa3d-users] Greetings,

[Johan J. <jo...@jh...>]

Greetings,

  This is just a short message to say 'I'm here !' :))

  I do have a couple of questions havn't after a cursory look found the
answers ,
  but I'll post the Q's here after I've done a little more research  :)

  Till later
-----------------
  Johan Jordaan
        Dask

[Mesa3d-users] Re: Cannot find libraries while compiling (Was: Re: [Mesa3d-users] Newbie question)

[Simos X. <S.X...@rh...>]

On Sun, 11 Jun 2000, THeL0RD/2k wrote:

> Hi all,
> 
> I'm trying to compile mesa demos (make check) and i always get this
> message "/usr/i486-suse-linux/bin/ld : cannot find -lXext" and exit.

It says it cannot find the library 'libXext.so.*' or 'libXext.a'.
Usually this resides in /usr/lib or /usr/local/lib. Try to look
for it. (I think it's an X library, location: /usr/X11R6/lib, and perhaps 
while installing SuSE, you missed installing it...). 
If you find it, you can add the directory it is in, using the option
-L/usr/X11R6/lib for example, to the gcc compiler.

> Also when i run an already compiled demo (ie GLUT demos), I always get
> "GLUT : fatal error : could not open display"
The application checks the environment variable 'DISPLAY' to see if you 
are running an X at the moment. The X server sets that variable
automatically. Most probably, you are not in X while you run the demo.

> I'm using SuSE linux 6.4 but i haven't installed the precompiled Mesa
> drivers, I'm using mesa 6.2.
> 
> Thanks for you help
> 
> Robert.

Simos

[Mesa3d-users] Newbie question

[THeL0RD/2k <lor...@so...>]

Hi all,

I'm trying to compile mesa demos (make check) and i always get this
message "/usr/i486-suse-linux/bin/ld : cannot find -lXext" and exit.
Also when i run an already compiled demo (ie GLUT demos), I always get
"GLUT : fatal error : could not open display"
I'm using SuSE linux 6.4 but i haven't installed the precompiled Mesa
drivers, I'm using mesa 6.2.

Thanks for you help

Robert.

[Mesa3d-users] Newbie, adding textures

[Simon L. <lem...@ya...>]

Hi,
	I was wondering if there were a GL utility function for adding textures from
pictures on disk?  Let say I want to make a simple image viewer, it would load
the user-chosen texture and place it on a polygon in front of an orthographic
camera.  Would that make a correct image viewer? No distortions, etc? So the
only tricky part would be to "load" the texture from disk...

Any ideas?

Thanks for the help,
	Simon Lemieux

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: [Mesa3d-users] Losing control of demo apps...

[Chris W. <re...@se...>]

Perms on /dev/3dfx and /dev/ttys0 (symlinked to /dev/mouse)...

crw-rw-rw-   1 root     root     107,   0 Oct 29  1999 3dfx

lrwxrwxrwx   1 root     root            5 Sep 16  1999 mouse -> ttyS0
crw-r--r--   1 root     tty        4,  64 May  5  1998 ttyS0

crw-rw--w-   1 root     privuser   5,   1 Jun  9 11:06 console

I've confirmed that every 3dfx app runs perfectly when logged in as root.
However, when run as a non-priveleged user (even if the app itself is suid
root), I do not have keyboard or mouse control. The exception is the
aforementioned glutfx program.

I'v determined that this is isolated to apps using Mesa...the 3Dfx glide
demo apps that are available on 3dfx's website (desktop, donut, surf) all
run fine from non-priveleged shells with full mouse and keyboard control.

What other files or devices should I check permissions on?

-Chris

On Sat, Jun 10, 2000 at 08:58:03AM +0100, Andrew C Aitchison wrote:
> Chris Woodfield wrote:
> > Another data point...I've found that the demo apps retain control of the
> > input when I run them as root, but lose control of input events when I ru
> > them as a non-priveleged user. Haven't tried this with Quake yet, but
> > that's the case with all of the apps in Mesa-3.2/demos and
> > Mesa-3.2/3Dfx/demos/.
> 
> In that case, are /dev/3dfx and /dev/mouse owned by the same
> user and group, and are the apps running as a user with permission
> to access them ? I'm not up to speed, but I remember a time when
> glide was setup to only available to users with extra permissions;
> it sounds as if the demos may be su-ing to someone who can't read
> input devices. I may be barking up the wrong tree.
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users

-- 
---------------------------
Christopher A. Woodfield		re...@se...

PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B

Re: [Mesa3d-users] Losing control of demo apps...

[Andrew C A. <A.C...@dp...>]

Chris Woodfield wrote:
> Another data point...I've found that the demo apps retain control of the
> input when I run them as root, but lose control of input events when I ru
> them as a non-priveleged user. Haven't tried this with Quake yet, but
> that's the case with all of the apps in Mesa-3.2/demos and
> Mesa-3.2/3Dfx/demos/.

In that case, are /dev/3dfx and /dev/mouse owned by the same
user and group, and are the apps running as a user with permission
to access them ? I'm not up to speed, but I remember a time when
glide was setup to only available to users with extra permissions;
it sounds as if the demos may be su-ing to someone who can't read
input devices. I may be barking up the wrong tree.

Re: [Mesa3d-users] Losing control of demo apps...

[Chris W. <re...@se...>]

Another data point...I've found that the demo apps retain control of the
input when I run them as root, but lose control of input events when I ru
them as a non-priveleged user. Haven't tried this with Quake yet, but
that's the case with all of the apps in Mesa-3.2/demos and
Mesa-3.2/3Dfx/demos/.

Is there a env variable or compiler option I'm missing?

-Chris

On Thu, Jun 08, 2000 at 02:31:45PM -0600, Brian Paul wrote:
> Chris Woodfield wrote:
> > 
> > I have a Voodoo3 AGP card, and I've compiled Mesa 3.2 with the latest
> > version of glide (downloaded from wdfx last week).
> > 
> > So far, every Mesa application I've attempted to run (from the demos to
> > Quake II) has refused to take keyboard or mouse control. In every case,
> > I've had to remotely kill the app, and even then I don't always get my
> > console back.
> > 
> > 1. In situations like this, how does one get the 3dfx driver to give X
> > back the screen?
> > 
> > 2. How to you force the Mesa app to take keyboard and mouse control?
> 
> 
> Remember, when you open a full-screen 3dfx display, you're not really
> creating an X window.  So, whatever X window happens to have focus
> "underneath" the 3dfx display will get the input events.
> 
> Check out the Mesa-3.2/demos/glutfx.c for one way to deal with
> this.
> 
> I haven't run QuakeII in a long time.  Don't know what the problem
> is there.
> 
> -Brian
> 
> _______________________________________________
> Mesa3d-users mailing list
> Mes...@li...
> http://lists.sourceforge.net/mailman/listinfo/mesa3d-users

-- 
---------------------------
Christopher A. Woodfield		re...@se...

PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B

Re: [Mesa3d-users] 3dfx + selection mode segv

[Brian P. <br...@pr...>]

John Watson wrote:
> 
> Hello,
> 
> I get a segv in the 3dfx renderer when attempting to use
> the gl selection mode.  It works perfectly with the software
> renderer.
> 
> Has anyone else experienced this problem?
> 
> This is a Linux system w/ voodoo3 and voodoo2, Mesa 3.2
> and latest Mesa CVS 3.3.
> 
> Thanks,
> JW
> 
> --
> // John Watson
> // Software Engineer         --        STScI Archive Team
> 
> #0 0x0 in ?? ()
> #1 0x40374142 in fxDDDoRasterSetup () from /usr/local/lib/libGL.so.1
> #2 0x4024c26b in gl_run_pipeline () from /usr/local/lib/libGL.so.1
> #3 0x402a6120 in gl_execute_cassette () from /usr/local/lib/libGL.so.1
> #4 0x401f9c81 in gl_cva_compile_cassette () from /usr/local/lib/libGL.so.1
> #5 0x402a6749 in gl_flush_vb () from /usr/local/lib/libGL.so.1
> #6 0x40214ad8 in gl_RenderMode () from /usr/local/lib/libGL.so.1
> #7 0x401d2fa1 in glRenderMode () from /usr/local/lib/libGL.so.1
> #8 0x400a1a72 in paint () at sel.cc:27

I thought I fixed that a while back.  I'll look into it tomorrow.

-Brian

[Mesa3d-users] 3dfx + selection mode segv

[John W. <jwa...@ho...>]

Hello,

I get a segv in the 3dfx renderer when attempting to use
the gl selection mode.  It works perfectly with the software
renderer.

Has anyone else experienced this problem?

This is a Linux system w/ voodoo3 and voodoo2, Mesa 3.2
and latest Mesa CVS 3.3.

Thanks,
JW

-- 
// John Watson
// Software Engineer         --        STScI Archive Team


#0 0x0 in ?? () 
#1 0x40374142 in fxDDDoRasterSetup () from /usr/local/lib/libGL.so.1 
#2 0x4024c26b in gl_run_pipeline () from /usr/local/lib/libGL.so.1 
#3 0x402a6120 in gl_execute_cassette () from /usr/local/lib/libGL.so.1 
#4 0x401f9c81 in gl_cva_compile_cassette () from /usr/local/lib/libGL.so.1 
#5 0x402a6749 in gl_flush_vb () from /usr/local/lib/libGL.so.1 
#6 0x40214ad8 in gl_RenderMode () from /usr/local/lib/libGL.so.1 
#7 0x401d2fa1 in glRenderMode () from /usr/local/lib/libGL.so.1 
#8 0x400a1a72 in paint () at sel.cc:27

Re: [Mesa3d-users] Losing control of demo apps...

[Brian P. <br...@pr...>]

Chris Woodfield wrote:
> 
> I have a Voodoo3 AGP card, and I've compiled Mesa 3.2 with the latest
> version of glide (downloaded from wdfx last week).
> 
> So far, every Mesa application I've attempted to run (from the demos to
> Quake II) has refused to take keyboard or mouse control. In every case,
> I've had to remotely kill the app, and even then I don't always get my
> console back.
> 
> 1. In situations like this, how does one get the 3dfx driver to give X
> back the screen?
> 
> 2. How to you force the Mesa app to take keyboard and mouse control?


Remember, when you open a full-screen 3dfx display, you're not really
creating an X window.  So, whatever X window happens to have focus
"underneath" the 3dfx display will get the input events.

Check out the Mesa-3.2/demos/glutfx.c for one way to deal with
this.

I haven't run QuakeII in a long time.  Don't know what the problem
is there.

-Brian

[Mesa3d-users] Losing control of demo apps...

[Chris W. <re...@se...>]

I have a Voodoo3 AGP card, and I've compiled Mesa 3.2 with the latest
version of glide (downloaded from wdfx last week).

So far, every Mesa application I've attempted to run (from the demos to
Quake II) has refused to take keyboard or mouse control. In every case,
I've had to remotely kill the app, and even then I don't always get my
console back.

1. In situations like this, how does one get the 3dfx driver to give X
back the screen?

2. How to you force the Mesa app to take keyboard and mouse control?

-Chris

---------------------------
Christopher A. Woodfield		re...@se...

PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B

Re: [Mesa3d-users] SVGA

[Brian P. <br...@pr...>]

Christoph Walzer wrote:
> 
> Hi !
> 
> Sorry to bother, but I'm stuck with the following problem:
> 
> Executing the SVGA demos leeds to a segmentation fault.
> All other demos work well. Upgrading of svgalib to version
> 1.4.1 didn't help. The demos of the svgalib package work,
> so it shouldn't be a problem of configuring svgalib.
> I compiled Mesa 3.2 with egcs release 1.1.2 on a linux 2.0.35/libc5
> system. Chipset is ATI Mach64 (svgalib uses autodetection).
> 
> Can someone give me a hint ? Thanx in advance !

Someone contributed a bunch of updates to the SVGA driver in 3.2.
I had trouble merely using the SVGAlib on my system and wasn't
able to test the updates.  It would be nice to have an ongoing
maintainer for that code.

-Brian

Re: [Mesa3d-users] vertex buffer

[Brian P. <br...@pr...>]

Matt Campbell wrote:
> 
> Could someone tell me which field inside the vertex buffer data
> structure holds or points to the indexed color information for a flat
> shaded ci triangle.  I want to put the data for that particular triangle
> in a message buffer but I'm not sure where the color info is.

If you look at src/triangles.c and examine the flat-shaded triangle
functions you'll see.  In general, the 'pv' (provoking vertex) parameter
is an index into the vertex buffer indicating which color or color index
to use for filling the triangle.

-Brian

[Mesa3d-users] SVGA

[Christoph W. <a88...@un...>]

Hi !

Sorry to bother, but I'm stuck with the following problem:

Executing the SVGA demos leeds to a segmentation fault.
All other demos work well. Upgrading of svgalib to version
1.4.1 didn't help. The demos of the svgalib package work,
so it shouldn't be a problem of configuring svgalib.
I compiled Mesa 3.2 with egcs release 1.1.2 on a linux 2.0.35/libc5
system. Chipset is ATI Mach64 (svgalib uses autodetection).

Can someone give me a hint ? Thanx in advance !

Christoph Walzer

[Mesa3d-users] vertex buffer

[Matt C. <mca...@vt...>]

Could someone tell me which field inside the vertex buffer data
structure holds or points to the indexed color information for a flat
shaded ci triangle.  I want to put the data for that particular triangle
in a message buffer but I'm not sure where the color info is.

Thanks.

Matt Campbell
mca...@vt...

Re: [Mesa3d-users] (no subject)

[Mircea M. <mm...@ss...>]

On Wed, 7 Jun 2000, david besnard wrote:

> how I use the mouse when the program run in fullscreen
You have to draw yourself the cursor. If you are using glut, use the
motion and passivemotion callbacks.

---
Mircea Mitu
mm...@ss...     http://web.ss.pub.ro/~mms
mir...@go...   http://mirceamms.go.ro (mirror)
...
Please ingnore spelling and punctuation - I did.