SKEWR

Dume question from me. If I deviate from my SimBrief flight plan, does this mean BATC will look at where I am and populate based on that or is traffic only created around my reality bubble? (Or am I totally wrong on traffic injection technique?)

The program worked flawlessly on my end if someone wanted to know how it performed. I see from the screenshots that I need to update but I guess I won’t have a chance now… Thanks for the guenseli. I appreciated your work for the flight sim community.

I went from instant purchase to nothing. As said here before, the marketplace would have worked for most of us. If the claim is that it’s “it’s not going away “ then I’ll get used to default buildings and call it a day. Bad enough that we have several passwords to remember and then they are trying to impose a password or background application per scenery? No thank you.

Can’t wait to see it! Nice surprise.

This looks SO much better then the previous version. The new dark mode is especially appreciated. If I HAD to complain I do not like the stationary right pane on the forums, but that's not a huge deal for me. I know people don't like change, particularly regimented folks who are into structured flight, but try to give it a chance!

I'm looking forward to this scenery, but I'm not looking forward to yet another flight sim app and another password.

My test flight is KEWR to KIAD. Or KEWR to KBOS.

Second flight from EWR to YYZ. Excellent Clearance and ground ops. For whatever reason that was a backlog of planes trying to take off from DD's KEWR 22R. I was 7 for takeoff. Planes were landing as they were supposed to on 22L. Not sure what happened there, but I waited awhile like I would if this was a real situation and then I just taxied through and took off. Got chastised a bit and got the "Bad Pilot" info block in BATC but it was worth the chuckle. Enroute, BATC was again excellent. Descent, landing changed from 15L to 5. (That was pretty good as it was a nice flurry of activity to get setup properly for the change.). Cleared to descend via the LINGG3 STAR, no issues. Again, there was an aircraft behind me getting some interesting speed demands, but not a major issue. This time the leave fix XXXXX at XXX degrees worked fine. Good landing on 5, nice taxi instructions to the gate. Overall, very nice. As the snark is sometimes heavy in AVSIM land, let me explain. I'm posting these so people can read what an average BATC airline (IFR) user is experiencing to see if it's "not there yet" versus just harping on one or two things. (I'll VFR to the VFR experts)

Looks amazing. I’m always into a good city builder.

Ok my 2 cents. Came back to BATC after being away from it for a few months. situation: Test flight from DD KEWR to Flightbeam KIAD FSTL A380 Around midday, few clouds bright sunshine and windy. PARKE HYPER9 at FL220. Landing 1R Pros: At level 9 across the board, no performance issues. (Flying the freeware A380 in MSFS202) The program understood every word I said with my NJ/NY accent Plenty of traffic and plenty of chatter on frequencies. Cons: Early descent. Not a huge deal as Airbus logic kept the 1000FPM until the path was captured Landing: was prepped for the visual to 1R and ATC had me at a good altitude. Was given the instruction “Leaving TICON, turn right heading 320.” Then “report field in sight”. As I was executing the turn I could easily see I would need way more than 320 to get aligned. At this time I was about 6.5 miles away and if I was a real world pilot, I’d be making arrangements for another approach as I didn’t like what I was seeing. However as a sim pilot, I had to land! I finally saw the field then turned 055 as the best intercept course. Once “field in sight” ATC happily cleared me in while I dealt with the justifiable complaints of the A380S computers. The visual approach is what scares me as I know I’ll be in relatively close to the field and have to do some serious maneuvering and configuring in a short window. BATC was doing that before I took the break from it and apparently it’s still an issue. Both a pro and a con: BATC did not give me any speed restrictions but BA219 Heavy (behind me) was getting an earful. When the traffic first came on frequency it was given the instruction, “reduce speed to minimum approach speed “. Seems like a bug. Then subsequent speed restrictions seemed plausible. Pro? Speed restrictions issued by the program. Con? Maybe not instructions you’d expect to be issued to a heavy at 12000. All in all, I’d recommend BATC. Know what you’re getting into and know the other alternative program can be pricey.

Right now, I'm doing well with Lossless Frame gen, the newest DLSS 310.3.6? and preset M. I'm seeing a lot of people saying preset "B". Is that the new recommendation? I've been avoiding the Nvidia app, but with I'm not sure I'm going to see a demonstrably better depiction. Willing to learn however! (For reference i13900K, 4090, 32GB RAM, MSFS2024)

I'm glad they fixed the slowly spinning AI planes. It used to annoy me but I kept quiet about it.

Interview really sold me. Great job out of that team!

We don't have 78s (sadly)! I'll trust you on the massive dust bunnies! I was once in an EVA 74-4 and it looked pretty well kept for the time.

In the 767 and 777 flightdecks I see, I can't say they are grimy. The bodies are dirtier than you'd expect but nothing crazy like some people on this site want. The MD11s and A300s are usually worn but not dirty. When PanAm went out of business, those 727 flight decks looked incredibly used and dusty, but not a pig sty. Probably the most grimy, dirty cockpit I'd seen was on a 152 during flight training. If dirty cockpits are true (as I haven't seen them) then some of these folks making 200-400K flying and leaving dirty flightdecks really should be addressed IMO. There isn't much you can do with the exterior dirt. (Well fly through some rain clouds lol) With the 787 being a relatively young airliner, I wouldn't expect to see a really worn-out cockpit.