I flew the PMDG 737-700 from CYWG to KATL earlier tonight... Everything went fine until my approach into KATL...ATC left me flying east at FL230 away from the airport. About 50nm away, I tried requesting a different runway, and Approach control vectored me back towards the airport to a lower altitude. Then had to fight with ATC to get on the least-popular runway, which involved 2 missed approaches..Finally land in very poor framerates. Ground sends me to gate C1, which turns out to be already occupied by another 737 or an airbus. Stop close enough behind so I can try requesting a taxi to another gate, but Ground insists I go to C1.So, I try South GA parking. Timed perfectly so I didn't need to hold for takeoffs or landings, and.... my assigned parking spot in south GA parking is already occupied by a 727.Try requesting a gate again, and get sent to gate C2. Have to hold for a couple landings, and find that C2 is also already occupied.Try Northeast parking. End up nose-to-nose with another aircraft and have to taxi around him into the grass, then have to taxi around behind a 767 or 777 that pushed back but wasn't requesting taxi for some reason (until after I passed him). Get to northeast parking, and, you guessed it, my spot was already occupied.Figure, I'll try northwest parking, then try the gates again (and take the closest available one to whatever I get assigned to since I'm getting tired of taxiing around KATL), but FS decides to crash with an illegal operation as I'm turning onto taxiway Alpha..Anybody else get this bug?

It's a bug?

Well, I don't think it's normal behavior for ATC to assign gates and parking spots to aircraft when those spots already have an aircraft parked there.... And then crash with an illegal operation for no apparent reason....So, I would call ATC forgetting which gates/parking spots were vacant or not would be a bug to some extent, although rare since it's the first time I've seen it...

Hi. I just assume the worst when anything awkward turns up for the atc to have to deal with. I have tried to land at Juneau in default conditions, i.e. onto 26 and I have come to the conclusion after watching a.i. planes go missed approach(!!) as well that atc hasn't a clue and that was why I assumed it wasn't a bug. Instead of worrying about a few bridges going awol, Microsoft has a few issues and upgrades to make atc function properly.imho.

For the first time, I also had a strange ATC experience. Was doing a short (150 nm) IFR flight. After takeoff ATC vectored me towards intercept with the course then promptly forgot about it. I tried to turn towards the proper waypoint and ATC yelled at me to get back on my assigned heading. After taking me at least 40 nm off course I cancelled IFR. I've had many issues with ATC ignoring separation between myself and AI especially on final, but nothing like the above before. The only thing I can think of is that I had only one intermediate point in the flight plan and maybe that threw off the ATC rountines.

Hi, further to my other post, I was 1/2 to juneau on one trip when I thought I'd be crafty and change the wind direction to force atc to send me onto rwy 8. If only I'd known. I was vectored all round the houses and then directed into a hillside and that was the end of that journey!