However, I uninstalled and reinstalled everything.
All my settings are set to 5.
However, I uninstalled and reinstalled everything.
All my settings are set to 5.
Is the basic voice model not working anymore? Everytime I select it I get an error. Also an app restart does not help.
Do you mean this?
It doesnāt work for me either. Strange that I havenāt seen any complaints on their Discord channel, so I was waiting if itās not a problem on my endā¦
On Friday, I was getting an issue initially with the Local voices (which are much better than Basic) and had to revert to Basic, which worked fine. I was not able to fly on Saturday but yesterday I was able to swap back to Local voices again.
That did it. I didnāt notice I had it switched to Local voices. I switched to Basic voices and now Iāve got voices again. Thanks!
Well, if local voices are better than I donāt mind that my basic model does not work.
Weird. I flew for about 2 hours Friday late afternoon, Saturday off and on for about 6 hours total, and a 2 hour flight Sunday mid morning. All on Local Voices. No issues.
Maybe there was a carrier issue that affected multiple service providers?
I think this is a new feature, at least I didnāt notice it before, just installed 1.7.5 Experimental version, and now the ATIS text is visible on the Frequencies page, for BOTH departure and destination airports!
And, now it shows who is speaking, and your own transmission buttons are available to push even when someone else is speaking.
Yep, both new features as listed in the changelog for the Experimental version:
Yes that works in the main window but not in the toolbar app that drops down which you need to use in VR.
Not just for use in VR. I hope they remember to update /support it. I use it daily.
I donāt see in the changelog that the core bug has been fixed, specifically the issue where BATC cannot be launched if Simbrief is not working. I donāt want to discuss this; Iām simply pointing it out.
In any case, itās good that they are fixing things at all.
Thatās not a bug. Itās a design decision. You are free to disagree with it but software depends on various services and simbrief is ubiquitous in the community and has fantastic uptime so I really donāt get the issue.
I clearly stated that I donāt want to discuss this. However, since you replied anyway, I hope you are a BATC developer and can confirm that this is indeed not a bug but an intentional decision.
Itās right there on their website. No need to keep banging on about it: Preflight - BeyondATC Help Center
I didnāt ask for a Simbrief user guide - Iāve been using it since 2013, from its very first days, and I assure you I know how it works. Since you already replied, I would very much appreciate a screenshot of the link you mentioned showing that if Simbrief is not working, BATC also wonāt start.
EDIT
With all due respect, Iād like to remind you that I donāt want to discuss.
So if you are not a BATC developer, please do not reply, as youāll be wasting your time. I am only interested in the position of the BATC developers.
If itās not in the change log, itās not fixed. Same as the MSFS release notes.
Please refrain from pointing this out every time, because itās getting a bit repetitive, to be honest.
I donāt know if thereās a Nolt-item for this? If not, it certainly will never be solved.
But again: and this is the last time that I will say it: your point is valid, but I think BATC has more important ānuts to crackā at the moment, as we say it in NL. Muts that affect many simmers in many flights.
To end the discussion, I understand that this is early access and that bug exist and will continue to exist. Iām simply pointing out again that if Simbrief is not working, BATC will not start, making BATC unusable. I believe this is important from a buyerās perspective, which is why Iām reminding others so they are aware of this before making a purchase.
Simbrief is currently a required dependency for BeyondATC, and this is clearly communicated. The requirement is explicitly stated under the download button on our website, and all of our documentation and wiki guides walk users through starting a flight using Simbrief. This is not a bug or an oversight but the intended and fully implemented workflow, and it is functioning as designed.
Regarding the recent Simbrief outage: these interruptions are rare, short-lived, and outside of our control, as Simbrief is a third-party service. A brief, temporary unavailability does not warrant a hotfix or an urgent architectural change to BeyondATC.
I understand the frustration when any external service experiences downtime, but the situation is being significantly overstated. Simbrief remains highly reliable overall, and its integration is a core part of BeyondATCās current design.
Woah there, letās keep things civil and avoid personal insults.