June 20, 20232 yr I have always found AAO to be essential to my enjoyment of MSFS. I can't imagine flying without it. My question: I have an addon [Blackbird FG-1d Corsair] in which several essential commands, e.g. Tail Hook, are not mappable to keyboard or any button or axis. According to the developer, they are only operable by using the mouse. Is it possible using AAO to convert mouse movements and clicks to events that are mappable to a joystick?
June 20, 20232 yr Commercial Member 15 minutes ago, TASCHMANN said: Is it possible using AAO to convert mouse movements and clicks to events that are mappable to a joystick? Yes, but mouse coordinates are absolute locations. This would only work together with fixed camera views where the virtual mouse event lands exactly where it belongs. You cannot use this while you are looking elsewhere (and they you can just as well use the mouse directly IMHO) 15 minutes ago, TASCHMANN said: only operable by using the mouse. I would need to see the actual code to believe that... There are rare occasions where that is indeed the case though. Is that the ex-MilViz model? Edited June 20, 20232 yr by Lorby_SI LORBY-SI
June 20, 20232 yr Author 1 hour ago, Lorby_SI said: would need to see the actual code to believe that... There are rare occasions where that is indeed the case though. Is that the ex-MilViz model? Yes it is the former Milviz model. I couldn't believe it myself until it was verified by the developer on the MSFS site. https://forums.flightsimulator.com/t/release-milviz-corsair-for-msfs/374413/1790 See question by SlideRule4848 and responses. Perhaps I am misunderstanding something? Edited June 20, 20232 yr by TASCHMANN
June 20, 20232 yr Commercial Member 35 minutes ago, TASCHMANN said: Perhaps I am misunderstanding something? I don't think that he means to say that you can only operate it with the mouse. The other guys are finding ways to trigger things too. So I am guessing that the developer uses LVars, BVars or HVars (or entire scripts). This is something that must be figured out in MSFS developer mode. Open "Tools->Behaviors" in MSFS devel mode, then hover the mouse over the button/lever in the cockpit, then press Ctrl&G. You should then see the code that is bound to it and normally one can find clues in there (= the names of the LVars/BVars etc, that they use or the script that is running when you operate the control). This can then be replicated in AAO. LORBY-SI
June 20, 20232 yr Commercial Member Looks like they are using LVars, one in particular: (>L:EVENTS_ID,·Enum) Example: RPN Scripts for the tail hook Down 0x1111E·(>L:EVENTS_ID,·Enum) Up 0x1111F·(>L:EVENTS_ID,·Enum) The tail hook seems to have three positions, UP, PARK and DOWN. So one needs two clicks to fully extend it. Tail Hook Status can be read from (L:FG1D189, Enum) and that yields values of 0-1-2 according to the hook levers position. Instead of "Enum" you can also use "Number" (may be the better choice, Number is the kind of the default for an LVar.) Make sure to replicate the code exactly as shown above - one(!) space character between the number and the first parentheses, and another one(!) space character between the comma and the unit. Edited June 20, 20232 yr by Lorby_SI LORBY-SI
Archived
This topic is now archived and is closed to further replies.