Leaderboard

If you have a request for any specific datarefs or commands, please do so in this forum thread. We have nearly 600 manipulators in the 737 and exposing every position possible as commands could result in over 1000 commands possibly (I have yet to audit all the positions). If you count the "feedback" datarefs as well, i.e. "annunciator lights", the list would get very long indeed. So while we do not mind exposing all these inputs and outputs eventually, we certainly want to focus on the most requested ones first if we don't get to them all by the next update. So if you have a request for a nominal (button / knob / switch), then don't bother posting as we are actively coding those up now. But for anything else not so obvious, please let us know. Note that we're starting with the overhead, pedestal and main panel controls first. Note that multi-position knobs and switches will have a command for each position, e.g. the left engine start switch (see below): -tkyler

I am going to start coding up commands for the overhead controls, we should be able to get these into the next patch. If not, then shortly thereafter. -tkyler

Also solved this Problem with this liverie - it is a nice working and very elegant solution! The liverie is made by Razor94, found here: https://forums.x-plane.org/index.php?/files/file/49405-hotstart-tbm-900-d-fsbg/ As described you can use the two overhead png's for your other liveries.

Hi all. This COVID thing has affected my employment and sent me in a different direction.....full time back on X-Plane! (note...I work on more than just the 737 though) We are working on the update every day as of late; however, we are still going to wait for some 11.50 stability before we release. In the meantime, we're cleaning up things we feel we can without putting the plane in the hangar with the major renovations like the FMS/holds/VNAV. We are back in the FMS code somewhat though and have made the coroutes loading more robust. We will be including that folder in our update so as to not cause confusion, but we also now support about 6 flight plan formats, X-Plane 10/11 (*.fms), PMDG and Quality Wings (*.rte), X-FMC (*.fpl), FSX (*.pln) and AirbusX (*.flp). Like the real FMS, if a waypoint can't be located because of database incompatibilities with the flight plan, then the FMS loads what it can until encountering such a point and then provides the message, "PARTIAL ROUTE LOADED". I was testing this code with random format downloads from Flight plan database...and nearly all of those flight plans contain out of date data, so getting the FMS to load a full route was a challenge. I had to go in and hand edit the flight plan files to 'up-to-date' data. Once done though, they can be saved through the FMS as before. These coroute. loaders do not load SIDs/STARS, only the enroute portions, which is typical. As time goes on, I'll continue to work on improving the route editing, which will have applicability for the holds and eventual "in air" vnav entries. More to follow as we get closer to our release point. -tkyler

FYI, we will create a more comprehensive set of custom commands for controls that can be mapped to "joystick settings". I will assess whether or not we can squeeze a bunch of them into the next patch. Creating them is relatively quick. If not the next patch, then perhaps shortly thereafter in a dedicated "commands additions" patch. -tkyler

Flo, Here is a response from one of our Saab pilots... (sorry for the delay) So descent in a Saab. Speed is planned at Vmo - 10 kts (240 usually). The v/s to use is 1500fpm. Calculate TOD using 3nm for every 1000 feet you need to lose. For example if I need to be at 2000ft AGL above the airfield on arrival, and I am at 20 000ft AGL, then I need to lose 18 000ft. So I will need to start my TOD at 54NM (3 x 18) from the airport. As far as wind goes, add 1nm for every 10kts of tailwind and subtract 1nm for every 10kts of headwind. The trick with this is to keep doing the calculations to see if you are high or low. So in the above example I know that passing 12 000ft I need to be 30nm from the field. So I can adjust my V/S to make sure I pass through that gate correctly. And of course if ATC gives a speed limit, then I may need to back off the V/S a bit so I can still meet my height and speed goals. Eg say in the above example I want to be at the aerodrome at180kts at 2000ft joining crosswind. So I obviously cannot keep at 1500v/s and 240kts till 3nm from the field. So I will need to start slowing down in enough time that I can meet those goals. The SAAB will happily descend at 1500ft at 240kts with minimal power set, so there has to be some planning in advance to start reducing the V/S and the speed to meet the speed requirements at the aerodrome.