Hi

Pulling my hair out.  BATC has been working great for me over the past month or so - and when they introduced Live Traffic, it was still GREAT!!

But - coincidentally or not - since Christmas after a small update, switching to VR basically now stops BATC in its tracks.  I thought at first it must be BATC itself, but it is definitely when switching to VR.  Come out of VR and BATC is instantly working as normal.  Thinking it might be a bandwidth/similar issue, I turned off the BATC Live Traffic in its menu this afternoon - and it started working OK.  But this evening, even when Live Traffic is off, 2D gives normal BATC and VR gives nothing - no mic ping - the rest of it just seizing up.

Very frustrating.  Anyone else got similar issues?

 

I suggest going to their Discord channel. Tons of community members can surely help you there.

36 minutes ago, edpatino said:

I suggest going to their Discord channel. Tons of community members can surely help you there.

Yup - already done that.  After a search (there are a LOT of posts) someone else in VR having very similar issues.  Hopefully someone will have a look although no responses yet.

 

Fine for me with the VR toolbar. 

Switching out of VR causes a fatal error in Beyond ATC for me since the last update too.

I've posted two or three times on the Discord channel.  This time quite a quick response but from someone who openly declares that they don't know anything about VR.  BUT, within minutes there was a post from another user having exactly the same issues - so hopefully it will get a bit more attention.

After lots of trials, including complete deletion and reinstallation of the package, the pattern is:

Pre-Dec 25th

- BATC worked splendidly in VR, even after introducing Live Air Traffic, in both the Pimax Crystal Light and the Quest 3 

 

Post-Dec 25th

- in the Pimax Crystal Light, there is now a major lag in the mic button registering, and total lag (ie locked up) for any response to a request.  If I click to 2D, still using the headset mic and headphones there is an instant resumption of the normal two-way BATC dialogue.  As soon as I click back to VR, BATC locks up again

 

- in the Quest 3.   BATC sort of still works, but is very laggy and makes the sim very laggy too.  However, all attempts so far, even when getting as far as final approach, have resulted in BATC going fatal crash before end of flight.

 

I run BATC as administrator, have deleted and reinstalled BATC as administrator, I have tried the alternative BATC Core Engines (DirectX11 and OpenGL)  Same result in all cases.

 

Anyone else, like @Zcott , got it running OK since Dec 25th?

Anyone else having issues like above since Dec 25th?

 

It's running here flawlessly with the G2.

Edited January 2, 20251 yr by roland_lfor

Running fine here, Pico4

There are more folks reporting the exact same issue on the BATC discord channel but, from @roland_lfor , @Bond & @Zcott 's responses, clearly not universal...

Could it be regional?  I'm UK, running on either the West Europe or North Europe servers (depending which is lowest lag)  Yourselves?

Maybe something specific to the Crystal Light layer?

I'm on the same servers.

4 hours ago, roland_lfor said:

Maybe something specific to the Crystal Light layer?

I'm on the same servers.

Hmmm...that's a thought.  It is interesting that the Quest 3 will run it, even though it was juddery.  I have tried the Crystal Light with both Pimax OpenXR and PimaxXR and it made no difference - I'll experiment with one or two of the other options and settings.

The odd thing is that it was running as sweet as a nut immediately before Christmas, even with Live Traffic at quite a high setting.  But it's worth me trying everything and anything.

Did you try to run FS in windowed and full screen? It could be a focus issue

37 minutes ago, roland_lfor said:

Did you try to run FS in windowed and full screen? It could be a focus issue

I've always used windows mode for MSFS2020, but I'll try full screen.  I'll also boot up the CPU/GPU performance tools to see if it's simply gone past its limit.

I had this issue from day one.  Turning HAGS off seemed to fixed it for me.  Worth giving that a try.  Although I've turned it back on now and it still works.  Could also t be something in your NVIDIA settings?