Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

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.

frank_m

Member
  • Joined

  • Last visited

Everything posted by frank_m

  1. Of course you have the OIS also on XBox.
  2. Where have you changed the fuel? In the OIS Loadsheet page? There you have to adjust the fuel, not in the MSFS EFB.
  3. How often has it to be repeated? Cabins are not supported any more!
  4. I'm not sure regarding D-ATIS, but CPDLC is working (as far as BATC supports it).
  5. frank_m replied to bluair's topic in General Discussion
    No problem here. Maybe you should show screenshots, what you have done: SimAppPro settings and profiles (in particular the operating mode of the throttle), Windows calibration, control assignment in the MSFS (Axis and buttons) and calibration in the plane (including the settings like "Reverser on Axis"). Be aware: ALL mentioned items are important, and we need information from all of them.
  6. Now you got it. There are several planes not allowing to set the simrate - Fenix is only one example. And others reduce the rate even if they allow it to be set using the standard key bindings - FBW for example. Good and complex planes ensure the simrate is small enough to guarantee a flawless simulation. This is usual.
  7. Yes. Please read #2, and you'll have the answer. It is not possible to enter 2x or 4x manually. You have to use the OIS.
  8. It is still the same reason as in the few hundred threads before asking the same question: Cabin Packs or incompatible addons like liveries. Details in the other threads.
  9. In the same way as in all other planes. You have to assign controls for the sim rate of course.
  10. You have to configure the Simrate 2x and 4x in the OIS. At Simrate 4x you can enter 8x or 16x manually using configured hotkeys.
  11. That is most likely a problem of your control configuration: Joysticks, pedals and so on.
  12. That is a typical problem if the hardware is overwhelmed with SimRate 4x.
  13. That is most likely due to the planned approach. Then you are using outdated navdata from 2023.
  14. There is a setting in the OIS for automatic remove of the covers. Alternatively you map a key in MSFS for "Quick Pre-Flight Control". I have mapped it to Shift+C, so the Pre-Flight control is performed automatically as soon as I enter the cockpit - and all covers are removed, not only the engine covers.
  15. You can do it "half by half" in an iterative way. Divide your add-ons into two halves and test which of the two halves is causing the problem. Then divide the problematic half into two halves again and test again to see which one is causing the problem. Divide it into two halves again and continue in this manner. Even with 250 add-ons you need only 8 steps to identify the bad one.
  16. You have incompatible Liveries, Cabin Packs or other addons installed. It is sufficient if they are installed, you do not even have to use them. Try again with empty Community folder.
  17. frank_m replied to ekosif's topic in Systems
    Yes, if it's new information. But why spread it across the whole forum? Developers have to search dozens of threads to collect information and get a complete view. Wouldn't it make more sense to have all the information in one thread? This is particularly important if the information comes from the same person. Whether these threads make sense if there is no new information and it is always the same question is something you can decide for yourself. Every forum I know has the following rule: Use the search function before you start a new thread. There is a reason for this. What conclusions can be drawn about the reported bugs if the thread creators can't even follow the simplest rules?
  18. frank_m replied to ekosif's topic in Systems
    The issue is known, there are plenty of statements from the team. It does not help, if always the same people are opening new threads.
  19. Yes. As I said, the TCAS is a known issue, and there are even more threads, and also statements from the team you asked for. If try your best, you will find it. Yes, you can! Your other thread is regarding a VNAV issue and not regarding TCAS, and it is in the 2024 version, while we are here in the 2020 section. I recommend to take care about your posts, otherwise people will get the impression, you are somehow confused. If you are using the plane in the same uncoordinated way like the forum, then your problems are most likely no bugs...
  20. You are ALSO NOT, GOT IT? As you can read here, nobody except you has tie problem. Guess what, this is an individual thing, but no bug. Thats what I tell you with 40 years experience in software development.
  21. But the same lasts for you. I'm just seeing the facts: no other users complainig about the issue, and I can't confirm it at all. Therfore I tell you: it is a bug when it is confirmed, but not before. You are perfectly right. And what is missing? The other users joining. If you ever have developed only one line of code, you know, that this is impossible on systems you can't control completely. Otherwise you have absolutely no clue about SW development.
  22. Yes, there is a problem and a recommended configuration to circumvent it as long as they are working on it. What else do you want? Oh, I have. In particular, people using outdated Navdata in Simbrief are creating invalid flightplans. Oh, that problem occurred for the large majority of the users. Additionally it was confirmed by the team. Your "bug" is observed by only one user and not confirmed. It becomes a bug if enough people are complaining about it, and it is confirmed by the team. Which both is not the case for your problem. No, that is definitely not the case. There may be problems caused by addons causing problems in specific other addons, but not in all. Think about the problems caused by addons having no "package_order_hint" entry in particular with Navdata. It looks like a problem of the plane or the scenery, but finally it turned out to be a problem with the Navigraph Navdata caused by old MSFS2020 sceneries not involved at all in a specific flight. It is enough if the old addons were installed to disturb the navigation. Oh, I'm sorry about that. Then you have never developed software for Operating systems the user can configure in an open way and install other software. Otherwise, you would know, how external components can influence the behavior of your software. Just let other tasks consume the resources like CPU or memory and lets see, how good your software performs with missing resources. A problem of your software or of the user not providing a clean environment?
  23. That is not true, there have been several statements from the team regarding TCAS in the past. Regarding your VNAV Problem: I can't confirm it. During the Christmastime I did a lot of flights with the A350 on random connections (chosen with https://where2fly.today/). There was never an issue with VNAV, neither in occupied areas (Europe, USA), nor in lonely regions (Asia, Africa). Neither with handcrafted airports, nor with standard airports. I think, either your navdata is not correct installed, or there are conflicts between your flightplan and your navdata. Maybe you are using outdated waypoints somewhere in the chain? Well, it is definitely not a bug of the plane, since otherwise a lot of people would complain about this issue, and you are the only one.
  24. An empty folder means an empty folder: Delete all (other) add-ons except the A350. In particular liveries, sceneries and tools.
  25. frank_m replied to jan_aviation's topic in Other
    Remove incompatible addons and liveries.

Account

Navigation

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.