This is strange as the texture management code was pulled straight from
r200 driver - I would have expected it to work.
Can you tell me how to get at these offsets? it will be easier to debug
compared to lockups :)
I started looking for the code to point you to and could not resist to
experiment
Does the same happen if you load them in a different order ? What is the
difference between these textures ?
the first and last texture are the only textures that work properly. If I
change the order it is still the first and last texture.
To me it smells like an texture allocation/management bu
Vladimir Dergachev wrote:
> On Sun, 30 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
This is indeed strange.. Is texture[4] used anywhere before ? Does the
same happen with latest CVS ?
There are 5 textures 0 to 4 (including 2 masks ) texture 0 and 4
appear stable 1-3 appear unstable.
On Sun, 30 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
This is indeed strange.. Is texture[4] used anywhere before ? Does the
same happen with latest CVS ?
There are 5 textures 0 to 4 (including 2 masks ) texture 0 and 4
appear stable 1-3 appear unstable.
With the latest CVS I once m
Vladimir Dergachev wrote:
>>> This is indeed strange.. Is texture[4] used anywhere before ? Does the
>>> same happen with latest CVS ?
>>
>>
>> There are 5 textures 0 to 4 (including 2 masks ) texture 0 and 4
>> appear stable 1-3 appear unstable.
>>
>> With the latest CVS I once managed to run the
On Sun, 30 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
Lesson 20 have 3 points that causes lockups (maybe more).
They are all related.
the first is at line 258-259:
glBindTexture(GL_TEXTURE_2D, texture[3]);
glBegin(GL_QUADS);
glBegin() is causing the lockup, but only when te
Vladimir Dergachev wrote:
>> Lesson 20 have 3 points that causes lockups (maybe more).
>> They are all related.
>>
>> the first is at line 258-259:
>>glBindTexture(GL_TEXTURE_2D, texture[3]);
>>glBegin(GL_QUADS);
>> glBegin() is causing the lockup, but only when textures 1, 2, or 3.
>>
fallback). As for lesson20 I have no idea - try commenting out drawing code
and checking which part creates a lockup.
Btw, I am getting a partial lockup with lesson20 even without
r300_dri.so (when it is absent the driver falls back to software
rendering), so it might be due to mode switchi
Vladimir Dergachev wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg & r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple programs or tutorials.
Try NeHe tutorial - nehe
On Fri, 28 Jan 2005, Rune Petersen wrote:
Vladimir Dergachev wrote:
On Thu, 27 Jan 2005, Rune Petersen wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg & r300_driver.
Are there any simple way to locate the functions that course lockups?
I w
Vladimir Dergachev wrote:
On Thu, 27 Jan 2005, Rune Petersen wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg & r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple progra
On Thu, 27 Jan 2005, Rune Petersen wrote:
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg & r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple programs or tutorials.
Try NeHe
Hi,
I get lockups running anything other than glxgears.
I am running the 25 jan. snapshots of Xorg & r300_driver.
Are there any simple way to locate the functions that course lockups?
I was thinking of something like simple programs or tutorials.
Rune Petersen
--
13 matches
Mail list logo
