By XPJavelinWhat it Speedy Copilot ?
Speedy Copilot makes for you the steps normally done by the first officer and pilot monitoring, when you are pilot flying and captain of a Boeing 737. Speedy copilot is intended for the IXEG 737 (version 1.21 and above).
It was tested and works with X-plane 11.20 and IXEG 1.21 along Better Pushback and JAR GroundHandling.
It is not very realistic to do all the steps required in the procedures on your own. The Flight Crew Operating Manual makes a clear separation between actions from the left hand seat and the right hand seat. So we'd like to have the right hand actions (F/O, PM) done for us in reaction to the phase of flight and to left seat actions (CPT, PF).
Several options exist to have a virtual copilot flying with you In X-Plane. But they might be technically complex, challenging to maintain, or require payware softwares.
The intent was to provide a simple solution!
We have made a transcript from the FCOM into a Lua script for the IXEG 737.
We have made the transcription of the following procedures :
Preflight procedure (triggered by the left hand side oxygen mask test)
Before start (triggered by the beacon to ON)
Before taxi (trigger by both engine generators to ON)
Before takeoff, securing the cabin (optionnal, triggered by strobe ON) Runway Entry procedure (including TCAS control, triggered by left outboard landing light)
Take off run : gear and flaps retraction schedule (automatic trigger)
Flight 100 and climbing items (automatic trigger)
Flight 100 and descending items (automatic trigger)
Approach, flaps extension schedule (automatic trigger with available selection of FLAPS 30 or FLAPS 40 configuration)
Go around (automatic trigger upon positive rate)
After landing procedure (triggered by speedbrake down on ground)
Apron entry (lights and doors) (triggered by runway turnoff lights OFF)
Shutdown procedure until turn around state (beacon to OFF)
The procedures are either manually triggered or automatically called.
The Copilot is not calling the checklist. The copilot is doing the procedure.
You can listen to the cabin PA and boarding music if PA receiver is activated on the left hand side Radio Management Panel. Cabin crew is handled by Speedy Copilot without pilot intervention according to phase of flight. In addition, the first officer pressure altimeter setting is linked to the captain's one. If you change the barometric settings, the F/O will synchronize his one.
Installation Extract IXEG_proc.lua and the sound directory into ..\X-Plane 11\Resources\plugins\FlyWithLua\Scripts
Download first the base version. Last minutes changes are applied in the separate download IXEG_proc.lua. Overwrite the Lua script from the zip archive. Download IXEG_proc.lua for incremental update.
Don't forget to read the manual !
Where to discuss it ?
You can discuss this file in the IXEG forum if you wish :
By falcon1823This is a mod to fix a lot of manipulators that are otherwise unusable in VR with the touch controllers in the Leading Edge Simulations Saab 340A Version 1.5 for XP11. Manipulators that have been tweaked to work in VR are:
Rudimentary Pilot and Copilot teleport hotspots! (WIP)
GPS Knobs, inner/outer
Sun Shades, slide on rail and lower/raise
All Light Intensity Rheostats
Autopilot Altitude Selector Dial
Com 1 and 2 Function Selector and Frequency knobs, inner and outer
Nav 1 and 2 Function Selector and Frequency knobs, inner and outer
ADF 2 and 2 Function Selector and Frequency knobs, inner and outer
Transponder Function Selector and Frequency knobs
CRS 1 dial
CRS 2 dial
IAS Bug knobs
Altimeter baro pressure knobs
Overhead DC Selector knob
Flight Number Digit Wheels have been tuned for functionality
Parking Brake orientation corrected (was previously reversed, now a push toward the floor pushes the knob down)
Steering Tiller orientation corrected (was previously reversed, now a push toward the floor pushes the knob down)
DCP Select knob tweaked
Decision Height Knob rotation and push in/out tweaked (was previously reversed)
And many, many other dials, knobs, and switches...
These changes make the aircraft fully flyable using touch controllers in VR! With the exception the yoke.
Known bugs or issues:
- Some manipulators are a bit fiddly/touchy/sensitive, but at least they work correctly. **most fixed in 1.1
- CRS 1 knob seems to have two grab points, and one doesn't work. If you grab the CRS 1 and it doesn't turn, aim more for the base of the knob instead of the top of the knob. You can also grab the obs knob next to the CRT screen, it works beautifully.
- Switches that should "snap" back to center, such as starter switch, bleeds, trims, V/S wheel, etc...they do not snap back to center using the VR controllers. I believe there is some custom "onmouserelease" gizmo code going on there, and the VR controllers aren't seen by gizmo as a "mouse". Fortunately the VR mouse works just fine, so I map the vr mouse to a button on my yoke and turn it on when I need to adjust trims. Everything else is still usable with the VR controllers. When you reset the bleeds it will stay in the reset position, but I've found that it's fine to leave it there. Same thing with the starter switch, it will just stay in the position of the engine you just started, but doesn't make a difference. If you want to snap it back to center, just use the VR mouse for now. I also map the vvi up and vvi down to buttons on my yoke so i don't have to use the V/S wheel when climbing/ascending using V/S mode.
- Some custom mouse wheel code in 2d gets broken while using the VR mod, so if you are going to fly her in 2d you may want to revert back to the old .obj files.
- gust lock only works using VR mouse. Again, I believe it's dependent on some custom gizmo mouse code.
Disclaimer: This is not an officially supported LES update, so don't expect support from them on it. If you need help you can always ask me or just put your old .obj files back in your folders. If you lose the old files and just want to reset everything just reinstall the aircraft.
Download the SaabVR-obj-v22.zip file (this is the latest version)
Back up your LES_Saab_340_cockpit.obj from your Passenger Variant folder, your LES_Saab_340a_Cargo_cockpit.obj from your Cargo Variant folder, and your LES_Saab_340a_AEW_cockpit.obj from your Airborne Variant folder.
Unzip the file, you'll find 3 folders, one for each Saab variant (passenger, cargo, airborne). Inside each folder you'll find a ***variant.txt file and a ***vrconfig file.
Step 1: The ***vrconfig files just go in your Saab's corresponding aircraft variant folders. Easy.
Step 2. You will need a text editor for this next part, I recommend notepad++ (free). The text inside these ***variant.txt files are intended to replace the current corresponding text in the obj files. Open the ***variant.txt file and copy all the text. Open the matching .obj file from you Saab's variant folder in your text editor. Search/find (or edit/find) for the world "TRIS". Highlight that line and all remaining text in the obj (shift click at the bottom of the file to do this quickly) and paste. Save the obj. (Not save-as, don't give it another name).
**What's New in Version 2**
This is a fairly major update. Along with the obj text modifications you'll now get vr_config.txt files to put in your aircraft variant folders as well.
Changed a lot of axis manipulated knobs to their correct manipulation, getting rid of the "sliding up and down the colored line" effect. Also changed the sensitivity of countless dials and switches for a much better experience. Also added teleport hotspots to the pilot and copilot seat (sort of...it's a work in progress, but it works. The blue hotspot indicator that you're probably used to is currently a hoop about where the head of the pilot would be, but it works).
All the manipulators that are still bound to color-line axis's can not be fixed because they are custom-code dependent (I think), and I've not found a way to fix them. They work as is, just have to deal with the axis slide.
By PyroLifeThai Airways: cabin announcement.
V1.0.0: Safety demonstration video
These files are made for the Airbus of JAR Design.
i can not confirm if the sound package also can be used for other aircraft.
To open .7z file: go to 7-zip.org and download the lasttest version
V1.0.0: .7z or .zip
V1.0.0: .7z or .zip
By PyroLifeFinnair: announcement V1.3.1
V1.0.0: Safety demonstration video for the A320 of Finnair. (2016 version)
V1.1.0: Safety demonstration video for A320 (2016 version + 2018 update)
V1.2.0: On-Board service information video announcement (2018 version) English with & without Finish language versions. in High/low audio quality.
V1.2.5: Safety demonstration video shorter version for other fleet of finnair. + Information & instructions are updated
V1.3.0: Before Landing arrival information announcement + Information & instructions are updated
These files are tested on the JAR Design A320 airbus aircraft.
i can not confirm if the sound package also can be used for other aircraft.
I hope i could help you for a wonderful flying experience with Finnair on Xplane!
V1.0.0: .7z or .zip
V1.1.0: .7z or .zip
V1.2.0: .7z or .zip
V1.2.5: .7z or .zip
V1.3.0: .7z or .zip
V1.3.1: .7z or .zip
V1.0.0: .7z or .zip
V1.1.0: .7z or .zip
V1.2.0: .7z or .zip
V1.2.5: .7z or .zip
V1.3.0: .7z or .zip
V1.3.1: .7z or .zip
To open .7z file: go to 7-zip.org and download the lasttest version
By admrozThis script adds command that toggles IXEG 737 mini-EHSI display:
FlyWithLua/ixeg/mini_ehsi_toggle and menu entry to do the same:
Plugins > FlyWithLua > FlyWithLua Macros > [IXEG] mini-EHSI toggle Requirements:
IXEG 737 FlyWithLua plugin Installation:
copy the script to X-Plane 11/Resources/plugins/FlyWithLua/Scripts folder Here is how it works:
By Dusty926Hello, and welcome to Environment+, or Enviro+ for short! The new and improved mod for your sim environment! The Enviro is what we've done to make the sim so much more immersive, and the + is your contribution to it! We love seeing what people will add on top of it! From skycolours, to cloud textures, to tweaks of the .lua itself!
This mod primarily came about when I noticed that most other .luas had their clouds placed as much as 7,000+ feet above where they were supposed to be! To bring the weather back down to its proper layer and keep it looking nice was a difficult, time consuming task, but with the help of MagikarpDrowned (Creator of the famous Project Better X-Plane), we've crafted an amazing new environment.
This of course isn't simply a .lua tweak, which is why it's not called any old .lua tweak. It's an environment tweak, and that means it comes with cloud textures! Courtesy of FSEnhancer's amazing work laying out the clouds, and Magikarp's tweaks to their already fantastic puffs, we've got some perfect fits for the new environment! I greatly encourage using the skycolours from the aforementioned mod, or Soft Cloud Art's similarly stunning skycolours!
But, you may be wondering, "What if the textures tank my FPS? What if it doesn't perform as well? What if I just don't have the VRAM for it?" Well, I had thought about that a lot, and that's why the .lua was primarily built to focus on making the DEFAULT cloud textures as magnificent as possible. If you have performance issues, or just prefer the look, I greatly encourage you try out the default X-Plane 11 cloud textures with this .lua!
Which leads me to tell you to MAKE A BACKUP OF YOUR DEFAULT CLOUDS. They can be found in Resources/bitmaps/world/clouds.
Now, the .lua was designed to be the tweaking man's .lua, so if you encounter issues, performance or visual, dive into the .lua! I've written down some notes and suggestions within it for you to be mindful of, and I highly encourage you toy around with the various settings to see what sticks with you!
To install Enviro+, dive into the Enviro+ folder and place Resources in your X-Plane installation folder, right where the .exe is! It'll ask you to overwrite some cloud textures. If you use vanilla or other cloud textures that you don't wish to replace right now, simply choose not to overwrite, and everything else will install as planned!
I hope you enjoy Enviro+, and I can't wait to see how it might evolve in the future! Take care, and have at 'er!
Clouds courtesy of FSEnhancer, without it I wouldn't have such fitting clouds to go with the .lua! Do please check out their Skycolours too! Ooh and ESPECIALLY their sun textures! Their sun textures in particular are stupidly amazing!
Shoutout to Soft Cloud Art for inspiring me to finish up the finer details of this .lua, and also having some amazing Skycolours of its own!
By Tom StianTCAS CleanUp for the IXEG 733.
This script is ment for version 1.2.
IF you have problems with TCAS targets not disappearing while using IVAO, VATSIM or PILOTEDGE, then this script may help you.
If you dont have any issues, dont use this script.
This script will only run when you are connected to IVAO, VATSIM or PILOTEDGE.
- You will need FlyWithLua installed -
- copy IXEG_TCAS_CleanUp.lua to [X-Plane]\Resources\plugins\FlyWithLua\Scripts
By danhenriA complete operating manuel for the marvelous JS 32 by Javier Rollon.
By Tom StianHello
I made this LUA-script for randomly enable the built-in IXEG failures.
The script enables the built-in IXEG failures + engine fire, engine failure and oil pumps.
Have your QRH ready.
Available failures by IXEG.
The script activates when your GroundSpeed is higher then 40 knots.
Settings: (edit the IXEG_Failures.lua)
-- Here you set if the failures should be default enabled or disabled when your starting up X-Plane.
-- Set true to enable failures, false to disable. Default is true. true and false have to be written with lowercase letters.
EnableFailures_WizVar = true
-- Mean time between failures (MTBF) is the predicted elapsed time between inherent failures of a system during operation.
-- Default is MTBF_hours = 20.0. See further down for of a example of MTBF set to 10 hours.
MTBF_hours = 20.0
-- Max simultaneous failures pr session
-- Default is Max_Failures = 2 -- The highest numbers of failures is 27 -- setting above this can crash x-plane
Max_Failures = 2
-- Set the level of failures you want.
-- 1 = Minor failures, 2 = Minor and Major failures, 3 Minor, Major and Critical failures.
FailureSeverity = 3
-- Set 'ImminentFailure' to 1 to enable the imminent failure option. When this option is enabled you can trigger a imminent failure with setting the SERVICE INTERPHONE to ON position on the overhead panel.
-- The SERVICE INTERPHONE will switch back to OFF when a failure is triggered.
-- The 'ImminentFailureMTBF' (in minutes) is the MTBF used when you enable the 'ImminentFailure' and set the SERVICE INTERPHONE to on.
-- Default is 0.
ImminentFailure = 0
-- Default is 5 (in minutes)
ImminentFailureMTBF = 5
The Service Interphone switch
How to enable or disable failures (for the session) with FlywithLua menu.
This graph shows a example how often you can expect a failure when you set the MTBF to 10 hours.
- You need FlyWithLua installed -
- Tested on X-Plane 11 with Windows 10.
- Simply place the script in [X-Plane]\Resources\plugins\FlyWithLua\Scripts
Every failure is logged. You can find the logfile in your X-Plane root folder. The logfile is called IXEG_Failures.log
Here is a sample of the logfile.
- None. But please report if you find one
For support please visit: http://forums.x-pilot.com/forums/topic/11350-lua-script-randomly-enables-ixeg-failures/
By skiselkovX-RAAS is an open-source plugin that simulates the Honeywell Runway Awareness and Advisory System. Version 2.0 is a complete from the ground-up rewrite of the original X-RAAS FlyWithLua plugin. Please note that this is not just an upgrade of the old plugin and cannot be simply downloaded and plastered over the old 1.0 version. See below for details on how to install this plugin.
X-RAAS2 is a standalone plugin written in C and as such no longer requires FlyWithLua. To install the plugin, unzip the contents into: <X-Plane>/Resources/plugins. If you have been using X-RAAS 1.0, be sure to remove it from FlyWithLua/Scripts, otherwise you will get strange doubled annunciations.
NEW FEATURES FROM VERSION 1.0
X-Plane 10 & 11 compatible New configuration GUI: no need to mess around with config files anymore. The config files method is still supported, refer to section 2.1 of the included user manual for details on how to migrate existing customizations from version 1.0. Much improved performance: no more stuttering when Lua decides to collect garbage on slow systems. No more audio compatibility issues: this resolves audio compatibility issues with 3rd party addons such as Ground Handling Deluxe and the LES SAAB 340A (among others). More sensible automatic scenery alteration detection and scenery data cache rebuild. The cache rebuild is now also much faster. Much more fine-grained control over each RAAS monitor. Nicer text rendering and substitutable fonts & sizes. Ability to switch between "LONG LANDING" and "DEEP LANDING". User manual rewritten in LaTeX with clickable hyperlinks. Much more streamlined embedding into 3rd party aircraft avionics. The avionics integration guide is now a separate PDF manual with much more detail on how fine-tune the embedded software and how it compares to and interacts with a stand-alone installation. DEMONSTRATION VIDEO
The video below is from version 1.0, but version 2.0 features virtually all identical annunciations.
X-RAAS2 is open-source software distributed under the terms of the Common Development and Distribution License ("CDDL"), version 1.0. The license text is included in the ZIP package under Documentation/COPYING.
By Tom StianHello Captains!
I made a simple LUA-script for v-speed callouts.
It includes callouts for 80 knots, V1, Vr, V2 (V2 is optional) and positiv rate / gear up.
The script is tested on X-Plane 10.51 and X-Plane 11 on Windows 10.
Feel free to leave a comment if you liked the script (or not)
- You will need FlyWithLua installed - http://forums.x-plane.org/index.php?/files/file/17468-flywithlua-for-xp9-and-xp10/
- Unzip the files in [X-Plane]\Resources\plugins\FlyWithLua\Scripts
You should get a structure something like this.
Edit the IXEG_vSpeed.lua for the settings.
Set to true to enable "V2" callout and false to disable. true and false have to be written with lowercase letters.
Enable_V2 = false
Set to true to enable "Positive rate/Gear up" callout and false to disable. true and false have to be written with lowercase letters.
EnablePosGearUp = true
Sync the First Officers speedbugs with what you set on Captain side. Default = false. true and false have to be written with lowercase letters.
SyncSpeedBugs = false
Change "SoundLevel" to adjust volume for the callouts. Adjust between 0.10 min - 1.00 max (default 0.55)
SoundLevel = 0.55
How to use:
This is how I use the bugs. It may not be correct compared to real procedures.
The required bugs you need to set for the call out to work is Bug_2 to V1 speed, Bug_3 to Vr speed, and set the MCP speed to V2 (if you use V2 callout).
You can set the other bugs to whatever you prefere.
- Speed bugs can only be set on Captains side.
@xplana for his excellent voice for the callouts
For support, please visit:
By Wakey0Time to give X-Plane a new modern look!
This is made to give a different and new look for X-Plane and changes it from the old one.
Not everything has been changed, but most visible items.
*INSTALLATION* Please make backup copy!! This is in case you want to go back to the original.
Copy 'Interface.png' from the Zip file into X-Plane 10\Resources\bitmaps and replace.
By BokehliciousThis is a quick and dirty Windows Console application i made in order to create Company Routes for the IXEG B737-300. To get company routes which you can open by the FMC you could also use a simple text editor, however it was a tedious process so i decided to do this converter.
All you have to do is to copy the route you are going to fly to the clipboard, only its waypoints and airways like this for example "XENAK UM985 LEDRI UL140 ALAMU DCT TEGRI UL605 NEKUL",
then run the "route to ixeg fmc.exe" which will now ask you for the ORIGIN and Destination Airport (4-Letter ICAO Format in CAPITALS for each),
once you entered those its done and there should be a coroute file ready to be opened by the FMC of the IXEG B737-300
If your ORIGIN is, as in this example, LROP and your Destination is LTBA just enter LROPLTBA into the "CO ROUTE" line of the FMC and the route will be loaded.
But first of all for setting it up you must check and enter the location of your IXEG Coroute file folder in the Settings.ini of the application.
Mine is "D:/Program Files (x86)/Steam/SteamApps/common/X-Plane 10/Aircraft/X-Aviation/IXEG 737 Classic/coroutes/" so i entered it as a default.
Also be carefull when you copy your route to the clipboard not to include any Airport, Runway, Flight Level, Sid, Star, Transition or anything else other than Waypoints and Airways (DCT and DIRECT is acceptable),
it also has to be in CAPITAL letters same as the ORIGIN and Destination.
By dr_nerdrageHere's a basic X-Camera config file for the IXEG 737 Classic.
- 15 Cockpit views
- 4 Wing views
- 15 External views
- 2 Orbits
- 1 Flyby
- a "walk around" type category that takes you around various areas of the aircraft
TrackIR or HeadShake users will have to enable these in the X-Camera settings.
No View IDs have been assigned, do this to your liking/need.
If you are unsure about what this or X-Camera does, please refer to the X-Camera website. It is an essentially free camera control plugin that provides advanced camera options.
It lets you set up a huge number of different views with smooth transitions and other snazzy features, like an orbit or flyby camera.
1. Make sure you have a recent/current version of X-Camera installed (such as 2.1.1 as of April 2016)
2. Go to your X-Plane 10\Aircraft\X-Aviation\IXEG 737 Classic folder
3. Copy this downloaded X-Camera_B733.csv to the IXEG 737 Classic folder
4. Enjoy (or adjust to your liking in the X-Camera settings)
If you have any comments or gripes, they belong here or to me via PM. I can also be contacted at firstname.lastname@example.org.
By dr_nerdrageHey everyone,
I found the stock checklist to be a little basic, so I made this expanded checklist in a style that I believe fits the aircraft. Checklist is based on real airline checklist for the 737-300. Big thanks to P3ROn for the help.
(Please note that the preview image compression makes the checklist harder to read than it is in sim.)
1. Go to your X-Plane 10\Aircraft\X-Aviation\IXEG 737 Classic folder
2. Make a backup of the current IXEG_checklist.png file (e.g. by renaming it to "IXEG_checklist.png.old")
3. Copy this downloaded IXEG_checklist.png to the IXEG 737 Classic folder
Please note that this checklist is not an official IXEG checklist. If you have any comments or gripes, they belong here or to me via PM. I can also be contacted at email@example.com.
By GiantUnicornI got alot of requests for this file so here it is.
IXEG 737-300 Classic camera view preset with wing views.
Preview right here
Like what you see? Check out my Twitch TV Stream right here
NOW WITH PRINTABLE EXTENDED VERSION!
B737-300 Checklist for IXEG 733
Available at x-plane.org and x-pilot.com
This document was taken from an original B737-300 checklist from 1998. I have re-typed up the checklist into a nice pdf format for easy download download. If you require any other format then please let me know.
It may be possible that some items may not yet be simulated.
DO NOT re-upload anywhere else.
FOR SIMULATION USE ONLY!
- DO NOT reupoload or distribute on any other site without my permission.
- The Text-To-Speech (TTS) voice is a payware voice and is not meant for commercial sale
- This sound pack is for your personal use only
-Locate your Boeing 777 aircraft folder in X-Plane/Aircraft/Heavy Metal
-Place the contents of this archive within the 777 directory (ensure that the folder you copy us titled 'sounds')
This is the checklist according to the tutorial provided with the aircraft. If it looks familiar, that's because i made it in the same style that Ramzzess used for his Sukhoi Superjet 100. It's really easy to read and understand, but it still isn't completed. If you're familiar with the aircraft already, you'll know where everything is. if not, you'll just have to bare with me until I can finish it off over the next few days. Enjoy!
By VanceAir and ground traffic are available for KILM (Wilmington Intl, payware). World Traffic aircraft and start locations are:
- KC-10 near gate 7
- F-14 near hanger behind control tower
- Columbia near Air Wilmington
- C-130 near Customs tarmac
A few things to keep in mind. KILM has crossing runways and sometimes World Traffic will place two aircraft on the same taxiway for a head-on collision. The KC-10 is rather large so any aircraft of similar size at gate 5 or 8 will need to taxi before the KC-10 has room to maneuver. The Columbia is hard to see when zoomed out from the airport because the light-colored wings match some taxiway colors. Use the optional object file for red wings on the Columbia. Flight plans begin in the air (not a departure airport) and all KILM runways have been defined; so landing should be possible for any wind condition.
By chris kX-Plane 10 Compatibility Library for X-Plane 9
Dec 31, 2012 - Version 1.0
By: "Chris K" and the ISDG Group
Happy New year to All X-Plane 9 users.! Here is a gift for you..... From Us.
WHAT DOES THIS DO:
This Library allows X-Plane 9 users to load X-Plane 10 Scenery files (with caveats, see below)
Here's something I thought about a few weeks ago; in terms of providing SOME kind of compatibility between XP10 sceneries and XP9 sceneries. I am primarily developing for XP10, and don't want to have to do 'parallel development' in terms of providing backwards compatibility to XP9. (I wish to work on one project, not two).
Instead of myself creating a "kludged" (Nerfed?) version of sceneries for XP9 (which I had done in the past to provide XP9 users something), instead I decided once-and-for-all to fix the problem at it's root.
HOW DOES THIS WORK:
This "shim" library file inserts blank objects, facades, forests, etc. where they exist in the new XP10 Library system. This is similar in nature to how the OpensceneryX "placeholder" library works, but this time we apply it to every single XP10 library object we could find.
This tricks XP9 into loading most XP10 scenery; as the library paths now resolve. The list is accurate as of XP10.20 beta 10.
I have tested this on my own scenery packages, and it works.
CAVEATS / WHAT DOES NOT WORK:
You will not see any XP10 objects (hangars, gates, lights, etc.)
You will not see any XP10 facades (terminals are a big one)
You will not see any XP10 forests
You cannot use large (4096x4096) textures:
If a scenery uses a draped polygon of greater than 2048 resolution on any side, XP9 will crash out. This is a known XP9 limitation; as it was only in XP10 that texture sizes were allowed to be increased.
You cannot use XP10-style facades
If a scenery uses an XP10 style 'custom' facade (FACADE 1000), XP9 will try to still load the facade, and proceed to crash out. I have tried the EDPORT_BACKUP trick, but it's a no go, since the file can actually be found (and still tries to use it, despite the version string).
You cannot use XP10-style Airport Layouts. XP9 Will Ignore them.
But! You *CAN* cheat!... and try to change the first few lines of the apt.dat file in a custom scenery to say "850" instead of "1000". I have tested this on YPAD for example, and it worked, despite there being custom ATC information encoded in it.
HOW TO EXTEND:
Got an object I missed? or a new facade showed up from somewhere?
Edit the library.txt file; find the "virtual" path that the scenery is using, and add the appropriate line to the library.txt file. Have a look at the text file - it's pretty self explanatory the 3 fields you need =)
Also, let me know if you found something. I'll include it in the master DB I have here.
This Library and associated files are provided "as is". No Warranty; No suitability of fitness for any purpose; May not even work.
Insert standard "Boiler Plate" Here.
© 2012 Chris K and the ISDG Group
By ShePooleyHow to install:
Select the version of snow you want: normal snow, deep snow or very deep snow. You only need one of it. For Alaska I prefer the version with very deep snow.
Replace the old Simple Season with the new one and delete the file "SP_version" in the root of the folder "zzzzzz1000 world terrain" or delete the folder "zzzzzz1000 world terrain" in your custom scenery folder.
This short python script will give you the 4 seasons!
The script puts a copy of the default scenery in the custom scenery folder and adds 4 sets of textures: winter, summer, spring and fall. If you are starting X-Plane 10 or moving the aircraft (location -> select global airport) it will calculate the needed season and activate it
No restart of X-Plane is needed.
January - March: winter in the north...summer in the south
April - June: spring in the north ...fall in the south
July - September: summer in the north...winter in the south
October - December: fall in the north...spring in the south
If the temperature at your airport is below -2° C it will set winter too
If it is winter and the temperature higher than +2° it will switch to autumn.
My script do not include any texture files, this must be done by the community.
That means you will not see any difference between summer, spring and fall until you have added textures for it.
It uses the default texture files to create a very simple winterworld for X-Plane. It is not really a nice winterworld but better than nothing.
I only added the simple winter to show that my script is working, do not expect too much.
X-Plane 9 users can install the well known WinterWorld into my script.
It is easy to add texture files to it.
If you add your own texture files to my system then you must do it to the folder "SP_texture_template" with the subfolders summer, winter, spring and fall. The folder "SP_texture_templatefall" will be the root of the scenery folder after the season fall is activated. If you put your files to the normal texture folders it can happen that you overwrite the default X-Plane texture files. If this happen then you must run the X-Plane installer to repair X-Plane!
Scenery designer can use my script to switch their scenery too
This script do not touch any real file, it is no more than a gigant softlink manager. That means you do not need free harddisk space untill you are adding texture files.
This script will work with all versions of X-Plane 9 and 10 till 10.99, X-Plane cant break it (at least i hope it) If my script detects a new version it will rebuild the system and every thing should work fine
How to install:
It requires Sandy Barbours Python interface
Drop it in the folder PythonScripts and start X-Plane
For the first start my script will need a very long time to copy the default scenery, my system needs around 17 minutes for it and my computer isn't slow
After the installation you must restart X-Plane to register the new scenery.
You can change all files inside the default scenery except the library.txt. This file is always the default version.
If you change it then X-Plane will crash!
If my script is switching the scenery than X-Plane needs a few seconds to do this.
During this time X-Plane is not responding. This is a limitation by X-Plane, there is no way to change it.
By JimboGHi there,
Thanks for downloading this file, I hope you will find it as useful as I hope to as I generally cannot cope that well in the Jetstream 32 without following the checklists - I always miss something and then: BANG! There goes an engine.. again.
The intention behind creating this series of (24!) checklists was to help people have an easy way of staying on top of the Jetstream 32 before it gets carried away or you get lost in what it's doing.
I've also seen a lot of people having problems that have been reported as bugs to JRollon when 95% of the time it's down to pilot error. Hopefully this series of checklists will serve to negate some of these errors.
Please read the "Installation Instructions" - I've taken the time to try and cover most issues/questions, so please check there for any pointers!
If you want some visual pointers, I have created the following accompaying YouTube videos, which shows these checklists in action!
X-Plane Bae Jetstream 32 Interactive Checklists - Introduction / Installation
X-Plane Bae Jetstream 32 Interactive Checklists - Aircraft Acceptance to Takeoff
More to come as I get time to do them....
Before Engine Start
Automatic Engine Start
Manual Engine Start (Left)
Manual Engine Start (Right)
Engine Fire (Left)
Engine Fire (Right)
Both Engines Fire
Engine Failure / In-Flight Shutdown
Descent/Approach - Single Engine
Landing - Single Engine
Go Around/Missed Approach
By iGoAppThe JRollon CRJ-200 Virtual Dispatch calculates various values required for your flight plan (distance between airports, fuel amount, weights, CG, V speeds, pitch trim, etc.). The application is developed for the JRollon CRJ-200 airplane (X-Plane) only.
The application is created in Java and therefore can be used on any platform (Windows, Mac, Linux). You must have Java installed on your compter to run the application.
Note to those on MACs: iMAC OS X does not support Java anymore and does not provide automatic update of Java. To run this application, you need to go to the Java website and download and install the latest update.
If this application does not work on your computer (Mac, Windows, or Linux), your Java version is out of date. Go to the Java website and install the latest version!
The zip file contains an exe file for Windows users, a jar file for those with Mac and Linux, and a brief manual (if you ever need one).
If you have any comments about the application, you may write me at: firstname.lastname@example.org.