Solved Suwon ATC Issue
-
@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.