Hmmm...
Please define "buggy." Aside from the poorly designed menus, I find F1RS 1.09
among the best sims I've raced. Perhaps providing some specifics about your
issues will lead to a resolution. Simply referring to it as "buggy" does
nothing. What are your problems getting it "running?" Frame rate? AI? Gameplay?
For tools and utilities to enhance the sim, check out
http://www.f1racingsim.com.
Cheers,
Jim
Keith.
and
What does wsock32.dll have to do with F1RS?
I haven't heard anyone with your soundcard using it with F1RS.
Especially with the 3D sound patch.
--
Header address intentionally scrambled to ward off the spamming hordes.
> > Is there a new patch coming out for this game I just bought it and it's the
> > buggiest game I've ever had. The patch 1.09 does nothing to get it running.
> It will be called Monaco Grand Prix Sim aka F1RS2 and will cost you another $40
> or so. I doubt there will ever be another patch for F1RS. My installation is
> staying at version 1.05 because all newer versions are much slower on my PC.
> Your mileage may vary.
l8er
ronny
--
Toys'R'Us '99: "So, would you like a hand gun with that action figure,
kiddo?"
|\ _,,,---,,_ I want to die like my Grandfather,
ZZZzz /,`.-'`' -. ;-;;,_ in his sleep.
|,4- ) )-,_. ,\ ( `'-' Not like the people in his car,
'---''(_/--' `-'\_) screaming their heads off!
Have you tried *all* of the following?
1) Have you set the min & max virtual memory to the *same* amount,
eg:- F1RS requires a min of 128Mb? its no good setting the min to say
100 and the max to 130 as the computer will take up valuable time
figuring out what the *actual* file size should be? if you set the min
& max to the *same* the computer spends zero time on it as the file
size is set!!!
2) Also, I have a K6 200 and F1RS rocks? is your pc set-up ok to run
games generally? do you run other games and do they run ok? If not you
might want to optimise your pc so that it is biased for games?
3) How much memery do you have? I started with F1RS and 32Mb SDram,
and it ran ok, but with 64Mb it really flies?
4) Did you do a *full* install when you installed the game? if not, do
it, as this will speed up the whole game in general.
5) You are running it in *3Dfx* mode aren't you? Make sure that when
you installed the game it recognised your 3Dfx card, and that when the
game starts it runs the f1voo.exe file and no other file?
Sometimes f1rs can move two important files during the istall process,
and this means it cannot 8see* your 3Dfx card? check your
windows/system directory for Glide.dll & sst1init.dll. If they are
there then fine, if they are not, copy them from your original f1rs cd
to the windows/system directory and f1rs will now be able to see your
3Dfx card ok. NB: It is recommended that you have at least a 4mb D3d
card, but a 3Dfx card is highly recommended.
6) Patches, make sure you have installed the latest patches for the
game as these do improve performance. The latest is v1.09 (get it from
any of the many good f1rs sites, just search for ubisoft & f1rs on
the net?)
7) Have you made the recommended changes to the sound files in the
game, this improves the first corner slowdowns that some people
suffer? To alter the sound files do the following.....
In the F1RS\CPA\dll directory you'll find a file called Snd_cpa.ini.
You've got to change the following parameters:
SXD_DIST_SATUR=5
SXD_DIST_FADE=75
The SXD_DIST_FADE option is the most important: this one determines
the distance at which another car can be heard (or to be more precise:
at which distance the other car's sound will fade in or out). The
default setting is way too high: when you're on pole position, a
number of 75 will let you hear all cars around, up to the one at the
back of the grid (it seems)! No wonder you can't hear your own engine
anymore. (And maybe, as I said before, the computer has a hard time
producing the sound of 22 cars, hence the framerate drop at the
beginning of the race?) Two cars in your neighbourhood is enough to
make it impossible to hear your own engine. Lowering this to a very
low number will do the trick, but then you may not be able to hear a
car coming up behind you until he's beside you.
SXD_DIST_SATUR seems to change the overall volume of the other cars.
But lowering this from 5 to 1 isn't enough. Especially if you don't
alter the FADE setting: being able to hear all 22 car engines will
still make you deaf.
Change the settings to.....
SXD_DIST_SATUR=1
SXD_DIST_FADE=15
Just fiddle around a bit with these numbers, and you'll see your
performance will get better.
8) Generally *less* wheel lock is preferred to more, only increase the
lock if you cannot get around the slow corners (hairpin at
Monaco?) NB: Also remember the default set-ups understeer badly, so
tweaking the set-ups is essential to getting the most from the cars
(or download some set-ups from the net).
9) Make sure the UBI.INI file in your \windows\ubisoft directory is
set to "3dfx=1" to get the 3Dfx version running.
10) Your *not* using a Cyrix cpu or an AMD K5 cpu are you? as these
will either only run F1RS very slowly, or not at all!
11) Make sure you are specifying in your windows game controller (in
control panel)that your controller is a *race car controller* and not
a joystick. Otherwise it places a deadzone in the calibration. In
control panel game controllers, go to "Add" and select custom, switch
on the "special characteristics" radio button, and select "is a race
controller"
8-)
*Peter* 8-)
(NB: remove asterix to e-mail)
Read the ubisoft FAQ for the answer to your question.