Leaderboard

We're thinking "time is money". My mortgage payments runs on a timeframe...my internet fees...my software subscriptions, my commissions.....special offers in the mail......all time frame limited to encourage folks to act to keep the economic cycle moving. Time and money is inextricably linked. Without this principle, no business would survive and we've have no products...no add-ons, no x-plane, etc. Who is John Galt anyhow. TK

People need to feed there families, he could of done his real job and earned a lot more money, but he chose to stick it out and give us the best 737 classic ever while putting up with the whiners and complainers. Yes they do know what they are in for. You should be happy.

Tom explained it in the recent video he did with Q8pilot - he had to make a decision whether to continue developing the 737 or going down another road in his life to make money. And he needs to eat now, he can´t go hungry for a few months with people on the fence waiting if they want to maybe update or not ("I want to wait until they put in the holds..."). That is why we nudge people to pay the money now.

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

Morning, Does anyone have a working profile for SAM GroundService? The one from XP11 does not work as SAM does not recognise it unfortunately. Thanks!

I din’t find any report on this issue but I have a desyncronization between the two pilot side altimeter gauges as the video shows. Also on de right side gauge the undreds of feet is stuck at “000”. It happens on both climb and descent. IMG_0098.mov

IXEG Team, please, consider adding cargo version. Thank you.

Your bug has been logged and we are going to look into it.

Talk about brain farts... I reset the permissions to unlisted. Anywhoo, there's nothing there that would have helped you figure out the cause so you didn't missing anything. Thanks, Jan and blue skies...

So....good example of why this port to XP12 is a pain. ..and this is just one of a lot. Went over this for a long while yesterday and just had trouble trying to code around it. Took it directly to Laminar and sure enough, the acceleration ramp between lightoff and idle is simply inaccurate. The acceleration curve shape between lightoff and idle is hard coded and not tweakable via PM. Below is the N2 ramp for the default 738 (which has the same problem). This is Laminar's own data of N2 vs. time (but my overlay comments). You can see the very rapid rise of N2 after lightoff...getting to within 80% of idle in a few seconds. So you may ask, "well why don't you custom code it"...and we do to some extent, but there is a limit. Some parameters, if we decide to override, means its all or nothing. So if we "override the engines" for example..then we have to write the entire engine model for all regimes and that is almost a product in and of itself. Besides, Laminar's model is mature and pretty good...no need to reinvent the wheel.....to me this is simply a "plane-maker design issue" oversight. A 'coefficient' should have been provided (and is what I'm lobbying for) to shape this curve...like a lot of curves in PM can be shaped. The good news is its official, we're filing a ticket to Austin. Also good news (but not perfect) is I've coded a workaround for the next patch to get us through.....because I'm sure it'll be some time before the next update to XP comes out with this fix. The limitation on my patch will be "don't mess with a running engine while the other one is starting". If you do, then the starting engine will exhibit this "rapid rise" behavior somewhat. ...but many folks may not notice it. and these kinds of sweeping modeling changes are all over the place, and have really wreaked havoc with the accuracy of our performance. BUT....we're working on that too now. TK

You (and Q8 Pilot) are absolutely entitled to your opinion. If you decide at a later stage that the (full) price for the XP12 variant is warranted, I am looking forward to seeing you as a customer. If you do not, I wish you always happy landings with a competing product, there certainly are a lot of great ones out there! All the best, Jan