JWNoctis

FSX ground traffic hits performance pretty bad, and one thing Vector did is to add lots of roads with traffic on them, especially in places already loaded with complex scenery. And yeah, been doing without them as well, even though FTX Global tail-lights looked pretty neat.

Been wondering about this as well. Would have been nice to have, especially GTN integration for Legacy and the general update. Hope those improvements would trickle back to FSX version too. EDIT: There seemed to be a newer entry: "We expect the Turbine Duke and Legacy updates will be available very soon (we are in the final testing stages). The Piston Duke V2 will also be updated in the near future to V2.5 including landing light options to address clickspot problems some users are having, plus full integration with GTN gauges, improved sounds, and installers for P3D v2 and v3." Sounded like soon for Legacy, and a bit longer for piston Duke...Gotta jump to P3D someday.

Also invest in more RAM if possible. As observation goes, extra RAM is used by OS as disk cache, thus FSX does not have to load things like VC textures from disk after initial load.

I see...does look good, thanks!

Just found that out on approach into Calgary Springbank...guess a tablet turned EFB is still necessary! Or maybe charts on another screen.

If you have an optical drive, you can replace that with a hard drive with an adaptor, preferably your current HDD, then get a SSD and fit that into where your hard drive once was. Also get a USB to SATA cable so you will still have an optical drive if needed.

Make sure to cap framerate in settings if you didn't, even though it would cause a general performance drop. Not capping framerate would cause ground texture blurring on mine on something as slow as a Cub for some reason, all other settings being the same. Also make sure FSX data is not NTFS compressed, I've made that mistake once. And defragment FSX drive.

Check motherboard for leaking capacitors, see if someone near had a spare PSU and try with that, check contact of power button. Also USB ports had a very limited cycle life, 1500 or so I thought. Maybe seek an USB hub if things get worse.

Garmin updated their GTN trainer a while back, for which F1 GTN basically got a free database update as they are in fact an interface to integrate said trainer into FSX. Performance loss with GTN is tolerable on the scale of about 5fps on my mid-line setup, from high 20s to mid-low 20s onboard A2A aircrafts with fair weather and scenery addons. Of the database themselves...Guess only the few that actually own or share an actual GTN-equipped aircraft and kept an up-to-date database could do much about it, as the price of one relatively complete set of such updates usually exceeded the rest of the average simulator setup combined, including hardware.

Also might be good to turn off crash detection - You don't need it to know if you messed up, and all it does is to reset your game with no option even for replay. I saw this myself a while back on my NGX into Ray Smith's KBOS. Got basically sucked onto 33L from 50ft...While I did go below Vref earlier on approach and did not quite stablize by 1000 AGL, no stall warning, or stick shaker, or windshear/microburst warning from ASN, or warnings of any kind were observed while the machine smashed down just past threshold, except for a EGPWS sinkrate as it did that. For a short while I thought I hit a seawall or something, but instant replay showed otherwise. No idea what happened or why it happened, but it didn't happen again for some time, at least not with the lighter aircrafts I've been flying around other airports.

I can confirm a 4-5 fps drop from about 20fps in complex autogen scenery, with my current Steam edition setup. Curiously, moving the mouse over some menu negated the drop, besides moving pointer outside window in windowed mode. Wonder what black magic is at work there.

FSUIPC's friction fix might help a bit. Add PatchSIM1friction=Yes to your FSUIPC4.ini under [General] section, and it works without the paid version. Taxiing is generally easier with that option, though I'm yet to try single engine taxi with that. EDIT: Haven't been able to get DynamicFriction.lua to work in any observable way. Guess I gotta try again.

Used to be A330 versus B767 and A340 versus B777, though the A330 came quite a bit later than 767 and was much heavier. B777 was again heavier. Also the Aerosoft bus was nice enough for what it claimed to do, as in most of normal operations save for relatively minor inaccuracies. For something that goes into study-level, one had to wait for that other upcoming bus.

Currently on this setup - Same hard drive, same dedicated-to-flightsimming partition too, and no conflict is observed, since they had separate installation folders and (AFAIK) registry keys. Doubt installing FSX-SE on a separate HDD would help, unless you want to run both at the same time and avoid the slowdown of two flight sims reading large amount of data on the same drive, or, say, wanted to dedicate a fast HDD or SSD to it for speed.

Words seemed to be that FSX defaults to full tank with no config option, but would keep fuel onboard number in a saved flight. Tools like FSPassenger do track fuel amount on aircrafts registered in them, though.

If this is any confirmation, I've just completed a SYD-LHR run in the 77L over 21 hours as a stability test. No OOM warnings and smooth from block out to block in, with no abnormalities observed. Setup is recent Win 10 upgrade from Win 7, FSX-SE on DX9 with PMDG 777 and a few other aircraft addons along with ASN, and no scenery or texture addons yet, running on 3-year old i7-3632QM/2.9GHz with recently upgraded 16GB of RAM and GT640M with 2GB of GDDR3 VRAM. Settings are one left of max for most sliders, except autogen and global texture resolution, which are on maximum, and weather sliders, which are on ASN-recommended settings, and antialiasing which is set to 8xSQ in NI. Framerate is limited via NI to 30, with no 1/2 sync due to intervening integrated graphic on laptop setup where Vsync settings in NI seemed to have no observable effect. FPS is 20-30 during cruise depending on cloud cover, 20-28 at low altitude around terminal areas with complex stock scenery like SFO in fair weather, and about 15 on stand in LHR with two layers of ASN overcast and limited visibility. FSX-SE seemed to give better FPS overall and work well without any tweak, especially with large amount of autogen. And Win 10 seemed to have no impact overall, except for crash on quit or aircraft switch for certain other non-PMDG addons, at least with my setup. Still, I wonder what performance I would have if I installed REX4 back in, or tried any scenery addons.

While FSX is largely CPU-constrained, a good GPU is still important for detailed models like PMDG ones. Be sure to get FSX-SE, framerates and VAS usage are slightly better there, as observed. Also be ready to lower settings if things get too slow. Also do not expect much performance with denser cloud covers. 15FPS might just be possible!

So far as I know, QW146 loads in FSX:SE, and all function of the aircraft itself seemed okay. Yet to do a test flight, though. Livery and payload manager only work for FSX boxed, so far...or at least only work on boxed on a boxed/SE dual install, which is my setup. Some manual copying might still work, but I'm yet to try.