Prophet

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.

Go to the D-ATIS page and press Update (make sure that an ICAO is set). LikeDroneSim said, you only get METARs when ATIS is unavailable, otherwise you'll get an ATIS. And also, as far as I know, you need a Hoppie ACARS account to receive both ATIS and METAR. You can create an account for free, and then enter your Hoppie logon code into the OIS options page, under 3rd parties. Create Hoppie account: https://www.hoppie.nl/acars/system/register.html

During my flights in the A350 I've found that the D-ATIS is quite hit and miss when it comes to actually finding the ATIS. I think this is an issue due to VATSIM ATC not necessarily setting the ATIS type correctly. For example, if there is a single ATIS for both ARR/DEP at an airport, sometimes it will be found when you select ARR, sometimes in DEP, and other times in NONE. Even if you have two separate ARR/DEP ATIS, you might find the ARR in ARR, and the DEP in NONE, or vice versa. Therefore my suggested solution is to implement a fallback system where if the desired ATIS doesn't return anything, the aircraft automatically looks for the next one, in this order: If DEP is selected: Try to retrieve DEP ATIS, then NONE ATIS, then ARR ATIS If ARR is selected: Retrieve ARR ATIS, then NONE ATIS, then DEP ATIS. If NONE is selected: Try to retrieve NONE ATIS, then ARR ATIS, then DEP ATIS. This way, irregardless of how the VATSIM ATC sets up the ATIS, as long as there is an ATIS available, you will find it with one click of the update button. Currently the pilot has to do this manually. Press update, get METAR, switch mode, press update, get METAR, switch mode, press update, and then you find the ATIS. An automatic fallback system as per my suggestion would make things much easier.

When you go on the POSITION/TIME page and set a time marker after midnight UTC, and the current time is before midnight UTC, the time marker will not appear on the ND, and it will also not display the remaining time on the TIME page. As soon as the current time passes midnight, the time marker will work correctly again.

It's supposed to show the external taxi cameras on your PFD if I'm not mistaken, but taxi cameras aren't supported yet in MSFS so the TAXI button does nothing at all.

As per the title, when you disconnect autopilot (by sidestick deflection in my case) and get the "AUTO FLT AP OFF" on the ECAM, you cannot stop the cavalry charge audio. Even if you press the MASTER WARN button, forcibly clear the clear the memo with the ECAM control panel, or even press the guarded EMER CANC button, the cavalry charge audio will keep sounding indefinitely.