-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Daniel Sperka wrote:
> I've noticed that glPointSize() seems to have no effect on a my radeon > (Radeon9200SE) card. A simple code snippet (hacked version of a redbook > example) is below. (The line stipple examples may be ignored. I just > hacked my stuff into this example.) > > When I run this program on an nVidea card it works as expected. On > radeon (r200 series) cards it doesn't - all point sizes are 1.0, > regardless of the glPointSize() setting. Point size, like the number of texture units, has a queryable maximum. The radeon and r200 drivers advertise the maximum as 1.0. Your program is buggy in that it ignores the driver advertised maximum. 'glxinfo -l | grep POINT_SIZE' will show you the relevant limits supported by the driver. That said, there were some patches floating around *years* ago that exposed larger point sizes. I could have sworn that those got committed. Does anyone know the status of those patches? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEkJySX1gOwKyEAw8RAqfXAJ430kQ4OPXaloahJOBgNfsR2W7I4gCfVP7q 5kdS/weNNlAA3IxDOAv3xyA= =20o7 -----END PGP SIGNATURE----- _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
