>25% might be OK for the brake, but I prefer 50% (or full linear) for
>throttle.
that out...
Jason
Jason
Jason
Anything under 30 is where you start to notice the slowdown.
How the hell any of you are getting anything near 40fps is beyond me,
cos' my system's a hell of a PC but it struggles just to make the high
20's!
In the past I would agree with you about how over 30 SHOULD be smooth.
Although there are plenty here who claim to be able to see the difference
between 30 fps and 60 fps. I just noticed a stuttering, and others have had
the same symptom, that for me went away after I got the fps UP. I don't
know the cause the stutter but it's banished from my system for now at
least.
With F1 2k2 for me it came from lower screen rez and turning down the
graphic details. Just what is your "hell" of a pc? :) cpu and video card?
Maybe we can goose it some.
dave henrie
Thanks for these tips. These helped a lot to increase the feeling and
general manuerability...
.mikko
--
/* reality is an illusion that occurs
due to the lack of *** */
30fps is adequate to give an illusion of motion, though mainly on films
where motion kind of blurs from one frame to the next due to shutter speed.
However, PCs are so precise with the drawing of each frame, you don't really
get an illusion of smooth motion until approximately 45-50fps. 60fps is the
mark that many game makers aim for - particularly for game consoles where
the TV redraws the screen 60 times per second. If they can maintain a rate
at or above 60, they can lock (or sync) the frame rate to the TV's redraw
(refresh) rate of 60/s and give the smoothest motion possible.
Jason
No, not really. You're still seeing 60 fields or "half-frames" per second.
Though, if a game generates 30fps, it will simply display the even lines of
each frame for the first field then the odd lines of that same frame for the
second field. Games that run at 60fps show the even lines of one frame then
the odd lines of the next frame so you effectively get to see 60 different
frames in a second, even if you are only seeing half of the frame at a time.
As far as I know.
I don't understand why some people seem to have low frame rates. I have a
Hmmm...
Iain
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----
MadDAWG
> MadDAWG
There is so many "little" things that can effect performance Here is just
a few things that popped in my head. Motherboard chipset and drivers, Add-on
Graphics, Higher poly count models, Sound card overhead, RAM quality/speed,
Video Card driver version, Operating system. While you'll never get a 1 ghz
CPU and GF3 card to run as fast as a 1.5 ghz CPU with a GF4 I have seen the
opposite. Another thing that really gets me is how many people will say they
have the settings "maxed" to only find out later they had the world detail
at 50%. I'm not saying you are, but check out some of the FPS threads at the
official NR2002 board.
MadDAWG
As someone else said, it's REALLY funky once you are in a slide.
-Larry
> -Larry
> > >I wish I could tell you what it is, but I can't put my finger on it.
All
> I
> > >can say is something just doesn't feel right with the physics model in
> this
> > >game to me.
> > >It just doesn't feel 'right'.
> > Ah, an ISI n00b. =) The key to getting f1 2002 to feel "right" is the
> > wheel setup.
> > You have a microsoft wheel no? Try these settings, it's what I've
> > been using and I'm pretty picky:
> > Speed Sensitivity - 0%
> > Lock all the Axes and set them to 25%
> > Lock all the Deadzones and set them to 0%
> > From there I'd adjust the axis sensitivity up and down until the wheel
> > movement matches the movement of your wheel. With a ms sidewinder 25%
> > for all axes seems just about perfect, but YMMV. You definitely want
> > deadzones and speed sensivity disabled unless you're using a joystick.
> > Jason
It's a quick, very momentary pause about 1/10th of a second in length. Like
it's going to the hard drive for something.
-Larry