Duke (Piston + Turbine) LVAR for MobiFlight
-
Thanks, I get the gist of what you're saying. Unfortunately, I'm not sure if the pop-out window is an option in VR mode. I currently run the Fenix A320 and have a tablet MCDU via local browser, which works a treat. Reason I ask is that I built a 2 seat sim so I can always have a buddy over to fly, one seat is VR, the other seat is a large screen monitor - and this way either pilot can operate the MCDU (or other EFB features) easily via the tablet, even if one pilot is using VR.
I'm wondering also if using a pop-out window might also be a little FPS hungry compared to a web interface (where the device is completely independant) ... but I'm unsure of that one.
-
I have a couple of further questions:
-
Is it easily possible to add a personal AIRCRAFT REGISTRATION (eg. VH-ABC) to all / any of the liveries? I had a read of this in the manual, and I can't really understand how to just to a simple REGO change.
-
In terms of overall operation of both the Piston and Turbine models, although I 100% understand the very realistic simulation of all systems, care and failures etc., is there an 'EASY' mode (no failures, no accumulation, easy starting etc), and/or a mode where engine care shortfalls etc., do not accumulate?
Thanks, John.
-
-
also ... On Page 57 of the Turbine Manual (2024) it states the blue propeller levers have been replaced with translucent blue handles with a light inside (to assist in feathering guidance). However, it actually states 'Piston Duke', is it meant to say 'Turbine Duke'?
-
The manual reads correctly. The Turbine Duke is a modification of the reciprocating engine factory model, hence it is the Piston Duke's handles being replaced.
-
I'm not exactly sure what you are trying to achieve with the registrations, so I was hoping someone else would jump in and provide an answer. The registration can be set from the simulator's aircraft selection menu. You can also permanently change the registration by editing the Turbine Duke's Aircraft.cfg file. Is that what you're looking for?
-
Unfortunately, there is not an easy mode, but you can turn off all the MTBF failures from the tablet's failure menu. As for the engines, they should hopefully not cause you too much trouble, so long as you aren't continuously over-torquing them.
-
-
Thanks, so just to clarify ... the blue propellor levers have the lit translucent handles on BOTH the PISTON and TURBINE models?
-
So, I note there are several liveries, and most have a USA aircraft registration on the aircraft skin. Am I able to modify any of these main liveries to show an Australian aircraft registration instead eg. VH-ABC ? When I changed the registration in the aircraft selection menu, the paintwork on the skin of most of those liveries still displays the original USA registration.
-
Thanks - if the engines were to be over-torqued too much over time ... can they be reset to new? How do I perform a routine 'engine overhaul', or 100 hourly etc., so as to return certain characteristics to new/default etc.? Is there an actual 'maintenance action' selection anywhere, or a 'factory default' selector to return all airframe and engine degradations to 'as new'?
Thanks and kind regards, John.
-
-
When a Piston Duke is converted into a Turbine Duke, it's original propeller handles are replaced with the lighted ones; hence, only the Turbine Duke has the lighted handles.
All of the default liveries were created with my dynamic registration system, and should respond accordingly when you change the tail number in the menu. Like I said, you can also edit the aircraft.cfg to make a permanent change to a livery's registration. If you're using 3rd party liveries, I know that some of them support my dynamic registration system, and some do not. If you believe there is something not behaving correctly with my default liveries, please let me know.
You can reset the condition of the engines using the "Repair Engine" button in the engine page of the tablet interface. There are also some additional buttons, like "Repair Starter" that can be used if you break anything else engine related. All other failure features can be disabled with the slider on the failures page of the tablet interface.
-
Hi, just wondering if there are LVARs for the following:
External power source / cart
Tablet interface access (rather than having to visually navigate to the left side panel and most select)
Pitot Heat ... the same variable appears in the manuals for both L and R Pitot Heat ...K:2:PITOT_HEAT_SET (are there meant to be two different variables for the Left and Right Pitot Heat?)
I will probably find a few more that I was unable to find, and will just post a query as I come across them if that's OK?
Thanks, John.
-
The external power is triggered with the native event, "K:TOGGLE_EXTERNAL_POWER". It will be automatically connected to the power system as soon as it is plugged in.
You can toggle the tablet interface on and off with "L:bksq_TabletVisible"
The pitot heat events take two inputs, as signified by the "K:2: prefix. The first input is the state (0=off, 1=on), and the second input is the pitot heat index (0=left, 1=right)
I hope that helps answer your questions! Always feel free to ask more.
-
Do you have LVARs for the Fuel Selectors and Crossfeed Selector (for both the Turbine and Piston Duke)? Also, I must be blind ... I'm looking everywhere in the actual flight decks and I cannot find either - can you please help me out there as to where I should be able to see them? Thanks, John.
-
They are on the floor, over the wing spar, between the two front seats. They are not controlled with L:Vars, but instead the native simulator commands. The same commands for the Analog Baron should work with both Dukes. They have been discussed very recently here. Let me know if you have any more questions!
-
Thanks, I've only just found the spare time to try coding these - but realise I don't actually know how to interpret what you've said about the Fuel Selector coding. I need to put a code in MobiFlight for my Fuel Selector switch and I've read the other post you've cross-referenced, but I don't follow the syntax of what I'd need to enter. Can you please assist further? Thanks.
-
Actually, I worked it out through some extensive trial and error, so for anyone else who might be wondering, here's what I have for working commands in MobiFlight for the Fuel Selectors:
Both to CROSSFEED
20 (>K:FUEL_SELECTOR_SET)
19 (>K:FUEL_SELECTOR_2_SET)Both to INDEPENDENT L and R fuel sources
19 (>K:FUEL_SELECTOR_SET)
20 (>K:FUEL_SELECTOR_2_SET)Both to OFF
0 (>K:FUEL_SELECTOR_SET)
0 (>K:FUEL_SELECTOR_2_SET)
