This gauge was designed specifically for Mike Hill's KingAir B200. It will not work for any other aircraft. Mike's plane has medical special effects which this gauge activates in a sequence based on a set of logical aircraft parameters for picking up or dropping of a medical patient. It was designed so no keyboard operation is needed.
Mike Hill made the plane.. I just made this little gauge.
PERSONAL AND NON-COMMERCIAL USE LIMITATION:
Unless otherwise specified in writing, the software provided herein is for your personal and non-commercial use. You may not modify, copy, distribute, transmit, display, perform, reproduce, publish, license, to create derivative works from in order to transfer and sell any information, software, products or services obtained from the use or review of this software package.
NO UNAUTHORIZED DUPLICATION, MODIFICATION OR REPACKAGING IS PERMITTED WITHOUT WRITTEN CONSENT AND/OR THE WRITTEN CONSENT OF THE AUTHOR(S) WHOS WORK IS INCLUDED AND DEFINED HEREIN AND HERETO. AS FREEWARE THIS GAUGE/EFFECT OR ANY OF THE INDIVIDUAL CONTENTS OF THE FILE(S) CANNOT BE REPRODUCED, IN PART OR WHOLE, FOR ANOTHER FREEWARE PACKAGE OR USED IN ANY PACKAGE THAT REQUIRES, SUGGESTS OR PERPETUATES A PURCHASE OR SALE OR ANY FORM OF COMPENSATION OR TRADE.
DISTRIBUTION
Only the websites and/or companies I have given expressed written consent to distribute this effects package are authorized to distribute it as FREEWARE. An authorized distributor falls under the same distribution guidelines as defined above. The end user is authorized to use this package strictly for personal use in conjunction with MS Flight Simulators. Proper acquisition of expressed written consent is required before reusing this effect, in part, in whole or in any other fashion in order to avoid legal issues from unauthorized reproduction and distribution.
DISCLAIMER:
All Microsoft products and the effects code used in the custom designed effects files contained herein are the property of Microsoft Corporation through the terms of the Flight Simulator End User License Agreement and are protected by registered trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries. No intent to defraud or illegally use the Microsoft trademark, its software, code, name or secure any income or compensation from the production of this effects package is expressed or implied with the creation of this effects package and supporting files. Any other company names, names of authors or their work displayed in this package are for reference only. Unless otherwise specified, no connection to them or their products is expressed or implied. The author of this software or the site it was downloaded from is not responsible for any damage that may result from its installation or use.
Any feedback, comments, suggestions or support issues should be directed to:
Nick Needham
klondikekit@yahoo.com
I sincerely hope the flight simulator community enjoys this awesome effect. Sincere thanks from me go out to everyone who has donated their valuable time to create flight simulator software for the community.
*************************** KNOWN ISSUES *******************************
Nothing serious but please read.
The only issue I know of is when the main cargo door opens or closes during engine 1 shut down/restart the sim may briefly loose the ability to zoom. No other view commands or any other problems have been noted when this happens. To correct the zoom issue, simply toggle or cycle the view mode.
I will also say here that if the panel that this gauge is used with contains gauges that are not calibrated or are completely different from the gauges I designed my XML gauge to monitor it could cause the effects/gauge to not function as designed and programmed. I really do not see this as a huge possibility however given the large amount of panels floating around out there which are not designed by experts, anything is possible.
This gauge monitors the RPM of prop1 and prop2. It also monitors the aircraft's flight mode and if it is not on the ground and the parking brake. I designed this gauge with a logical set of variables based on the plane being involved in a medical transport operation. It would stand to reason that a patient would not be loaded or unloaded while the engine or prop on the cargo side f the aircraft is active and blowing dust around so therefore I based the effects on the state of prop1 and how much thrust it is pushing.
First,... for the effects to even appear.. the aircraft must be completely on the ground and the parking brake set ( Ctrl + . ) Engine or prop2 MUST remain above 1200 RPM at all times or the gauge will consider the plane is being taken out of service and parked. I had to set up some type of variable so the aircraft did not display the effects every time the engines were cut or feathered equally and therefore I made engine 2 the deciding factor in that. It stands to reason if an aircraft is called in for emergency medical transport that it would land and remain in a partial running state so to take off as quickly as possible. Same with arrival at a medical facility.. patient is dropped off and the aircraft leaves so the aircraft remains in a state of flight readiness.
Second,... to start the first effect prop1 must be under 900 rpm in order for the patient cargo door to open. This can be accomplished by feathering prop1 all the way back. (not throttle,.. feather) It does not require this step be done however if you would like to open the cargo door without the patient gurney or ambulance showing up, this step is how it is done.
Third,... to make the patient gurney appear, simply cut engine 1 completely off. Do NOT touch engine 2 or drop it below 1200 RPM or as I said the gauge will consider the aircraft is being parked and taken out of service and the sequence of effect will reverse. Once the RPM of prop1 drops below 25, the patient gurney will unlock itself and proceed to move out of the aircraft by the onboard lift system. Once the gurney is greater than 60% out of the aircraft the medical ambulance will appear.
Forth,... to reverse everything you have a choice.. shut engine 2 down -OR- restart engine 1 (Ctrl + E). The effects will operate in the opposite sequence. First the gurney will start to be retracted, and then the ambulance will leave. Once the gurney is inside the aircraft the cargo door will close and you are ready for parking or takeoff.
Unzipping this downloaded KingairMedControl.zip -or- KMC.zip to a location of your choice will produce the following files inside a KingairMedControl folder:
a. KingMedCtrl_FS2004.exe = For automatic FS9 (2004) Installs
b. KingMedCtrl_FS2002.exe = For automatic FS FS2002 Installs
c. screenshot.jpg or screenshot.gif = Introduction Image
d. FILE_ID.DIZ = A synopsis of the effect
e. README_FIRST.txt = This instruction file and tutorial
AUTOMATIC .xml GAUGE INSTALLATION:
(If you prefer manual installation, not recommended for inexperienced users, it is described below this step)
The following files will install the needed effects files and gauges to their proper location.
For ease of installation I the provided two automatic installation files in this package:
a. Simply double click the .exe file for your version of Flight Simulator and a WinZip box will appear which is preset to install the needed files to the proper Flight Simulator directories as shown below:
For FS9 (FS2004) Users:
C:\Program Files\Microsoft Games\Flight Simulator 9
For FS2002 users:
C:\Program Files\Microsoft Games\FS2002
b. When the Winzip window appears click "unzip" and allow the contents to extract directly into the directories. If your version of Flight Simulator is located other than where I have indicated above you MUST browse the Winzip extractor manually to the correct location.
c. Skip down to STEP 2 located below the MANUAL GAUGE FILE INSTALLATION heading.
MANUAL GAUGE FILE INSTALLATION ONLY:
(Not recommended for inexperienced users)
a. Choose the proper .exe file for your version of flight simulator and double click it. MANUALLY browse and extract it to a location other than your main FS directory. There will be 1 main directory extracted and 1 sub directory:
Gauges\nn-gauges
b. Open the \Gauges directory and inside you will find a folder named: nn-gauges. Copy the ENTIRE nn-gauges folder into the \Gauge folder of your main Flight Simulator directory. This should be:
For FS9 (FS2004) Users:
C:\Program Files\Microsoft Games\Flight Simulator 9\Gauges
For FS2002 users:
C:\Program Files\Microsoft Games\FS2002\Gauges
If your version of Flight Simulator is located other than where I have indicated above you MUST browse manually to the correct location.
WARNING: DO NOT COPY/PASTE THE ACTUAL GAUGE FILES LOCATED INSIDE THE nn-gauges FOLDER INTO THE FLIGHT SIMULATOR GAUGE FOLDER. COPY THE ENTIRE FOLDER nn -gauges AND PASTE IT INSIDE THE FLIGHT SIMULATOR GAUGE FOLDER JUST THE WAY IT IS.
*****************************************************************************************************************************************
IMPORTANT: IF YOU HAVE ALREADY INSTALLED *** Nick's Prop Dust *** TO YOUR RFDS KINGAIR B200:
*****************************************************************************************************************************************
Simply add the following gauge code line to your already edited RFDS_Kingair_B200 panel.cfg file under the [VCockpitXX] section which you created when installing my program Nicks Prop Dust:
Friendly Reminder:
REMEMBER TO ALWAYS BACKUP ANY CONFIGURATION FILES THAT YOU EDIT AS YOU GO ALONG PRIOR TO MAKING CHANGES. The easiest way to do this is simply right click the panel.cfg file before editing and select copy, and then paste it in the same directory. This will create copies of your original configuration file named:
Copy of panel.cfg
...ready to be restored if needed.
Since there is no way for me to know which panel everyone is using for their RFDS KingAir B200 installation, the following instructions are designed to be generic so any panel may be edited properly.
1. Inside the \Aircraft\RFDS_Kingair_B200 folder located in your main FS installation directory there is a folder named: Panel. Open the Panel folder, then open the panel.cfg file located inside that directory in notepad. You should now have this tutorial open and the panel.cfg file for the RFDS_Kingair_B200 installed on your system.
This entire code section must be properly placed in the panel.cfg file for the RFDS_Kingair_B200. It must be typed or copy/pasted from the above example exactly as it is displayed. Improper location, typo errors of the code lines or gauge file name, or any numbering or syntax errors in that section will render the gauge totally useless and cause the effects to display constantly on the screen with no control.
For the benefit of those who have never edited a panel.cfg file before, below there is a shortened example of my RFDS_Kingair_B200 panel.cfg file which will demonstrate the following instructions:
3. In the panel.cfg file, Scroll down to almost the end of the file and look for the last:
[VCockpitXX]
... heading entry. The XX in the name above is the heading number. There will be a list of supporting code with a gauge list below the heading. At the very end of the gauge list of the last [VCockpitXX] section, start the new heading. Copy/paste the entire code section provided above into the panel.cfg file. Review the example below to clarify the instructions.
NOTE:
In cases where there are NO virtual cockpit entries in the panel.cfg file, simply add the entire section at the very end of the last [WindowXX] -OR- FIXED WINDOW section.
Follow the notes: <-------------*** instructions*** as shown below in this sample panel.cfg file:
My RFDS_Kingair_B200 panel.cfg file:
===================================
// This Panel.cfg file created by FS Panel Studio - http://www.fspanelstudio.com
// Built Saturday, November 01, 2003 at 15:23 FSPS Build:8294
[Window Titles]
Window00=Main Panel <--------*** This list will show you how many sections there are before the [VCockpitXX] sections start ***
Window01=Radio Stack
Window02=GPS
Window03=Throttle Quadrant
Window04=Caution Annunciator
Window05=Warning Annunciator
Window06=Compass
Window07=KLN90B
Fixed Window30=Forward Right
Fixed Window31=Right
Fixed Window32=Rear Right
Fixed Window33=Rear
Fixed Window34=Rear Left
Fixed Window35=Left
Fixed Window36=Forward Left
Fixed Window37=Forward Up *** Scroll down toward the end of the file ***
[VIEWS]
VIEW_FORWARD_DIR=1.0, 0.0, 0.0
VIEW_FORWARD_RIGHT_WINDOWS=30
VIEW_RIGHT_WINDOWS=31
VIEW_REARXXXXXXXXXXXXXXXXXXXXX
*** NOTE: I EDITED OUT 99% OF THIS FILE FOR THE TUTORIAL ***
[Vcockpit03] <-------------------------------*** Locate the LAST original VCockpit entry ****
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$Kingair_3
[VCockpit04] <----*** Edit in the entire new code section and MAKE SURE it is properly numbered in the list based the one above*
size_mm=512, 512
pixel_size=512,512
texture=$h_cluster
background_color=0,0,0
visible=0
gauge00=nn-gauges!RFDSKingAirMedControl.xml, 0,0
+++++++++++++++++++++++++++++++++END OF panel.cfg FILE EXAMPLE
Note the LAST original numbered VCockpit entry. Below that last section is where you want to edit in the new control gauge VCockpit code section. Dont forget to verify the new VCockpit section number is in the proper numerical sequence with the one above it. My section is numbered [VCockpit04] however if for some reason your panel.cfg is numbered differently make sure the new code line is in the correct numerical order with the list. Change the number if necessary. The numbering system is as follows:
[VCockpit01] <----NOTE: If there are NO original VCockpit entries, your new VCockpit section will be numbered 01
[VCockpit02]
[VCockpit03]
[VCockpit04]
[VCockpit05]
