Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Aamir

Commercial Member

Everything posted by Aamir

  1. So was this a poll of real pilots only, or was this a poll that was posted in the chat of a livestreamer for anyone to participate in? I don't understand your feedback. You keep pulling out random numbers of people agreeing with things and disagreeing with things, but I find that kinda disingenuous because you seem to be using these as figures of speech? We are always open to opinion and welcome constructive discussion and criticism. This really isn't it. This is just going "I don't like it!" and then offering no explanation beyond that. And of course, saying "and other people don't like it either!", but we don't really know who these people are, what their experience is, and what relevance this has to the actual problem. From our side, we have plenty of people that agree with us. So we then come to a difficult question. Which is more valid and why? Again - I'm happy to discuss what people feel the problem is, I'm not really bothered with how many people agree or disagree with you or me if you can bring some decent constructive feedback in the first place. Just as an additional to this, I'm very curious about these sorts of things. What makes this streamer/pilots opinion more valid to you than others? As we say, there are some that love it, some that don't like it. This is normal with change. Are you identifying with this opinion because of your own struggles with landing? And then, to draw another interesting tangent - If you do struggle with landing, how do you feel your struggles with landing relate to what is more or less realistic, and why? And finally, do you feel like if we make it easier to land, conversely it would be more realistic? Or do you feel the opposite - like if it's more realistic, it would be easier for you to land (I ask this because what is easier for you may not necessarily be right for someone else, as we have determined so far - some really like it, and some don't!). I don't ask these questions with any ill intent. I would like to fully understand your position and context because I see it here and there from different people that bring me YouTube or Twitch clips to support their own opinion, and it's been something I've been quite curious about in general. I always wonder about the difficult to land > realistic relationship too - and I'd like to try and cycle some of this type of feedback into the development process to see how it affects some of our outcomes.
  2. This is a very interesting observation as drag was untouched in all 320 FMs from V2 to V3.
  3. This is true to the real aircraft. This is also correct depending on your inputs. No bug reports received around this functionality so I would say this is working as intended. This will happen if you ride the brakes. If you're taxiing an IAE, there is a well known procedure in place. Let it get up to 30-35knots, apply a single brake application, reduce to 10knts. Let it accelerate again. The fact there is a procedure for this should tell you everything there is to know about the IAE's idle taxi characteristics and how common it is to have hot brakes thanks to it. :) Also small sidenote - this patch did not change anything at all with the taxi. It is the same as V3. I'm not sure what the differences you're feeling are, but I'm not so sure they came from us at least. Checked in here and it is working as intended. Do you have any tertiary addons besides Fenix? Camera addons, FSHud, FSR, etc etc, that sort of thing?
  4. There is a whole 45 minute section on VNAV in the video we released on the Fenix YouTube channel. The A320 is not an A350. They do not do the same things in a managed descent. The model and equipment fitout on the A320 we have modelled could not be further from the behaviour on the real A350. Levelling off at a deceleration point is a major feature of the A320's VNAV in the guise we have built it. You may be unfamiliar with it as afaik no one else simulating an A320 has gone this deep on their respective suites. I would highly recommend familiarising yourself with the aircraft before suggesting it needs to be adjusted :D
  5. I will copy and paste my response to the content creator or real pilot in question, I suppose. There's a section in the video we made where we encourage users to spend a moment with things like this to allow it to digest and everyone to do a bit of homework and research (us included!) before reiterating such as fact, usually quite vehemently - especially if you're claiming it as woefully off. Just my 2c!
  6. https://support.fenixsim.com/hc/en-us/articles/12458972723087-How-to-update-or-import-navdata Try this
  7. Can you submit your logs to our support please? Same for both of you.
  8. What is still unclear is what “always 3D” actually means in the current WXR implementation. The published API documents the display controls, but I have not seen any public documentation defining the underlying sampling model: whether the radar is sampling a true volumetric beam, a slice through a volume, or some other projection. The documented cone angle appears to be display coverage; I have not seen any documentation describing beam width or sampling geometry. There is also a more basic limitation. DevSupport (https://devsupport.flightsimulator.com/t/allow-reading-environment-simvars-from-non-aircraft-simobjects/4976) previously stated that accurate weather information can only be returned at the ownship position, plus a small radius around the aircraft when needed, and that this is why there is no general Weather API for arbitrary world positions. That creates a direct problem for WXR developers trying to reason about forward sampling, cell structure, or any radar-derived hazard logic. The current official API also appears to be display-oriented, not data-oriented. Publicly, it gives a rendered MapView texture and display controls, but no official way to query cells or extract structured weather/radar information from the return. That matters because placing symbology at a given position requires access to the underlying radar/weather data at that position; merely displaying the rendered MapView texture does not provide that. The useful SDK clarification would be: - whether the WXR return is a true volumetric beam or a slice/projection - whether any beam width / beam broadening with range is modeled - whether attenuation, occlusion, or shadowing are modeled - whether structured weather/radar data is planned beyond the bitmap output - whether any structured Doppler / cell-motion data is planned for turbulence and predictive windshear logic Goes without saying we all massively appreciate the work being done, and look forward to further improvements!
  9. Reach out to support - ideally with a video of what you're experiencing, they will be able to offer 1:1 help
  10. Sounds to me like the startup flow for the FCU/FMGS etc, these units are "waking up" and initializing. Can be seen on a cold and dark startup too, once you sort some power to the aircraft!
  11. Huh, that is a new one. Well, every day is a learning day - but could you do me a favor and just ping support with what you've found and where you're at on this? It's quite an odd one to me, I will go double check my own bindings in 2024 a little later today as I am also running a combination rudder/tiller on my foot pedals. No worries re Discord, happy to leave things here so people can find it in the future, but one thing of note is that our Discord is for "verified" customers only - it's an automatic process, you can read about it here, should just take a minute: https://support.fenixsim.com/hc/en-us/articles/12458469647119-How-to-Join-the-Fenix-Sim-Discord
  12. no problem, thanks for being willing to work on it with us - just hit up support when you have what you need and they'll take it from there, good luck!
  13. To start with, if you've got a set of rudder pedals - make sure ONLY the rudder is bound to them in MSFS. If you've got a set of rudder pedals and a tiller - make sure both are bound to their requisite functions. Unchecked bindings can cause this kind of havoc. At baseline, if you've got a simple rudder axis bound in MSFS correctly, you load in to the runway (without anything else in your community folder) - no FSUIPC/FSR/Chaseplane all that sort of stuff - and you you move your rudder left to right after load in and initialization is complete, and nothing happens, get in touch with support as something is not right on your system and needs a bit of 1:1 investigation.
  14. This is not how it works IRL - that is just how it works on that product. This is correct
  15. You don't. Just set a rudder axis per normal in MSFS and click the rudder pull tab when you want to use nosewheel steering. You don't need to deactivate it either when lining up, it will automatically do so when you apply takeoff thrust.
  16. Depends on a lot of things - the fuel burn computed in the trip field should be close enough within around 200-300kg provided the winds are uplinked, the runways on both DEP and ARR are selected, and the procedures on either end are selected. This also means that if Simbrief has/includes step climbs, step descents, etc - that they too are programmed and inserted into the FMS to reflect. Then finally, double check the Simbrief wind uplink to ensure the winds are reflective of the reality you find yourself in - i.e the data is good - sometimes it deviates! All in though, the next update should also provide some enhancements to the accuracy in this area.
  17. Right, hence why I said I found your comment disingenuous. You're moving the goalposts a bit from what you said initially below, to what you're saying above, now. There's a difference between "it should displace more", and below - where you're quite firmly claiming nothing happens. While I am happy to say I can review the amount of effect, there's little I can do with feedback that falls into a fallacy of composition - "it doesn't move enough, so it doesn't move at all". Much more so when posted as a matter of fact. I feel the need to point this out as people do read what is said, and people within this community do have influence on, and within, prevailing opinion - a longstanding and well respected community member such as yourself, more so. Even scarier, most do not check for themselves, but will repeat it allowing such to propagate as fact. Have been on the receiving end of such, multiple times. fwiw, I also quickly tried a failure at 5000ft, 250knts, and a lightweight airplane so neither engine was producing a lot of thrust, in other words the most sympathetic situation to support your initial claim - it still deviated laterally, offset by a few degrees. If you feel it needs more beta target deviation, that's fine, but beta target and the actual aerodynamic yaw deviation are two relatively separate concepts. Yes, they mingle, but they are not one another, and there is a long, long list of factors that influence beta target that could cause it to deviate less than you feel appropriate - but again, equating that with physical yaw deviation due to thrust asymmetry and leaving it at that is very much an unfinished picture.
  18. Hm, I find this statement sliiiiiiiiiightly disingenuous. Did a takeoff cut, not a V1 cut, so you can see the asymmetry. Not sure why you don't need any rudder at all, but at least on my end - you need to respond to align your beta target. I think the amount of rudder trim needed is slightly less than reality, but more a problem with the trim units and the power of the rudder which I will review later. Asymmetry is alive and well 🙂 Sorry for the short video, using a debug build which tends to have many oddities going on with it, so usual caveats apply et al.
  19. You're not supposed to use it for timing anything. It's a procedural reminder, it has absolutely no idea what's going on besides playing in concert with it's relatively rigid logic. The FWC places these callouts into a buffer sometimes when they are activated rapidly in sequence, e.g retard callout - and it is not smart enough to "cancel" it like the newer aircraft when no longer required. The A320's logic and processes are from the 80s after all 🙂
  20. That's... not how VAT works - we absorb the cost of VAT for EU customers. The US charges sales tax per state, each state charges their own. We pay these too, again, we simply absorb it. Globally, Australia and NZ have their own schemes, as does pretty much every country on earth really. We absorb these costs across the board. We are not charging VAT. We are paying it.
  21. This picture caught my eye a bit - I'm not entire sure when your ECAM alert for LO LVL triggered, but the sensors and fuel are simulated in a more physical sense that you may expect i.e you're banking and pitching, 30 degrees of bank and 10 degrees of pitch - the fuel is sloshing around in the tank as a result and the sensor feeding this information to the flight warning computer (and therefore triggering it) can flag as dry with sustained bank/pitch earlier than it should, although it does look a tad on the low side anyway 😄
  22. Better to have and not need than need and not have 😁
  23. There are CBs that are required for MELs, failures, and troubleshooting - e.g if a system fails, you can pull the CB for it to reset power to it, observe it go through it's startup process, and depending on how long you power cycled it for, observe the effects of it fully resetting or not. That stuff is simulated, so if you fly with random failures turned on, there's a chance you may need to use the CBs to try and recycle power to broken things sometimes.
  24. Unfortunately we have never rewritten VNAV, we have rebuilt various sub-functions, algos, bits of math, bits of performance data, all sorts - but structurally and fundamentally it's been the inherited code from ProSim dictating the degree of flexibility we had. Yes, we have put quite some work into it as is - but the thing with keeping the wheels on the bicycle is that we can't address all things at once, so sometimes we must choose to do smaller work to make a smaller iterative improvement (like we have the last 3 years on VNAV) to keep things ticking along, maintained and improved, but not fully overhauled - until we have the resources or time necessary to do the overhaul. When we do start overhauling though, not only can we design from the ground up - but we can carry the learnings and "do not dos" from the old code and extensively working with it. Lots of overhaulin' going around and resources are limited ultimately, ECAM etc is also a very big job, very long in the making - we perpetually have more to do than time, but we're trying to balance as much as possible! We actually hired a full-time programmer to the team over a year ago specifically to work on an all-new VNAV that isn't rushed, or "good enough", instead building it to a specification that is closer to aerospace than home software. We could have probably done something in half the time that was a decent upgrade on the current VNAV, but that's not our M.O. Take the time, do it right. Which we have been, and will continue to do despite many calls for us to rush out whatever we have in development now.
  25. Hey - we're dialing in this new sound implementation so volume levels were sort of all over the place, we're knocking them back into shape now, but if you wish to try some fixes, a branch is available. Simply click the little icon on your installer, right next to Fenix A320 Base Pack that looks like a little fork almost. Enter: bfu-sound-fixes-2, and then click OK and update your install.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.