Tom Stian

Uploaded a new version of the script. I learned that randomize with LUA isen't that random. So the script should work much better now.

I recommend to increase the FailurePercent to maybe 30 or 40. 10 is very rarely. Its hard to test out that setting ^^

delete please. View File delete please Submitter Tom Stian Submitted 08/09/2016 Category Plugins and Utilities

Hello 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 "ADVANCED OPTIONS" -- 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. MTBF: This graph shows a example how often you can expect a failure when you set the MTBF to 10 hours. Requirement: - You need FlyWithLua installed - XP10: http://forums.x-plane.org/index.php?/files/file/17468-flywithlua-for-xp9-and-xp10/ XP11: http://forums.x-plane.org/index.php?/files/file/35579-flywithlua-for-x-plane-11-and-10-windows-linux-mac-os-x-version/ - Tested on X-Plane 11 with Windows 10. Installation: - Simply place the script in [X-Plane]\Resources\plugins\FlyWithLua\Scripts Logging: 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. Known bugs/limitations: - None. But please report if you find one Changelog: 0.113 - Added failures for landing gear. 0.112 - Added option 'Imminent Failure'. - Changed default MTBF from 10 to 20 hours. You can download the script here: http://forums.x-pilot.com/files/file/1054-randomly-enables-failures-for-ixeg-733/

Your welcome

I think there is a typo in the datarefs from IXEG. ** This dataref is working, but is spelled wrong. missing 'u' in hydraulics ixeg/733/failures/hydralics/systemA_leakTime2Empty_mins = 0 ** This dataref is NOT working, it works when I add the missing 'u'. ixeg/733/failures/hydralics/systemB_leakTime2Empty_mins = 0

I found them, excelent. Thanks. Will try them after job today. Thanks to you both. ixeg/733/failures/electrics/acstby = 0 ixeg/733/failures/electrics/batt = 0 ixeg/733/failures/electrics/dc1 = 0 ixeg/733/failures/electrics/dc2 = 0 ixeg/733/failures/electrics/acelectronic1 = 0 ixeg/733/failures/electrics/acelectronic2 = 0 ixeg/733/failures/electrics/dcelectronic1 = 0 ixeg/733/failures/electrics/dcelectronic2 = 0 ixeg/733/failures/electrics/dcstby = 0 ixeg/733/failures/electrics/gen1 = 0 ixeg/733/failures/electrics/gen2 = 0 ixeg/733/failures/electrics/hotbatt = 0 ixeg/733/failures/electrics/main1 = 0 ixeg/733/failures/electrics/main2 = 0 ixeg/733/failures/electrics/swbatt = 0 ixeg/733/failures/electrics/xfr1 = 0 ixeg/733/failures/electrics/xfr2 = 0 ixeg/733/failures/hydraulics/engine_pump_A = 0 ixeg/733/failures/hydraulics/engine_pump_B = 0 ixeg/733/failures/hydraulics/electric_pump_A = 0 ixeg/733/failures/hydraulics/electric_pump_B = 0 ixeg/733/failures/hydraulics/engine_pump_A_blowout = 0 ixeg/733/failures/hydraulics/engine_pump_B_blowout = 0 ixeg/733/failures/hydralics/systemA_leakTime2Empty_mins = 0 ixeg/733/failures/hydralics/systemB_leakTime2Empty_mins = 0 ixeg/733/failures/hydraulics/systemA_blowout = 0 ixeg/733/failures/hydraulics/systemB_blowout = 0 ixeg/733/failures/hydraulics/systemA_slowLeak = 0 ixeg/733/failures/hydraulics/systemB_slowLeak = 0

Hello Is there any datarefs on the "IXEG failures" that are available on the left failures menu ?

I dont have any problems with reverse thrust. I have sim/engines/thrust_reverse_toggle assigned to a button. And just use that when I want to apply reverse thrust. And of course push the button again to get out of reverse thrust mode. EDIT: If I remember correct I think JAR A320 maybe exits the reverse thrust mode when you put your throttles in idle. And here is a video about the ghost throttles.

What command do you use for reverse thrust ?

Its still the same folder when using Navigraph navdata. I recommend you to use Navigraph FMS Data Manager (https://www.navigraph.com/FMSDataManager.aspx) Just make sure you select the correct folder if the FMS Data Manager dont find it for you.

I did delete D194N as a workaround. And that worked fine. But just wanted to report it

Im a "Tom", but not THE Tom ^^ What are you wondring about that folder ? Problems installing navigraph navdata?

Hello On the STAR ORMOS1C and VDMA09 I get a strange drawing. I guess some of the reason is that D194N and D189N are pretty close. IXEG_FMS_debug.txt

What was your previous version on the Nvidia driver ?

What weather injector are you using ? Default x-plane, FSGRW, NOAA plugin, other ? (Skymaxx pro dosent download weather) And default x-plane weather, as of 10.45, only have wind alofts in USA if I remember correct.

Im havent tried the visual approach, but to add my experience to this, you have to complete your route for the FMC to reset. So lets say you go from LNAV to HDG mode to intercept LOC, and you skip a waypoint when doing that, your FMC will not reset. To solve that I just use direct to the next waypoint i know im crossing. From facebook, Tom Kyler says this about the FMC reset: The criteria for FMS reset currently is "flight phase = descent", "be on the ground" and groundspeed < 60 knots. FMS reset assumes the flight is "complete" and has all the required phases....and that they have been flown.

Thanks for your feedback everyone. Ill stick to 4x SSAA for now. The FXAA is too blurry for me. :/ Im running X-plane at 1440p and get some stuttering at detailed and mesh'y areas with 4x SSAA. Waiting for the Intel gen 7 before ill do any CPU upgrades. And yeah. 2x SSAA would maybe be the "perfect" setting if it existed.

HUD forward view is now available. Im not sure what they are meaning with this one, but its not Heads-up Display :)

Your welcome

Hello I see that on b737.org.uk says the following: Anti-Collision: Are the orange rotating beacons above and below the fuselage. They are universally used as a signal that the engines are running or are about to be started. They are typically not switched off until N1 has reduced to below 3.5% (or N2 below 20%) when it is considered safe for ground personnel to approach the aircraft. http://www.b737.org.uk/aircraft_general.htm#Lights And I see some say N2 15% and some N2 10% The boeing manual says this. So the question is what the definition on "complete stop" is maybe I switch it off around N2 10%.

Hello I have always used 2x SSAA + FXAA for HDR settings. But, specially, at nighttime the instruments looks blurry. So I tried out 4x SSAA and everything got crystal clear. But it will of course hit a bit on the framerate. Im not 100% sure, but is the IXEG 733 more affected by the HDR setting than "other" aircrafts ? And is there anyway to tweak the 2x SSAA + FXAA to make it more clear via Nvidia Control Panel or something? What are you guys using ? My setup is GPU: 980Ti CPU: i7 4790 Click on the images to see the difference better. 2x SSAA + FXAA (daytime) 4x SSAA (daytime) 2x SSAA + FXAA (night) 4x SSAA (night)

Yes, but are gonna disable it for a week or so. So its more smooth to remove the folders instead of disabling it via the menus every time

Thanks to both of you. I did remove the SilverLing and RWC folder from plugins folder. But I have some weired altitudes on the clouds with the default clouds. So just had to check if it is some more I have to remove when I test this out.