Litjan

Hmm, that looks strange, indeed! Are you running the latest drivers for your graphics card? Also, just for troubleshooting, try to change the texture resolution and anti-aliasing setting to see if that changes anything? Thanks, Jan

So I sleep for 8 hours and this is what I wake up to :-/ I believe that you have a problem with the font - I sometimes run X-Plane on my 4K monitor in 1920x1080 and get a distinct visual downgrade besides the resolution, a fuzzyness, so to say. If I run at anything but full fractions of 4K it gets even worse. I outlined that we know about the readability problems of the menues in 4K and explained why we did not cater to 4K at the time we developed those menues...in addition to mentioning our plans to enhance this in the future. It is your right as a customer to be upset about it or not be satisfied with it - as Cameron said (and you can verify this by searching this forum dating back many years) - this is not a widespread problem (i.e. only one or two complaints about it) and therefore does not warrant an emergency fix from our side. We will get to it when we get to it. Sorry for not being able to offer another solution, Jan

Hi Keith, I already replied to your problem on avsim as well. I know that the font is a bit small on 4k - but it is not hard to read on my screen at all. I use 4K as well, and while I wish the font was bigger (and the boxes a bit more easy to hit with the mouse), it still is absolutely possible for me to do so. I believe that changing the font to something odd like 2560x1440 might have cause the pixels to get blurry - it is always best to change resolution to a full fraction of the native resolution (i.e. for a 4K monitor you would need to drop to 1920x1080), otherwise pixels will get cut off. Let me know if this helps - and we are definitely planning to make the menus work better in 4K! Cheers, Jan

You are right, it is unlikely - but maybe there is some errant axis assigned to throttle? Try to land without using reverse thrust (yes, it is against procedure, but it is possible to fly the 737 with reversers inop) - just to check if that is the problem?

The spoilers get "autostowed" if any thrust lever gets advanced past a certain point (this guarantees that they will be stowed in case of a go-around). Make sure that this is not triggered in your case by some axis assigned to "throttle"?

Hi, first - pilots are trained to always trigger the ground spoilers upon touchdown and in case of a rejected takeoff manually - just as a safeguard in case the automation doesn´t work. We always prided ourselves to yank the lever back before the automation could get to it. The correct procedure for the takeoff is to leave the speedbrake lever in the stowed position. When reversers are triggered (like for an RTO), the spoilers will deploy automatically. The correct procedure for the landing is to set the lever to ARM (and observe the green ARM light) - this will deploy the spoilers when the wheels spin up into the FLT position and then to full GROUND deploy when the strut compresses. If this does not work (like in an aquaplaning scenario) and the pilot forgets to yank it manually - the reversers will deploy the spoilers (like in the takeoff scenario). Cheers, Jan

Well, I am holding up the flag in it!

Hi Lerno1, we are using the default autobrake system for the 737 - it is very close, but not completely the same as the real logic. Especially the fact that it can be disarmed by accident very quickly and will not engage unless all wheels are on the ground. So if you feel that the autobrake is not working well enough for you (I checked deceleration values against the real 737 autobrake, and they are very accurate) make sure that the autobrake is really working. You can check by displaying the DATA OUT values for "gear and brakes". Another possibility is that you set the runway to be "wet" in the environmental setup by accident...and then have temperatures set to below freezing which will in fact turn the we runway to an icy one with very bad braking coefficients. Cheers, Jan

If worse comes to worst I could take this as an opportunity to redo them...maybe with XP12 .

Hi there, I just checked - you are right, I can´t call the up, either... I will try to find out why that is! Welcome back to flying the 737, Jan Edit: In the meantime, here are some more videos I made about our 737, like what the "recent" updates brought and also some further system explanations... https://www.youtube.com/playlist?list=PLGRsg_6rB1D6f7lKjdw5r9P99swJtryhQ

Hello and thanks for the nice words! The FD in TOGA mode will only work if both FD switches are on. This is the same as in the real aircraft. Make sure you turn the correct one on first (left if you are sitting in the left seat) - this will light up the little MA lights (master) and determine which flight control computer is master and references the on-site VHF nav radio. For example if the left FCC is Master and you tune the ILS on the right NAV radio, you can not engage the APP mode. The red gear lights are part of the gear warning...I don´t recall the EXACT logic off the top of my head, but if power is idle (and flaps not up?) the lights will come on. Cheers, Jan

Hi, this is what I have set up and what we recommend for the 737:

Yes, that should be the case. Let´s take a look at the log.txt, then - it should show what part of the vrconfig.txt is creating a problem in your case. Cheers, Jan

Hi, 1.) These are "special" detents - when you fly a go-around, you will retract your flaps to 15 for a normal approach and to 1 for a single-engine approach. The gates make it impossible to move the levers past these detents "by accident". A safety feature. 2.) There is - but you need a second crew member in the cockpit to say it (just like in real life). There is no automatic callout. Maybe ask your wife, or your brother... ;-) 3.) That is correct - we are thinking about implementing something for the avitab that allows reading the checklist (you can also manually add that .png into the avitab folder and access it there). Cheers, Jan

Hmm - are you running the latest version of the IXEG 737? It is 1.33 - and a lot was done in the latest version to improve the VR experience. If you do run the latest version, please attach your log.txt file (found in the root X-Plane folder) here and I can take a look what X-Plane is complaining about with regard to the VRconfig file. Thanks, Jan

Glad you got it to work and thanks for sharing your findings. This may help others with the same problem immensely! Cheers, Jan

Good morning! Interesting - there is no obvious "smoking gun" in your log.txt, but you are running quite a few plug ins that are historically kown to be very invasive and weak in compatibility...especially when not updated to their latest version. I personally doubt that Windows 11 is the problem. I would suggest the following: Move all of your plugins (except for the ones needed to run X-Plane and Gizmo) out of your plugins folder. Just move them, don´t delete them (so you can move them back in one by one). Also move any Custom scenery you downloaded...basically we want to have a "Vanilla" X-Plane with just the IXEG installed. Run X-Plane this way and see if the IXEG 733 works fine. If it doesn´t, make sure to update all drivers, but I suspect it will. Then move all plugins back one by one (or in batches) until the crash returns. Once you have found the conflicting plugin, make sure you run the latest version of that plugin and try again. If that doesn´t help, we can further investigate why we crash in conjunction with said plugin. Thanks for your help! Cheers, Jan

Hi NeoLux, this is pretty unusual - can you describe further what you experience? What kind of crash is it, a blue screen, crash to desktop? Can you attach your Log.txt so we can see if there are any error messages? The majority of problems are from incompatible plugins or other add-ons, but X-Plane can also crash from memory exhaustion. Windows 11 is still in beta, so it might also play a role in this incompatibility... Cheers, Jan

I agree that this would be nice to have! I can´t imagine that it would be too much work...I will put it on the list! Ideally this would be an option in Avitab (like most other options as well)...it should be possible to use all options while in VR! Cheers, Jan

Are you running HDR? It is required for all lighting to show up properly.

There is a position on the switch for the position lights that is labeled "ON BAT" - this means that the external position lights will be powered off the HOT BATTERY bus, even if the battery switch is off. The intention is to make the aircraft being lighted (to avoid other vehicles crashing into it) when it is parked on very dark areas. Best regards, Jan

No

I recommend using FL CHG as the descent mode for now - V/S for smaller altitude changes. You can also use the "descent calculation" table I provide to view in the avitab, or in an external viewer. It will give you a ballpark figure for range vs altitude in an idle-power descent. Cheers, Jan

The spoilers in flight should only be deployed to the FLT position - above that "buffeting may occur", says Boeing. One of the skills in flying a jet airliner (and especially the 737) is to plan your descent so you don´t need the speedbrake. It is a mean of "destroying energy", so a good pilot will rather start the descent earlier...and save fuel that way. Think of it as approaching a red light. A smart driver will get off the gas and coast when he sees a red light, not speed up to it and then hit the brakes last second. Cheers, Jan

Thanks for the nice offer! Currently the development is halted because Tom (the other team member) is tasked with a lot of work for Laminar Research and the upcoming XP12... no idea when development on our 737 will continue, but we have a long list of things that we still want to add. I am personally already flying version 1.34 with a lot of "small" fixes...but we do want to get some big ones into the next update (whenever that will come). Anything else we can help with in the interim, please just ask! (Also make sure you watch the videos on my channel here: ) https://www.youtube.com/playlist?list=PLGRsg_6rB1D6f7lKjdw5r9P99swJtryhQ Cheers, Jan