Hi GPL gang,
I'd like to find out, what part of my system needs an update to get the
important 36 fps again. I missed my 36 after going to FF with an MSFF!
The specs: PII350, 64MB, Voodoo2 8MB, GPL.1.2.0.1, MSFF non USB.
I guess, it is not the Voodoo2: I get nearly the same fps's in all the
resolutions from 512x384 to 1024x768! The "Quality" and "Effects" do
not seem to have any noticeable effect. "Deatail Bias" seem to have
an effect. No very strong, though. The same with the mirrors.
I also guess, MSFF uses the processor heavily? Or does it? What could be
the component to be updated? Where actually the needs of MSFF are?
Processor? Memory? Video card?
Arto
Your system should run 36fps easily.
If it does not, I can only think it is the MS-FF wheel that eats
CPu-cycles. It seems that DirectX-7 makes the MS-FF a lot easier on the
CPU, so give it a try!
And I thought Voodoo2's don't do 1024x768!!
Make sure it's in Glide, not D3D.
[snip]
Voodoo2 can do 1024x768 in GPL as it doesn't
make use of a z-buffer. This frees up enough
framebuffer memory that the card can run at
the higher resolution. This includes when running
in Glide.
Jason
I asked:
There seemed to be no one to know, where the bottleneck is. So I repeat
my question. Better luck this time? :-)
Arto
Arto, I didn't read the previous messages in this thread, but I've
read that the MSFF does take a big hit on the processor. The LWFF
doesn't use much processor power.
Andre
You're using DX-7? Seems to be better (less CPU) with the MSFF.
You really should be able to get 36fps, without any upgrades. I get 36fps
with aa PII-233 (V2), so.
You run it in Glide-mode, right?
>Arto, I didn't read the previous messages in this thread, but I've
>read that the MSFF does take a big hit on the processor. The LWFF
>doesn't use much processor power.
>Andre
Though I'm using an Act Labs RS Force now (mostly for the RS shifter), I
have a MSFF and I can tell you that while it may use more processor cycles
than some of the other wheels, it's a relative thing and the hit is just not
that significant in terms of slowing frame rates. I never had a problem
getting good frame rates with it (PII-400).
I'd say go for a V3-2000 or V3-3000. I had a Voodoo2 12MB and after
changing to a V3-3000 AGP GPL is running much better. I got almost a
10 fps increase in the starting grid at Monza and I now get constant
36 fps during races (online and offline) after the start.
--
Greger
The MS FF wheel takes a significant amount of CPU time. I don't recall the
figures off hand, but I suspect if you dig through dejanews you'll see a
post from me with some comparisons. So an increase in CPU speed would be
required to offset its needs.
Its only connection to the machine is at the game port. To use its FF
capabilities, data (force commands of some form or another) must be sent
from the computer to the wheel through this port. The game port is not
primarily an output device, and so it has no hardware support for
transmitting data to a connected device (like the old days of serial ports
without 16550 UART's, only worse). Thus, any clocking of data out to the
device (and potentially clocking in any data being read from it) must be
done in software.
Randy
I once compared my standard game port Ecci wheel to the MSFF. The conclusion
was that the MSFF is slightly less efficient in GPL than the Ecci when used
without FF (-3% to -5%), and much less efficient when used with FF (-10%).
In GP2 the Mssw is slightly less efficient than the Ecci, but the difference
is very small (-2%). Full report here: www.xs4all.nl/~westrab/msswfps.htm .
This comparison was made before the release of DirectX 7.
Bart Westra
> The MS FF wheel takes a significant amount of CPU time. I don't recall the
be
