Hi again @Jummivana.
I downloaded the latest update including World Update 4 and all related packages to see if it fixed any of the problems I referred to in my last post.
After installing the update:
(1) Again some of my settings had changed in the ‘ASSISTANCE’ menu - I have now changed them back to my preferred settings and it appears they have not changed since.
(2) My missing hours from when my logbook reset have still not returned (any hours logged since the logbook reset are still there (I have six hours, though it does say my “next level” is 600hrs) so evidently it knows I have previously achieved 500hrs+
(3) Re: the earlier ATC Azure voice problems - please completely ignore what I said. I think it was playing Azure voices the whole time after all. The pilot’s voice had changed (and didn’t sound as realistic to me) so I thought I was hearing the ‘Windows Offline’ voice for the pilot. It turns out that, when the sim changed some of my settings, it also changed the pilot/co-pilot avatars all to ‘DEFAULT’ in the MISC menu. Selecting ‘DEFAULT’ for the avatar causes an alternative pilot/co-pilot voice to be used for ATC communication.
However, I may have discovered a completely separate bug (see below)!
Other observations:
Changing ATC Text-To-Speech Mode Causes Brakes To Be Applied
After changing the Text-To-Speech setting while taxiing (I was toggling between Windows Offline and Azure) I observed that, if this setting is changed, when returning from the menu to the aircraft, the aircraft’s brakes are automatically applied despite me not pressing anything. Once the aircraft comes to a stop, pushing the brake pedals and releasing them releases the brake (you can also solve the issue by apply the parking brake, then releasing it again). This happened in the A320 FBW, however to make sure it wasn’t the add-on, I have tested this in the Asobo default/stock TBM Daher with the same result.
AI CONTROL 'Manage Radio Comms’
After changing the ATC voice settings, the AI Co-pilot wouldn’t respond to ATC, even though ‘Manage Radio Comms’ was selected. I know there is a long-standing well-known intermittent issue where the ‘Manage Radio Comms’ being delegated to the AI Co-Pilot sometimes doesn’t work when activated, but thought I’d mention it here.
It does seem as though this ‘packages’ error has caused quite a lot of issues, though most of them thankfully have been resolved, the missing log book entries being the main one.
If you need anything else (or need me to file a Zendesk) please let me know. In the meantime, I’ll leave it in your capable hands and await any feedback you may have on the issue