Michael Kuhne Posted October 2, 2014 at 06:20 PM Posted October 2, 2014 at 06:20 PM I just experienced that I can't make the aircraft to hold when connecting via the FSD server. If I connect to the sweatbox with the same scenario file they can hold. With the FSD server I don't even see the list of possible holdings, as opposed to when on the sweatbox. Similarly, all departures drop to an altitude of 600ft when using the FSD server, instead of maintaining 1440ft as defined in the scenario file. Therefore they are not able to depart and just "hold position", regardeless of my inputs. On the sweatbox the departures work perfectly. Any help? Link to comment Share on other sites More sharing options...
Eric Bocaneanu 906549 Posted October 3, 2014 at 06:22 PM Posted October 3, 2014 at 06:22 PM Michael, What are you using to create the Scenario File? Eric Bocaneanu ROvACC Director Link to comment Share on other sites More sharing options...
Michael Kuhne Posted October 4, 2014 at 08:22 AM Author Posted October 4, 2014 at 08:22 AM I use an Excel spreadsheet, where I put the different items together as defined in the ES-wiki or a scenario file out of the ES scenario editor. The holding or airport altitudes is defined the same way a in the ES scenario editor file. Link to comment Share on other sites More sharing options...
Michael Kuhne Posted October 4, 2014 at 09:00 AM Author Posted October 4, 2014 at 09:00 AM When adding a line on top of the scenario file with "PSEUDOPILOT:ALL" it seems to work! Whyever this helps I can't imagine, but as the problem is solved I don't complain any further. Link to comment Share on other sites More sharing options...
Recommended Posts