 |
Johku, can I get a screenshot of you established on the ILS, with the HUD showing GS, and with the rate of descent visible in the screenshot? Id like to establish whether the ILS is improperly angled, or if the documentation should be corrected. |
 |
Here are some pics with their descriptions. ------------ x2021-01-25_191219_loc.png: I have just started descending around -2.5 deg on FPM after crossing DME 16. According to the chart, ILS glideslope (GS) and localizer (LOC) should have been captured by this time. x2021-01-25_191048.png: Around DME 13, still no GS nor LOC. x2021-01-25_191130.png: Taken just before the ILS GS comes alive. x2021-01-25_191158_before_gs.png: ILS GS alive. x2021-01-25_191200_gs.png: Taken just before the ILS LOC comes alive. x2021-01-25_191218_before_loc.png: ILS LOC alive. |
|
|
My apologies, the descriptions of my previous note were wrong. These are the correct ones: ------------ x2021-01-25_191048.png: I have just started descending around -2.5 deg on FPM after crossing DME 16. According to the chart, ILS glideslope (GS) and localizer (LOC) should have been captured by this time. x2021-01-25_191130.png: Around DME 13, still no GS nor LOC. x2021-01-25_191158_before_gs.png: Taken just before the ILS LOC comes alive. x2021-01-25_191200_gs.png: ILS GS alive. x2021-01-25_191218_before_loc.png: Taken just before the ILS GS comes alive. x2021-01-25_191219_loc.png: ILS LOC alive. |
|
|
Sure looks like a bug to me. Good catch. |
|
|
Does Osan have differently defined ILS? In the attached sample image, I have already captured GS and LOC for Osan RWY 09L ILS with more than DME 16 to the airfield. |
 |
Yep. Probably an issue in Suwon. I have the same then you on Kunsan (about 18Nm) . No idea what it can be. |
|
|
I bet on a frequency conflict (108.50) between Suwon and Pyontaek and/or GImahe (all are sharing 108.50) I will give a try by setting another ILS freq. |
|
|
Pyeongtaek ils 108.75 instead of 108.50 to avoid frequency conflict with Suwon. Check fix in next BMS version (not 4.35 update). |
|
|
@Johku, is this fixed for you in 4.35 U1? I thought the fix was aimed at 4.36. If its still present in 4.35 U1, we can leave this one as Resolved, and close it once its fixed in the public version. If its fixed in 4.35 U1, we can go ahead and re-close. |
|
|
Yes, the issue persists still as of BMS 4.35 U1. I just thought this ticket could be closed as Dee-Jay commented the issue has been fixed in the upcoming major version. It's fine if you like to keep the issue in "resolved" state instead of "closed". |
|
|
We will leave it as resolved for now - when you test it in 4.36 and its fixed, then we can close it :) Part of that is to save someone else coming along and reporting the same bug, which was already fixed by the devs but there was no open issue describing the bug here. So if you search for your issue and you cant find it in the open issues, you can report it. Obviously, if we close this issue while the issue still exists in the public version, people wouldnt see that the issue is known, and has been fixed for a future release, which is what we want to achieve with this site :) Thanks again for reporting, and helping to make BMS better. |
|
|
This has been solved in BMS 4.36. Glideslope and localizer could be captured at the shown chart distance (BMS_4.36\Docs\03 KTO Charts\01 South Korea\Suwon\Suwon_ILS_33R.png). |
- Anonymous
