Leaderboard

Updated September 2023, Version 1.5 Hi everyone. While it seems to be the economically "smart" thing to do to NOT talk about the shortcomings of your product (and then sometimes to just ignore the complaints after you cash in the money), we are trying to run things a bit differently here at IXEG. I would therefore like to share a list of things that will NOT be in version 1.5, and also give a little background of why, and wether we are planning to add it later. I will try to make this list as encompassing as possible, if I forget something, please don´t sue me! I will add/remove from this list as warranted. Aircraft visual 3D model Ancilliary vehicles (catering, fuel truck, loading crew) - this is now accomplished by using the XP11 native ground vehicles, the docking locations for those are correctly added in planemaker. Cockpit keypad entry mechanism Omitted due to security reasons. Deployable emergency slides.Omitted due to time constraints, planning to add later. Deploying oxygen masks. Omitted due to time constraints, planning to add later. Sound effects/visual model for passengers and their (assumed) behaviour. Too complex a simulation off it´s own, most likely won´t be added for fear of having something repetitive or cheesy. Cabin crew voice interaction. You can communicate via menues that are invoked by pressing the cabin call button, though. FMS Pilot entered HOLDS. While we have database-inherent holds (like at the end of a missed approach), we won´t feature the HOLD page where you could enter all sorts of HOLDS. Omitted due to time constraints, definitely planning to add later. RTA feature. Omitted due to time constraints, planning to add later, but low priority. OFFSET feature. Omitted due to time constraints,planning to add later, but low priority. ABEAM points (after shortcutting route, for example). Omitted due to time constraints, definitely planning to add later. You CAN enter stuff in the FIX page, and "find" a PBD point that way (enter a fix, enter a radial and a distance to see the green radial and distance-circle) Entering descent wind forecast (normal wind entry on PERF INIT page possible). Display of "RTE DATA" on EHSI/map, i.e. showing ETA and restrictions next to waypoint. You can see that on the LEGS page, for now. Omitted due to time constraints, definitely planning to add later. Automatic entry of performance data (weight, etc.). We might include that for the "ready to fly" scenario, not decided yet. For now it must be entered manually, if FMS performance assistance is desired (not mandatory). Fully working PROGRESS page - we started to code it, but much of the things shown are placeholders. We expect this to be one of the first things we will add soon after release. Full VNAV functionality for descents with speed and/or altitude restrictions. The FMS gets confused by changing the cruising altitude while enroute and multiple descent restrictions and restrictions of a certain type. Basic unrestricted descents work, though. GUI Dedicated flight-planning software. We feel that this is not necessarily within the scope of our add-on. We model the plane like you get it after delivery from Seattle (+ free lifetime fuel!). There are plenty of flight-planning solutions out there, we include a basic "ballpark" fuel calculator. Complex and visually appealing load+trim software. We feel that clicking empty seats to fill them and pulling sliders to load cargo is fun for a few times - but really all you get is a weight and a center of gravity. And you might just as well set those directly in the gui. We have simple sliders and click-buttons for that (or you can use the default X-Plane menus). No way to output any CDU, EADI or EHSI onto an external device like iPad or such. Would like to have that (especially for cockpit builders), though. Exception: it is possible to use AirFMC, available at the Apple App Store. No pop-out 2D displays of flight instruments/CDU/EFIS to make reading or entering stuff easier, no hiding of yoke to not obscure view. We feel that the ergonomics (or lack of) an airliner cockpit is an important part of the experience, so we don´t want to "help" too much. We have "preview pop-ups" of the EHSI when making changes on the EFIS control panel to help you see if you have the right setup. Other systems Wxr radar returns can only be displayed on the left EHSI/map. Omitted due to time constraints, definitely planning to add later. Terrain colour display can only be shown on the left EHSI(map. Omitted due to time constraints, definitely planning to add later. Operating circuit breaker (CB). We decided that most CBs will never be moved in normal operation. We will add moveable CBs with the yellow collar later (to be used in abnormal situations), and possibly some others as well (standby altimeter vibrator!). Automatic startup/shutdown "macros". Won´t add that. This plane is about realistic operation (it´s not hard!). If not desired, just select "ready to fly" or "turnaround-state". IRS using "false" position. It is not possible to deliberately enter a "false" position and have the IRS align to that. The entry will be rejected unless reasonably close to the real position. In the real plane the GPS would also "correct" your wrong entry (if close enough) or warn you. A position far from the old "shutdown" position would be rejected once. A wrong latitude would be detected during the alignment process...It would be a lot of coding effort to maintain a "wrong" position with the corresponding effects (map-shift, etc.) A dedicated way to fly the same plane together in multiplayer. Note that SmartCopilot has made great progress in making our plane flyable with a crew of 2, and while not perfect yet, it is working very well, going by user reports: http://forums.x-pilot.com/forums/topic/9714-smartcopilot-first-attempt/?page=1 Volume control for radios/navaid ident checking. We have implemented a better volume (more loud), but it can not be adjusted yet. We are trying to be as upfront about the shortcomings of our model as possible. I have myself bought many aircraft for flight-simulations boasting great things, only to be disappointed. I want to avoid that for everyone, so if you find a "must have" feature on this list, I encourage you to hold off on purchase until we added your feature in a later patch. I could make a feature list of things we have that would take you hours to read, but instead you can assume that our plane can do everything that the real one does, except for the things noted above. Cheers, Jan

Kicking off a series of development updates, we will travel to the past, from when DC-3 was born to today, to understand the significance of this aircraft for the whole airline industry. Douglas Aircraft Company, after a TWA inquiry, started development of a new series of aircrafts, designated as Douglas Commercial (DC), the DC-1 in 1933, and DC-2 next year. Although DC-2 was successful, it was a bit narrow for what American Airlines wanted, which led to the development of one DST prototype. DST stands for Douglas Sleeper Transport! Yes beds in the airplane! Flew first time on December 17, 1935, the 32nd anniversary of Wright Bros first flight. The aircraft was fitted with 21 seats (instead of 14-16 sleeping berths), and designated as DC-3! Totally built, up to 1943, 607 DC-3 aircrafts. But WWII has begun and many DC-3s were put into military service. The needs for a military transport aircraft were huge, and with DC-3 fitting the bill, the C-47 Skytrain was created. It was based on DC-3 with few changes needed for the operations in the military, most notably the reinforced floor that allowed for higher gross weight, and the dual cargo doors. A total of around 10,000 C-47 aircrafts (and variations) were constructed. Many C-47s, after WWII, became available for civilian use, and even today, there are many DC-3s and C-47 in use! Later, in 1990, another variation was developed by Basler Turbo Conversions, retrofitting P&W PT-6 turboprop engines, and airframe modifications, designated as BT-67. Our Leading Edge Simulations DC-3 (v2) is based on the original, 21-seats, variants. The aircraft has a maximum gross weight (MGW) of 25,200 lbs for take off and landing, and can reach speeds up to 207 mph (180 knots). 2 Pratt and Whitney PW R-1830 Twin Wasp radial engines, providing 1,200 hp each, driving a 3-blade Hamilton Standard propeller. In the next weeks leading to the release, as development progresses, we will look into each area of the aircraft in more detail. For now, I will leave you with a few more random images. Keep in mind that everything you see here, up to the release, is work-in-progress, not final! (source: Wikipedia)

Hi, this is a known bug with a "timer" in Gizmo, it should get fixed with the next Gizmo version (I am already running a test version that fixes it). Indeed you can not power the left GEN BUS with the GPU anymore after it has been powered by the APU or engine generators. The current workaround is to either accept that (no electrical users that you need during turnaround are on the left GEN BUS), or reboot gizmo once you are parked. The view (W) was intentionally moved over so you can see more of the important stuff (like the landing gear lights)...you can freely adjust it in planemaker (viewpoint) or set up a "saved view" with the CTRL-NumPad keys (you can bind recalling those views to a joystick button, too). Cheers, Jan

I believe I have come up with a solution that will at least work for now. I changed over to Vulkan and started X Plane 11. I then changed TerraMaxx to each of the settings (Auto, Summer, Autumn, Mid Winter, Deep Winter) exiting X Plane after each change since TerraMaxx does not update the settings.dat file unless X Plane is exited. I then copied each of the individual settings.dat files to separate folders, one for each setting. Then I changed the properties of each of those files to make them read only. I then changed over to OpenGL and started X Plane 11. TerraMaxx now retains the settings in the settings.dat files since it cannot overwrite them. So depending on the season I will have to copy over the appropriate settings.dat file depending on the time of the year. But the file permissions are still the same for the TerraMaxx and SeasonsXP folders regardless of whether X Plane 11 is in OpenGL or Vulkan so I can't explain it either why it isn't working as expected. My only thought is if it is related to some change LR made in 11.50 as it relates to Windows 10 2004 which I am running as 2004 broke some other plugins which needed to be updated for that Windows version. Update. I normally like to keep TerraMaxx in Summer so that my winterized ortho textures stay in Summer and I used a weather engine to create seasons for Autumn and Winter as it works on all scenery types. So I just tried copying the Summer settings.dat file over and started X Plane and then tried changing over to Autumn and then exiting. I was glad to see that TerraMaxx was still set to Summer when I restarted X Plane. So this workaround will do for now.

by: Farhad Mashregh-Zamini UJS Fairchild PT-19 is here! A production by Uncle Jack Simulation at X-Aviation. If you have set your plane to "Start with engines running" in X-Plane 11, immediately after uploading plane, you will encounter a crash! Starting the PT-19 is not as easy as you think! First you have to turn off Automatic start in aircraft settings. Then, in the right side of the cockpit, there is a Manual that you have to click on it. When this manual is opened, you can choose the "Automatic Engine Start" from there, and your adventure with this beautiful airplane begins. If you are not a patient pilot and want to fly this Popular World War II trainer aircraft right away, and you don’t have time to read the POH and learn how to control this Taildragger aircraft on the ground, you need to disable the Truevintage and set the Tailwheel to Always Locked, then you may be able to take off and land safely. Flying with this aircraft is really a challenge that shows what the difference is between a Game and a Flight simulator.

Could please someone make this beautiful livery? https://www.planespotters.net/photo/1087322/oy-mmf-maersk-air-boeing-737-3l9 Thanks

We wanted to implement it, but then we saw that the new Microsoft Flight Simulator has no opening doors on aircraft, and since everyone says that that is a much better program than X-Plane we have not done the opening doors, because we want to be more like them! Cheers, Jan

I reinstalled the IXEG yesterday and messed around with converting my 737-200 overhead in Air Manager to the 733, it's about 70% done and working very nicely. Took my EXS livery for a short flight, I'd forgotten what charm this aircraft has, a real credit to the development team. Very much looking forward to it getting even better with the impending update(s).

Yes, they're done (apart from Inter European which I think still needed some work, but to be honest I gave up on this aircraft because of the lack of development and for me personally lack of certain dataref availability - I switched to the 732 and developed my cockpit software around that. I have a load of 90% finished liveries - if they do update it as indicated then I have several liveries which could be released once I dust off my painters hat. Would be nice to see a new version of the IXEG, I have a lot of real-world affection for the 737 Classics. A handful of WIP shots from 2017.

Certainly once we get all the 3D assets converted to the new workflow, a cargo variant would not be terribly difficult. We'll put this on the wish list. -tkyler