Jump to content

touchdown84

Members
  • Content Count

    73
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

11 Neutral

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Gender
    Male
  • Location
    Germany

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Recent Profile Visitors

825 profile views
  1. Happens rarely to me as well that it loads in that state. After a simple restart of the flight it loads correctly.
  2. Biggest issue for me as well, the databases included in the trainers get rarely updated and often over a year old. And Garmin charges hefty prices for their updates, as they are targeting real pilots. Should they ever release an affordable "sim-use-only" plan for the complete worldwide dataset I'd be tempted, but not like this.
  3. I'm using the rotary on the Honeycomb Bravo, which is not a good rotary encoder to begin with, that's just registering as normal joystick buttons. So I'm not surprised that it works better with other devices. At the moment, with the "fast"-assignments defined first, I got it working as good as the hardware allowsI think. Also I got much better result using RPN-scripts controlling the increments, like: (A:AUTOPILOT·ALTITUDE·LOCK·VAR,·Feet)·(L:0-KNOBS-ALT_INC)·+·(>K:AP_ALT_VAR_SET_ENGLISH) Much less additional "slow" ticks on a "fast" turn than using ALT_VAR_INC. Anyway, I think I got it working in a way I can live with now, thanks for the help.
  4. I just tested tried that. That works (kinda, on a fast turn it mostly triggers the normal as well, so using 900 for a fast turn gives the intended result) when you create the Fast-Turn before the normal turn, such that the Fast-Turn is defined before the normal turn in the Config-XML. But when you create the normal turn first (such that it comes first in the Config-XML), than you still have the bug I described that both actions are triggered no matter how slow/fast you turn. So the logic is depending on the internal order of the assignments.
  5. The usecase you are describing is exactly what I want, I just used different events in the example to illustrate the problem better. What I want is the e.g. the Heading to increase by 1 on a normal turn and faster, lets say by 10, on a fast turn. Could you provide an example on how it is intended to be configured? Because when I only have 1 single assignment with Fast Turn, I get nothing for normal turns. And when I make 2 assignments on the same event (e.g. I tried calling the same RPN script just with different values from both assignments) I get the behavior I described in my first post.
  6. Sorry to bother you again but I seem to have a bug when having a Fast Turn and a normal assignment to the same rotary, that also depends on the order of the entries in the ConfigDatabase_MSFS.xml. This is with AaO 2.07 b12 and MSFS. I made a very simple example to reproduce it with a Fast Turn and a normal assignment where on Fast Turn it should increase the heading bug and on a normal turn it should increase the altitude bug. When in the config xml the normal entry is before the fast entry (like in the xml example below), then on each input both HDG and ALT are increased, even when it's too slow for a Fast Turn. When in the config xml the fast entry is before the normal entry (the reverse of the example xml), then on a slow turn it only increases ALT as expected), and on a Fast Turn it increases HDG (as expected) but also ALT as well (what I would not expect). Maybe it's possible to have a single assignment for normal/fast like with the Long/Short-Click option? Thanks, Jan The example xml-snippet: <buttons> <GlobalHotkey> <downEvent> <Group>Autopilot</Group> <Description>Increments reference altitude</Description> <SimulatorEventName>AP_ALT_VAR_INC</SimulatorEventName> <MinValue>0</MinValue> <MaxValue>0</MaxValue> <ValueToSet>0</ValueToSet> <IsAaoVirtualEvent>false</IsAaoVirtualEvent> <type>SINGLE</type> </downEvent> <repeat>16384</repeat> <repeatFrequency>1</repeatFrequency> <joystickGuid>3e1d4070-447c-11eb-8001-444553540000</joystickGuid> <joystickName>Bravo Throttle Quadrant</joystickName> <joystickButton>12</joystickButton> <joystickPovControl>-1</joystickPovControl> <joystickPovDirection>-1</joystickPovDirection> <midiDeviceId>-1</midiDeviceId> <midiChannel>-1</midiChannel> <midiEvent>-1</midiEvent> <endless>false</endless> <midiEncoder>NONE</midiEncoder> <isSimKey>false</isSimKey> <comboSuppressesEvent>false</comboSuppressesEvent> <comboIsToggle>false</comboIsToggle> <longClick>false</longClick> <longClickTimeoutMs>0</longClickTimeoutMs> <fastTurn>false</fastTurn> <timeoutMs>0</timeoutMs> <assignedKeys /> <vkModifiers /> <vkKeys /> <Action>AP_ALT_VAR_INC</Action> </GlobalHotkey> <GlobalHotkey> <downEvent> <Group>Autopilot</Group> <Description>Increments heading hold reference bug</Description> <SimulatorEventName>HEADING_BUG_INC</SimulatorEventName> <MinValue>0</MinValue> <MaxValue>0</MaxValue> <ValueToSet>0</ValueToSet> <IsAaoVirtualEvent>false</IsAaoVirtualEvent> <type>SINGLE</type> </downEvent> <repeat>16384</repeat> <repeatFrequency>1</repeatFrequency> <joystickGuid>3e1d4070-447c-11eb-8001-444553540000</joystickGuid> <joystickName>Bravo Throttle Quadrant</joystickName> <joystickButton>12</joystickButton> <joystickPovControl>-1</joystickPovControl> <joystickPovDirection>-1</joystickPovDirection> <midiDeviceId>-1</midiDeviceId> <midiChannel>-1</midiChannel> <midiEvent>-1</midiEvent> <endless>false</endless> <midiEncoder>NONE</midiEncoder> <isSimKey>false</isSimKey> <comboSuppressesEvent>false</comboSuppressesEvent> <comboIsToggle>false</comboIsToggle> <longClick>false</longClick> <longClickTimeoutMs>0</longClickTimeoutMs> <fastTurn>true</fastTurn> <timeoutMs>200</timeoutMs> <assignedKeys /> <vkModifiers /> <vkKeys /> <Action>HEADING_BUG_INC</Action> </GlobalHotkey> </buttons>
  7. With MSFS and I was using an automated script to set two lvars with the current heading in degrees so I could display those in the same gauge: (A:PLANE·HEADING·DEGREES·TRUE,·Radians)·rddg·(>L:CUSTOM_HEADING_TRUE,·number)·(A:PLANE·HEADING·DEGREES·MAGNETIC,·Radians)·rddg·(>L:CUSTOM_HEADING_MAGNETIC,·number) But for some reason the issue seems to have resolved itself, I cleaned up my streamdeck profile and removed all buttons/gauges and recreated them again, and now it works and I cannot reproduce it. Had it all day yesterday, so not sure by what it was caused. The second point is still there though, a very simple to reproduce: Create a TextGauge where both variables are set to A:BRAKE PARKING POSITION, bool . When the parking brake is set shows two "1"s, but when not it shows only one "0" and nothing else.
  8. I've tried with plugin version 3.0 and 3.15, same result on both: When I use a TextGauge to display two different(!) LVars it does not work. Both LVars show fine on their own or when I use the same LVar for "Variable 1" and "Variable 2", but when I use two different LVars it does not (display does not update, for neither variable). Also another small glitch I noticed, when "Variable 2" is "0" it shows up as an empty string instead of "0" (with both A: and L: vars). Thanks
  9. I'd like to ask the same question. Using the trim wheel on the Honeycomb Bravo there is no button to hold down for repeat. I can set the trim wheel value (in the -16k/+16 range) via the K:ELEVATOR_TRIM_SET event, but I have not been able to get the current value of the trim wheel with RPN to increase it by, lets say, 100 per tick. What I'm doing at the moment is with RPN 1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN)·1·(>K:ELEV_TRIM_DN) which kinda works but I don't really like it. Anyone knows if there is sim var to read the position of the trim wheel in the same range used to set the event?
  10. This lever can be stuck when state saving was active. To unstuck it you can deactivate state saving and then load a state like "Ready For Takeoff".
  11. Do you have another device attached that is mapped to rudder? I had those rudder problems when I had a gamepad attached that had the rudder axes mapped on the triggers.
  12. I noticed that when using Navigraph that the names for airports where Navigraph is updating the navdata the name of the airport is missing. In the change notes for LNM 2.6.1 beta I see "Updating administrative names like city in airports now. This also corrects missing city and airport names for the Navigraph navdata update.", so maybe this was already addressed but no longer working in LNM 2.6.6? Maybe it's possible that when the airport name is missing it will fallback to either the next lower file in the hierarchy of that airport or to the data from the Navigraph database used in LNM? Thank you
  13. Are you using an (external) FPS limiter? Because then the FPS will be halved when you pop out a window.
  14. Install 2013 rev. 3. That bug was fixed in that revision.
×
×
  • Create New...