|
|
Post by niksan29 on Aug 30, 2019 8:51:09 GMT
What needs to be done to make the button active?  |
|
|
|
Post by Herve Sors on Aug 30, 2019 10:21:29 GMT
This button is available only when data are compatible with published current AIRAC data
In this particular case, there is no Rwy 13 at UMMS but 2 Rwy 13R and 13L.
IVX ILS is servicing runway 13R.
Details are available on the AIRAC ILS data menu you could have a look at
I don't know exactly how Rwy 13 appears in your project but in case you're working on a 3rd party scenery or default FSX/P3D data that didn't renumbered available runways, the first thing you will have to do is to change Rwy 13 id to Rwy 13R. This is what I already did in the updates I propose. The other runway (13L) doesn't exist in default scenery
Hervé
|
|
|
|
Post by niksan29 on Aug 30, 2019 19:09:53 GMT
Thanks, I figured that out.
I still have a question, where to get the information at what distance from TH there are PAPI lights? On the charts Jepessen did not find this information...
|
|
|
|
Post by Herve Sors on Aug 30, 2019 21:14:53 GMT
Some AIP provide this information (UK, USA in the past) but most dont. In such a case, your only option is to measure it either from published airport diagrams or more easily from satellite views (Google Earth)
|
|
|
|
Post by niksan29 on Aug 31, 2019 8:18:13 GMT
from published airport diagrams I have the latest diagrams , but I don’t see where the information about the distance of PAPI lights from the TH. I see only the angle of the glide path and which system of lights is used PAPI L+R and ALS. Or did you mean other graphs? Сan take a screenshot?   And if the scenary does not initially have ILS, I can’t add it using your utility?  |
|
|
|
Post by Herve Sors on Aug 31, 2019 10:09:42 GMT
Jeppesen airport charts do not display Papi positions. For that you will have to retrieve airport diagrams directly from AIP providers (when available online and at the condition they display papi positions) Russia is here www.caiga.ru/common/?lang=enbut unfortunately UHSM is not included Then the only (and preferred) solution is Google Earth  For creating ILS, you first have to provide airport Id, Rwy, but also ILS Id (IMO here) so as the new button is active |
|
|
|
Post by niksan29 on Aug 31, 2019 13:47:57 GMT
I understood it! I am grateful for your answers, I want to understand further. I noted the magnetic variation right? I’m in other circles of marks which information to enter, where to get the right one?  |
|
|
|
Post by Herve Sors on Aug 31, 2019 15:49:22 GMT
I will suggest you ALWAYS check the "Align LOC" checkbox if you know it is not an offset ILS (the case here).
Also take care to SCO objects that sometimes can be placed outside airport boundaries (especially LOC and TR). May be you will have to uncheck those or use the "Do not create.." check box). To be verified visually or on an airport editor after the ILS has been created.
Preferably use the magnetic variation value at which the ILS was calibrated. This value is usually indicated on most AIP ILS approach charts (but not on Jeppesen..). Otherwise use the airport magvar (as indicated on Jeppesen airport diagram, here -9). ILS Magvar is only used for getting a correct display on map view. If ILS is aligned, you can check it is correctly set by calculating
Sim RwyTrueCourse - MV and compare it to published ILS magnetic course (014° here)
Sim RwyTrueCourse can be retrieved from the "Display Runway Data" menu or more simply directly from the ILS creation window if the "Align LOC" has been checked
It should be ok here (5.29 - (-9) =14.3)
27 NM is the standard range in FSX/P3D but you can perfectly use a lower value if you have some indication it is different
Beam width can be autocalculated using the "auto" button. Standard range is 3.00 to 6.00 so any value below 3 should be set to 3 and any value above 6 to 6
|
|
|
|
Post by niksan29 on Aug 31, 2019 19:27:03 GMT
I will suggest you ALWAYS check the "Align LOC" checkbox if you know it is not an offset ILS (the case here). Also take care to SCO objects that sometimes can be placed outside airport boundaries (especially LOC and TR). May be you will have to uncheck those or use the "Do not create.." check box). To be verified visually or on an airport editor after the ILS has been created. It's really complicated))) May I have more details? Сan I see this in the screenshot from you? And this parameter is also of interest, it is also not in Jeppesen? Only verified visually in google map? I think it will not be visible on Google maps, especially the position of the loс transmiser is how many feet from the antenna and to the left or right;( What am I doing wrong, why is course 356?  |
|
|
|
Post by Herve Sors on Aug 31, 2019 22:14:36 GMT
Not complicated at all after a not so long learning curve
Align LOC will ensure localizer course is aligned with rwy course in the simulator (Sim rwy course may differ more or less from real one). Quite simple to understand
That's all you have to do in addition to the parameters I explained
I don't know where this 356 comes from. Magnetic and Rwy headings are 014 and it is correct
If you are still in trouble, feel free to send me your UHSM bgl file and I will do it for you ;-) and show you the final screen shot (AIE data+visual result on ADE or FSX planner)
Edit: I found why you have 356. You set you ILS magnetic variation to 9 that is 9E not 9W..Just edit the ILS you created and change it to -9!!
|
|
|
|
Post by niksan29 on Sept 1, 2019 16:59:35 GMT
Edit: I found why you have 356. You set you ILS magnetic variation to 9 that is 9E not 9W..Just edit the ILS you created and change it to -9!! Exactly! I'm just learning, thanks for noticing this  I still have questions, I will be glad if you answer: 1) if we want to have an exact location SCO objects , where can we find this data? Airport diagrams directly from AIP providers? And if you have time for this,can give a screenshot of each of these objects that you created in the landscape by default, where by default there were none at all? 2)Where can we find this data? Also in airport diagrams directly from AIP providers?  |
|
|
|
Post by Herve Sors on Sept 2, 2019 6:56:19 GMT
Hi Exact (true) location of SCO objects is available for localizer and glide slope antenna from AIP as well as AIRAC data I provide since they are precisely located at the position of loc and GS as defined. There is no data regarding the position of transmitter. May be you can locate it from time to time from Google Earth pictures. In default simulator sceneries, it is usually located at approximately 300 ft on the right or left of the loc antenna. AIE make all these calculations automatically but usually do not locate loc/gs and their associated SCO objects at their true positions for reasons that are explained here in (15) aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updatesIncluded (displayed) SCO objects are those defined in default sceneries. I think there is a list in the SDK, otherwise you may have a look here lc0277.gratisim.fr/sceneobjects/Runway lighting system is available from AIP (section 2.14) and also Jeppesen as well as LIDO airport diagrams. However stobes number (when there are some) are usually not indicated. Use at your conveniance (and do not expect an absolutely fully realistic picture in the sim anyway since many current systems are not implemented in the simulator) Also, the best way is sometimes to look at the effects of changes you perform directly in the simulator using AIE. It is very easy although you will have to reload the scenery. You may also look at them using some editors that can directly show BGL content (ADE or FSX planner) So as not to overload the forum with more details regarding your personal project, feel free to email me directly if you have any further question. I will be glad to answer them if I can. Hervé |
|
