Tons of shader recompilation in TRLegend and screen set issues

[Artur Szymiec]

Greetings,

I would like to point out 3 issues with TR Legend game:
1) wine is outputing a ton of messages like:
    fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times
fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times
fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times
fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times
fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times
fixme:d3d_shader:IWineD3DVertexShaderImpl_CompileShader Vertexshader
0x13fb3028 recompiled more than 50 times

2) the game itself contain a gfx config dialog. Then at next startup it
should use this settings
    saved somewhere (I guess registry) but instead it dosen't - always
running the game will bring
    the config in the first place. Why is that ?

3) Still something is wrong with the  vertex shaders  and buffers - see
this screenshoot:
    http://img171.imageshack.us/my.php?image=screen3ub0.jpg

And the tons of shader compilation warnings happens in every water scene
like in the screenshoot.

Best regards
Artur

[Stefan Dösinger]

Am Freitag, 7. März 2008 21:06:01 schrieb Artur Szymiec:
> Greetings,
>
> I would like to point out 3 issues with TR Legend game:

Please file bugs at bugs.winehq.org instead of posting it to the mailing list

[Paweł Różański]

Hi

Artur: or you could find that at least one of these bugs is already filled
 http://bugs.winehq.org/show_bug.cgi?id=11357

But I have question which is more general (not only for Stefan Dösinger):

I tend to check if something changed in game/program that I'm
currently monitoring. Are new comments for bug like "it still not
woking at wine-....." need ?

Because i can add them :) every weekend or so. I really appreciate
developers time which was invested in wine. I just want to ask what is
more desired:

- report often that something doesn't work (to keep information current)
- leave it until dev response that this particular problem is solved
(but something can slip out)

Again - I don't want to look like impatient one (like i said - I
really appreciate what I have) I just want to know what will do better
job.

Keep care, your project keeps me thinking that everything is possible :)

[Edward Savage]

I wouldn't mind knowing this as well.  For example there is a bug in
the rendering of the planet in the eve loading screen (this affects
all in game planets too) and has been a bug for a year or more now.
I've been trying to work out if it is worth poking the bug report on
it or just leaving it till some one has time to go back over older
bugs.

2008/3/8 Paweł Różański :
> Hi
>
> Artur: or you could find that at least one of these bugs is already filled
>   http://bugs.winehq.org/show_bug.cgi?id=11357
>
> But I have question which is more general (not only for Stefan Dösinger):
>
> I tend to check if something changed in game/program that I'm
>  currently monitoring. Are new comments for bug like "it still not
>  woking at wine-....." need ?
>
> Because i can add them :) every weekend or so. I really appreciate
>  developers time which was invested in wine. I just want to ask what is
>  more desired:
> - report often that something doesn't work (to keep information current)
> - leave it until dev response that this particular problem is solved
>
> (but something can slip out)
>
> Again - I don't want to look like impatient one (like i said - I
>  really appreciate what I have) I just want to know what will do better
>  job.
> Keep care, your project keeps me thinking that everything is possible :)
>
> Paweł Różański

[Stefan Dösinger]

Am Samstag, 8. März 2008 06:53:53 schrieb Edward Savage:
> I wouldn't mind knowing this as well.  For example there is a bug in
> the rendering of the planet in the eve loading screen (this affects
> all in game planets too) and has been a bug for a year or more now.
> I've been trying to work out if it is worth poking the bug report on
> it or just leaving it till some one has time to go back over older
> bugs.

Retesting with every wine release is welcome, with some message 
like "Confirming bug in wine x.y.z" or similar. That way anyone who is 
interested in fixing the bug doesn't have to ask for a retest and wait for a 
reply when he wants to attack the bug.

@ The eve online problem: I've had a look at that, and Eve uses fixed function 
processing with somewhat insane transformation matrices, some fields are 10^6 
or even bigger.  Doing something like that is asking for precision problems, 
I am not sure if we can fix that