mrueedi

The app is now no longer considered as beta from today on. You can get version 1.0.11 as freeware from flightsim.to or from the MS Store. Here is the user final manual: https://flightzoomer.com/downloads/PushbackZoomer 1.0 User Manual.pdf In the last chapter of the user manual I have provided the full SRGS grammar of the speech recognition. If you dare to read a bit XML, you can see the large number of variations how commands can be spoken.

Thanks for posting! As I am the developer of the app, I just wanted to add to this thread the demo video, that I made:

That's true of course. I tried once doing the KaiTak IGS 13 Turn with the 747 in VR. Did not taste well (but still was a fantastic teaser about the potential of VR)...

For me it was mindblowing despite having seemingly the worst hardware specs ever mentioned by somebody. My hardware is a notebook with i7-8750H and 1060GTX, the headset a 1st gen WMR Acer AH101. The thing is, VR impossibly can be catched in a screen recording or screen shots. The realism of "feeling the position in the air" or "checking where the airport is" by very short glances is unbeatable. Anyway I made this video, that maybe can give you a little bit of an impression, how VR is working:

Oh, and I forgot to add this: This also applies to me, like you I am so engaged in fun engineering projects (multiple ones, and as the short list of activities is full I had to put some extremely appealing ideas on my long list) at the moment, that I can't stress enough: don't let you put under pressure! This stuff needs to be enjoyable. Progress has to be one step at a time in a pace comfortable for everybody involved. I certainly appreciate your efforts for the A320 mod. Anyway we might have a chance to discuss the controller topics bilaterally. What would be the best channel? The discord #fbw channel?

The 210 are from the link above: Fly-By-Wire - SKYbrary Aviation Safety About the other rates, have you seen this document? FlyByWire (flightzoomer.com) It mentions a G range from -1.0G to 2.5G. It also has a diagram "stickdeflection&G Load&Pitch vs time". Unfortunately the time axis is not labeled so pitch/s can't be seen! I agree that it makes sense to have a sets of factors for these configs.

Many thanks Andreas, great post! Your fbw approach sounds very comprehensive indeed. May I ask some things more? - Out of curiosity, what is the information source for the Airbus FBW system? E.g. where have you found this 12.4 factor? - Is the speed dependent blend between pitch rate and load demand implemented? Above 210kts it should be G only, right? - Looking in code, the feedback to the sim seems to be just setting the three elevator/rudder/aileron axes variables. How is it handled, that the control input by the user does not interfere with your calculated positions? - How do you tune the controller? I am interested because deriving the PID factors (yes, such a fbw system has all the ingrediences of an autopilot!) automatically was exactly what I did in 2002. I used a method similar to the one described here. By measuring a bode plot of the control line ("Reglerstrecke", which meant simply letting oscilate the pitch of the aircraft from maybe 0.01HZ up to the point where the phase of the FPA response lagged more than 135°) I was able to get the PID factors easily and consistently. Regards, Martin

No, not the pitch protection. The normal flying with the stick where "Stick neutral = 1 G flight = unaccelerated flight vector". It would be nice, if the requirements met (= capability) by the fbw implementation would be described a bit somewhere. I have looked in code, it looks extremely comprehensive, but still the exact capability is not evident. I ask because I have programmed a gauge many years ago (for FS2002) which realized this G-Load pitch controller (with much simpler code). The paradigm is totally different than normal aircraft are flown, because no manual trimming is ever required anymore. Simply bringing the stick to the center position means the aircraft keeps the flight vector no matter what. For this reason the Airbus stick is simply spring loaded and force feedback is not available (it would even be counterproductive). Some things more, that follow from this approach: - Assume the stick is kept centered and the aircraft climbs with a particular climb rate, if now the thrust is increased, as speed increases, vertical speed is automatically increased as well in order to maintain 1G. Basically FPA needs to be kept constant. - Assume level flight, if the stick is deflected to the side, a turn begins while the system maintains level flight no matter what (in order to maintain 1G on the pitch axis) More cases and details can be looked up in the linked PDF....

What are the exact features of this FBW mod? Is it this "stick deflection = G loading" capability of the real Airbus? Capabilities as described in the following document: http://flightzoomer.com/downloads/Flybywire-English.pdf ? Sorry for asking this basic question, but I was not able to find out before. If that would be the case, you could pull the stick fully for any time and get consistently the fastest possible climb out. After moving the stick to the side, you would get a roll rate proportional to the stick deflection. Bringing the stick to neutral and not moving it ever again would mean, that the vertical G loading (in essence the current Flight Path Angle) would be kept constant all while the turn at the reached bank angle would continue eternally.

I can imagine, that they could implement a procedure like this one: Use 3D Building models from the normal map as shown e.g. for Dubai in one of the posts above. Processing normal vertically aerial imagery by AI, they could try to determine things like the color or the structure of walls. The result of this AI operation would be a classification for each building, which allows to pick the best fit from maybe 400 generic building walls, which then simply will be applied as textures. That way, the building might not be 100% accurate, but if you don't know a building well, you won't notice it....