|
|
Post by legendli on Jul 7, 2018 21:31:15 GMT -5
|
|
|
|
Post by peter on Jul 8, 2018 4:21:54 GMT -5
Hi Legendli,
MSD violations are explained in appendix 7 of the user guide. Normally, you wouldn't get a penalty during arrival, but it could happen over mountainous terrain where the MSD is higher. If you send us your log file, we can see where you got the penalty.
Best,
Peter
|
|
|
|
Post by Travis on Jul 8, 2018 18:35:28 GMT -5
Hi Legendli,
I can only restate what Peter wrote. We need your FCDU/FSCaptain logs for all of your flights to see if we can find where the MSD violations occurred. -----
MSD currently does not account for any scheduled departure / arrival / approach procedure. (That may change in FSCaptain 2, with our new API. Third Party ATC programs could have us suspend checks if they say they are 'in charge.')
Currently for flights into and out of VHHH, you need to be above 1400ft AGL outside of a 5nm radius of the ARP.
If you dip beneath this level, you will begin to accumulate "MSD Violation Points". Less will accumulate at night, since it's dark then.
Currently for flights into and out of ZPPP, you need to be above 2400ft AGL outside of a 9nm radius of the ARP. ZPPP is in a "mountainous area" so the guidance here is greater/larger.
All details are in the User Guide as Peter noted.
We conducted hundreds of flights in and out of various areas in our tweaking of MSD values, but we did not consider ZPPP nor many mainland Chinese airports in our tests.
For the next point version of FSCaptain, I will add a value to the 'extensions' configuration file to allow anyone to hard-code an MSD value for individual airports.
You cannot remove the penalties (the 20 point penalty is for the MSD violation, and the 5 point penalty is for 'frightening PAX') without appealing them.
Best,
|
|
|
|
Post by legendli on Jul 8, 2018 18:53:57 GMT -5
Thanks Peter and Travis, During the troubleshooting, I lost the track of those 2 flights from VHHH to ZPPP, I will fly again once I have time in most likely next weekend .
And I'm pretty sure the issue occured in final(ZPPP), I heard my F/O said a lot of words.... didn't catch that as always! LOL
BTW, during the trouble shooting I found MakeRwy didn't catch add-on.cfg for my P3D V4, does Add-On Organizer is required to generate a file called MakeRwys_scenery.cfg for MakeRwy?
(https://forum.simflight.com/topic/83459-important-makerunways-and-new-add-ons-structure/)
Couldn't wait for V2!!!!!!!!!!!!!!
Thanks again for you guys!
|
|
|
|
Post by ajurt37 on Jul 17, 2018 10:32:31 GMT -5
Hi legendli,
I flew into ZPPP a few month ago and didn't have a problem with MSD. I also use Radar Contact 4 but make sure I can override altitudes ATC on mountainous terrain. When in doubt I do pop up FSC for a second to make sure I'm not accumulating MSD points. One difference on my flight was that the approach was for runway 22.
Andre
|
|
|
|
Post by legendli on Jul 19, 2018 21:06:03 GMT -5
Hi legendli, I flew into ZPPP a few month ago and didn't have a problem with MSD. I also use Radar Contact 4 but make sure I can override altitudes ATC on mountainous terrain. When in doubt I do pop up FSC for a second to make sure I'm not accumulating MSD points. One difference on my flight was that the approach was for runway 22. Andre Hi Andre, Thanks for the reply, my problem is kind of complex and I think I should put it here if anyone need. First of all, I really hate any add-on scenery install themselves into my P3D directory(not include FSCaptain  ), so I managed to move all my add-ons outside of my p3d main folder and after P3D V4, I switch to add-on.cfg instead of scenery.cfg. then, this is what happens....... ZPPP moved to a new location few years ago, someone created a free scenery of new ZPPP and replace the stock old ZPPP with a fake ICAO code ZPPX, I suppose to replace/overwrite the stock bgl file with the new one, but again I hate change anything from original in p3d folder, so I just put the ZPPX bgl file outside and load it above the default one, normally it works, but this time, the old,default ZPPP was changed to ZPPX, so this means I have ZPPP and ZPPX at exactly the same place. The worst is at that moment I don't understand how makerunway catch the add-on.cfg coming with P3DV4(Lorby-SI AddonOrganizer needed!!), so actually fscaptain didn't know my new freeware scenery of ZPPP at all, this means both ZPPP and ZPPX at same location(the old one). But in my flight, I landed in the new ZPPP. any warning or penalty will not surprise me after I knew this. |
|
|
|
Post by ajurt37 on Jul 20, 2018 1:17:08 GMT -5
Legendli,
Ah I see. I created the new ZPPP myself. When I did that I also located the old ZPPP and renamed the original BGL file to BGL_ORIG. That did the trick as there is quite a bit of altitude difference between the new and old airport.
Andre
|
|
|
|
Post by legendli on Jul 20, 2018 1:56:46 GMT -5
Legendli, Ah I see. I created the new ZPPP myself. When I did that I also located the old ZPPP and renamed the original BGL file to BGL_ORIG. That did the trick as there is quite a bit of altitude difference between the new and old airport. Andre I did created some airports myself, not a easy job , and the freeware is pretty good let me know if you want it.  |
|
|
|
Post by Travis on Jul 21, 2018 13:05:32 GMT -5
I believe I have that freeware, and this will be one of my first tests once my system is 100% again. I don't recall reading that the airport moved, but I'm sure I'll run into that soon enough.  Best, |
|
|
|
Post by ajurt37 on Jul 22, 2018 1:09:03 GMT -5
Travis,
This from the wiki entry for ZPPP:
"The new airport has two runways (versus the single runway at Wujiaba), and handled 37,523,345 passengers in 2015, making it one of the 50 busiest airports in the world by passenger traffic, the first time it earned this distinction. In 2020, it is expected to handle 43 million passengers."
The old airport was right in the city of Kunming. I believe the new airport is about 210m/689ft higher than the old one.
Andre
|
|
