Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-29 Thread Jacek Poplawski
I build Quake3 from source and on my r300 Mesa CVS falls into indirect rendering just after video mode initialization (tried both SDL GL and GLX drivers). I thought that stencil is the reason, but disabling it didn't help. There are no r300 warnings visible (there are in Cube, which also disables

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-29 Thread Roland Scheidegger
Jacek Poplawski wrote: I build Quake3 from source and on my r300 Mesa CVS falls into indirect rendering just after video mode initialization (tried both SDL GL and GLX drivers). I thought that stencil is the reason, but disabling it didn't help. There are no r300 warnings visible (there are in

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-16 Thread Rune Petersen
I found the problem: In Mesa MAX_TEXTURE_UNITS, MAX_TEXTURE_COORD_UNITS, and MAX_TEXTURE_IMAGE_UNITS are all set to 8. (src/mesa/main/config.h) And there are no sanity-checks done on the values returned by the drivers. Changing the defines to 16 makes everything work. Changing only

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-16 Thread Rune Petersen
Brian Paul wrote: Rune Petersen wrote: Brian Paul wrote: Rune Petersen wrote: I found the problem: In Mesa MAX_TEXTURE_UNITS, MAX_TEXTURE_COORD_UNITS, and MAX_TEXTURE_IMAGE_UNITS are all set to 8. (src/mesa/main/config.h) And there are no sanity-checks done on the values returned by the

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-16 Thread Brian Paul
Rune Petersen wrote: I found the problem: In Mesa MAX_TEXTURE_UNITS, MAX_TEXTURE_COORD_UNITS, and MAX_TEXTURE_IMAGE_UNITS are all set to 8. (src/mesa/main/config.h) And there are no sanity-checks done on the values returned by the drivers. Changing the defines to 16 makes everything work.

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-05-16 Thread Rune Petersen
Brian Paul wrote: Rune Petersen wrote: I found the problem: In Mesa MAX_TEXTURE_UNITS, MAX_TEXTURE_COORD_UNITS, and MAX_TEXTURE_IMAGE_UNITS are all set to 8. (src/mesa/main/config.h) And there are no sanity-checks done on the values returned by the drivers. Changing the defines to 16

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-04-27 Thread Rune Petersen
Adam Jackson wrote: On Wednesday 26 April 2006 10:14, Rune Petersen wrote: Hi, Since the 12 of April there has been a change that causes Quake 3 and Doom 3 (demo)not to exit properly. Quake 3 locks up the system, and Doom 3 does a double fault. The suspect as I see it is: Ensure all GART

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-04-27 Thread Brian Paul
Rune Petersen wrote: Adam Jackson wrote: On Wednesday 26 April 2006 10:14, Rune Petersen wrote: Hi, Since the 12 of April there has been a change that causes Quake 3 and Doom 3 (demo)not to exit properly. Quake 3 locks up the system, and Doom 3 does a double fault. The suspect as I see it

[r300] problems leaving the game (Quake 3 + Doom 3)

2006-04-26 Thread Rune Petersen
Hi, Since the 12 of April there has been a change that causes Quake 3 and Doom 3 (demo)not to exit properly. Quake 3 locks up the system, and Doom 3 does a double fault. The suspect as I see it is: Ensure all GART allocations are freed on context destruction But I have yet to confirm it. If

Re: [r300] problems leaving the game (Quake 3 + Doom 3)

2006-04-26 Thread Adam Jackson
On Wednesday 26 April 2006 10:14, Rune Petersen wrote: Hi, Since the 12 of April there has been a change that causes Quake 3 and Doom 3 (demo)not to exit properly. Quake 3 locks up the system, and Doom 3 does a double fault. The suspect as I see it is: Ensure all GART allocations are