July 10, 201312 yr I've been using Alacrity for some time, in a previous life of Windows and FSX. I'm nearly finished reinstalling enough of my addons for now. I decided to configure Alacrity. I started by copying Paul's settings from the How-To, and then added all the obvious ones of my own. I set Stop then Restart to 10 programs, and ditto to 35 Services. I'd post a couple of pictures if I knew how. The result this time is that Alacrity takes 2mins 15secs to process, and FSX then takes 5 mins 30secs. This is far longer than I was used to before. While I've been installing addons and checking FSX, I've started FSX direct. I've got Corsair Dataplex, and without Alacrity FSX takes 55 secs to load a flight, ready to fly. I'd like to get the benefits of Alacrity, without this long wait! Jim Asus Rog Maximus VIII Hero, i9-10900k 4.8GHZ, Corsair H100 cooler, 32GB Corsair Vengeance 2666, RTX3090 20GB, Win10 HP 64-bit, 3 Monitors "19-22-19", Reverb G2 Headset.
July 13, 201312 yr The fact that it takes only 55 seconds to load a flight when Alacrity is NOT enabled indicates to me that something is wrong with your Alacrity program. Without Alacrity, it is starting up in 55 seconds even after making Paul's suggested config changes and you making your 10 changes to the config. Enabling DX10 Preview will not adversely affect the operation of Alacrity. Best regards, Jim Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
July 13, 201312 yr Check the "Log" tab in the Alacrity Profile which you're using, Jim, then check the shutdown times of each process as it is shut down. There are a number of programs that won't like being shutdown, so they take a while of "Attempting to close xxx" - and the time between this "process shutdown start point" and the start of the next "process shutdown start point" will be recorded in the log. If it's a few seconds - this would be normal. If it's twenty seconds or more - then just remove it from the list - make it a "Nothing". All the Best, i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
Create an account or sign in to comment