Leaderboard

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/

Hello everyone, First things first, I would like to thank all the IXEG team for their work upon the 737-300, it is in my opinion, one of the best addon ever created. Hopefully it will shine on XP11 soon enough. Now, this issue doesn't only concern the IXEG 737-300; it does concern most of the planes within XP11. To me, the ingame rendering has a huge impact on immersion, that said, it appears to me that most PFD/ND, cockpit lights and backlight are colourless and doesn't really reflect reality. Those lights should be way brighter than what we currently have. I'm sure we got plenty of pilots out here who spent enough time inside a cockpit and may confirm my statement. I haven't seen anyone pointing this out hence the reason I'd like to get your toughts regarding this feature guys. May the IXEG team consider that ? If no, is there a way to manually tune the brightness of the PFD/ND from core files ? Finally, sometimes having pictures help... Those lights are clearly visible and all informations are easily readable; I'm refering mostly to the PFD/ND, MCP, FMC rendering. Now that's what we got on a stock shot. Indeed, colourless on the displays, the MCP is barely readable, the PFD and the ND lack of punch, especially the MCP backlight. How I'd imagine it should render... I made few changes using PS, those tuning may not be perfect for everyone, but I did so people would get "the big picture". I suppose those engines gauges displays should be also more visible, that said, I haven't edited that part of the panel. What do you guys think ? Do you agree ? Thanks and happy flying !

Thanks Jan I'll try it and see if it's going better. Best, B

On what do you base this opinion on? Photos of LIT panels are generally useless, especially those you find on Airliners net etc. Most of what you find is overexposed or has been tampered with to look better. Have been building sim panels for almost 18 years. As for pilots who spent enough time in the 737, I'm sure you know that Jan on our team has spent over 6000 hours in them and he has approved it. However there ARE issues in XP11 with atleast some of the backlit annunciators etc are too dim, we are aware of that. So if you wan't to judge anything at this point you need to do so in XP10 for which the aircraft is built. And just to give you an idea how complicated it is to judge those pics, look at your first photo. Compare the PFD horizon colors on both sides. The right side is set more dim than the left.

*Update* Assuming I was alone with this issue; however following V1.1 update the engine sounds are back and better than ever! Keep up the good work IXEG team.

Thanks for the update Morten. I'm not complaining, the aircraft is great. I love flying this aircraft every day. Just here to pass along the information

You could also implement some kind of failure level. Maybe 1,2,3 where 3 triggers the badass failures. 1 triggers the "light" ones and 2 the "medium" ones. This ensures that the user can finish his flight when chosing the lower levels. Sometimes you want to reach your scheduled location :-)

Thanks for this, Tom. The newfound stability with 1.1 should make using actual failures more fun. Installed, we'll see what happens

Oh, there may not be 32 days in May in the UK. But then again, you guys drive on the wrong side of the road, too...

A little story from my last flight. Had a interesting flight yesterday between LSZH (Zurich) and ESSA (Arlanda) during a VATSIM event, when a failure was triggered. Its fun to (try) troubleshooting and find out what has happend without looking at the logfile or the failures menu. (All picture is taken on ground just to illustrate) I had about 400-500nm left on my flight to ESSA when I got this master caution. I obvious have some issues with flight controls and the hydraulics. So my next step is to look at the overhead panel. The first I notice is that both hydraulic pumps for SYSTEM B is indicating LOW PRESSURE. And I noticed the indicators for the flight controls, but my main concern was the hydraulics. So I checked the pressure and quantity for SYSTEM B and confirming that I have a total loss of that hydraulic system. So I was thinking, what to do, what to do. I had no problems flying the aircraft with the autopilot. And everything else worked fine. My next step was to check if the QRH was covering this issue. And it did. Luckly for me. First two steps is to set SYSTEM B FLIGHT CONTROL SWITCH to STBY RUD and set both hydraulic pumps for SYSTEM B to off. So far so good. Still flying. And I made a decision to continue my flight to my destination as planed, it was after all a nice VATSIM event with alot of traffic. I started planing my next steps. What system have I lost ? How do I handle that ? The QRH says this. Systems that are handled by SYSTEM B is. Outboard flight spoilers. Autopilot B. - No issue for me, flying on Autopilot A. Yaw damper. Alternate nose wheel steering. No issue SYSTEM A is covering Nose wheel steering. Normal brakes. SYSTEM A have to handle the brakes, and that means that Autobrake is INOP. Manual braking only. SYSTEM B is also covering flaps, so alternate flaps have to be used. The QRH says I should plan for a FLAP 15 landing. Not sure why, but could be performance issues with a go around or if I lose of a engine, since I cant retract the flaps with the alternate system. Active runway for landing at ESSA this night was 01R (2500 meters). I did ask ATC for 01L (3300 meters) for landing, but it was denied (shame on you ATC) So 01R it is. Winds calm. VREF with FLAPS 15 was 144knots + 15. So my approach speed would be 159kts. The QRH says that alternate flaps extension from flaps 0 to flaps 15 takes 2 minutes. So had to plan this and make sure I was able to set flaps 15 in time. On the approach. At < 230kts I enabled the alternate flaps. Set the flap lever to desired flap position and extend flaps on maneuvering speed schedule using the alternate flaps position switch. Landing checklist: I was able to set the flaps in time and the landing went fine. You can learn so much from the failures IXEG have made availble for us. And a 2 hour "boring" flight from A to B can be pretty busy when you need to start troubleshooting and flying the aircraft at the same time. Pretty sure I was doing a lot of mistakes, but it was great fun From the logfile. The flight on vatsim: https://vataware.com/flight/5926fe4253523315c9000008