kevinh
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by kevinh
-
-
Departing EIDW 28R, using the PESI2J SID. The A320 levelled off at FL090 after passing waypoint DW991 because the next waypoint (DW122) has a -FL090 ALT constraint. However it recommenced CLB before reaching that waypoint. A pseudo waypoint for the 250/10000 speed limit appeared between these two waypoints and I think that may have broken the CLB constraint logic. A later ALT constraint at -FL230 was correctly respected.
AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4).
Kevin
-
I was flying the SUTE4L STAR to EIDW 28L. This creates several waypoints at FL070 from SORIN to DW706. After passing DW706 the A320 did not resume the descent automatically, as I expected. I had to press the ALT selector again to make it continue.
AIRAC 2508 was still current when I flew this today but I see the FMGC says 2509 is active (from tomorrow, Sept 4).
Kevin
-
On 8/28/2025 at 5:20 PM, richboy2307 said:
Hi @kevinh
Thanks for your report.
If you can, please provide the OFP (PDF) for your route where you noticed this so I can share with the team for reproduction/fix testing.
Thanks!
Hi Vrishabh,
The OFP is attached. Note, I had to regenerate the OFP for the original date and time as Simbrief had deleted the saved OFP.
Best regards
Kevin
-
1
-
-
On 4/8/2025 at 6:15 PM, richboy2307 said:
Thanks, reported.
@richboy2307 I see the latest A350 version has a much improved ECS pressure controller, but the cabin is still a bit slower than it should be climbing and descending. The cabin altitude is always behind the target value. It works well enough during climb but the simulated cabin had to resort to a sudden 2000 ft/min rate of descent to catch up with the aircraft before touchdown. That would have made some ears pop. If you don't have ECAM pressurisation page selected you probably won't notice this but I did as I was checking to see if it worked properly now.
Kevin
-
1
-
-
On 6/18/2025 at 5:03 PM, kevinh said:
Likewise. I've never seen an ON/OFF switch on that panel before, Airbus or not. There's usually only the STBY-AUTO-ON and STBY-TA-TA/RA. TCAS still works with it OFF, displaying traffic and TA/RA mode on the ND, so one way or another something is wrong.
Correction, the ON/OFF switch is there in the Fenix but it defaults to ON. I've never noticed it because it's already in the ON position.
-
On 10/18/2024 at 6:02 PM, airernie said:
Thanks..
I tried both TA and TA/RA knob without success, but apparently there are two more that need to be set. One titled STBY-AUTO-ON and the other OFF-ON. This Airbus is a different beast than the 737. 🙂
Likewise. I've never seen an ON/OFF switch on that panel before, Airbus or not. There's usually only the STBY-AUTO-ON and STBY-TA-TA/RA. TCAS still works with it OFF, displaying traffic and TA/RA mode on the ND, so one way or another something is wrong.
-
4 minutes ago, Peter said:
Just start the apu, and change it on the settings for next time
I realised that eventually, the problem was I didn't know what the start up state was. However, it seems possible you could be in a position where there was no external power and no fuel for the APU. I think having a way to use the OIS regardless of simulated power state would be beneficial.
-
After updating to v1.0.11 I loaded the A350 and it had battery switches on but no External Power connected. That doesn't correspond to any of the preset states. So I guess the sim starts up in the state it was left last time it was run. That's quite a nice idea but if you aren't careful it's possible to be without power to the OIS on loading and have no way to change the sim configuration.
With only battery power I had no OIS and no way to connect external power. It should be possible to force the OIS to power up in such a condition so you can at least make changes to the configuration, load a panel state, remove the annoying engine covers, etc. PMDG use the CDU MENU button (held for a few seconds) for this purpose, an OIS lighting control button could do the same job in the A350 to wake up the display.
It should also be possible to choose your preferred start up panel state instead of having it load as it was left last time.
Kevin
-
For a cold and dark state this might be realistic, but not with GPU or APU power (which will usually be at a gate or stand). Certainly not realistic for Ready for Takeoff.
Please update the panel states so engine covers are only on for cold and dark.
Kev
-
1
-
-
Cabin altitude should change at a rate that equal to the cabin vertical speed. It is far slower than that and so cabin altitude is usually well behind the commanded cabin altitude. This has been a problem since initial release of the A350.
In a steady managed climb the Cabin VSI shows 400 ft/min, which is a reasonable value. However the indicated cabin altitude only climbs at 100 ft/min, 25% of the rate it should be. This means that as you get close to cruise altitude the cabin altitude is far too low and cabin differential pressure is in the amber or red range, which should never happen under normal conditions.
On my last flight, as I reached cruise level (FL390) the cabin altitude was still only 3,340 ft (6,000ft being the commanded cabin altitude), cabin diff press was 10.2 psi and it took over 24 minutes for the cabin altitude to finally reach 6,000 ft.
During descent, with cabin vertical speed stabilised at the commanded rate of -250 ft/min, the cabin altitude rate was -75 ft/min. Thats 30% of the value it should be.
Kev
-
I usually fly offline. I don't have a Hoppie account as I don't use it often enough, so it lapses. It seems D-ATIS is unavailable in this situation. It would be really useful if, after importing the OFP from Simbrief, the DEP and ARR METAR were displayed in the EFB, such as on the FLT OPS STS page.
-
3 hours ago, Alvariteus said:
Other bug I found for the team of iniBuilds to solve asap. In this case in the A350-1000.
[FLIGHT CONTROLS]
- The plane does not turn on ground, having all well configured, and with the gear showing like it's turning. The plane, however, goes straight and it was not possible to solve it, so a good flight that wasruined and a lot of time wasted in its preparation. Photo is attached. This one is so far the most frustrating bug and the first one that produces me a no-go.
It sounds like the nosewheel is skidding (applying too much tiller angle before the turn rate builds up). Taxying in MSFS isn't great (it's improved a lot in FS24 apparently). You must make tiller inputs slowly or the nosewheel will skid. Only make tight turns with GS less than 10 knots.
Nosewheel skidding will happen in a real airliner if you apply too much tiller too quickly. So this is a realistic effect and you need to keep tiller inputs slow and only increase the tiller as the turn rate builds up. I find setting reactivity to 0 in the tiller axis helps as it responds slower.
-
17 hours ago, Seth2413 said:
- AP siren wotn turn off (unless go to external view to turn off - BUG!!)
It works for me. Press the AP disconnect a second time. That shuts the warning off.
-
1
-
1
-
-
FMS Navdata Update does not work as per FAQ
in Systems
Posted
I hadn't updated navdata for a couple of months, so I've only just come across this issue. With cycle 2509 released, I went into the OIS to update it (I already had NAVIGRAPH data selected and linked). I did this with the aircraft on external power, no engines running. I downloaded the latest revision (2509r1) and that showed up correctly in the OIS with a green success banner and an updated revision nymber. However the FMS is still on the old revision. I tried powering off the aircraft completely then reapplying battery and external power. That didn't load the new database. I had to go back to the main MSFS menu then reload the A350 to get the new revision loaded.
So how is this supposed to work? Is a reload now a required step? If so that's not great, as it takes up a lot of time in MSFS. The PMDG 777 EFB updates the navdata loaded in the FMS so there's no need to reload the sim. So it is possible.
An offline method of updating navdata would be much faster and more convenient unless this can be fixed. Managing this via the Navigraph Hub would be a way to do that.
Finally, a suggestion. The sim doesn't keep a back up navdata revision (unlike the real aircraft). That would be a nice feature to implement so you could easily revert to the previous revision in the FMS in case there's a problem with the latest data.
Kevin