by Steve Waite » Thu Oct 01, 2015 10:43 am
...a few notes for FSX-SE users:
After an update to the steam edition, run the new version from the steam menu and you will notice it comes up with the EULA and installs the update. We have to do that before we run the IF10 setup program so that the new version data is read, and not the old data. With that data, the IF10 setup program updates its installation for the version of FSX-SE installed.
Since the Steam edition of FSX normally starts with the UAC to elevate privileges, with IF10 we can do something to help that:
1. We can set the "Run as Admin" checkbox on the IF10 Desktop Icon, once IF10 is running as admin, when we then use IF10 to start FSX-SE, we find the UAC is not presented since we are already in admin mode.
2. We can instead, run the IF10 setup program, and in the popup menu (right-click), at the bottom of the Other Settings menu, we can set the FSX-SE executable to not require Admin mode, and then we don't have to set IF10 to admin either.
If we run FSX-SE as admin, we must also run IF10 as admin. Windows operating system only allows some functions to run when the two apps work with the same privileges, e.g. IF10's setting FSX Captionless Borderless Window would fail with different privileges.
FSX-SE Installation location problems
When we install FSX-SE in the default location, the path is very long and can cause a problem in the FSX Scenery selection window, when we add some sceney we might get an error, due to a relative path that is overlong. We can put the full path in the Scenery.cfg, or we can install FSX-SE in a short path of our own. If we make our own path, remember to add Write and Modify permissions for the Users group on our new folder. This problem should be resolved in future updates from DTG.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)