January 11, 201511 yr I would start to look at a system issue then. First question.. do you have 1X8GB RAM or 2X4GB installed? Bert
January 11, 201511 yr My advice to you (and to the fsx community in general) is to stop tweaking and messing around, delete your config file and just enjoy flying for a while. 95% of the problems with fsx are the result of overtweaking. Highmemfix=1 is the only tweak I have in my config, and I have a wonderful experience. Cheers!
January 11, 201511 yr My advice to you (and to the fsx community in general) is to stop tweaking and messing around, delete your config file and just enjoy flying for a while. 95% of the problems with fsx are the result of overtweaking. Highmemfix=1 is the only tweak I have in my config, and I have a wonderful experience. Cheers! He is getting this even with a default FSX.cfg file and a slow moving plane. He tweaked to try and fix his situation, but that didn't help. Now what should he do?
January 12, 201511 yr My advice to you (and to the fsx community in general) is to stop tweaking and messing around, delete your config file and just enjoy flying for a while. 95% of the problems with fsx are the result of overtweaking. Highmemfix=1 is the only tweak I have in my config, and I have a wonderful experience. Cheers! +1 for this! At the very least it gives you good starting point for diagnosing any potential problems. Also, make sure nothing is running in the background (anti-virus background scans, for example). Have a look in the task manager while FSX is running and see if any processes are eating processor time. Whilst a number of people recommend Bojote's automatic tweaking site, it hasn't been updated for a number of years and technology has moved on. I found that his tweaks made FSX worse for me. The only tweak I now have is highmemfix. I run in DX10 mode with the Scenery Fixer (highly recommended) and find that FSX runs well on my old i7-920 with an equally old nVidia GTX 275 graphics card (all of 896mb of video RAM). Backup your fsx.cfg, delete it and start again - you have nothing to lose and everything to gain. i7-14700k | Asus ROG STRIX Z790-F Gaming WIFI | 32GB DDR5 RAM | MSI RTX 4080 Super | WD Black SN850X 1TB & 2TB | Corsair HX1000i ATX3.0 | MSI MAG401QR 40" monitor | Win 11 Pro 64-bit | Meta Quest 3
January 12, 201511 yr He is getting this even with a default FSX.cfg file and a slow moving plane. He tweaked to try and fix his situation, but that didn't help. Now what should he do? He never said that. He said that with "everything from ground zero" (his words) he still get them. Well, I don't know what "everything" entails, but I'm inferring that it involves some tweaking.
January 12, 201511 yr Guys, please read post #15. Did you read what I wrote at all? In post #15, he says: "I've done it again, everything from ground ZERO". From his previous posts, what I understand is that doing everything from ground zero, to the OP, involves tweaking the config file and using that Bojote tool, that frankly, should be taken down, because it's the worst thing you could do. What we are recommending is to him just delete his cfg file and let FSX rebuild it, and see what results he gets with a "virgin" one. From his posts I don't get the impression he ever did that. Cheers!
January 12, 201511 yr As a sanity check, you can turn the 3DMark benchmark, freely available. It is a combined test of processor speed and GPU and will give you a reference point to "similarly configured" systems. I thought I was going nuts (I have a similar thread here on AVSIM) so it was nice to see my system was performing as expected and that "something" else was the culprit. http://www.futuremark.com/support/downloads John Howell Prepar3D V5, Windows 10 Pro, I7-9700K @ 4.6Ghz, EVGA GTX1080, 32GB Corsair Dominator 3200GHz, SanDisk Ultimate Pro 480GB SSD (OS), 2x Samsung 1TB 970 EVO M.2 (P3D), Corsair H80i V2 AIO Cooler, Fulcrum One Yoke, Samsung 34" 3440x1440 curved monitor, Honeycomb Bravo throttle quadrant, Thrustmaster TPR rudder pedals, Thrustmaster T1600M stick
January 12, 201511 yr You have quite a high Fiber Fraction setting in your fsx.cfg, but at the same time, you have not limited the frame rate internally. Limit your frame rate and test it again, since the Fiber Fraction is only effective then. See here: http://forum.avsim.net/topic/458488-is-the-fiber-frame-tweak-only-effective-if-fps-is-limited-internally/#entry3142655
January 12, 201511 yr Who's got popcorn? In my experiences, stay away from tweaks like Bojote. K.I.S.S. is the best approach, then slowly add tweaks if needed or desired. Remember, FPS means nothing in FSX, it's How smooth is it? I have had smooth as glass experiences at 13 - 15 FPS. Consider DX10 and Steve's Fixer. Ric Elmore
January 12, 201511 yr It's a bit of a problem with fast jets. I don't fly them because of this. FSX can't seem to keep up with high speed aircraft unless you turn down the settings. IAN Bingo, I love flying them just not in fsx.
January 12, 201511 yr FSX Fiber Accelerator can help with problems such as these. I would suggest giving the free demo a try Michael Turner
January 12, 201511 yr Who's got popcorn? In my experiences, stay away from tweaks like Bojote. K.I.S.S. is the best approach, then slowly add tweaks if needed or desired. Remember, FPS means nothing in FSX, it's How smooth is it? I have had smooth as glass experiences at 13 - 15 FPS. Consider DX10 and Steve's Fixer. This is actually really accurate. I landed in a massive storm at LAX yesterday with rain, all the clouds from REX, FSDT LAX, plus my UT2 and it was about 17 FPS on approach but it seemed much smoother than I had experienced before. Of course after landing the FPS dropped to around 10 and it got choppy but I have just come to expect that as I don't think there is a way to run all those add-ons and still get high FPS even with the system I have.
Create an account or sign in to comment