October 30, 201213 yr Hi How could it possibly be that there is no posts, no FAQ and no nothing about frozen and unusable start switches on the LDS 767. What am I doing wrong/missing? Is it supposed to be like this in FSX? And why is there a forced engine auto start on the LDS? Further explanation: I used the LDS for years in FS9 and never had an issue with both engines trying to start themselfs up all the time. When I went over to FSX I decided to not go for the LDS 767, until two days ago and now I cannot fix this issue. The engine start switches are frozen solid in both VC and 2d, and are not usable. I simply cannot put them in OFF GND or CONT or anything.. They are simply stuck in AUTO And I did download the engine start fix, so either there is a setting somwhere that im missing or this is a bug. Ive searched up and down for posts concerning this issue in here and at LDS forums, but no one seems to have had this problem as far as I can see.. Anyone have a clue to whats causing the start switches to be unusable? Its on a WIn7 64 system So thank you for any help here! Yngve GiljebrekkeENZV NSB
November 9, 201213 yr I have no issues with the panel. Maybe you should post this in the official Level D forum and hope Daryl comes to your assistance. FSX is a fickle beast and installing it correctly from the get-go is of paramount importance. You can check out NickN's lengthy post on Win/FSX installations in the Flight 1 forum. MSI Pro Z690-A DDR4 | i5 13600KF | G.Skill Ripjaws V 32GB 3600MHz | RTX 3080 (12GB) | Samsung 980 M.2 NVMe 500GB | Samsung 980 M.2 NVMe 1TB | Samsung 850EVO 500GB | Crucial P3+ 2TB NVMe | 2TB Seagate HDD | Deepcool AK500 CPU Cooler | Thrustmaster T16000M HOTAS | CH Yoke | Various Winctrl hardware | 21:9 1440p UW monitor | Win 11 23H2 build | MSFS2020 | Tony K.
Create an account or sign in to comment