Some 0.1.9 issues
-
- When overweight, the gross weight in the EFB is solid red without any visible text.
- When clicking into text fields on the "Plane" page, the text goes away and needs to be entered blindly with the onscreen keyboard, it only shows when pressing enter.
- The MWS test has a recurring "red" caution which may be related to the TMS warning annunciator failing to light up.
Additionally, when importing loads from Simbrief, the cargo appears more or less random and unrelated to Simbrief numbers, and there are always 80 passengers. (This is a holdover from 0.1.8.)
On a positive note, I appreciate being able to control the heading bug with hardware inputs now :-D
-
@laurreth Worth reporting all of this to our support team who can log the issues and investigate further...
-
@voice-of-reason Did that, when I tried getting some B-roll screenshots, entering values in the EFB broke some more too :-)
-
@laurreth I have same issue, i think there is something strange in passenger's average weight, and something else, cuz always when importing simbrief data plane transfer it to best of optional MTOW . or i don't understand , i hope they fix it :)
-
@laurreth said in Some 0.1.9 issues:
On a positive note, I appreciate being able to control the heading bug with hardware inputs now :-D
I have had the heading bug working all the time on a hardware keybind (simply using the ingame input assigner) before this patch.
I have another issue with the new patch, where the onscreen keyboard disappears in the tablet, and I'm unable to change any values with key inputs as well. Only way to change is clicking the + and -, which is annoying for obvious reasons and means I'm unable to get exactly the load I want.
-
@avionic I'm running one of two Honeycomb Bravo setups, and I'm not sure which one is used for the 4-engine binds. By default, one knob will trigger the selection of an input, e.g., ALT, V/S, HDG, etc., and the encoder will then simply bind to MSFS "plus" and "minus" functions. My other setup uses key combinations so the selector sort of acts as a "shift key" for the encoder, and HDG increase and decrease will be bound to "HDG input + encoder up/down". The 146 didn't use to respond to whatever I was using.
I reported the vanishing keyboard in a ticket as well, that was the B-roll issue :-D
