Litjan

Yes. The light says "autobrake disarm". It says so, because when it lights up, the autobrakes are disarmed. In other words - they are not working. The reason is because something is "disarming" the autobrakes in your aircraft. I tried to explain how it works, but I feel we are going in circles - it is pretty complicated system. The autobrakes are working fine on this aircraft - just like they do on the real aircraft, same logic. If you can´t get them to work, I would suggest just using manual braking - this is perfectly acceptable. If you really want to find out and understand the system, I would suggest to google "737 autobrake system" and I am sure you can find a good explanation online. Cheers, Jan

Well, we had almost 90% in favour...but that means that we would still make over 10% unhappy, if we removed it. And we don´t like to make users unhappy (more than absolutely necessary). So it will be the best of both worlds: We will add an option to the preferences menu. Thanks to everyone who voted, Jan

There certainly is room for improvement. We have increased external lighting already a bit (landing lights, taxi light, turnoff lights) - and will certainly look at other external lights over the course of the next weeks as well... Cheers, Jan

Yes, please let me know how it goes! You paid a lot of money for this aircraft and I am proud of what we did...so I want you to fly it!! ;-) Cheers, Jan

Hi Jim, don´t worry about my flying - I am grounded indefinitely due to this Corona thing. If my company doesn´t survive you guys will have to deal with me here all the time... ;-) Anyway - I think your hardware is the root issue here - especially the external harddrive. All components are woefully inadequate to run XP11 at a decent clip and especially the external drive (yes, it is an SSD, but the connection to your computer is going to be so incredibly slow...). There are a couple things you can try to verify this (before you go and buy a real computer ;-): 1.) Drag all your X-Plane graphics settings sliders to the bare minimum 2.) Load the IXEG up at TXKF (Bermuda islands airport) Make sure you have set up NO (as in zero) AI aircraft! Make sure you disable all your other plugins, especially the X-Life, Better pushback and ATC Chatter by jardesign etc. Lets see how that goes? Cheers, Jan

I have registered the request. Paschalusta!

You mean like in more polished/reflective?

Hmm, did the "autobrake disarm" light illuminate during the landing roll? Or maybe the plane IS braking but it feels like it is braking too slow? All I can say is that it works fine on my end. Maybe you can tape your landing and post a youtube video of it (showing the region of the instrument panel, engine instruments and autobrake switch...)? Cheers, Jan

Hi Jim, what you are describing does not sound like a problem with the antivirus...this usually only rears its head when you have an active route (with several waypoints) entered into the FMS and then modify that routing. If you are encountering lags of this magnitude while only aligning your IRS units, something else must be going on. Can you please attach your Log.txt file from the main X-Plane folder? Also, do you run your software from an external (USB-) Harddisk drive? Which X-Plane version are you running? Cheers, Jan

Ok, try again with thrust at idle - thrust levers must be at the rear stop for the autobrake to work. It is a safety feature - otherwise the brake may try to slow down the aircraft if the pilot wants to abort the landing and take off again. No, the oil quantity can not be changed by the user...and just to quantify the urgency if this as a feature request - this is the first time I heard someone have a problem with that ;-) If you find the oil quantity at dispatch (engines off) be at 3 gallons or below...then we would have something more urgent to fix (minimum dispatch amount). Cheers, Jan

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