YoursTrulyJack

I have to agree. I'm only just learning (the hard way) that all of the iniBuilds Airbus' use the default navdata having tried to perform a flight between VHHH and ZSPD, whereby the data for the STAR (BK91A > ILS Z 35R) shows waypoints along it 6000nm miles away, bringing the EFOB to its knees and dragging the frame rate with it. Load the same route into the Fenix A320 and it is faultless; with Fenix using Navigraph's navdata. Whilst I haven't faced the same issue at other airports yet (barring VHHH initially but managed to fix this), it troubles me to think that, at any one time, I'm not using the reliable Navigraph navdata that I have installed and am instead relying on the "somewhat" reliable default navdata. It's a big shame for me as the A330 was the aircraft I was looking forward to the most out of all the aircraft that came with the sim upon launch. With the A350 round the corner and very hotly anticipated by the community, myself included, I can't help but worry about the cost of the product vs its functionality when it comes to navdata.

Another theory I've had is more hardware specific, pertinent to a separate issue I've been having across both simulators (2020 and 2024), whereby my TCA sidestick would mysteriously and rather elusively turn itself off or disengage during the flight; with me only noticing when I go to disengage the autopilot at 500-1000ft on approach. When I unplug it and replug it back in, it causes all sorts of trips to the primary and secondary controls (throws thrust levers out of the CLB gate, extends full spoilers and adjusts flap settings), leaving me scrambling at short notice to reconfigure the aircraft safely. For anyone experiencing the same issue, I have deactivated Windows' ability to "allow the computer to turn off the device to save power" in Device Manager, by right-clicking any of the "hubs" in the 'Universal Serial Bus Controllers' directory, navigating to the Power Management tab and un-checking the box (craftily as I've never noticed it before). I will update below if I experience the phenomenon again.

Hi all, I've seen a few topics on similar to this but none of them quite sum up the same issue I'm having. I've flown the A330 on a number of routes since the sim launched, more frequently in the last week or so. However, on two occasions, I have experienced a phenomenon during cruise at different stages to eachother whereby the aircraft loses all power to both engines instantly, not progressively. I get basic power to the PFD, ECAM and SBY instruments as you would expect, along with deployment of the RAT along with a whole host of cautions and ECAM items relating to loss of power. The aircraft will still hand fly; the ECAM mentions a loss of both blue and yellow hydraulic systems. The engines will not relight, with the usual means applied (APU + bleed on, THR IDLE, IGN/START selected and the cutoff switches re-engaged), no matter how many times I try they won't relight. Most of the other topics that I've seen regarding this issue advise to un-bind any mixture bindings/axis' in the controls menu, to which I have since employed (only bindings on the keyboard which is rarely used in the cruise). I've removed all these bindings since, but this phenomenon does not discriminate when it occurs as I have had two successful flights of 3+hrs between the occurrences, both of them with bindings intact, and both incidents taking place at random stages during the cruise and without input from myself, simply monitoring. Thus, I'm not sure if it is indeed a problem with mixture bindings as I am not making any inputs when this takes place. Naturally, I will persevere and see if it repeats itself for a third time. The IGN levers are in the ON position both in the aircraft and on my TCA when and after it happens, so I'm satisfied that they haven't tripped and caused the engines to shut down in flight. The system itself quite literally just glitches and all of a sudden I'm in a state of basic power. I have attached a screenshot of the aftermath (taken after APU started to try and relight engines). I'm not sure how much help this can provide as it does not highlight all of the failures from the ECAM, but it might go some distance to explaining something to whomever is best able to analyse. I have a theory, and whilst I wish not to blame the simulation, it is almost as if a panel state is being triggered whereby the aircraft is provided with basic power but nothing else. It's loose at best, but it's all I have. Any further light that anybody might be able to shed would be greatly appreciated, and if the devs are able to look into what is now becoming a sporadic problem experienced by a few users, it would be most appreciated. Please let me know if I can provide any further information.