4 hours ago, Noel said:

About a month ago or so when I asked on Discord if BATC was aware of the plane's altitude because it behaves like it doesn't, and the answer was an unequivocal NO.   And the rationale was:  the pilot knows where the plane is supposed to be so there is, apparently, no need for ATC to know.   This must be why BATC directs me to 'Descend to 5,000 feet', then doesn't say another word.  My problem is I never know if BATC is going to tell me, soon, to descend to 3,000 feet or what have you.  And this often leaves me coming in too high.   I can happily follow my own navigation just dandy but the problem comes when BATC directs the descent then suddenly stops directing.  How do others deal with this?  

What? Please show me the link of that discussion, I want to know who said that. That's total BS. Of course BATC is aware of the planes altitude. It will even give you delay vectors if you're too high.

Yesterday I let VNAV start my descent before asking ATC (my bad).   Barely 2000ft below cruise level I was promptly instructed to immediately climb back.

6 hours ago, Fiorentoni said:

What? Please show me the link of that discussion, I want to know who said that. That's total BS. Of course BATC is aware of the planes altitude. It will even give you delay vectors if you're too high.

3 hours ago, Noel said:

So, does this mean BATC thinks you've joined the circuit?   Was there any trigger for this?

5 hours ago, Noel said:

Hello,

This statement is incorrect. BeyondATC does take altitude into consideration, including with the older vectoring system that is currently used in the Early Access version. That said, this does not mean the system is completely free of bugs in every scenario or during specific arrivals.

This is precisely why we always ask for log files. I understand that it can become frustrating to hear this request repeatedly, but it is the only reliable way for us to determine what actually happened. With the logs, we can reproduce the flight and review the situation under the exact same conditions to understand the cause of the issue.

15 hours ago, Noel said:

And the rationale was:  the pilot knows where the plane is supposed to be so there is, apparently, no need for ATC to know.

To be fair, I find this statement somewhat misleading. Although the response given by the community mentor was incorrect, it was never suggested that ATC does not need to know the pilot’s altitude. Presenting it that way makes it seem as if we misunderstand how operations work, which is not the case.

On a related note, the comment in question was made by a community mentor. Community mentors are extremely helpful in providing first-line support and answering general questions for the community. However, they are users just like everyone else and are not part of the development team. As such, they may sometimes share their own interpretation of how certain things work when users encounter issues, but that does not necessarily mean they have the full picture of how the system actually functions or how it was designed.

Hope this clears things up.

Yeah, for future reference: Developers on Discord are Gold in Colour, not Green.

12 hours ago, Fiorentoni said:

What? Please show me the link of that discussion, I want to know who said that. That's total BS. Of course BATC is aware of the planes altitude. It will even give you delay vectors if you're too high.

Right now, I'm glad that BATC... let's say... doesn't mind your altitude. Cause when getting vectored to the rwy, the descent path management is so bad right now (not using the experimental version) that you must ignore the descent instructions very often and go lower to be a responsible pilot (and not come into the IAF with 3000 to 5000ft above).

3 hours ago, Dialex said:

This is precisely why we always ask for log files. I understand that it can become frustrating to hear this request repeatedly, but it is the only reliable way for us to determine what actually happened. With the logs, we can reproduce the flight and review the situation under the exact same conditions to understand the cause of the issue.

The support Discord is filled with logs and posts from the same issue.  I'm finding tons of similar posts and no resolution.  

There seems to be at least two situations too:  One where the logs show the application is "panicking" and basically not working properly.  The 2nd, and likely way more common one is it just doesn't give good instructions.  While it doesn't "lose" you, it seems aware that you exist, but you're on your own as far as flying.  Of course there's the 3rd situation where the program actually works well, which does happen a lot.  

Most of my situations are the 2nd one, where there's nothing in the logs.  I'm looking at a similar post from over a month ago and the logs aren't useful because they don't really show anything (and the thread was never followed up on).  

I mentioned before too, I'm on the official build, so there's also not much point in debugging a version that already has been replaced with an experimental one.  I'll submit some if I see the same problem with the new build when it is released.  

11 minutes ago, kerosene31 said:

The support Discord is filled with logs and posts from the same issue.  I'm finding tons of similar posts and no resolution.    

One of the biggest issues we often encounter is how quickly people make assumptions based on the reports they see. It’s quite common for different reports to be grouped together as if they all describe the same problem, when in reality they may stem from entirely different causes. This is why it’s important to leave that assessment to the dev team, who have far more insight into how the system works and where it may fail under specific circumstances.

The same applies to log files and their usefulness. Just because a log file does not clearly display the exact issue in plain text does not mean it is useless to us. Log files contain far more detailed information than that. They allow us to examine entire flights, including the sequence of events, aircraft positions, timing, and the context in which an issue occurred. This information is essential for identifying patterns and understanding what may have gone wrong, especially when the bug is proving to be difficult to identify. That is precisely why we ask to always upload them, there is no harm in sharing them even if you personally think they are useless (and quite frankly, they rarely are).

It is also worth mentioning that the Discord server contains many reports because it is the main support platform we use. In some cases, there may not be an immediate resolution, simply because not all issues are straightforward to solve (and the dev team would certainly prefer if they were).

Some problems may require deeper changes to core systems, as was the case with the latest experimental update. While the development team can work on multiple things simultaneously, they cannot address every issue at once. As a result, certain problems may need to be temporarily set aside while others are prioritized and resolved.

3 hours ago, Watsi said:

Right now, I'm glad that BATC... let's say... doesn't mind your altitude. Cause when getting vectored to the rwy, the descent path management is so bad right now (not using the experimental version) that you must ignore the descent instructions very often and go lower to be a responsible pilot (and not come into the IAF with 3000 to 5000ft above).

This is the case for my use of BATC far too often.  What I find bizarre is BATC will direct me to descent to X, then stop giving further descent instructions leaving me wondering if I'm supposed to WAIT for another instruction, or just dive on down to where I need to be.  Very strange this, and, why in the heck does BATC's ground traffic behave so poorly vis a vis my aircraft:  way too often it will tell me to hold for x traffic and that traffic might be heading right for me on the taxiway whereupon it becomes a Mexican standoff, or will tell me to hold while on a taxiway when the only traffic near me is the one landing on an adjacent runway.  Just yesterday I'm taxiing to the takeoff threshold and another plane turns directly into me.  To be honest this actually happens as much or more than when I only use FSLTL's injection which is hard to fathom.   I would have thought these core features should have been resolved well before adding other less basic features.   That being said it's certainly not all bad there is a lot of good in it, especially if you're willing to pay for premium controller voices but wish there were a few more premium capt voices beyond British and American I would love to have German, some Scandinavian, French, etc.

Been having no issues using batc giving me  the descent, last flight i did was at 36000  directed me to flight level 19000 got down to that level few minutes later said to descend to 12000 than to 5000 than  vectored me to the final.   One time i was over  the  alt by 2000ft and batc wasnt happy and said to descent to my correct alt