Prophet

As per the title, the auto update simply doesn't auto update, last tested in 1.1.8. During my flights when I have auto update turned on and then manually update a good while later, I usually get a newer ATIS that the auto update didn't detect for whatever reason, making the auto update feature quite useless. PS: Friendly reminder about my other thread, regarding the lack of the green auto update symbol on the D-ATIS page:

Had the same issue on final during my last flight while intercepting the localiser in IMC and icing conditions, freezing the airspeed during deceleration. No ECAM warnings at all, no indications of airspeed disagreement or probe blockage/failure. I guess all probes iced up at the same time, or ECAM warnings simply haven't been implemented yet in the iniBuilds A350 for these types of situations.

Still got the same issue in 1.1.8. I had a real TCAS alert in close proximity with another aircraft on VATSIM, before we got separated by ATC. After that incident, I was flying 15 nm behind that same aircraft in the same direction with similar ground speed, and it was still giving me intermittent collision alerts, telling me to climb, the traffic symbol for the other aircraft turning red.

I've had the same issue, and it seems completely random. Sometimes it works, sometimes it doesn't.

Any update from iniBuilds regarding this issue?

Any update from iniBuilds regarding this issue?

Any update from iniBuilds regarding this issue?

I've used BTV without navigraph with no issues at all in the iniBuilds A350, but since the v1.0.11 patch, I've encountered an issue. When entering a manual landing distance for BTV on the ND, as soon as I enter my desired value, a different higher value appears in the box. For example, if i type something like "2000" into the landing distance box, when I press enter, it turns into something like "2198" instead. The issue can be "solved" by entering lower values, like "1800" and then I get something like "1998" or whatever, which is close enough, but obviously a suboptimal solution. Like I said, never had this issue before, seems to be tied to the v1.0.11. And I cleared out my WASM folder before patching.

Every time I have tested the CPNY T.O. REQUEST function on the MFDs, it always gives some strange takeoff data. Even though the OIS takeoff calculator can give perfect calculations without any user input, the CPNY T.O. REQUEST always gives full TOGA takeoffs (even if you select FLEX or DERATE), and some of the fields you cannot even enter information into. It would be nice if the CPNY T.O. REQUEST worked as well as the OIS takeoff calculator does.

When a station is set to AUTO UPDATE on the D-ATIS page, there should be a green symbol visible next to where the "new message" symbol is, indicating that AUTO UPDATE is indeed active for that station.

When the night charts mode was first added to the OIS of the iniBuilds A350, MSFS 2024 didn't support night LIDO charts, so iniBuilds stopgap solution was to simply invert the colours of the regular LIDO charts. MSFS 2024 has since added support for the actual LIDO night charts with correct colour schemes and it has been supported for quite some time now, but the iniBuilds A350 still uses inverted colours, meaning that the colour scheme is completely incorrect on the charts. So my request is simply that iniBuilds adds support for the MSFS 2024 supplied LIDO night charts.

If you forward this suggestion, could you please also request the ability for .pdf chapters to be recognized, so you can quickly jump between sections, add a basic text/word search function, and also the ability to jump to a specific page number. Another thing that would be great would be support for basic image formats, like .png or .jpg, so we can download stuff like current and forecasted SIGMETs and access them through the OIS.

The have added a W.I.P version of AOC in the OIS, where you can actually receive your final loadsheet as a message, but at the moment, you only get the requested ZFW, not the final ZFW. Hopefully they add a final loadsheet message once loading is completed.

As per the title, when entering fuel values manually for alternate and final fuel, and then you change the taxi fuel, the alternate and final fuel values will be reset.

I have the exact same issue. All physical buttons work without issue, but screens have really bad hit detection. I usually use TrackIR for headtracking during departure/arrivals and it feels like the hit detection gets even worse with headtracking while moving your head. If I stay completely still without moving my head the hit detection is about the same as without headtracking.