TASCHMANN

Oswald was arrested for murdering a Dallas police officer and the President of the United States. He is in custody for about 24 hours during which time he is questioned intermittently by many different law enforcement personnel. No one records a single word he says during that time. I have always wondered why.

Jorg always uses many many words to say absolutely nothing. One thing seems to be clear: ever since "The Announcement" development of and for MSFS has come to a screeching, grinding halt. Why can't they just, for once, drop the BS and be straight with the community.

T That "update" occurred on the day the Local Legend was to be released. Last week the "Development Roadmap" showed the delay for SU13 but still listed for September 21 as the day for the Local Legend. My question, and I ask this because I am genuinely curious, is Why have something called a Development Roadmap when it is always outdated and contains completely inacccurate information? Of what possible use could that be to anyone? It creates the appearance of keeping the community informed when, in fact, is does exactly the opposite.

Any word on Local legend 13 which, according to the Development Roadmap, was to be released today along with its video?

Why does the "Development Update" published today bear the date of July 6,2023? It is also current as of two and a half months ago. Can it be that someone at Asobo is not checking their work before it is released? Is this the extent of quality assurance we can continue to expect going forward?

Thanks. I will try these suggestions and report back.

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?

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?

This is a beautiful addon with one very large drawback. There have been quite a few requests for Blackbird to let us know how to bind some of the important controls. I hope they do so. It seems strange to have sophisticated systems without any means to control them. Use of the mouse in VR is extremely difficult and a real immersion killer. For example, if you are using your right hand for the stick it is almost impossible to work the following important controls using your left hand on the mouse: oil cooler intercooler supercharger fuel tank selector hydraulic hand pump tail hook engine primer engine starter If these controls were bindable, the Corsair would be among the best planes IMHO in MSFS. I really hope we hear from Blackbird on this question of binding soon. Edited 4 hours ago by TASCHMANN

This is a beautiful addon with one very large drawback. There have been quite a few requests for Blackbird to let us know how to bind some of the important controls. I hope they do so. It seems strange to have sophisticated systems without any means to control them. Use of the mouse in VR is extremely difficult and a real immersion killer. For example, if you are using your right hand for the stick it is almost impossible to work the following important controls using your left hand on the mouse: oil cooler intercooler supercharger fuel tank selector hydraulic hand pump tail hook engine primer engine starter If these controls were bindable, the Corsair would be among the best planes IMHO in MSFS. I really hope we hear from Blackbird on this question of binding soon.

It seems very clear that MSFS of whichever iteration is about exalting novelty over quality. We've had a lot more of the former and not nearly enough of the latter with this project since the beginning. I see no reason to expect anything different in the time ahead. As just a single (yet fundamental) example, this program still does not launch reliably and often requires a reboot of the sim, or Windows or both just to begin using it. Let the gamers have it. I quite sincerely hope they enjoy it. After all it was always designed for them. There is a serious flight simulator available to those of us who want one.

This is really a first rate, and sorely needed, mod. The only deep system modeling of a radial engine twin that I know of. My question: I was able to map the *position* of the primer knob (left right and center) using the parameter listed in the documentation. However I have not yet been able to find the parameter to map the actual *pulling * of the primer control. Does anyone have any advice regarding this? I am using Axis and Ohs.

Just to let you know. I made both of the changes that you suggested and, of course, the axis works perfectly now on the 3 way switch. Great example for other developers to follow of first rate support for a first rate product! Thanks

Thanks for the reply. In answer to your question, I guess I misunderstood section 3.6.5 of the documentation. Although I enjoy AAO tremendously as it adds a great deal of depth and enjoyment to MSFS, I have very little understanding of programming concepts and, at age 75, I suspect my mind is not as sharp as it once was . I do understand how I made a fundamental error in the "Axis min" and "Axis max". I will continue to work on the axis assignment in light of the things you have pointed out and report back. Once again thanks for writing a great program and for your help thus far.

Thanks for a tremendously useful [read essential] program for MSFS. I am having trouble understanding the directions in the manual for assigning an axis to a three position switch. The documentation for the plane lists the following commands: Starter selector: (Left-Center-right) CARVAR_SW_STARTER_LR (LVAR) - (0-1-2) In an effort to set the left position, I have made the following entries: Enter Variable: L:CARVAR_SW_Starter_LR, 0 [I manually added the comma, space and 0 as suggested in the documentation] Axis min: 0 Axis max: 1 Update value: “on change” “float” are checked Device: Thrustmaster throttle Move Joystick axis: Slider 0 Input Ranges: Left margin: 47% Center: 73% Right margin: 0% Deadzone: 9% The switch does not move in the sim when I move the slider axis. One or more of my entries is obviously wrong. I just don’t know how to fix it. Any help or suggestions on how to set the left, center and right positions for the switch using this axis would be very welcome. Thanks