UIWM

Good product, enjoying so far. Is there any way to set specific anticipation angle beyond which flyover logic will trigger (not fly by?) Even better if waypoint can be designated as fly-by or fly-over specifically, but I understand this is not Garmin's GTN functionality. Thanks.

Hi there, Takeoff obstacles is an important implication on performance capability. For years, flight sim community in general was V-speeds centric so to speak, will little attention paid to obstacles. Consequently, we have a lot of tools that determine other takeoff parameters but completely ignore assessment of takeoff flight path. So I would like to ask you how do you approach this problem on your routine flights what are the techniques you use, specifically how do you determine the appropriate obstacles (1) and how you assess your aircraft's performance in this regard (e.g. limiting takeoff weight) (2). Question includes both all engines operation and one engine out configuration, so a side question is how do you come up with engine-out escape route/EOSID (2-A). My question is for simulated commercial operations under IFR. Personally, when I used to use PMDG B737, TOPCAT did a job, but I did find it either too limiting or inaccurate in difficult cases. Also, obstacles database it uses (even if updated per airac) sometimes significantly differ from the data from airfields' AIP, requiring manual entry. Another issue is that is gives EOSIDs, yet these are generic EOSIDs without a note to which aircraft they apply, effectively rendering them useless. My question may seem trivial to people who mainly operate on plains, but consider this: suppose you are to depart from Sion, Switzerland, LSGS. One of the SIDs for runway 25 requires terrain-limited gradient of in excess of 13%. How would you determine whether your aircraft is capable of it? PS. This topic is for simulated environment, assuming that there is no access to real world RTOW tables, OPT software, etc. Thank you.

Finally I found workable solution, JS41 now follows Flight1 GTN 750 ! http://forum.simflight.com/topic/84449-custom-autopilot-and-gtn-750/?do=findComment&comment=510693

While trying to get my JS41 follow Flight1's GTN 750 without any luck, I noticed that with GTN set for heading hold steering mode (through config file), with JS41 in V/L VOR1 mode, if you keep pressing NAV button on autopilot panel continuously (several times per second), aircraft will follow the track from GTN !, albeit EHSI will not show CDI needle, etc, but it doesn't matter. The problem is that this NAV button is not default and pressing NAV1 button from default control assignments will not do the same trick. Has anyone got an idea how to somehow determine this custom NAV button and bind it for continuous engagement (through Fsuipc, etc.)? PS. What is also interesting that JS41 follows KLN-90B from this developer ( http://www.fsdeveloper.com/forum/threads/the-kln90b-for-fsx-prepar3d-in-beta.432845/ ), it has override function for heading hold. Aircraft follows KLN perfectly, so I guess GTN could do too. Thank you.

I found that given you don't restart 430/530 unit during your flightsim session, it almost certainly won't crash, BUT you have to assign "affinity mask" for garmin proccess (task manager/details) to the last core only (uncheck all other cores) at the beginning of each flight AND restart PC before each flight. This solution tends to work for me for 80% of the time. This adds so much hassle given that the 430/530 is typically used on GA aircraft, with several landings/etc, you naturally want to do several flights without closing flightsim. This is madness, sorry, but even real-world driving doesn't give you as much anger as when some bs sim garbage crashes constantly. Yet Reality-XP decided to abandon excising customers without resolving this bug and pursue X-Plane. No need to mention again lack of navdata support from navigraph/etc, expecting sim customers to use several years old navdata is simply disrespectful these days. I don't care how accurately you replicate all those features if the primary objective of gnss unit - safe navigation/sit awareness using actual and relevant navdata can not be achieved. Shame on you, Reality Xp. My win is 8.1 and FSX, in case anyone is having stable 430/530 on win 8.1, could you please post your RXPGNS.INI config as I'm convinced some settings may actually cause this problem (although I tried many combinations).

It seems my G1000 MFD has an issue with navigraph navdata - display doesn't show airport identifiers/navaids and I can't enter any waypoints in FPL / DIRECT TO page (see screenshot attached), also doesn't identify current airport upon startup. I tried using original navdata cycle provided and the latest one (I observed navdata index building without problems), also completely reinstalled Phenom 300. I also got Phenom 100, which works fine when it comes to G1000 functionality. Specs: FSX, win 8.1, Phenom 300 version 1.3 + navigraph extension pack. Navdata install path C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\CarenadoNavigraph\Navigraph\NavData Has anyone got a suggestion? Thanx