Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-21 Thread Leif Delgass
On Wed, 20 Feb 2002, Michael Thaler wrote: > when I start UT I get the Intro. The Sound is o.k. but the Rendering > does not seem to delete old objects correctly. The same objected is > displayed at different positions of the screen without deleting the > old objects. The lights are just big whit

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-21 Thread Michael Thaler
On Thu, Feb 21, 2002 at 03:43:27PM +, Keith Whitwell wrote: > That's a bogus argument (though it may be true...) It's a sad state of > affairs that people are writing games with such crippled network/physics > subsystems that can't operate correctly unless the graphics adaptor has > certain

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-21 Thread Keith Whitwell
Gareth Hughes wrote: > > Keith Whitwell wrote: > >> > >>What is the point of sustaining such a frame rate that has no pratical > >>advantage? > >> > > > > You do "see" the partial frames, it seems. The eye seems to do a reasonable > > job of integrating it all, providing you with a low-latency v

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Gareth Hughes
Keith Whitwell wrote: >> >>What is the point of sustaining such a frame rate that has no pratical >>advantage? >> > > You do "see" the partial frames, it seems. The eye seems to do a reasonable > job of integrating it all, providing you with a low-latency view of the game > world. Hardcore game

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Keith Whitwell
José Fonseca wrote: > > On 2002.02.20 22:04 Gareth Hughes wrote: > > Jose Fonseca wrote: > >> > >> The maximum framerate you'll ever get is limited by your screen refresh > >> rate. > > > > If you implement sync-to-vblank, which no DRI driver other than tdfx > > does... > > > > -- Gareth > > > >

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread José Fonseca
On 2002.02.20 22:04 Gareth Hughes wrote: > Jose Fonseca wrote: >> >> The maximum framerate you'll ever get is limited by your screen refresh >> rate. > > If you implement sync-to-vblank, which no DRI driver other than tdfx > does... > > -- Gareth > mmm... so in fast cards, they render frames

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Gareth Hughes
Jose Fonseca wrote: > > The maximum framerate you'll ever get is limited by your screen refresh > rate. If you implement sync-to-vblank, which no DRI driver other than tdfx does... -- Gareth ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Dieter Nützel
On Wed, Feb 20, 2002 at 15:48, José Fonseca wrote: > On Wed, 2002-02-20 at 15:10, Michael Thaler wrote: > > On Wed, Feb 20, 2002 at 01:06:58PM +, José Fonseca wrote: > > > > > I usually get 10 to 20 fps with the settings attached. > > > > Thank you very much, Jose. I used your UnrealTournament

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Jose Fonseca
On Wed, 2002-02-20 at 15:10, Michael Thaler wrote: > On Wed, Feb 20, 2002 at 01:06:58PM +, José Fonseca wrote: > > > I usually get 10 to 20 fps with the settings attached. > > Thank you very much, Jose. I used your UnrealTournament.ini and it > really works fine for me! I even can use 640x48

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Michael Thaler
On Wed, Feb 20, 2002 at 01:06:58PM +, José Fonseca wrote: > I usually get 10 to 20 fps with the settings attached. Thank you very much, Jose. I used your UnrealTournament.ini and it really works fine for me! I even can use 640x480 and it is still really o.k. My chipset seems to be a little f

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread José Fonseca
On 2002.02.20 10:48 Michael Thaler wrote: > On Wed, Feb 20, 2002 at 11:07:49AM +0100, Michael Thaler wrote: > > I played a little bit with the UnrealTournament.ini options. If I set > > [SDLDrv.SDLClient] > NoLighting=True > > I don't get these errors anymore. But UT is slow. I think I get 5 to

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Michael Thaler
On Wed, Feb 20, 2002 at 11:07:49AM +0100, Michael Thaler wrote: I played a little bit with the UnrealTournament.ini options. If I set [SDLDrv.SDLClient] NoLighting=True I don't get these errors anymore. But UT is slow. I think I get 5 to 10 fps or something. Any hints how you can improve that.

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-20 Thread Michael Thaler
On Tue, Feb 19, 2002 at 03:47:44PM -0500, Leif Delgass wrote: First of all, I installed the same UT CD on a friends new Toshiba laptop with a Geforce2Go and Unreal works just fine on this laptop. It is definitely not the UT installation > Could you be more specific about what "just rubbish" loo

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread José Fonseca
On 2002.02.19 20:47 Leif Delgass wrote: > On Tue, 19 Feb 2002, Michael Thaler wrote: > > > Unfortunately Unreal is not working. It is loading and running just > > fine, the menues are displayed correctly but the intro and the game > > graphics are just rubbish. Has anyone seen that before? I inst

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread Leif Delgass
Try rebuilding from the current CVS branch, I commited a fix to make lightmap lighting work. On Tue, 19 Feb 2002, David Bronaugh wrote: > I know that at least in quake3 with my Rage Mobility P/M chip in my > laptop, lightmap lighting doesn't work. I am not sure if this is peculiar > to my setu

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread Leif Delgass
On Tue, 19 Feb 2002, Michael Thaler wrote: > Unfortunately Unreal is not working. It is loading and running just > fine, the menues are displayed correctly but the intro and the game > graphics are just rubbish. Has anyone seen that before? I installe UT > from a windows CD with the newest packag

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread David Bronaugh
I know that at least in quake3 with my Rage Mobility P/M chip in my laptop, lightmap lighting doesn't work. I am not sure if this is peculiar to my setup (I just thought, hey, it's a crappy old chip) but it might be relevant to the UT problem (I think UT is big on lightmap lighting). David Bro

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 07:20:13PM +, Jose Fonseca wrote: > > Thank you for all your efforts to get the Mach64 driver working. I > > Finally... :-) I think you made a lot of laptop guys happy:-)) > Yes. I manage to run Unreal with a 4 Mb ATI Rage Mobility. You really Is the intro displaye

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread Jose Fonseca
On Tue, 2002-02-19 at 18:51, Michael Thaler wrote: > On Tue, Feb 19, 2002 at 05:17:16PM +, Jose Fonseca wrote: > > > No, there's no need. You probably just have to change the order on which > > /usr/lib/ and /usr/X11R6/lib/ directories appear on /etc/ld.so.conf and > > run '/sbin/ldconfig' >

Re: [Dri-devel] Unreal [was: Mach 64 success and problems]

2002-02-19 Thread Michael Thaler
On Tue, Feb 19, 2002 at 05:17:16PM +, Jose Fonseca wrote: > No, there's no need. You probably just have to change the order on which > /usr/lib/ and /usr/X11R6/lib/ directories appear on /etc/ld.so.conf and > run '/sbin/ldconfig' I just symlinked the libGL and the libGLU in /usr/X11R6/lib to