That is a huge drop, and it shouldn't happen in
properly coded software. I believe the RS wheel
should require less cpu resources than, say, the MS
or Saitek FF wheel.
The Force RS, and any other I-Force based FF wheel,
has an on-board FF effects processor that controls
the wheel. This processor should free the cpu from
most of the overhead associated with force feedback.
If I was more conspiritorially-minded, I might
theorize the the slowdown was intentionally produced
for Immersion products in CPR :)
Can someone with an MS or Saitek FF wheel comment
as to any slowdown it produces in CPR?
I don't notice a slowdown in the Viper demo,
but haven't done a comparison with and without
FF enabled. The Viper FF effects are very
well done.
--
Pat Dotson
IMPACT Motorsports
http://www.impactmotorsports.com/pd.html
I have a quick question about the Force RS and framerates in games. I am
running a P2 300 with 64 megs of ram and voodoo2 SLI. In Cart Precision
Racing I usually get 85 - 100 frames per second. When I enable Force
feedback, however, the frame rate drops to 17-30 frames per second. Why such
a dramatic drop? Does Force feedback require that much of the cpu's power,
or is it just the way that particular game handles forcfeedback commands?
Will I see a drop like tat in all Force enabled games?
Any reply would be appreciated!
Cory
The MSFFW also has an on-board processor to handle this.
-Larry
Quoted text (7 lines)
> The Force RS, and any other I-Force based FF wheel, > has an on-board FF effects processor that controls > the wheel. This processor should free the cpu from > most of the overhead associated with force feedback. > If I was more conspiritorially-minded, I might > theorize the the slowdown was intentionally produced > for Immersion products in CPR :)I think that's the key in this case. That's some pretty bad software,
and it probably doesn't have the best FF effects routines on the block.
-Larry
> That is a huge drop, and it shouldn't happen in
> properly coded software.
