Jerome Glisse schrieb:
> On Wed, 27 Feb 2008 10:36:49 +0100
> Markus Amsler <markus.amsler@...> wrote:
>> nks for pushing, but it doesn't solve my problem :(
>> Idiotic, but valid wow-shaders like
>> ATTRIB v18 = vertex.normal;
>> MOV result.position, vertex.position;
>> lock up my r300 (but not Chris Rankins?). I could also handle it in
>> r300, but arbprogparse seemed the right place.
>> arbprogparse is quite complex, and I'm a mesa newbie, so there may be a
>> more elegant/correct solution.
> It might not be the program who lockup your gpu but others conditions,
> we know for sure that we are doing few things wrong on the syncronization
> area. Did you try this simple vertex program in dumb gltest ? You can
> hack one of the mesa example. And does it lockup too with such test.
> Jerome Glisse <glisse@...>
It's for sure the shader, I tested it with progs/vp/vp-tris. Chris, does
the above shader lock up your gpu with vp-tris?
r300VAPInputRoute0 doesn't find the attrib in inputs and returns
0xffffffff, which in turn locks up my gpu..
Chris Rankin schrieb:
> The only GPU lock-ups I see are when I try and bring another application window onto the screen at
> the same time as WoW, or with a particular "flame"/"cloud" effect that happens in Hellfire
> Peninsula or Silithus.
No problem with multiple windows here. I run wow in windowed mode
without winedesktop you too? I can't test flame/cloud because currently
i have no wow account, but it sounds like a vertex/fragment shader bug.
Chris, does the flag on the bottom-right corner off the startscreen also