Chris Trotter Posted July 27, 2017 Author Share Posted July 27, 2017 Running through that and this: Will report back once this is done. Link to comment Share on other sites More sharing options...
Nick Cooper Posted July 27, 2017 Share Posted July 27, 2017 Hello, For future reference, the active scenery.cfg file is to be found at C:\ProgramData\Microsoft\FSX. The ones in the FSX root folder and the appdata folder are back up copies, not used to record active scenery. Link to comment Share on other sites More sharing options...
Chris Trotter Posted July 27, 2017 Author Share Posted July 27, 2017 Thanks, Nick. Noted. FSX itself is now reinstalled, will be establishing some benchmarks and taking backups of key files, then moving on to testing the Orbx add-ons one at a time. The order I'll test: (install, run FSX, run Sitka Approach) - Orbx libraries - FTX Global - FTX Trees - FTX Vector - FTX NA - Each of the 3 Pacific Northwest packs - Friday Harbour airport pack Link to comment Share on other sites More sharing options...
Chris Trotter Posted July 28, 2017 Author Share Posted July 28, 2017 Ok, so after following both sets of instructions, things are working. The instructions didn't allow me to test one-by-one, but as to root cause, I'll have to assume something happened at some point to cause this. I've even copied back in the old Logbook.bin, no issues. The only pieces left to test are how it works with the normal set of monitors/instruments/controls/etc, but pretty sure the only difference I'll see is "amount of lag determined by hardware restrictions". As of right now, with every single detail setting maxed out at 1440x900, smooth as butter, and looking nice. Thanks for the patience everyone. Unfortunate we couldn't solve it without a reinstall, but hay, could be worse. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.