Setup Guide Piper Arrow III ___________________________ Prepar3D v4+ installation: - If you already have an install of the Piper Arrow III by Rien Cornelissen remove it (always make a backup) - Extract the archive in a temporary folder. - Copy from the archive folder 'Piper Archer-III__RC' to your sims SimObjects\Airplanes folder. - Copy the effect files and 'texture' directory from the EFFECTS folder in folder 'Piper Archer-III__RC' into your sims 'Effects' folder. No need to overwrite files. - Copy all the content from the 'Gauges' folder into your sim's 'gauges' folder. Also here no need to overwrite files EXCEPT for 'CockpitSounds_2.ini.ini' if present in your CockpitSounds. Note that the new 'CockpitSounds_2.ini' file is backwards compatible with possible previous versions... Same counts for 'KeyEvent_Piper_Warrior_II_RC.xml' - DONE if you did an install for P3Dv4.5+. FSX and Prepar3D v3 installation: 1. Same as above but you do not need to copy file 'dsd_p3d_xml_sound_x64.dll' into your sim's gauges folder. 2. Copy the file in the 'Gauges_FSX' folder into your sim's gauges folder. No need to overwrite dsd_fsx_xml_sound.gau if you already have it. 3. Inside the 'Panel' folder of the aircraft rename file 'Panel.cfg' to 'Panel_x64.cfg' Inside the 'Panel' folder of the aircraft make copy of file 'panel__FSX.cfg' and rename the copy to 'Panel.cfg' 4. DONE. SOUNDS The sounds of this aircraft are aliased to the stock FSX Cessna 172SP. So you must have an install of that plane in Prepar3D or you must alias it to another similar Lycoming powered aircraft. Open in that case the Sound.cfg file in the Sound folder of the Archer III with a text editor like Notepad and edit and save the file. LIGHTS The outside model has a built in Landing light at the right wing tip. I did find that strange and in one POH of the Archer III I read there should be 2 lights, one on each wing tip. So I did add an extra light on the other tip as well, but that looks a little bit strange. Anyhow, if you want to change my mod in this respect edit the aircraft.cfg and find the [Lights] section. There you'll find: light.9 = 5, -0.289, -17.160, 0.928, fx_landing ;// Flanker256: ADDED light.10= 5, -0.289, 17.160, 0.928, fx_landing ;// Flanker256: ADDED //light.9 = 5, -2.289, 17.160, 0.928, fx_PA_3d_landing ;// Flanker256: ADDED //light.10= 5, -1.989, -17.160, 0.928, fx_PA_3d_landing ;// Flanker256: ADDED The fx_PA_3d_landing.fx files will have a more balanced look than the fx_landing.fx files So, it's up to you. Or remove all the 4 lines above and use the one landing light configuration as the original configuration. MINI PANEL If you like to fly with a MINI PANEL with F10 key than you have to edit the Panel.cfg file as follows: - Make a backup of your Panel.cfg first, optional but recommended. - Go to the [Window00] section - In that section remove the string ';//' before each gauge definition so it will look like: gauge00=P28A-R!ASI_A, 0,1,100,100 gauge01=Cessna!Turn_Indicator, 102,0,100,100 gauge02=MiniPanel!Attitude, 207,0,100,100 gauge03=P28A-R!DG, 312,0,100,100 gauge04=P28A-R!Altimeter, 417,0,100,100 gauge05=Cessna!Vertical_Speed, 531,0,100,100 - DONE