Litjan

Hi! 1.) It is very important to not brake manually (at all) for the autobrakes to work. If you brake manually, even for a very short time, they will "disarm" (the orange light comes on) and not work anymore. It is also important to reduce thrust to idle at touchdown for them to work. 2.) The oil quantity in the real aircraft is basically NEVER the same. It would be pure coincidence if they were ;-) Cheers, Jan

We had code for the "hot start" scenario at a point in time - but I think we removed it again. Simulating things like that is in the realms of X-Plane...not add-ons, I think. Add-ons like ours utilize the underlying structure of X-Plane. It simulates aerodynamics, environment and also a lot of the "core" systems, like lighting, engines, etc. We are willing to infringe on this boundary where absolutely necessary to achieve a realistic simulation of the 737, but every time we do, there is the risk of getting weird results and also the risk of that core feature changing and rendering our "hack" not working right. Some good examples are the hacks we did to the ground model and drag model (needed for XP10). Austin improved his code, so now we have to go back in and change or remove our hacks. It also turned out that our hack did not work well in certain regimes (like the engine failure on ground), which is always the danger if you start hacking core X-Plane functionality. Who knows what calculations X-Plane does for simulating the parameters of the jet engine? I think the best way to add this would be to add a bug report or feature request to Laminar Research (providing steps with the default 737). I bet Austin will be all over it! Cheers, Jan

It is certainly within the realm of the possible! Not for the upcoming patch, though. We collect all requests and suggestions, of course. Thanks for your nice words, Jan

Thanks to everyone taking part!

No single answer here - it just depends on personal taste too much. There is the "hardcore realistic" viewpoint - according to the FCOM from Boeing. Then there is the "go back as far as possible to see everything" option. Throw in different FoV settings. I think 60 deg is probably the most realistic - but you will have to turn and squirm a bit (or set up different views) to see everything. Going higher distorts the view unnaturally (fisheye view), but has the benefit of seeing more without having to turn your view. Ultimately the answer is VR. Yet that brings its own problems (mainly resolution and framerate concerns). I am considering moving the cockpit default viewpoint (W key) to cater to the new yoke height/slant...but am afraid that this will throw off a lot of people that are used to flying with it that way, too. The married man knows that problem. Whatever you do... Cheers, Jan

3...and counting

Hi everyone, we consider removing the "preset views" pop-out panel that triggers when you bump the mouse against the bottom left corner of your screen. It is one more thing to port when moving to a new GUI. It is redundant - now that X-Plane has up to 10 view saving spots that can be configured freely. It can be bothering people when it pops out unwarranted. What do you think?

No problem - I haven´t heard of this before - maybe some more people will sound off with the same problem, then we have something to troubleshoot. Not quite sure I understand the "JoyToKey" concept...why don´t you just map the button directly to the command via native X-Plane? Hope you find the solution, viele Grüße, Jan

You can also map that to a keyboard button..

Hmm, I just tried - I can click the button on my joystick assigned to "one notch up" as fast as possible and don´t see anything like you show. There are also separate commands in the IXEG command menu for every flap setting - so you can just map a button to "flaps 15" and that should take care of the problem. Cheers, Jan

Here is the latest BETA for gizmo - I run it and it works great (more smooth on the framerate). However - make a backup of your old folder, first, then overwrite it with the new beta. Two things: 1.) You will have to "copy and paste" your email for authorization, the new beta does not recognize the @ key sometimes. 2.) You will have to edit manually: X-Plane/output/preferences/gizmo_prefs.txt Find (or create) this: { name="AutoLicenseUpdate_Always", value=false, },   Make sure the value is false.  Otherwise it will run in an endless loop asking you to update your license. Cheers, Jan

I have to say again that we have not heard of any incompatibilities like this before. I would assume that there are many people running Skymaxx and the IXEG. So there may be something more specific to your case than simply those two "not being compatible"... Cheers, Jan

Hi Speedbird1229, it is really not possible for us to tell what is going wrong on your system - at the least we would need to see some of the diagnostic files - like the Log.txt from your X-Plane folder and the GizmoLog.txt. I think that the IXEG and SkyMaxxPro run well together, as otherwise we would have heard a lot more about it. Chances are that they are either interfering with another add-on you are running, or that you are running an older version...or maybe have upgraded to 11.50beta? Cheers, Jan

Thanks for your help and input everyone!

Hi Jim, sorry to hear that you have problems - first time I heard about the AVG...and I don´t have that myself. I am sure there must be a way to set up an exclusion, maybe google it or even ask at the forums. Maybe someone with a Mac and AVG can chime in? Cheers, Jan

There are two strenghts brake that you can set in X-Plane. One is 50% (B key) and one is 100% (V key). I am sure you could map those to different buttons? Cheers, Jan

Not sure I understand that request? I can set the amount of brakes individually with my brake pedals going from 0 to 1.0 seamless. Using the autobrake allows preselecting a deceleration rate. Note that MAX is not the maximum possible. That can only be achieved with full manual braking or the RTO mode (not to be used for landing). Cheers, Jan

Doing some testing and shakedown flights to make sure all new features and fixes work as planned. So far things are going really good. ...at least for the passengers on MY aircraft .

Hi Cassio, The update will be applicable and work for all XP11.30+ users - and with some caveats to all other users at well: It must be noted (and we will make everyone aware at the time of download) that it is tuned for the "new experimental flight model". This means that if you run an X-Plane version that does not have this flight model option (which will become the norm in the future), your IXEG 737 will still work and fly - but the performance will be off (a bit). To make our 737 work well with the new flightmodel required tuning of the aerodynamic model in planemaker and airfoil maker, and it is not possible to switch those modifications on and off in the code like we did for our "scripted" flightmodel adjustments. So for the XP10 and pre XP11.3x fliers out there: The 737 will still work as before - you can either not apply the patch or you can live with the slight discrepancy in the flight model. I really don´t see a reason to not upgrade your XP11 version to the latest, though (you can still run OpenGL mode in 11.5x+!). In general it is obvious that we would like to have continuous support for all three versions (XP10, XP11.0x and XP11.3x+), but eventually the complexity of this is getting too big. Just like X--Plane itself our product is evolving and following progress...which means that older versions may become obsolete after a few years. I know that some people can´t afford to upgrade to newer hardware that supports XP11 or have built elaborate home cockpits that run XP10, only - but I don´t think it is fair to the vast majority of users that stay in tune with the development of technology and X-Plane to forego an evolving product to cater to this small (yet sometimes very vocal!) minority. Cheers, Jan

It is the former (equivalent amount of time). The FMS is getting more of a full rework as opposed to just adding a few items to patch it up - this will entail a full shakedown testing and therefore require a bit of time (work is underway on that). This isn´t necessarily dependent on XP12 - if that was never to come out, we would still do this FMS update. We know that XP12 will come out sometime. I don´t think it will take "years" until we see it. It will probably bring new features and requirements that will make us want to adopt our aircraft to it. So it is an apt milestone for us to aim at for the next big update. Cheers, Jan

You can "tweak" your response curve accordingly - basically drag it all the way down to "0" around the middle point - that way a slight deflection will yield no response -> null zone. Cheers, Jan

Buon giorno, there could be many reasons for that - I suggest reading/watching/following along the tutorials I made for this aircraft, all found in the "Documentation" folder of your IXEG 737 installation! Ciao, Jan

You may also want to look at the tutorials I have done for this aircraft - they are included with your installation (look in the folder Documentation). They are both in written format and include a link to youtube tutorials as well. Cheers, Jan

That is correct - Airbus recommends to keep autothrust on (they know the pilots they train )... Airbus´ flight-law augmentation will compensate the pitch moment from the engines for you, so this does not pose the same problem that Boeing has. Cheers, Jan

Hi Doeke, 1.) Not sure - if you just got this aircraft, you should already have the latest version. 2.) I don´t have enough information on what you did (or more importantly what you didn´t do!). Are you sure the GS was armed (APP mode)? 3.) Oil pressure and quantity have no real effect in X-Plane - but I haven´t seen them being low, I think. So maybe you can include a screenshot of what you see so I can tell you if it is normal or not? 4.) Yes, unfortunately our VNAV code still has some problems with altitude restrictions during the descent. We are working on fixing that - for now use the FL CHG or V/S mode to descend te aircraft in time to make the restrictions. Cheers, Jan