You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
(11) |
Apr
(46) |
May
(65) |
Jun
(85) |
Jul
(94) |
Aug
(99) |
Sep
(62) |
Oct
(58) |
Nov
(85) |
Dec
(39) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(90) |
Feb
(29) |
Mar
(90) |
Apr
(96) |
May
(78) |
Jun
(58) |
Jul
(44) |
Aug
(65) |
Sep
(40) |
Oct
(38) |
Nov
(79) |
Dec
(63) |
2002 |
Jan
(53) |
Feb
(61) |
Mar
(43) |
Apr
(53) |
May
(35) |
Jun
(59) |
Jul
(18) |
Aug
(12) |
Sep
(28) |
Oct
(61) |
Nov
(54) |
Dec
(23) |
2003 |
Jan
(16) |
Feb
(42) |
Mar
(38) |
Apr
(35) |
May
(20) |
Jun
(9) |
Jul
(10) |
Aug
(30) |
Sep
(22) |
Oct
(32) |
Nov
(25) |
Dec
(21) |
2004 |
Jan
(39) |
Feb
(36) |
Mar
(59) |
Apr
(32) |
May
(21) |
Jun
(4) |
Jul
(8) |
Aug
(21) |
Sep
(11) |
Oct
(21) |
Nov
(22) |
Dec
(19) |
2005 |
Jan
(62) |
Feb
(24) |
Mar
(17) |
Apr
(16) |
May
(16) |
Jun
(17) |
Jul
(26) |
Aug
(14) |
Sep
(13) |
Oct
(8) |
Nov
(23) |
Dec
(20) |
2006 |
Jan
(41) |
Feb
(18) |
Mar
(21) |
Apr
(47) |
May
(13) |
Jun
(33) |
Jul
(32) |
Aug
(21) |
Sep
(27) |
Oct
(34) |
Nov
(19) |
Dec
(46) |
2007 |
Jan
(21) |
Feb
(26) |
Mar
(13) |
Apr
(22) |
May
(5) |
Jun
(19) |
Jul
(56) |
Aug
(43) |
Sep
(37) |
Oct
(31) |
Nov
(53) |
Dec
(22) |
2008 |
Jan
(74) |
Feb
(31) |
Mar
(15) |
Apr
(35) |
May
(23) |
Jun
(26) |
Jul
(17) |
Aug
(27) |
Sep
(35) |
Oct
(30) |
Nov
(29) |
Dec
(17) |
2009 |
Jan
(35) |
Feb
(39) |
Mar
(44) |
Apr
(28) |
May
(20) |
Jun
(28) |
Jul
(49) |
Aug
(53) |
Sep
(23) |
Oct
(13) |
Nov
(12) |
Dec
(11) |
2010 |
Jan
(45) |
Feb
(28) |
Mar
(41) |
Apr
(11) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Dave M. <mo...@ni...> - 2000-05-24 09:52:51
|
For the record, today I found a XF86 FAQ entry suggested renicing X to -10. That unsticks the mouse, even if I'm drawing graphics as fast as possible. Dave Morse writes: > I'm experiencing some bad behavior in a game I'm writing. > > My problem is that if Mesa draws my scene faster than 30 Hertz then I > never get any x events. So as far as my client can tell, the mouse never > moves again. > > All other applications recieve X events normally. > > If I comment out the Mesa drawing code, then I get X events normally. > > During the locked times, top reports that X is consuming 90% cpu time. > > My machines are K6/450 and PII/333 running software mesa 3.3 beta. > > Can someone explain why X is so studiously ignoring the event sending half > of its job, in favor of the rendering half? > > Any ideas for a solution? |
From: Brian P. <br...@pr...> - 2000-05-23 14:54:49
|
David Bannon wrote: > > Hi Mesa experts, > > I am compiling a large programme (not of my making) called molmol. It > claims to use Mesa without problems however it wants to link in > GLwCreateMDrawingArea and cannot find it. It is mentioned in the Mesa > header files and has a source file (in widgets-mesa/src). I found that the > Makefile did not mention it, nor make it. I added it to the makefile and > therefore to the library. > > However (and there is always an however) now the linker says > glwMDrawingAreaWidgetClass is undefined. I can find no source for that > modual although it is mentioned in a number of defines. > > Any suggestions ? > > I did find a similar question in the 'old' list but no answer. I'm using > Redhat linux, 6.1 and LessTif. It shouldn't be hard to compile the GLW code by hand. There's a preprocessor flag (don't recall the name) which has to be set if you want the Motif version of the widget (vs. the regular Xt version). -Brian |
From: Annette J. <ja...@ma...> - 2000-05-23 07:18:03
|
> > Hi Mesa experts, > > I am compiling a large programme (not of my making) called molmol. It > claims to use Mesa without problems however it wants to link in > GLwCreateMDrawingArea and cannot find it. It is mentioned in the Mesa > header files and has a source file (in widgets-mesa/src). I found that the > Makefile did not mention it, nor make it. I added it to the makefile and > therefore to the library. > > However (and there is always an however) now the linker says > glwMDrawingAreaWidgetClass is undefined. I can find no source for that > modual although it is mentioned in a number of defines. > > Any suggestions ? Hi, For Mesa-3.2 I have some experiences: Yes, you have to make Motif Widgets manually from widgets-mesa. Did You "configure --with-motif" within widgets-mesa? With this option "configure" generates Makefiles in widgets-mesa and its subdirs and produces libMesaGLw.a and libMesaGLwM.a. I think all You need is in libMesaGLwM.a: sunos2.7%nm libMesaGLwM.a | grep glwMDrawingAreaWidgetClass 0000047c D glwMDrawingAreaWidgetClass U glwMDrawingAreaWidgetClass sunos2.7% Annette Technical University Berlin Germany Institute of Mathematics > > I did find a similar question in the 'old' list but no answer. I'm using > Redhat linux, 6.1 and LessTif. > > david > ------------------------------------------------------------ > David Bannon D.B...@la... > School of Biochemistry Phone 61 03 9479 2197 > La Trobe University, Plenty Rd, Fax 61 03 9479 2467 > Bundoora, Vic, Australia, 3083 http://bioserve.latrobe.edu.au > ------------------------------------------------------------ > ..... Humpty Dumpty was pushed ! > > _______________________________________________ > Mesa3d-users mailing list > Mes...@li... > http://lists.sourceforge.net/mailman/listinfo/mesa3d-users > |
From: David B. <D.B...@la...> - 2000-05-23 03:11:27
|
Hi Mesa experts, I am compiling a large programme (not of my making) called molmol. It claims to use Mesa without problems however it wants to link in GLwCreateMDrawingArea and cannot find it. It is mentioned in the Mesa header files and has a source file (in widgets-mesa/src). I found that the Makefile did not mention it, nor make it. I added it to the makefile and therefore to the library. However (and there is always an however) now the linker says glwMDrawingAreaWidgetClass is undefined. I can find no source for that modual although it is mentioned in a number of defines. Any suggestions ? I did find a similar question in the 'old' list but no answer. I'm using Redhat linux, 6.1 and LessTif. david ------------------------------------------------------------ David Bannon D.B...@la... School of Biochemistry Phone 61 03 9479 2197 La Trobe University, Plenty Rd, Fax 61 03 9479 2467 Bundoora, Vic, Australia, 3083 http://bioserve.latrobe.edu.au ------------------------------------------------------------ ..... Humpty Dumpty was pushed ! |
From: Brian P. <br...@pr...> - 2000-05-22 14:11:51
|
animesh jana wrote: > > Sir! > is mesa installable in irix 6.3 systems ? > if so, please mention the necessary steps to install it. After unpacking, cd Mesa-3.2 make irix6-n32-dso -Brian |
From: Brian P. <br...@pr...> - 2000-05-22 14:10:16
|
DaRKFoRCe wrote: > > Hi, > > I have workaround my last problem. Now the problem I'm facing is gcc > complains the following errors when compiling 'dosmesa.c' : > > DOS/dosmesa.c: In function `set_buffer': > DOS/dosmesa.c:1012: `buffer' undeclared (first use this function) > DOS/dosmesa.c:1012: (Each undeclared identifier is reported only once > DOS/dosmesa.c:1012: for each function it appears in.) > DOS/dosmesa.c: In function `DOSmesa_setup_DD_pointers': > DOS/dosmesa.c:1325: warning: assignment from incompatible pointer type > DOS/dosmesa.c:1340: structure has no member named `WriteColorSpan' > DOS/dosmesa.c:1341: structure has no member named `WriteMonocolorSpan' > DOS/dosmesa.c:1342: structure has no member named `WriteColorPixels' > DOS/dosmesa.c:1343: structure has no member named `WriteMonocolorPixels' > DOS/dosmesa.c:1344: structure has no member named `WriteIndexSpan' > DOS/dosmesa.c:1345: structure has no member named `WriteMonoindexSpan' > DOS/dosmesa.c:1346: structure has no member named `WriteIndexPixels' > DOS/dosmesa.c:1347: structure has no member named `WriteMonoindexPixels' > DOS/dosmesa.c:1351: structure has no member named `ReadIndexSpan' > DOS/dosmesa.c:1352: structure has no member named `ReadColorSpan' > DOS/dosmesa.c:1353: structure has no member named `ReadIndexPixels' > DOS/dosmesa.c:1354: structure has no member named `ReadColorPixels' > DOS/dosmesa.c: In function `DOSMesaCreateContext': > DOS/dosmesa.c:1421: too many arguments to function `gl_create_visual' > DOS/dosmesa.c:1426: too few arguments to function `gl_create_context' > make.exe: *** [DOS/dosmesa.o] Error 1 > > How can workaround this problem? > > Also, I'm trying to contact Charlie Wallace at cwa...@dr... > but my e-mails keep bouncing back. The server response is 'user > unknown'. Anybody know how to contact him or anyone familiar with > Mesa/DJGPP compiling problems? No one has maintained the DOS (or Windows) driver in some time. I know the DOS driver needs substantial work to make it function again. Any volunteers? -Brian |
From: Brian P. <br...@pr...> - 2000-05-22 14:08:49
|
Stephen J Baker wrote: > > On Sat, 20 May 2000, FragDance Galore wrote: > > > That is because (as I understand it) the windowed mode on a Voodoo3 is a > > hack. Voodoo3 is designed to run in fullscreen, and Mesa allows Voodoo3 to > > run in a window by first rendering to an offscreen buffer and the copying > > the results to screen > > That's true for Voodoo-1 and -2 but a Voodoo-3 should be able to do this > directly without the Mesa hack. When using XFree86 4.0 and the DRI, of course. -Brian |
From: Stephen J B. <sj...@ht...> - 2000-05-22 13:35:10
|
On Sat, 20 May 2000, FragDance Galore wrote: > That is because (as I understand it) the windowed mode on a Voodoo3 is a > hack. Voodoo3 is designed to run in fullscreen, and Mesa allows Voodoo3 to > run in a window by first rendering to an offscreen buffer and the copying > the results to screen That's true for Voodoo-1 and -2 but a Voodoo-3 should be able to do this directly without the Mesa hack. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@ht... http://www.hti.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |
From: DaRKFoRCe <dar...@th...> - 2000-05-21 20:16:37
|
Hi, I have workaround my last problem. Now the problem I'm facing is gcc complains the following errors when compiling 'dosmesa.c' : DOS/dosmesa.c: In function `set_buffer': DOS/dosmesa.c:1012: `buffer' undeclared (first use this function) DOS/dosmesa.c:1012: (Each undeclared identifier is reported only once DOS/dosmesa.c:1012: for each function it appears in.) DOS/dosmesa.c: In function `DOSmesa_setup_DD_pointers': DOS/dosmesa.c:1325: warning: assignment from incompatible pointer type DOS/dosmesa.c:1340: structure has no member named `WriteColorSpan' DOS/dosmesa.c:1341: structure has no member named `WriteMonocolorSpan' DOS/dosmesa.c:1342: structure has no member named `WriteColorPixels' DOS/dosmesa.c:1343: structure has no member named `WriteMonocolorPixels' DOS/dosmesa.c:1344: structure has no member named `WriteIndexSpan' DOS/dosmesa.c:1345: structure has no member named `WriteMonoindexSpan' DOS/dosmesa.c:1346: structure has no member named `WriteIndexPixels' DOS/dosmesa.c:1347: structure has no member named `WriteMonoindexPixels' DOS/dosmesa.c:1351: structure has no member named `ReadIndexSpan' DOS/dosmesa.c:1352: structure has no member named `ReadColorSpan' DOS/dosmesa.c:1353: structure has no member named `ReadIndexPixels' DOS/dosmesa.c:1354: structure has no member named `ReadColorPixels' DOS/dosmesa.c: In function `DOSMesaCreateContext': DOS/dosmesa.c:1421: too many arguments to function `gl_create_visual' DOS/dosmesa.c:1426: too few arguments to function `gl_create_context' make.exe: *** [DOS/dosmesa.o] Error 1 How can workaround this problem? Also, I'm trying to contact Charlie Wallace at cwa...@dr... but my e-mails keep bouncing back. The server response is 'user unknown'. Anybody know how to contact him or anyone familiar with Mesa/DJGPP compiling problems? DaRKFoRCe dar...@th... |
From: animesh j. <aj...@ma...> - 2000-05-21 13:29:04
|
Sir! is mesa installable in irix 6.3 systems ? if so, please mention the necessary steps to install it. Get your FREE Email at http://mailcity.lycos.com Get your PERSONALIZED START PAGE at http://my.lycos.com |
From: FragDance G. <fra...@ho...> - 2000-05-20 13:33:21
|
That is because (as I understand it) the windowed mode on a Voodoo3 is a hack. Voodoo3 is designed to run in fullscreen, and Mesa allows Voodoo3 to run in a window by first rendering to an offscreen buffer and the copying the results to screen FragDance >From: "david besnard" <sup...@ho...> >To: mes...@li... >Subject: [Mesa3d-users] (no subject) >Date: Sat, 20 May 2000 02:34:30 PDT > >I have a problem when I try tu use hardware acceleration in a window >the programm run in fullscreen but more slower (30 image per second ) >whan I compute to fullscreen (it is 100 image per second) >I have a voodoo3 > > >________________________________________________________________________ >Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > >_______________________________________________ >Mesa3d-users mailing list >Mes...@li... >http://lists.sourceforge.net/mailman/listinfo/mesa3d-users ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com |
From: david b. <sup...@ho...> - 2000-05-20 09:36:17
|
I have a problem when I try tu use hardware acceleration in a window the programm run in fullscreen but more slower (30 image per second ) whan I compute to fullscreen (it is 100 image per second) I have a voodoo3 ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com |
From: Brian P. <br...@pr...> - 2000-05-18 23:02:07
|
Frank Warmerdam wrote: > > Folks, > > I am trying to build MesaLib 3.2 with Sun's C and C++ compiler. It seems > that the Makefile.in's use the gcc flag "-Wp,-MD,.deps" which doesn't work > with Sun C. Is it intended that Mesa only be built with gcc when using the > Unix/X11 configure mechanism? Should this be a configure time controlled > thing? > > For now I am just hacking out the switch and things seem to be working > (albeit with many warnings). If interested, I could try and prepare patches > so configure will and the Makefile.in's will work properly with Sun (and > other non-gcc) compilers. Should I? Sure. Thomas Tanner contributed the original configure scripts but apparently doesn't have the time to maintain them much anymore. Any volunteers? -Brian |
From: Gareth H. <ga...@pr...> - 2000-05-18 21:10:02
|
From: Brian P. <br...@pr...> - 2000-05-18 15:20:36
|
Simos Xenitellis wrote: > > Hello, > This is another question of "is this hardware supported". > I would be glad if you could nack/ack the following... > > A graphics card is 'supported', if it is supported in > > * XFree86 version x.y. = for 2D graphics > * Mesa3D = for 3D graphics (plus 2D, ...) > > A user to be (initially) happy, needs the first, the Xfree86 support. > Then, for 3D graphics, only MesaGL-enabled applications with Xfree86 > supported graphics cards provide fast and nice graphics. > > My card, with the Savage4 Pro chipset, is supported by Xfree86 > and that is nice. > > However, at www.mesa3d.org I see no reference to Savage4, so no Mesa3D > support. > > The OpenGL(r) hardware acceleration support for a specific chipset is > only total or can also be partial? That is, some 3D graphic primitives > may be supported by my card although no developer has tried them. I > could be lacky that a 3D operation may work because it coincides with > another card? > > Please nack/ack the above, I would like to have a clearer view on the > issue. Any links to FAQ are welcome too. If there's a version of XFree86 which supports it then with Mesa you can certainly do software 3D rendering. Hardware 3D rendering would require DRI support which doesn't exist at this time. -Brian |
From: Simos X. <S.X...@rh...> - 2000-05-18 14:20:32
|
Hello, This is another question of "is this hardware supported". I would be glad if you could nack/ack the following... A graphics card is 'supported', if it is supported in * XFree86 version x.y. = for 2D graphics * Mesa3D = for 3D graphics (plus 2D, ...) A user to be (initially) happy, needs the first, the Xfree86 support. Then, for 3D graphics, only MesaGL-enabled applications with Xfree86 supported graphics cards provide fast and nice graphics. My card, with the Savage4 Pro chipset, is supported by Xfree86 and that is nice. However, at www.mesa3d.org I see no reference to Savage4, so no Mesa3D support. The OpenGL(r) hardware acceleration support for a specific chipset is only total or can also be partial? That is, some 3D graphic primitives may be supported by my card although no developer has tried them. I could be lacky that a 3D operation may work because it coincides with another card? Please nack/ack the above, I would like to have a clearer view on the issue. Any links to FAQ are welcome too. Regards, Simos Xenitellis |
From: Robert S W. <rob...@ju...> - 2000-05-17 22:18:30
|
Hi, I'm a beginner at OpenGL/Mesa... I just dled Mesa 3.2, and I unzipped MesaLib and MesaDemos into a mesa folder. I tried to see if I could compile for djgpp, but that doesn't look like it would be too feasible, so I tried MingW32 (2.95.2), crtdll version. I read docs\readme.mingw32 and other readmes in there and followed the directions. I made mingw32 my "active compiler" (ie setting path and stuff for mingw32 instead of djgpp and restarting) and in mesa\mesa-3.2 I typed mingw32 and got some not-too-clean messages from that. Despite all the warnings, things seemed to work ok. Here's what I get when I type mingw32 again, just to give you an idea of how it starts out: F:\mesa\Mesa-3.2> mingw32 F:\mesa\Mesa-3.2> echo off Out of environment space Out of environment space Directory already exists Out of environment space Bad command or file name Bad command or file name Invalid directory F:\MINGW32\BIN\DLLTOOL.EXE: Can't open def file: wing32.def GCC.EXE: wing32.a: No such file or directory GCC.EXE: No input files Required parameter missing F:\MINGW32\BIN\MAKE.EXE: Entering an unknown directory F:\MINGW32\BIN\MAKE.EXE: *** : No such file or directory. Stop. F:\MINGW32\BIN\MAKE.EXE: Leaving an unknown directory Cannot move \libGL.a - No such file or directory F:\MINGW32\BIN\MAKE.EXE: Entering directory `f:/mesa/mesa-3.2/src-glu' ar ru libGLU.a glu.o mipmap.o nurbs.o nurbscrv.o nurbssrf.o nurbsutl.o projec t.o quadric.o tess.o tess_fist.o tess_hash.o tess_heap.o tess_winding.o tess_cli p.o F:\MINGW32\BIN\MAKE.EXE: Leaving directory `f:/mesa/mesa-3.2/src-glu' F:\MESA\MESA-3.2\SRC-GLU\libGLU.a => F:\libGLU.a [ok] F:\mesa\Mesa-3.2> ...and yes, I did change the mesaroot variable in mingw32.bat to f:\mesa\mesa-3.2 which is where that dir is. So that *seems* to work, but the problem is that all the examples aren't compiled and there's lotsa makefiles everywhere to do stuff that I don't know about. How can I get the examples and whatnot compiled? And what do I need to do to be able to use mesa in my programs? or should I just get an OpenGL book for that? there should be more of a guide for this, like a readme in the root directory or something. thanks for reading this far... hope you can help here's my specs: Windows 95 (4.00.950) MingW32 v2.95.2 crtdll version, mummit khans verison S3 Trio 64V+ w/2mb vram P120 16mb ram other compilers available to me: Borland 5.5 (but I haven't figured out how to use it) DJGPP 2.03 gcc 2.95.2 that other version of mingw32 (msvrt is it?) If all this doesn't work out for Mesa, is there another OpenGL implementation I could try? Is Sun's good on Win32 and Linux? does it do DOS? Does Mesa do DOS? Practically? And yes, I have run OpenGL programs on this system before. This is just my first time developing for OpenGL. thanks for any help -- Robert Whitlock http://www.geocities.com/CapeCanaveral/Hangar/9520/ |
From: DaRKFoRCe <dar...@th...> - 2000-05-17 20:14:26
|
Hi, I can't compile mesa under DOS with DJGPP either with GCC 2.8.1 or PGCC 2.90. The first problem encountered is when compiling \src, 'make' can't find 'depend.dos', which I worked around it by adding '\dos' to 'include depend.dos' line. Is it right to do so? 'cause I found 'depend.dos' in \src\dos. The second problem which I can't seem to understand that GCC/PGCC can't find 'GL/gl.h'. I have checked '\include' and found the file there but why does the compiler can't found it? I even give absolute addresses to 'INCLUDE' and 'LIB' variable but nothing improved. How to work around this problem? DaRKFoRCe dar...@th... |
From: Stephen J B. <sj...@ht...> - 2000-05-17 13:15:31
|
On Wed, 17 May 2000, david besnard wrote: > is it possible to use hardware 3dfx in a window not in fullscreen > if it is possible how to do Depends on which 3Dfx card you have - but I'm guessing from the question that you have either Voodoo-1 or Voodoo-2. If that's the case then you need to set the shell variable 'MESA_GLX_FX' to 'windowed' as in: BASH: export MESA_GLX_FX=windowed tcsh: setenv MESA_GLX_FX windowed This is nowhere near as fast as full-screen mode - but a lot faster than software rendering. If you have a Voodoo-1/2 card then that's as good as it gets because the hardware is physically incapable of rendering into a window and Mesa has to copy the image out of the 3Dfx card's frame buffer and into the 2D graphics card...which takes something like a tenth of a second for most "reasonable" hardware setups. If you have a Banshee or a Voodoo-3 then rendering into a window should be fast. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@ht... http://www.hti.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |
From: david b. <sup...@ho...> - 2000-05-17 08:16:29
|
is it possible to use hardware 3dfx in a window not in fullscreen if it is possible how to do ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com |
From: Stephen J B. <sj...@ht...> - 2000-05-16 14:41:04
|
On Tue, 16 May 2000, david besnard wrote: > what is more faster write aplication with opengl or with glide > if glide is faster than opengl how many percent of performance I loose Well, three issues here: 1) GLIDE is 'going away' - it's evident in the Windoze world that 3Dfx is finally losing interest in it. It had to die sooner or later because it doesn't suit hardware T&L - and *eventually* 3Dfx will wake up to the realisation that if they don't get their act together and produce a machine that can do 20M triangles a second in hardware, they are out of the business. 2) If you write in GLIDE, your program will only be able to run on 3Dfx hardware. OpenGL is portable and will work on lots of different hardware and under lots of operating systems. 3) If you think you can write the higher level transform/clip/lighting code better than the guru's who wrote and optimised Mesa - then GLIDE will certainly be faster than OpenGL/Mesa because (on 3Dfx machines) Mesa runs on top of GLIDE. However, if you are not a truly great optimisation nut with *WAY* too much time on his hands - you are probably better off using OpenGL/Mesa. Conclusion: Don't use GLIDE. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@ht... http://www.hti.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |
From: Christopher <pe...@pa...> - 2000-05-16 13:21:31
|
Can anyone help me with the problem: For a research project I am trying to use various Mesa primitives to do rendering. I am attempting to create a single XMesa Context, and have multiple XMesa buffers. Then I need to be able to tell the Context to render its information into any of these given buffers at any given point in time. I do this by simply having the context refer to the respective buffers. The problem is not with the switching of the buffers in respect to the context, I've been able to manage this. After I switch the buffer, meaning that the context now points to a completely different XMesa buffer, all the rendering information still gets set to the original buffer instead of the new one. I suspect that the context must be keeping track of the original buffer but I can't determine how. I've tried just about everything (ie. Use makecurrent, doing things with XImages at an even lower level). Any ideas? |
From: david b. <sup...@ho...> - 2000-05-16 08:20:42
|
what is more faster write aplication with opengl or with glide if glide is faster than opengl how many percent of performance I loose ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com |
From: Frank W. <war...@ho...> - 2000-05-15 17:55:31
|
Folks, I am trying to build MesaLib 3.2 with Sun's C and C++ compiler. It seems that the Makefile.in's use the gcc flag "-Wp,-MD,.deps" which doesn't work with Sun C. Is it intended that Mesa only be built with gcc when using the Unix/X11 configure mechanism? Should this be a configure time controlled thing? For now I am just hacking out the switch and things seem to be working (albeit with many warnings). If interested, I could try and prepare patches so configure will and the Makefile.in's will work properly with Sun (and other non-gcc) compilers. Should I? Best regards, -- ---------------------------------------+-------------------------------------- I set the clouds in motion - turn up | Frank Warmerdam, war...@ho... light and sound - activate the windows | http://members.home.com/warmerda and watch the world go round - Rush | Geospatial Programmer for Rent |
From: Stephen J B. <sj...@ht...> - 2000-05-15 15:16:18
|
On Mon, 15 May 2000, Arnfried Griesert wrote: > Hi, > > I've written a simple routine to get the frame rate of the monitor. The > program is very simple, it uses a loop for calculating the time of 100 > glXSwapBuffers(). On my SGI with OpenGL it works fine, but with MesaGL > it failed, because the swapping of the two buffers is not syncronized > with the vertical monitor sync. > > My question is if anyone knows why glXSwapBuffers() doesn't wait for a > vertical sync or if this behavior is correct. It depends on what 3D hardware you have. 3Dfx cards have environment variables to select between wait-for-vsync or not. Some cards don't do this at all - or at least don't advertise the fact. Even with hardware that lock the swap to a vertical retrace, they may return from the glXSwapBuffers call immediately and only block your program's execution when you next do an OpenGL call that can affect the frame buffer. (I thought that SGI's machines did this) Some PC hardware can do triple buffering and allow an entire frame of rendering to occour whilst you are waiting for the buffer to swap on the previous frame's rendering. The deal seems to be that there is certainly no portable way to do this - and possibly no way to do it at all on some machines. Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@ht... http://www.hti.com Home: sjb...@ai... http://web2.airmail.net/sjbaker1 |