Anybody running F1RS on a PII450?

I don't think the p2 350 uses a 100 mhz bus; seems like that was what made the jump to 400 larger than normal. I expect to be corrected if I'm wrong. rob. >>Path: >>You don't happen to remember anything about the subject headers or keywords >>in these posts do you? Last night I spent like 15 minutes on deja news >>searching this group and couldn't come up with anything. >>Anyway, this ticks me off because UBISoft says they won't do anything about >>it since my system is overclocked. But I'm betting it does the same thing >>on true P2 450s, or any CPU with the 100MHz bus for that matter. I just >>need to verify that so I can get back with their tech support and tell them. >Not true. I'm running on a P2-350, no problems. >Z.

Do you have problems with the internal game clock running 33% too fast (100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This game runs 33% too fast when I have the bus clocked at 100MHz. If you time the lap clock, you will see that 1 minute of game time is 40 seconds real time. This makes it a real *** to drive! It runs normal when I have the chip running at 300. I'm wondering if people with true P2 450s are having the same trouble. What the heck is the game timing itself to? I have my motherboard set as if there were a real P2 450 in there, but F1RS gets confused. -- Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith

Several months ago there were posts about your exact complaint. I don't think there ever was a resolution to the problem either. I am just glad I have a lowly P5-200MMX as the game runs perfect :-) -- Header address intentionally scrambled to ward off the spamming hordes. cisko [AT] ix [DOT] netcom [DOT] com >Do you have problems with the internal game clock running 33% too fast >(100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This >game runs 33% too fast when I have the bus clocked at 100MHz. If you time >the lap clock, you will see that 1 minute of game time is 40 seconds real >time. This makes it a real *** to drive! It runs normal when I have the >chip running at 300. I'm wondering if people with true P2 450s are having >the same trouble. What the heck is the game timing itself to? I have my >motherboard set as if there were a real P2 450 in there, but F1RS gets >confused. >-- >Jarrod Smith >The Scripps Research Institute >http://www.scripps.edu/~jsmith

You don't happen to remember anything about the subject headers or keywords in these posts do you? Last night I spent like 15 minutes on deja news searching this group and couldn't come up with anything. Anyway, this ticks me off because UBISoft says they won't do anything about it since my system is overclocked. But I'm betting it does the same thing on true P2 450s, or any CPU with the 100MHz bus for that matter. I just need to verify that so I can get back with their tech support and tell them. Thanks. You lucky dog with the P200 MMX ;-) Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith >Several months ago there were posts about your exact complaint. >I don't think there ever was a resolution to the problem either. I am >just glad I have a lowly P5-200MMX as the game runs perfect :-)

>You don't happen to remember anything about the subject headers or keywords >in these posts do you? Last night I spent like 15 minutes on deja news >searching this group and couldn't come up with anything. I found it. The "keystone cops" thread, right? This is terrible. Ubisoft must fix this or their game will be unplayable on newer PCs. Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith

Please elaborate. What version F1RS are you running? What motherboard are you using? I'd really like to get this game running. Help please! Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith >Tested it on a 450 and a Celeron 300a at 450--runs fine (normal speed) on >both. >Marc.

Thanks to all who responded. It turns out to be something very stupid that Ubisoft tech support should have been well aware of, but wasn't for some reason. The problem turned out to be the sync on vertical refresh setting in my voodoo2 driver control panel. I had disabled it, and this caused the clock in F1RS to coincidentally run 33% faster than real time. With vsync on, game time runs spot-on what it should. Combined with the response I got from Ubisoft blaming my overclocked computer (66->100 = 33%), I was incorrectly making a connection between the two things. Running the chip at 300 slowed the machine down enough to where the problem didn't appear (another coincidence). Back to racing :-) Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith

Quoted text (14 lines)

>Do you have problems with the internal game clock running 33% too fast >(100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This >game runs 33% too fast when I have the bus clocked at 100MHz. If you time >the lap clock, you will see that 1 minute of game time is 40 seconds real >time. This makes it a real *** to drive! It runs normal when I have the >chip running at 300. I'm wondering if people with true P2 450s are having >the same trouble. What the heck is the game timing itself to? I have my >motherboard set as if there were a real P2 450 in there, but F1RS gets >confused. >-- >Jarrod Smith >The Scripps Research Institute >http://www.scripps.edu/~jsmith

Tested it on a 450 and a Celeron 300a at 450--runs fine (normal speed) on both. Marc.

Quoted text (14 lines)

>Do you have problems with the internal game clock running 33% too fast >(100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This >game runs 33% too fast when I have the bus clocked at 100MHz. If you time >the lap clock, you will see that 1 minute of game time is 40 seconds real >time. This makes it a real *** to drive! It runs normal when I have the >chip running at 300. I'm wondering if people with true P2 450s are having >the same trouble. What the heck is the game timing itself to? I have my >motherboard set as if there were a real P2 450 in there, but F1RS gets >confused. >-- >Jarrod Smith >The Scripps Research Institute >http://www.scripps.edu/~jsmith

My system is a Abit BH6 with a Celeron 300a overclocked to 450Mhz. I'm using a 100Mhz busspeed but I've got the PCI bus set to 33Mhz. The timing is perfect. Game runs smoothly. Only problem is it defaulted to installing for my 3Dfx card. I'd like to try it with my G200. A true 100Mhz busspeed system runs with the memory bus at 100Mhz, the AGP bus at 66Mhz and the PCI bus at 33Mhz. For the Abit you need to set this in the processer setup screen by picking 2/3rds as the ratio. On other motherboards you need to tape pin B21 as described on Tom's Hardware page. Don't know if you are overclocking the PCI bus or if that is your problem. Just know, I am not...and it works here. >Do you have problems with the internal game clock running 33% too fast >(100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This >game runs 33% too fast when I have the bus clocked at 100MHz. If you time >the lap clock, you will see that 1 minute of game time is 40 seconds real >time

Quoted text (9 lines)

>Path: >You don't happen to remember anything about the subject headers or keywords >in these posts do you? Last night I spent like 15 minutes on deja news >searching this group and couldn't come up with anything. >Anyway, this ticks me off because UBISoft says they won't do anything about >it since my system is overclocked. But I'm betting it does the same thing >on true P2 450s, or any CPU with the 100MHz bus for that matter. I just >need to verify that so I can get back with their tech support and tell them.

Not true. I'm running on a P2-350, no problems. Z.

Yes that sounds like the right thread. -- Header address intentionally scrambled to ward off the spamming hordes. cisko [AT] ix [DOT] netcom [DOT] com >>You don't happen to remember anything about the subject headers or keywords >>in these posts do you? Last night I spent like 15 minutes on deja news >>searching this group and couldn't come up with anything. >I found it. The "keystone cops" thread, right? This is terrible. Ubisoft >must fix this or their game will be unplayable on newer PCs. >Jarrod Smith >The Scripps Research Institute >http://www.scripps.edu/~jsmith

>Thanks to all who responded. It turns out to be something very stupid that >Ubisoft tech support should have been well aware of, but wasn't for some >reason. The problem turned out to be the sync on vertical refresh setting >in my voodoo2 driver control panel. I had disabled it, and this caused the Wow! Cool glad you found the answer!!!!! I'll be saving this message incase I upgrade :-) -- Header address intentionally scrambled to ward off the spamming hordes. cisko [AT] ix [DOT] netcom [DOT] com

Can't help you, but, that's a 50% (not 33%) speed increase that you're talking about. Sorry, pet peeve (hey, at least I'm not correcting your spelling and grammar :). NAR Northeast Regional Contest Board site - points and more...

v 1.09 on an Asus and a Abit mother board. Obviously, there is something not quite right with your system...but, of course, that is true of 99% of the problems raised here... Marc.

Quoted text (13 lines)

>Please elaborate. What version F1RS are you running? What motherboard are >you using? I'd really like to get this game running. Help please! >Jarrod Smith >The Scripps Research Institute >http://www.scripps.edu/~jsmith >>Tested it on a 450 and a Celeron 300a at 450--runs fine (normal speed) on >>both. >>Marc.

Right you are. How about this: Real time is 33% slower than F1RS time? :-) In case you didn't see the resolution to this problem, make sure you have vsync turned on in your voodoo drivers, folks. Otherwise trading ghost laps is pretty much a farce! Jarrod Smith The Scripps Research Institute http://www.scripps.edu/~jsmith >>Do you have problems with the internal game clock running 33% too fast >>(100MHz bus vs 66MHz bus)? I'm having trouble with my Celeron 450a. This >>game runs 33% too fast when I have the bus clocked at 100MHz. If you time >>the lap clock, you will see that 1 minute of game time is 40 seconds real >>time. This makes it a real *** to drive! It runs normal when I have the

Quoted text (12 lines)

>>chip running at 300. I'm wondering if people with true P2 450s are having >>the same trouble. What the heck is the game timing itself to? I have my >>motherboard set as if there were a real P2 450 in there, but F1RS gets >>confused. > Can't help you, but, that's a 50% (not 33%) speed increase that >you're talking about. Sorry, pet peeve (hey, at least I'm not >correcting your spelling and grammar :). >NAR Northeast Regional Contest Board site - points and more...

> I don't think the p2 350 uses a 100 mhz bus; seems like that was > what made the jump to 400 larger than normal. > I expect to be corrected if I'm wrong. The P2 350 does indeed use a 100 mhz bus. Trips

>I don't think the p2 350 uses a 100 mhz bus; seems like that was >what made the jump to 400 larger than normal. >I expect to be corrected if I'm wrong. Actually it does. Multiplier 3.5, FSB 100 makes 350 mhz. The P2-333/ Celeron 333 are the highest 66 FSB Intel processors available. Remco

>I don't think the p2 350 uses a 100 mhz bus; seems like that was >what made the jump to 400 larger than normal. >I expect to be corrected if I'm wrong. >rob. Z.