Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by radeon29

  1. strange, the angle papi and the angle glide path in afkad are correct and it is exactly 3.2 degrees.
  2. if these two ILS have the same frequency(108.75 MHz) then the default will be used(this priority is set by the sim engine ) 99% this is your problem...
  3. these are really great updates, but they don't update third party scenary;( look at the sim map, maybe you will have two ils beams for one runway, check it first.
  4. I have the newest version and I have duplicate default buildings... I am really into scene-building(mostly for myself) and first of all checked exclude for default building in this scenario( in forder: Welcome to Kolyma V5\Scenery) and as expected did not find any... Can anyone check this out?
  5. this FIX has been available here for a long time:
  6. + My log + event error ASUpdater_App_Log.txt Event.txt
  7. MSFS not installed... ASUpdater_1600_Test_2.zip671.73 kB · 2 downloads didn't help me;(
  8. probably talk about it, I'll just leave a direct link here:
  9. I sent the link to you in private messages
  10. for runway 27 papi angle 3 is incorrect, should be 3.4. and also the ILS course 89/269 on the sim map, should be 87/268 (this is a problem almost in all aeroports from various authors). and now I have fixed it for everyone. ENVA.rar
  11. this button is pressed only once , after start checklist: flight controls( and after test we return button back) and no more pressing is required. and if we press it, then we completely lose control of the nose gear, which is unacceptable during takeoff. during runway acceleration, we must have nosewheel range up to +/- 6 degrees turn, and not as with an active tiller: nose wheel range up to +/- 75 degrees turn.
  12. this was assigned by default, this is convenient when we do not have a separate axis for the . but this creates some problems when runway acceleration, tiller continues to work together with rudder... it is useful to have the function of disconnecting the tiller from the rudder axis(twist axis) before runway acceleration. p/s and sorry, I created this topic in the wrong topic, I have a 64 bit bus, if possible move this to the correct section.
  13. how to disable the relationship between the twist axis and tiller when accelerating in runway?
  14. I made this fix for you, before installing the fix, be sure to set the configurator settings as in the screenshot: after installing the fix, you can set the configurator settings to your liking. LSGG.rar
  15. until we install it, SODE in LSGG will not work correctly ... hopefully in the future it (legacy SimConnect.DLL) won't be required. we always have a working CTRL-J alternative anyway.
  16. light must be here somewhere: --- Also, for P5, no NDB RСA is required, so in the stock data it already exists and has more correct coordinates. And correct airport name just: Reggio Calabria and not Aeroporto Tito Minniti Di Reggio Calabria.
  17. I noticed that when updating scenes, your tool checks the date of the files and if any have been changed by a newer date(I often make changes to AFCAD for myself) then it does not change them, but reports that the update is successful and it will not be possible to update again and you have to do a complete reinstallation of the scene...😟 it seems to me it was logical to force update all files if the name matches🤗 Any ideas, suggestions?
  18. ok, nevertheless, if you create a additional mini-mesh area for only such a problem area, then you can solve this problem.
  19. seems to be available v2.0.0.0 for P5 now: https://www.aerosoft.com/en/flight-simulation/prepar3d-v4/sceneries/2777/chania-ioannis-daskalogiannis-airport
  20. yes, there is a tag there(below under the spoiler I posted more .xml code). yes, but they are not in a hurry with this, and I myself am interested in finding a solution, thanks for helping. it is interesting, it looks like it really is so but not in all cases, a riddle... I changed only: LTAI_SVET to LTAI_Svet2 and now there are no warning now: --- but why then no warning for LTAI_SVET, because the naming(letter size) is different(.xml=LTAI_SVET, SimObjects=model.LTAI_Svet)?:
  21. I also thought about it, I specifically conducted this tests and it turned out that it does not matter. you made me think again and oops, it turned out that on the contrary there was an excess tag, because it was already higher then it is not needed again: or did i do it wrong? p/s yes, I did it wrong, this is another SIM object and I should not have deleted the closing tag: ERROR SODE.XML : Failed to load file 'C:\ProgramData\12bPilot\SODE\xml\LTAI.xml
  • Create New...