Haha “Ain’t nobody got time fo dat!” I’m not entering all my Simbrief data manually. Thats just nlt going to happen. However, I’m currently doing a Dublin to LA recreation with 3 hours to go and there appears to be a problem with fuel burn, though.
Strange…
Yeah I mean to be fair, as long as you press exit to menu and not end flight, it logs the flight before it freezes so makes no difference
I have noticed on longer flights it thinks you won’t have enough fuel but then it realises that you do as you get closer. Definitely something weird happening there
Yeah a couple of times I’ve had to add a little more fuel on the EFB with an hour or so to go. Lets see what happens. If i can stay awake, that is.
Note: I’ve just realised that for 90% of this flight thus far, I’m travelling East to West at 34,000ft-38,000ft, I’ve been flying into the wind. I now wonder if this is a factor that Simbrief takes into consideration?
Simbrief does take wind into account so it shouldn’t be that that is causing the problem. On shorter flights it seems to get the fuel right but definitely something going on with longer ones
who said they have QA ??? WE are QA, cheap and report instantly.
Just a heads up,
In regards to the fuel burn issue. After a few more long hauls this week, I suspect it may in fact be down to step climbs. We dont have any indication of when to perform them except but to take notes from the OFP.
When I tried this, I managed a long haul without running out of fuel even after recieving the yellow EFOB warning.
A fair point. Have noticed the OFP mention step climbs for various flights. But strangely enough I find some flights start with a yellow EFOB but don’t end with one
I suspect tail winds may also be a factor.
We do. You enter step climbs into MCDU and they will be shown on PFD.
I’ve tried inserting them before and they won’t register.
You used wrong format then. Below is an example of a step climb from waypoint CIM. The format to enter it is CIM/390 and then you press top left button. As you can see there is an arrow pointing up on PFD indicating start of climb.
The initial cruise level in this flight plan was FL370 and if I stayed at this level for the entire flight I’d land with 0.1T of fuel, according to MCDU calculations. After entering step climb to FL390 the estimated fuel jumped to 2.6T.
I’ll have an in-depth look at this tomorrow as I’ve just managed to get the A380 in the air and don’t want to quit out. But thank you. Much appreciated.
Yep, that worked. Thank you very much.
I am enjoying this plane which is really fantastic for a default aircraft. Before the beta I was getting a lot of CTDs but in the beta haven’t had any stability issues except that it sometimes freezes on exit. I really wish that they would add a checklist as I fly in VR and although I know the Airbus procedures fairly well by now a checklist is always helpful.Maybe it is there and I just can’t find it.
I’ve experienced quite a few freezes when I change the destination star with A330-300 GE. I do not encounter this issue with A330-200GE, only with A330-300 GE. This can happen during the initial MCDU setup when I am at the gate, or in air during the final approach when you need to switch to a different approach based on what ATC tells you. When this happens, all avionics freeze, nothing seems to be responsive to input, and I can’t ever move the speed brakes. The plane still flies and you can bank/change altitude via manual control but nothing on the panel is refreshed to show the current state. The only thing that indicates your action’s result is the game’s HUD displays for altitude, v-speed, and airspeed.
It also seems to only happen to certain STARs, i.e., choosing another STAR looks fine but not certain STARs. One problematic STAR/runway that would resolve in freeze is LSZH runway 28 (runway 14 is fine).
Yep it is only the ils28, the rnp28 works in LSZH. But it is also other approaches around the world. Over on the inibuilds forum they said they had fixed it internally more than a month ago but nothing on the live builds yet it seems
I am on the SU1 beta 3 build and it’s not fixed.
I hit this issue again on an A330-200 GE today with the same airport LSZH on ILS28 approach change after flying 9 hours. Please get this fixed in SU1 this makes this plane unplayable.
There was no official bugreport before, so I made one for it.
Not sure if it’s mentioned and I’d imagine that it’s probably fixed, but the left logo light points the wrong way from some camera angles and doesn’t light up the tail
Also, I forgot to turn the fuel pumps and on the engines started anyway
