Leaderboard

Hi dreambox, First off, I gave you a reputation-click because I feel that you are touching a point that is very present for a lot of our customers. But I would also like to add our perspective to some of your points. I think you are correct in your assessment that our patch 1.1 for XP10 took too long already. Cameron and Ben gave the reason for the latest delay (flooding of Ben´s area), but we concede the point, it has been too long. The patch is ready to go out, Ben is working hard to update gizmo so we can roll it out ASAP. No time estimate, though. Here is my take on XP11: When you bought the plane, it was "for XP10". No mention of "...and future XP versions" or "will be upgraded to future versions as soon as they come out" etc. So while we feel the moral obligation (and the business need) to update it to XP11, we don´t feel the need to do a rush job on it and reserve the right to take as long as we want. We ALL have fulltime jobs. We could not allot the time for a XP11 update in due time, with some of us having other obligations that preclude serious XP-dev work for months or even years. We learned about XP11 not earlier than anyone else, and Ben warned all developers to NOT update their aircraft before XP11 was final. XP11 is STILL not stable. In fact 11.01r1 just broke the landing lights of our plane - going from historical evidence we expect XP11 to stay "somewhat unstable" for another half a year, or more. The 1.1 patch will bring some "ninja-fixes" for XP11 users, the worst problem being the sliding at slow speeds/in cold&dark. The remaining problems you mentioned (especially the engine problem) can be fixed with planemaker tweaks you can do yourself. The only thing that will still be off in XP11 with 1.1 will be the drag being too low and the annunciator lights being too dim. Thank you again for the nice words about our plane (in XP10). I assure you we are working on the XP10 update and also on the XP11 compatibility patch. I may actually do my next preview video for 1.1 in XP11 just to show you how well the plane already works in it. Cheers, Jan

Hallo, I demand the XPlane 11 update by yesterday at the latest. I also demand to know what progress is being made for the XPlane 12 and 13 updates. I have listened to much nonsense about progress being delayed because of storms, floods, hurricanes, meteorite showers etc. Do you think I am stupid!! Everyone knows that weather can be switched off on the settings page! Do not make any further silly excuses! Finally; if wing flex is not fully implemented immediately I will throw my rattle out of the pram!! Get to it now!!!! Kind regards, Michael

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/

Yep pretty damn funny given the stupid comments of a small minority here.

A new semi "major" update is available 0.109- You can now only get one type of hydraulic leak pr system. Example: You cannot get a fast leak and then a slow leak on system A.- You can now only get one type of failure pr engine. Failures available is engine fire or engine failure.- Bug fix: The same failure will not be triggered twice.