After a bit of experimentation, I think it's the engine noise. I suppose the noise cancelling headphone simulation works by reducing the higher frequency components, making the rumble more noticeable.

It's the EFB tablet itself that has been updated, i.e. the 'physical' device. It's now black, has a smaller bezel, extra buttons, higher detail etc.

yup, it was....I'm stupid...thanks ^^"

The camera's bounding box is baked into the model, so it would not be something you can adjust on your end, unfortunately. You could set a camera preset for this location, or use the native "toggle landing view" control in MSFS, both of which should ignore the bounding box. I try to create the bounding box to give as much vertical height as possible, so I suspect that there isn't much I can do in that respect without the camera beginning to clip through the geometry. I hope that answers your question. You know where to find me if you have any more!

@Black-Square: I hope you had a good Christmas and nice holidays. Is there any news on the update timeline?

Found this with chat gpt https://aviationarchives.blogspot.com/2017/09/avro-vulcan-b-mk-2-aircrew-manual.html

@Black-Square thanks

Hi Mark, Apologies for not responding, Christmas & families.... Many thanks for getting back to me. Regards, Neil.

Ive put a lot of hours into the Bonanza and Baron since they dropped for FS24 and I use the premium pms50 gtn's without any CTDs. In fact, thinking about it, the only CTDs I have ever got in FS24 are from within the GUI or within the SDK when building airports.

I am now routinely checking this and can unfortunately confirm that this is always the case. The FMS is simply unable to calculate accurately. It regularly estimates the aircraft to reach the T/D - which is often 80-110 nautical mile before the destination - only 1-2 minutes before reaching the destination. Obviosuly, the closer you get the more realistic the estimation will gradually become, but this is not how the real FMS works. PMDG, Leonardo, Fenix programmed their systems to do very accurate calculations. I hope Justflight will refine this aspect, it is certainly more important from the pilot's perspective than to be able to play nice boarding music. [image: e63b4a94-7da8-4b50-826a-4581304e895e.jpg]

@Martyn You're very welcome, thank you to the whole JF team for bringing the F28 to life! In a way, you're part of preserving history with recreating these vintage airplanes. One day the last F28 will fly, but they will always fly within our simulators. I am looking forward to your beautiful F70/100 with the Tay engines and your A300B4 as well. Thank you for passing that along to your sound team in case it could ever be improved!

Hi Martyn, I am using the JF store version on a personal computer. This hasn't come up since I reinstalled the product (although it was installed for only 2 days when it occured) and this time I did NOT enable state saving. I suspect state saving was somehow involved. I cannot prove it but the aircraft which had this issue was used in the previous session and I was unable to ever get its TRP come alive again, not even with loading a new panel state. I tried cold and dark, ready for take off, but the TRP was dead. I decided to reinstall when this happened and I did not enable state saving. So far so good.