Jump to content

foliainfx

Member
  • Posts

    114
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by foliainfx

  1. I requested that iniBuilds move the camera to the proper position months ago, they didn't do anything about it, so you'll have to adjust it manually.
  2. What MSN and airline do iniBuilds use as reference?
  3. The ini A350 isn't able to comply with altitude restrictions, on the FCU there are no dots indicating managed mode
  4. The HUD in the A350 isn't implemented at the moment
  5. Try using alternate download
  6. How soon will this be?
  7. Does this happen if you go to the main menu and then load in? I've found that "restart" causes issues
  8. iniBuilds advertised it as a feature over a week ago, and it still doesn't work.
  9. No, it couldn't actually do them reliably from the start. There were always issues like dives, going off center and just floating off the runway.
  10. Is it enabled in the PRINTER menu under DATA?
  11. The A350 is unable to perform proper autolands.
  12. The HUD will most likely release next week. With iniBuilds, keeping a backup version of versions before the update is a good idea to prevent things like this.
  13. The FMA should be fully reworked by iniBuilds imo. I've reported a lot of FMA related issues already, and ini just don't wanna fix them.
  14. Hi, "The TO CONFIG TEST should be able to be performed and get NORMAL result, even without the cabin being ready, at the moment you have to wait for Cabin Ready before being able to complete the TO CONFIG test, this is incorrect." - This is actually an airline option. "Turn Around Time on BVT is still the same regardless of the exit selected. (BTV Information also doesn't now show up unitl A/BRK is pushed, before we used to get the information on the exit, by selecting it on the map, even before A/BRK button pushed. - will check which is correct" - The turn around logic is still not implemented, and still WIP. Regarding the A350 in general: iniBuilds should make the A350 from the ground up, many basic system functions are incorrect. VNAV and VD are currently unable to calculate and properly display missed altitude constraints. This was supposed to be fixed in V.1.1.0 but was, aswell as many other issues, not fixed. There are a lot more issues not included in this post like TOW and LW calculations. There are several failures are incorrectly simulated or just do not work. Here is a list of key things that should be reworked in the iniBuilds A350 which pose a significant issue: - ECAM - FMA - FCU - MCDU - Model - Sounds - FBW - Electrical network - Hydraulic network - ANF - VNAV - LNAV - EFB - AC network - Fuel system - Flight controls - DRAIMS - VD - Failures - Effect of mass on MLG and NLG - Texures - ROPS -ROW - ANF I could keep going but I'm sure you get the point.
  15. foliainfx

    HUD

    Hope it'll be fixed by then
  16. foliainfx

    HUD

    1. 11 lines in the ini - 10 irl 2. Wrong position of approach data 3. -Disregard- 4. VLS line should stop at Vαprot 5. VS isn't displayed (I assume this is due to the HUD being WIP) 6. Missing target altitude (I assume this is due to the HUD being WIP) 7. Can't really tell in the ini, the 2 upper triangles should touch eachother when neutral 8. The HUD goes over the glass screen itself in the ini A350
  17. Performance is still the deciding factor, missing ITO also really affects images in case you haven't noticed. But there are a lot of windows in the A350 which you'd need several different dynamic states for and that, I expect, will really affect performance,
  18. It's for MSFS2020 and not 2024. You can try using the 2020 folder for 2024.
  19. The cockpit proportions will get fixed.
  20. I assume iniBuilds will soon push a HF, please include this in it.
      • 1
      • Like
  21. The art will be revisited in the future, so it might get fixed then.
  22. Fyi, ini regularly include things in the changelog that's not implemented, so don't take the changelog too serious.
×
×
  • Create New...