ATIasHold version 1.8.3 - MAR/2022 ================================== Open ATIasHold when you sit on a Runway or On Air. You must select a Destination Airport and a Runway; then fly as you like. Read about the Filter Selection. ATIasHld.pdf file Never release the Yoke fast but always gentle. Flight Plan View Before you start open the [ APLF ]Panel and the [ FR ]Panel. Check Lights, Fuel, Frequencies Please read the separate and specific "Saitek Pro Joystick Defaults.txt" File. There is a precise description of all 3 ATIasHold Default Joystick settings x FSX, MSFS, X-Plane. The new ATIasHold "BackGround" View - Flight Plan View. Hide the Desktop. ------------------------------------------------------------------------- Open the big Radar. Flight Panel > R-click on the [R] button. or Radar > [ flp ]-Button > R-Click On the Flight Plan Bottom centre there is a circle. Click on it. - the BackGround view with 4 different colors. If you use 2 Monitors then you cover the whole Desktop screen behind the various ATIasHold views. (don't click on the background) The new ATIasHold Timer speed settings - Flight Plan View. ---------------------------------------------------------- On the bottom left corner there is a very small point [ . ]button. It is possible to change the Timer speed. Default = 200 ms. If you decrease this value, you increase the response rate. A value of 150 may be fine. A lower value influences too much the response of the Joystick and keyboard which reacts like a "double click". Conversely, a higher value might be useful for a slower PC. The New Runway TakeOff and Landing Panel View --------------------------------------------- Open this Panel using: - Radar [Runway]button or ShortCut (this panel has a [K]button for setting your ShortCut) - or a Joystick command. This Panel includes all the useful data for a flight even in the dark. New is the addition of the PFD Horizon display which includes the Bank and Pitch Value. Bank values ​​over 25° are highlighted in red. Pitch values over 15° are highlighted in red. This Panel is connected with any Flight Plan, Direct-Fly-To (Adf, Vor) and Free Flight. The New Radar display Flight Plan, Apt's, Vor, Adf, Intersections ----------------------------------------------------------------- How to use these procedures has been changed to: - On Ground - On Air - Flight Plan interruption/suspend - flyto Adf, Vor (sightseeing) return to Flight Plan. View at a distance of your Range setting. L-Click on Radar > use the Mouse-Wheel - All selections are accessible. - Adf, Vor, Intersections Click into the white circle. Selected Item is copied into the relative Field in Flight Plan for direct use. Intersection are listed with a separate ListBox (select a Item). Dont' forget the RANGE setting for a better view. - Apt's on Radar. - The Radar Button [vor/adf/int] is only opening the ADF + VOR. Direct Fly to Adf, Vor. <<<<< Any selection is changing the Flight Direction >>>>> Pls. read the ToopTips ADF + VOR data evidenced on Top ADF + VOR Frequencies copied directly into the relative Radio section. <<<<< Nota >>>>> On Ground Adf, Vor, Intersections Distance is related to the destination Runway ! Used for Flight Plan Rwy alignments. On Air Adf + Vor is related to your actual Airplane distance ! (free flight) Flight Plan interruption. ------------------------- When you interrupt a flight plan the plane is continuing and therefore when you return to the flight plan you have to consider whether the plane is in front of or behind the waypoint before the interruption. Then change the waypoint. (Flight Plan must be active 'red') Choose (click) select a Waypoint (Flight Plan or Radar) Item and then close and re-activate the flight plan. Joystick settings - Saitek Pro Flight Yoke System ------------------------------------------------- My test settings for the FSX, MSFS and X-Plane simulators. The "as is" program includes 3 ready-to-use Joystick *.ini files. You can change settings or create new files for each Simulator and each individual airplane. Don't forget the Joystick combination values like: Shift button + Button 4 or T4 ecc... The Default Joystick files include the AP Autopilot and the ALT Altitude commands using the buttons below the Yoke watch: [ Watch ] [ ] [ ALT ] [ HDG ] When ATIasHold reads wrong joystick return values ​​the error is not from ATIasHold. Simulators often are setting own values ​​and this can cause the problem. In this case it is sufficient to reinstall, for example: Flight_Yoke_System_x64_8_0_213_0.exe Please read the separate and specific "Saitek Pro Joystick Defaults.txt" File. There is a precise description of all 3 ATIasHold Default Joystick settings x FSX, MSFS, X-Plane. <<<<<<< General Q / A >>>>>>> ----------------------------- - RADAR: Don't forget to switch between Map + North oriented. - RADAR: On Top a "Alert" message is appearing if a airplane is within your flight zone. - Airport approach, instrument reading: Don't forget to exchange the NAV1 Frequency with the NAV2 Frequency. - Flight Plan View When you open the Flight Plan for the first time, wait a few seconds. The various data files are about to be loaded. - Flight Plan changes > When you change anything on the Flight Plan you must: save and reload the Flight Plan! - Flight Plan not starting immediately > Depending on Default or Add-ons. Free the AP-Heading > Set Heading on + off. - Flight Plan flying When the Flight Plan ends, the Flight Plan Listing closes and the Rwy-Heading and Rwy-alignment begins. The Label [Apt] color changes to 'Red'. A Landing procedure [V/S Rwy] must be started by the Pilot only. - Autopilot Many Defaults and Add-On Airplanes use an incorrectly coded Autopilot. Applies to all Simulators. The autopilot for each simulator includes the exact same functions and therefore they should work, receive and transmit, the same way. There are a lot of complaints in all the Forums. I paid $70.00 for a beautiful plane. On Air beauty succumbs to the lack of a proper autopilot. (not receiving or returning correct data) It is sufficient to test a autopilot set up correctly: MSFS - Textron Aviation Beechcraft King Air 350i (using FSUIPC7) X-Plain - King Air C90 (using XPUIPC) FSX - Beechcraft 58 G1000 (using FSUIPC) - Don't fly overspeed! Especially with X-Plane. The ALT-Hold of the autopilot may not maintain the set Altitude. - Automatic ATIasHold Runway Landing. [V/S Rwy] If you enter the Glide Path with an incorrect height ATIasHold corrects the error only partially if the ALT difference is too high. In any case it is always possible to correct the error manually with the Yoke. In FSX the trim is working perfectly too. When you engage the automatic [V/S Rwy] and the Autopilot is not reponding correctly to the ATIasHold command then >>> - Toggle the AP-ALT OFF + ON - Pitch down not responding as it should. (not depending on ATIasHold - ALT Lock) ATIasHold is doing it in automatic (Off/On) but not all Simulators are responding correctly. - Runway Identity: When you select a Rwy, maybe the Simulator is using a different Nr-Identity. Example: LOWS Rwy 34 in MSFS it is 33. ATIasHold Runways can be changed, added and created with 2 programs included: - AddAirports - RwyLength - Take Off and Landing View: big Radar [ Runway ] - Departure Rwy Length If your Rwy is not corrisponding to the Simulator Rwy-Identity select a Rwy with the same length. This is here the only important factor for a correct Runway graphic. Especially during the night. Use the track to the end safely. - Fuel procedure Now on Air again working at user request. R-click on Fuel. - Free flight and heading after Take Off. The autopilot may lock the 'Heading' function. In this case toggle Heading on / off. (free before take off) - The Stay-On-Top buttons [ T ] Use it, toggle, if other views or messages opens behind the Radar. - Radar > The automatic [ V/S Dist ]Button Make sure your PFD Horizon is over 10° and stabel. V/S dist - Control the ALT indication. (ascending or descending). Control your Apl asset. Distance: Use the big Radar [ 0..50000 ] feet selection on the right of the [Runway]-button. or for a correct Runway approach read the max Glide Path entry ALT Hight at 10 or 20nm before the Rwy. [GP Alt]-Button. The automatic Rwy-Approach or Glide Slope (Diamond) is always starting at 20nm before the Runway. With or without automatic active. It is suggested to start with a automatic Landing approach at 10nm distance. You have more time for a preciser alignment. Don't forget the "Blue Circle Range" selection. When the [V/S Dist] is active the Blue-Circle-Range is set in automatic. You can increase or decrease the Range. <<< Be careful >>> the Range setting, here, is changing the V/S value. This is meaning that you reach the desired ALT at a shorter distance! (depending on your engine power) - Engine Pressure indication > Main-Menu, Runway Take off and Landing Panel. If not starting > click on the [ A,N,I ] button below the PFD Instrument on the small Main-View. - The [ A,N,I ] Button > Adf, Vor, Ils The [N] selection (NAV2) > Read the DME distance. - [V/S Rwy] Aircraft AP not responding correctly x descent ? Try Close the AP-ALT Off and ON. - The Approach Radar > Flight Panel View > [ Rwy ]-Button on top. This is a absolute precise approach Radar with all Glide Path/Slope/Diamond details. This was the first ATIasHold Radar 10 years ago and is still up-to-date. - You open a View but you don't see it. The view is simply 'out of bound'. The << Lastloc >> File is damaged. This file contains the Video coordinates. Delete this File which will be created ex new. OR the Panel / View is behind another open View. - LastLoc Files - single Video View Coordinates LastLoc1 to LastLoc5 - LastLoc7 - LastLoc1.txt > ATIasHold Main-View - LastLoc2.txt > The Flight Panel View - LastLoc3.txt > The small Radar - LastLoc4.txt > The big Radar - LastLoc5.txt > The Runway Take Off/Landing View - LastLoc7.txt > The Flight Plan View - Flight Plans - SubDirectory Program-Path\FlightPlan FLPL example test: LJMB-32-EDDM-08L This is only a Test flight using all waypoint references. <<<<<< Use only an aircraft specified in the "Autopilot" items above. You understand the AP errors of other Planes. >>>>>>> Fly this route which is predistributed in order to bring us closer to what was said before. FLPL example test: LJMB-32-LOWG-35C / a short test flight 33nm - Your Monitor quality and brightness What you see and how you see it is only depending on your Monitors. I'm using 2 HP 27' (2021) Monitors with a fantastic brightness. That makes the difference. Pls. think like a Pilot and read all the Tooltips, [H]elps and ATIasHld.pdf file. Half of what is explained here would be superfluous. End.