There's a dedicated page on the EFB, for Ini's own custom system. Press the small gear/cog icon in the top right of the EFB.

I only get the brightness option, the Power off EFB, Lock EFB and the panel states (cold and dark, Ready for Takeoff, on APU and on GPU) nothing about time compression unfortunately.

I only get the brightness option, the Power off EFB, Lock EFB and the panel states (cold and dark, Ready for Takeoff, on APU and on GPU) nothing about time compression unfortunately.

Then you haven't successfully updated to the latest A300 Premium version I'm afraid.

Unless you don't have the Premium version of the A300, and only have the 'compatible' MSFS2020 version? I don't think that version got the update that added the time acceleration.

The A300 Premium page on the Ini Manager does state that you need to manually delete your present A300 folder and download it freshly in full. So if you do have the A300 Premium verison, I'd recommend deleting your Ini A300 main folder, then going into Ini Manager, hitting "uninstall", then doing a fresh install.

Edited May 17May 17 by JYW

Then you haven't successfully updated to the latest A300 Premium version I'm afraid.

Unless you don't have the Premium version of the A300, and only have the 'compatible' MSFS2020 version? I don't think that version got the update that added the time acceleration.

The A300 Premium page on the Ini Manager does state that you need to manually delete your present A300 folder and download it freshly in full. So if you do have the A300 Premium verison, I;d recommend deleting your Ini A300 main folder, then going into Ini Manager, hitting "uninstall", then doing a fresh install.

Thanks, I'll remove everything and re-install! Many thanks for the help!

Thanks, I'll remove everything and re-install! Many thanks for the help!

You're very welcome.

When I first installed this update, it didn't work for me either.

But a full uninstall then reinstall rectified the problem.

After manually deleting the main folder from the Community folder, make sure you also hit "Uninstall" in the Ini Manager. Then I'd recommend closing the Ini Manager, relaunching it and then re-installing.

Edited May 17May 17 by JYW

anyone having an issue with overhead click spots being extremely tiny? Like the over head buttons, the mouse needs to be in the exact middle of them to click on them

flip switches are fine. buttons everywhere else are fine, it's just the overhead panel.

Yes. Microsoft/Asobo bug. The click spot somehow doesn't scale up correctly with this model (or something similar). Not sure Ini can fix it or if it has to be Asobo.

You're very welcome.

When I first installed this update, it didn't work for me either.

But a full uninstall then reinstall rectified the problem.

After manually deleting the main folder from the Community folder, make sure you also hit "Uninstall" in the Ini Manager. Then I'd recommend closing the Ini Manager, relaunching it and then re-installing.

You're very welcome.

When I first installed this update, it didn't work for me either.

But a full uninstall then reinstall rectified the problem.

After manually deleting the main folder from the Community folder, make sure you also hit "Uninstall" in the Ini Manager. Then I'd recommend closing the Ini Manager, relaunching it and then re-installing.

It worked! I removed everything (including WASM folder + cache) and reinstalled! Now I get the time compression options! Many thanks again!

It worked! I removed everything (including WASM folder + cache) and reinstalled! Now I get the time compression options! Many thanks again!

That's great! Enjoy.

Does the latest version 1.0.8 fix the WILCO CPDLC message bug?

Just loaded the update and had a quick test flight - and reminded myself why I simply love this aircraft! It has a real 'trad meets modern' feel about it - I find it similar in that respect to the equally splendid Avro RJ series from Just Flight.

For tubeliners, I have learned the hard way that the best approach is to stick with one model and master (well, rookie-master) the flight planning and flight procedures from cold and dark to arrival and shutdown before moving onto another model. And this is the one I will be sticking with for a while 😊

OK - failed at the first hurdle. I can't ground steer the aircraft. There's an option to disable the auto tiller or not - which I assumed was the correct one to be able to get the tiller to turn with the rudder pedals or not? But that seemed to make no difference whether it was switched one way or another.

I'm sure it's something I'm not doing correctly - any clues how I can steer it on the ground?

Edited May 18May 18 by AJZip2

OK - failed at the first hurdle. I can't ground steer the aircraft. There's an option to disable the auto tiller or not - which I assumed was the correct one to be able to get the tiller to turn with the rudder pedals or not? But that seemed to make no difference whether it was switched one way or another.

I'm sure it's something I'm not doing correctly - any clues how I can steer it on the ground?

Scrub that - got confused between the subtle difference between 'Yes' and 'No' on the control settings 😄 All good now

You really expect further updates for a platform that has been replaced over a year ago?

I can understand that. However, as someone who doesn't have a decent internet connection, I still use MSFS2020, and it would be great to get some of the improvements. I don't have much hope that they will, though.

I cleared the wasm folder after updating to 1.0.8 and had my first flight with this version yesterday without any problem. During my second flight today, as I was programming the FMC to plan for the descent, I had my first ever wasm crash with this plane.

Anyone else with the same problem?

I cleared the wasm folder after updating to 1.0.8 and had my first flight with this version yesterday without any problem. During my second flight today, as I was programming the FMC to plan for the descent, I had my first ever wasm crash with this plane.

Anyone else with the same problem?

Hi, we are noticing an increasing set of WASM issues relating to A300 following SU5, something we are looking into as we continue to do with A340 and A350. The only thing that makes things more difficult is that we don't have any logging of current like the latter aircraft so we don't get a save or log to look at immediately so we're doing things by route basis. I have yet to have one naturally occur but have been able to reproduce some that the community have shared. I know others that are getting them consistently. If you do come across any WASM crashes, you can add them in detail with the route and actions taken at the time so that we can reproduce them and see what is happening on our end. Thank you.

https://forum.inibuilds.com/topic/35422-inibuilds-a300-master-wasm-crash-thread-v108-fs24/

Edited May 20May 20 by IniJamir

Hi, we are noticing an increasing set of WASM issues relating to A300 following SU5, something we are looking into as we continue to do with A340 and A350. The only thing that makes things more difficult is that we don't have any logging of current like the latter aircraft so we don't get a save or log to look at immediately so we're doing things by route basis. I have yet to have one naturally occur but have been able to reproduce some that the community have shared. I know others that are getting them consistently. If you do come across any WASM crashes, you can add them in detail with the route and actions taken at the time so that we can reproduce them and see what is happening on our end. Thank you.

https://forum.inibuilds.com/topic/35422-inibuilds-a300-master-wasm-crash-thread-v108-fs24/

Ok thank you for replying and providing some insights. Will definitely contribute to this thread in the future. I had my third flight with the plane yesterday and I made sure not to go too fast through the FMC especially with SIDs and STARs and I didn't get any WASM crash. It was the same route as the route from the day before when the crash happened.

I also wanted to know if the latest version 1.0.8 fixed the WILCO CPDLC message bug reported here: https://forum.inibuilds.com/topic/35823-cpdlc-wilco-not-working-on-the-hoppie-network-v107/