Thread: RE: [Plib-devel] Another New Demo Program for PW
Brought to you by:
sjbaker
Menu
▾
▴
plib-devel
|
From: Fay J. F C. AAC/W. <joh...@eg...> - 2004-04-27 16:55:43
|
Steve,
I have a couple of notes on your changes. The first is that the
"%lf" is good for the "printf" statements but we need to be careful with the
"sscanf" statements. I've put in a "float_value" variable which actually
gets read from the strings.
The second is a PW issue which I think I raised earlier. The fifth
argument of "pwInit" is "int multisample" which in the "pw_demo" program is
set to "false". I think an "int" should be "TRUE" and "FALSE" rather than
the strict boolean values of "true" and "false". I propose that we either
change the "pwInit" function to take a "bool" or else we change "pw.h" to
include definitions of "TRUE" and "FALSE" and change the sample programs to
pass those. My personal preference is for the latter.
John F. Fay
joh...@eg...
-----Original Message-----
From: pli...@li...
[mailto:pli...@li...]On Behalf Of Steve Baker
Sent: Sunday, April 25, 2004 4:24 PM
To: pli...@li...
Subject: Re: [Plib-devel] Another New Demo Program for PW
Fay John F Contr AAC/WMG wrote:
> Since I can never leave well enough alone ... here's a Lorenz strange
> attractor demo program.
I eventually managed to compile this under Linux - there were a few
problems:
1) '%lf' is not allowed in printf's - the 'l' modifier can only be applied
to integers - not doubles. Just a plain '%f' is sufficient.
2) FALSE is undeclared in line 332.
3) The variable pargc isn't used.
---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...>
HomePage : http://www.sjbaker.org
Projects : http://plib.sf.net http://tuxaqfh.sf.net
http://tuxkart.sf.net http://prettypoly.sf.net
-----BEGIN GEEK CODE BLOCK-----
GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M-
V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++
-----END GEEK CODE BLOCK-----
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
plib-devel mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-devel
|
|
From: Fay J. F C. AAC/W. <joh...@eg...> - 2004-04-30 20:06:49
|
OK, I think that sounds like a plan. Since the "bool" is in the sample program, I think we can just change it right away. How does PW decide what is the best possible multisampling? John F. Fay joh...@eg... -----Original Message----- From: pli...@li... [mailto:pli...@li...]On Behalf Of Steve Baker Sent: Tuesday, April 27, 2004 7:59 PM To: pli...@li... Subject: Re: [Plib-devel] Another New Demo Program for PW <snip> > The second is a PW issue which I think I raised earlier. The fifth > argument of "pwInit" is "int multisample" which in the "pw_demo" program is > set to "false". I think an "int" should be "TRUE" and "FALSE" rather than > the strict boolean values of "true" and "false". I propose that we either > change the "pwInit" function to take a "bool" or else we change "pw.h" to > include definitions of "TRUE" and "FALSE" and change the sample programs to > pass those. My personal preference is for the latter. Actually, we should probably step back and think a bit more about that. When you turn on multisampling, there is generally a choice as to the number of subsamples - and sometimes other qualitative parameters. Perhaps we should change it to some kind of enumeration such that zero means "no multisampling", one means "best possible multisampling" and other values could be added later. This would keep existing programs working - but allow for more fancy stuff later. <snip> |
|
From: Steve B. <sjb...@ai...> - 2004-04-30 23:45:08
|
Fay John F Contr AAC/WMG wrote: > OK, I think that sounds like a plan. Since the "bool" is in the sample > program, I think we can just change it right away. How does PW decide what > is the best possible multisampling? Well, probably we just try 16 multisamples and work down towards zero until X says we have a valid rendering context. On nVidia hardware, there is an additional GL_NICEST hint that selects between what was once called 'quincunx' mode and the simpler, basic mode. ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- |
|
From: Fay J. F C. AAC/W. <joh...@eg...> - 2004-05-03 14:49:43
|
To coin a phrase, I think you are being slightly X-centric <grin>. I don't see anything about multisampling in the MSVC documentation ... so I guess Windows will simply continue to ignore that parameter. We do have another parameter in "pwInit", though, the "num_samples", which I hadn't noticed last Friday. Suggestions? John F. Fay joh...@eg... -----Original Message----- From: pli...@li... [mailto:pli...@li...]On Behalf Of Steve Baker Sent: Friday, April 30, 2004 5:46 PM To: pli...@li... Subject: Re: [Plib-devel] Another New Demo Program for PW Fay John F Contr AAC/WMG wrote: > OK, I think that sounds like a plan. Since the "bool" is in the sample > program, I think we can just change it right away. How does PW decide what > is the best possible multisampling? Well, probably we just try 16 multisamples and work down towards zero until X says we have a valid rendering context. On nVidia hardware, there is an additional GL_NICEST hint that selects between what was once called 'quincunx' mode and the simpler, basic mode. ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
|
From: Steve B. <sjb...@ai...> - 2004-05-05 23:11:37
|
Fay John F Contr AAC/WMG wrote: > To coin a phrase, I think you are being slightly X-centric <grin>. No - there is certainly multisampling under Windows. > I don't > see anything about multisampling in the MSVC documentation ... Yeah - well, Microsoft don't exactly enthusiastically support OpenGL. OpenGL can do it under Windows *for*sure* - but you'll have to look away from Microsoft to get the information. nVidia or ATI perhaps? > so I guess Windows will simply continue to ignore that parameter. That would be a disaster! Multisampling is very important these days. > We do have another parameter in "pwInit", though, the "num_samples", which I > hadn't noticed last Friday. Suggestions? Ah - now you come to mention it - that is the number of multisample samples. ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- |
|
From: Nick M. <nic...@ds...> - 2004-05-06 03:26:40
|
I don't have time myself to 'understand' and then fix this problem right now ... but if someone is interested in adding Multisampling for Windows to pwInit then here is a tutorial that might be useful ... http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=46 Steve Baker wrote: >Fay John F Contr AAC/WMG wrote: > > >>To coin a phrase, I think you are being slightly X-centric <grin>. >> >> > >No - there is certainly multisampling under Windows. > > > >>I don't >>see anything about multisampling in the MSVC documentation ... >> >> > >Yeah - well, Microsoft don't exactly enthusiastically support OpenGL. >OpenGL can do it under Windows *for*sure* - but you'll have to look >away from Microsoft to get the information. nVidia or ATI perhaps? > > > >>so I guess Windows will simply continue to ignore that parameter. >> >> > >That would be a disaster! Multisampling is very important these days. > > > >>We do have another parameter in "pwInit", though, the "num_samples", which I >>hadn't noticed last Friday. Suggestions? >> >> > >Ah - now you come to mention it - that is the number of multisample samples. > > |
|
From: Fay J. F C. AAC/W. <joh...@eg...> - 2004-05-06 16:16:33
|
I looked at the example and downloaded the code but it doesn't compile. It looks for two header files "<gl/wglext.h>" and "<gl/glext.h>", neither of which I have. Spending a little more time with it, I find "wglGetProcAddress" which helps a little. I can call functions now, but the defined constants (like "WGL_DRAW_TO_WINDOW_ARB") are still undefined. Help! They certainly don't make it easy, do they? Looking further, I find mention of "accumulation buffer" bits in connection with antialiasing. Is this Windows-speak for multisampling? John F. Fay joh...@eg... -----Original Message----- From: pli...@li... [mailto:pli...@li...]On Behalf Of Nick McEvoy Sent: Wednesday, May 05, 2004 10:20 PM To: pli...@li... Subject: Re: [Plib-devel] Another New Demo Program for PW I don't have time myself to 'understand' and then fix this problem right now ... but if someone is interested in adding Multisampling for Windows to pwInit then here is a tutorial that might be useful ... http://nehe.gamedev.net/data/lessons/lesson.asp?lesson=46 Steve Baker wrote: <snip> > >>We do have another parameter in "pwInit", though, the "num_samples", which I >>hadn't noticed last Friday. Suggestions? >> >> > >Ah - now you come to mention it - that is the number of multisample samples. > > |
|
From: Steve B. <sjb...@ai...> - 2004-05-06 23:13:42
|
Fay John F Contr AAC/WMG wrote: > I looked at the example and downloaded the code but it doesn't compile. It > looks for two header files "<gl/wglext.h>" and "<gl/glext.h>", neither of > which I have. Well, GL/glext.h (it *should* be a capital 'GL' so it compiles under case-sensitive OS's) can be obtained from www.opengl.org. It contains the #define or GLenum tokens for *all* known OpenGL extensions. I believe GL/glxext.h is also there - but I don't know about GL/wglext.h. > Spending a little more time with it, I find "wglGetProcAddress" which helps > a little. I can call functions now, but the defined constants (like > "WGL_DRAW_TO_WINDOW_ARB") are still undefined. Help! They certainly don't > make it easy, do they? No they certainly don't. Microsoft would dearly like OpenGL to 'go away' so that you'd have to own a Windows machine in order to do 3D graphics. > Looking further, I find mention of "accumulation buffer" bits in connection > with antialiasing. Is this Windows-speak for multisampling? No - an accumulation buffer is something different. You can do kinda-sorta antialiasing on a machine that doesn't implement it properly if it has an accumulation buffer - but I wouldn't recommend it! ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- |
|
From: Steve B. <sjb...@ai...> - 2004-04-28 01:02:21
|
Fay John F Contr AAC/WMG wrote: > I have a couple of notes on your changes. The first is that the > "%lf" is good for the "printf" statements but we need to be careful with the > "sscanf" statements. I've put in a "float_value" variable which actually > gets read from the strings. Yep. > The second is a PW issue which I think I raised earlier. The fifth > argument of "pwInit" is "int multisample" which in the "pw_demo" program is > set to "false". I think an "int" should be "TRUE" and "FALSE" rather than > the strict boolean values of "true" and "false". I propose that we either > change the "pwInit" function to take a "bool" or else we change "pw.h" to > include definitions of "TRUE" and "FALSE" and change the sample programs to > pass those. My personal preference is for the latter. Actually, we should probably step back and think a bit more about that. When you turn on multisampling, there is generally a choice as to the number of subsamples - and sometimes other qualitative parameters. Perhaps we should change it to some kind of enumeration such that zero means "no multisampling", one means "best possible multisampling" and other values could be added later. This would keep existing programs working - but allow for more fancy stuff later. ---------------------------- Steve Baker ------------------------- HomeEmail: <sjb...@ai...> WorkEmail: <sj...@li...> HomePage : http://www.sjbaker.org Projects : http://plib.sf.net http://tuxaqfh.sf.net http://tuxkart.sf.net http://prettypoly.sf.net -----BEGIN GEEK CODE BLOCK----- GCS d-- s:+ a+ C++++$ UL+++$ P--- L++++$ E--- W+++ N o+ K? w--- !O M- V-- PS++ PE- Y-- PGP-- t+ 5 X R+++ tv b++ DI++ D G+ e++ h--(-) r+++ y++++ -----END GEEK CODE BLOCK----- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X