swissdani

Another 2 hours later the ETA has dopped to 1803z and the EFOB to 15.9t. How is this plane so inaccurate?

I had the same thing this morning and then noticed that in the sim settings a different profil was loaded for my pedal. Once I changed that back to my main profile for my pedals, all was going fine again. No idea why it suddenly changed the profile, but have a look in the joystick settings.

I noticed the same thing, also with the Thrustmaster TCA Airbus.

At the moment flying from London to Cape Town. I have all the winds loaded before departure. After takeoff my EFOB was just unter 10t, and my expected landing time was 1712z, now after around 3/4 of the flight the EFOB did rise to 14.6t. According ot the simbrief planning, around 11.3t would have been expected. Where does this huge difference come from? The winds are spot on, as planned in the flight plan. Also the arrival time has now fallen back to 1752z. How is this possible to have a 40mins gap (no reroutes or detour) but having more fuel left at the end?

over a month and nobody from Inibuilds has said anything about this issue? Not really the best customer service.

Since the newest upgrade the cabin altitude indication / arrow in the ECAM cruise page is always flickerung and changing value from 0 to 50 up. Can you please have a look into this?

was also the case in previous versions as soon as flaps 3 was set.

Sim was running stable for me, but since going to 1.0.8 I had two freezes on longer flights and had to use autosave to continue the flight. On both flights the aircraft was not holding the CRZ ALT anymore and also setting BTV was no longer possible after the the autosave. Can you habe a look into this please. Hopefully autosave won't be necessary at all in the future again...

also on landing it already turns green in the ckecklist when flap 3 is selected, even if you plan to do a full flaps landing.

Does somebody else have the problem that this scenery has a very big hit on the fps. For me it's the 2nd ini-scenery in msfs2024 after Dubai that has this big hit on fps. London however is just fine. When "parked" on the runway I get solid 27 to 29 fps (locked) but during high speed phases like takeoff or landing the fps drop to 3 to 5, which is unflyable. My system is pretty decent and I do not have these problems at other big airports from other developers, so there must be something with the ini-sceneries that hits the fps very hard. Any ideas?

After a few more flights I only see this problem over the oceans, over land it works fine. Especially on longer oceanic crosses this function is needed the most. Can you have a look into it?

Had the same happening to me also today on one of my flights.

Hi there When flying the ILS 30L the PAPI indication does not match with the glide slope. The glide slope seems to be too high. When following the glide slope the threshold is crossed around 130ft instead of 50ft. Cany ou please have a look at this? Kind regards Daniel

Thanks, didn't see that post.

Hello Another bug spotted in 1.0.6. The ETA according to the FMS and ND is shown as 18:21, when I am fact at 17h55 I am only 1.4nm away from the runway. No way I am gonna need another 25mins for this short distance. Can you please check this out? Daniel