Race Sim Central
Rec.Autos.Simulators Archive

GPL: Why do FPS change for same settings ?

6 posts by 6 people · 22 Dec 1998 - 07 Jan 1999

rob 22 Dec 1998#441413
Are you in the same position within the grid in each case? >Hi All, As my subject says, I've experienced differing frame rates for >exactly the same configuration. Eg. One day turn on short novice race at >Silverstone 5 opponents, on grid get 22FPS. Next day exactly the same but >get only 16-17FPS <snip> rob.
> My only theory that I can come up with is the old problem of Win95 not > handling memory over 64Mb too well, I don't know whether this is still a > problem with OSR2. Any thoughts would be appreciated. Dave. This has nothing to do with Win95, but is a hardware limitation of (older) motherboards. Memory over 64 MB can't be cached, which makes programs that run in that memory slower. There's nothing Win95 OSR2 can do to fix that (except not use it :-). Greetings, Marcel
Rob Adla 29 Dec 1998#442398
You say this is a hardware limitation with older motherboards. Does this mean this was rectified with the new 100 mhz motherboards (BX?)? -- Rob. >> My only theory that I can come up with is the old problem of Win95 not >> handling memory over 64Mb too well, I don't know whether this is still a >> problem with OSR2. Any thoughts would be appreciated. Dave. >This has nothing to do with Win95, but is a hardware limitation of >(older) motherboards. Memory over 64 MB can't be cached, which makes >programs that run in that memory slower. There's nothing Win95 OSR2 can >do to fix that (except not use it :-). >Greetings, Marcel
> You say this is a hardware limitation with older motherboards. Does this >mean this was rectified with the new 100 mhz motherboards (BX?)? The problem occurs exclusively with some of the older "classic" Pentium (non-II) chipsets by Intel, most notably the TX chipset. The BX chipset for Pentium II is not affected, since the cacheing takes place on the processor itself. A P II with 512k of L2 cache and a 16 bit TAG RAM (I believe) can cache up to 65536 x 512k = approx 32 GigaByte. This limit shouldn't pose a serious problem for another year or two. :) A Celeron A still can cache up to 8 GB with its 128k L2 cache, provided the TAG RAM is indeed 16 bit wide. BTW, the 64MB limit was neither a technical necessity nor a bug. The newer chipsets for the old Pentium were designed by Intel that way for marketing reasons. The message was: "if you need more RAM, buy a Pentium II". Chipsets by other manufacturers (VIA, Ali, etc.) weren't limited like that.
Quoted text (8 lines)>>> My only theory that I can come up with is the old problem of Win95 not >>> handling memory over 64Mb too well, I don't know whether this is still a >>> problem with OSR2. Any thoughts would be appreciated. Dave. >>This has nothing to do with Win95, but is a hardware limitation of >>(older) motherboards. Memory over 64 MB can't be cached, which makes >>programs that run in that memory slower. There's nothing Win95 OSR2 can >>do to fix that (except not use it :-).
-- Wolfgang Preiss \ E-mail copies of replies to this posting are welcome.
Charlie 06 Jan 1999#443875
One odd thing I found was that if I use Direct Input for the joystick (with "Poll with Interrupts Enabled") I get a much better frame rate than if I use Generic Input. I thought that I wasn't changing anything important, but I had been having problems with Direct Input so switched to Generic and it took me a while to find the cause of the loss in frame rate. Good Luck Charlie
% One odd thing I found was that if I use Direct Input for the joystick (with % "Poll with Interrupts Enabled") I get a much better frame rate than if I use % Generic Input. I thought that I wasn't changing anything important, but I % had been having problems with Direct Input so switched to Generic and it % took me a while to find the cause of the loss in frame rate. I would hazard to guess that this is because the Win95 routine for polling the gameport is less precise (and thus less intensive) than Papyrus' generic input. The polling range produced by Direct Input is much lower than the range when using generic. I assume this is because Win95 polls the gameport less often than does the generic. Thus, more cycles devoted to video refresh via direct input and more cycles spent polling the game port in the generic mode. [Of course this is just an educated guess/hunch.] -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

Sponsors

Affiliate Links

Sim Gaming Expo MOZA Racing Sim-Lab Fanatec TrakRacer Asetek Internet Privacy From NordVPN Dreamhost Capital One Credit Card Application Fanatical CDKeys Amazon Amazon UK Project Motor Racing iRacing Get your racing gloves, boots and more from Demon Tweeks. Enlist at Roberts Space Industries, developers of Star Citizen and Squadron 42


Back from the ashes since July, 2019. First created in 2001 with the merger of Legends Central (founded 1999) and simracing.dk.

A site by a sort of sim racer, for sim racers, about racing sims. News and information on both modern and historic sim racing software titles.

All products and licenses property of their respective owners.


Facebook Threads Bluesky Twitter Mastodon Instagram YouTube Tiktok Twitch Reddit Google News Apple News Subscribe via WordPress Flipboard eBay

Race Sim Central © 1999-2026 | Some links pay RSC a commission. Advertising does not equal endorsement.Cookie Policy