Solved Suwon ATC Issue
-
Current version
Stock KTO
No 3rd party modsI’ve been using Suwon as my home airbase for my current Rolling Fire campaign. I like the airbase, but I’ve had a couple of issues with vehicles on the runway, and tonight on the below mission, ATC was directing audibles to takeoff on 15R, but everybody was taking off on 33L, so I did to (we spawned at the 33L EOR, so I think it was a ATC screwup).
I was worried about what vector we would get when returning to the airbase. Sure enough, ATC was directing traffic to 15L, but everybody was landing on 33R. I’ve never run across this glitch before.
Oh, and on the above described mission, I just accomplished my personal best ever Air Interdiction mission. I was incredibly lucky to find 3 different battalions all bunched up at a crossroads. So I was really motivated to land correctly and not run into somebody, despite the ATC confusion.
-
our DB guys are looking into it also. Thanks everyone @Mav-jp
-
Current version
Stock KTO
No 3rd party modsOkay, the same ATC bug has happened two more times since my original post.
I’ve been using Suwon as my home airbase for my current Rolling Fire campaign for the past few weeks. T/O is almost always on 15R, landing on 15L, but about 5% of the time, everybody (me and the other monkey flights) spawns on the other side of the runways, and the monkeys all use 33L to take off, despite ATC incorrectly calling out 15R vectors.
Further, everybody lands on 33R despite ATC giving incorrect directives to 15L.
Three missions now, I’ve spawned on the 33L/R side of the airbase, and every single time, ATC calls T/O and landing vectors for 15L/R, and the monkeys all ignore the ATC, going and coming back.
Like I said the first time, I’ve never run across this glitch before, but then again I’ve never flown out of Suwon before until now.
Also, the single solitary military vehicle has become a permanent fixture on the left side of 15R, half way down. I think I saw homeless people living in it.
Seriously, though, it’s been about 10 days since my first post, and I hope that somebody can at least acknowledge this issue.
-
@SoBad Hmmm I think someone else has had some complaints; let me see if I can dig that up.
edit: https://forum.falcon-bms.com/topic/26867/suwon-runway-directions/4?_=1711350828063
-
-
@MaxWaldorf ground units on the airbase will be improved for u4, for sure (still some edge cases though). The inverted runway issue I did not check, more @Mav-jp realm.
-
Do we have a clear repro case for aircaft landing on opposite runway than ATC instructions ?
-
@Mav-jp said in Suwon ATC Issue:
Do we have a clear repro case for aircaft landing on opposite runway than ATC instructions ?
Landing AND taking off, Mav. But ONLY when the mission spawns on the 33L/R end of the Suwon airbase.
And it’s happened to me every time we spawn at 33L. However, the software only starts a Suwon-based mission at 33L about 5% of the time, and I have no idea how to control what end of the runway a Suwon-based mission starts.
And even if I could, how am I supposed to “repro” the situation for you? I’m telling you that it happens every single time a Suwon-based mission spawns on the 33L/R end of the runway, and it’s happened to other players as well according to forum reports.
My best answer to you is that the bugged scenario reproduces every single time we spawn on the 33L/R end of the Suwon runways.
-
@SoBad I’ve seen this a couple times too, but cannot offer the golden repro case so let it slide.
What are the weather conditions, specifically wind direction at the point you hit the cockpit?
Edit - repro submitted, let’s cross fingers
-
@Malc said in Suwon ATC Issue:
@SoBad I’ve seen this a couple times too, but cannot offer the golden repro case so let it slide.
What are the weather conditions, specifically wind direction at the point you hit the cockpit?
Edit - repro submitted, let’s cross fingers
I have the “T” shirt too but it was not repo and only ever got it in CAMP missions so I never submitted it.
Lets hope it gets sorted.
Ironman
-
in the data base, the runways have heading 152 / 332
in ATC file, the runways are decleared heading 144 / 324
thats why the code is failing as it does not find matching runways
it is IMPERATIVE to make the runway heading match between Database and ATC file
change the ATC file to 152 / 332 and you will see the bug will be gone
-
@Mav-jp said in Suwon ATC Issue:
in the data base, the runways have heading 152 / 332
in ATC file, the runways are decleared heading 144 / 324
thats why the code is failing as it does not find matching runways
it is IMPERATIVE to make the runway heading match between Database and ATC file
change the ATC file to 152 / 332 and you will see the bug will be gone :
MAV the magician !!! just makes things disappear
-
our DB guys are looking into it also. Thanks everyone @Mav-jp
-
-
-
Comparing the Suwon ATC file (Suwon.dat) to Osan which is also a dual runway airbase, it seems that it’s not only the runway headings that are off if I understand the ATC file structure.
The 4 sets of {Marking,Overhead Side} should be unique right ? For Suwon, there are two 33L in the ATC file (Marking=33, Overhead side = -1) and two 15R entries (Marking=15, Overhead side = +1). While for Osan there are no duplicates.
@tiag Maybe I am off about this, but better to ask, right ?
-
@Mav-jp said in Suwon ATC Issue:
in the data base, the runways have heading 152 / 332
in ATC file, the runways are decleared heading 144 / 324
thats why the code is failing as it does not find matching runways
it is IMPERATIVE to make the runway heading match between Database and ATC file
change the ATC file to 152 / 332 and you will see the bug will be gone
Mav, I think your callsign should be “Terminix” because you find and kill bugs dead. You have to be old enough to remember the old TV commercials to get it.
Thank you, along with @tiag and @digle and any others who helped with this.
I’ve edited/updated my Suwon.dat pending the release of U4. If I happen to spawn on 33L/R in a future mission in this campaign, I will report the outcome on this thread.
-
@jayb said in Suwon ATC Issue:
Comparing the Suwon ATC file (Suwon.dat) to Osan which is also a dual runway airbase, it seems that it’s not only the runway headings that are off if I understand the ATC file structure.
The 4 sets of {Marking,Overhead Side} should be unique right ? For Suwon, there are two 33L in the ATC file (Marking=33, Overhead side = -1) and two 15R entries (Marking=15, Overhead side = +1). While for Osan there are no duplicates.
@tiag Maybe I am off about this, but better to ask, right ?
No they don’t need to be unique
-
@jayb All good.
-
Super cool news:
Tonight, I fragged a 2-flight (AI@4-F16CM50 w/ ESCORT@4-F15C) in my ongoing Suwon-based campaign. I was using my edited Sowon.dat data file as explained by @Mav-jp .
Our package happened to spawn on the 33L/R end of the runway where ATC gave us correct queueing directives for takeoff, and correct approach vectors for landings, confirming Mav’s analysis and solution. Thank you Mav, and thanks again to @tiag & @digle for following up with corrected data for U4.
Follow-up: The next day, I fragged a similar mission that started (departure) on the 15L/R end of the runway. During the mission, the weather turned bad and prevailing winds changed. Upon returning to Suwon (approach), we were vectored to 33R. ATC was flawless.