I have MASSIVE framefrate problems whenever the action gets nasty.
System:
Dell 1.7G P4, 256M RAM, 64M GeForce3, Windows ME, unknown DirectX but probably 7.xx
AH Settings:
FPS limited to 45
Resolution: 600x800
Color: 16-bit
Connecting via 28.8k dial-up
History
Initially, I didn't have the FPS limiter set. All video settings were default (800x600, 16-bit color, unlimited FPS, all details on, max horizon distance). When flying, the FPS meter said 60 and never changed. But when I'd saddle up on a lone nme plane at alt, nothing on the ground cluttering up things, I'd go into serious stutter mode. Then I heard about limiting FPS in the Video settings and that solved this problem. FPS meter now says 45, sometimes dips to 43, and I have no FPS problems vs. single nmes at say 5k+ AGL.
Current Problem
Smoke utterly destroys my FPS. This happens with smoke from burning target planes but is especially bad near burning buildings on the ground. For instance, manning a gun or vehicle at a damaged airfield. When I traverse the gun across the smoke of a nearby burning building, my FPS drops to zero. The video freezes when the sight touches one edge of the smoke cloud and doesn't start going again until continued control input has moved the sight to the other edge of the smoke. Then the video jumps the sight to that position and all bullets, planes, etc., also jump to the positions they've reached during my frozen video time. During the frozen time, even the FPS meter is frozen so continues to read 43+ FPS despite it really being zero.
I find this all rather strange. Previously I was flying with a Celeron 450, 128M RAM, and a TNT 1. I had nothing resembling this sort of problem, although I did have to run with medium horizon distance. So why does going to a way faster machine result in much worse video performance?
[ 08-20-2001: Message edited by: Bullethead ]