Andrey Novikov

I do not see any problems in XP11. I never rotate rheostats to full brightness. For me setting them to half is enough to clearly read all gauges.

Looks like result of rendering in some 3D modeling software. External lights in X-Plane are not so cute as on the picture.

I'm writing a Lua script for automatic cabin crew announcements. Currently I have welcome message, safety instructions, meals and drinks, start of descend and before landing announcements working. Next I want to implement "welcome to destination" announcement. To properly differentiate landing at destination from emergency landings I need to know if I'm at destination airport. FMC shows distance to destination airport on a PROG screen. This is what I need. Can I access this data from Lua script?

@63 Degrees Right -

That's the best present for my birthday.

It's a known bug. RNAV works ... sometimes. So it's better (and more realistic) to plan descends by yourself.

Yet another question regarding recent TCAS video: I do not know how X-Plane TCAS system work, so I wonder will it work with X-Life and Vatsim traffic?

I've tried to set flaps 15 without gear down during approach to Innsbruck. Warning horn started to sound. I've pressed horn cutoff button but it didn't turn it off. Do I misunderstand the purpose of this button or it does not work?

Concerning pushback and ninja-fixes - would ninja-fixes addressing taxi also fix plane crashes during pushback?

For VNAV to be calculated by FMC I have to enter STAR for destination airport before route activation and execution. But as I know the STAR is supplied by ATC just before or during descend. How is it done in real world?

VNAV simply does not work. Most of the time T/C and T/D are calculated incorrectly. It's not 1-2 miles shift, it's 10-20 miles error. Many times it says "Unable CRZ altitude" but in fact there is a reasonable level flight segment for that FL. Changing route during descend due to RWY change is a nightmare. You will either get software crash or crazy AP behavior after new route execution. In "real" life you can ask for vectors, but flying offline expect all your approach to be messed unless you cheat. What I've ended with is not using VNAV at all for descends (and someone on this forum was right - it's a great fun to calculate everything by yourself) and switching to HDG in case I need to amend route until I'm pretty sure that new route is not messed. Another thing I'm very disappointed with is that IXEG do not use built-in simulator commands for many systems. You have to write scripts and assign yoke buttons to custom commands to be able to manipulate them through hardware buttons. This makes switching to other planes a real pain in the ass! I hate this! Sometimes I want to fly another plane just for fun but I have to spend 10 minutes to reconfigure my yoke buttons! What else? The way how cockpit is modeled is outstanding! It's 12 points out of 10. You can not look at other aircraft cockpits after you have "visited" IXEG's one. But external visual model is acceptable. Not even good. It is acceptably good at daytime but at nighttime it's not good at all. I prefer flying at night and this fact disappoints me very much. And, yes, I like to watch replays of my landings from the outside. This is the part of simulation that amuses me.

Just an advice: remove X-plane configuration folder and it will start like just installed. I did this when I changed some graphics settings and it crashed and refused to start anymore.

It's very very very buggy. It's very very very unfinished. It's very very very cute. It's very very very addictive.

Good, thanks!

Thanks a lot, Jean! Everything looks self explanatory except `create_command` function. Where can I find API reference? I'm curious about last two parameters and why function call is inside double-array (if it is double-array).

Can someone show an example of such script? (Lua) I have added some hardware switches but do not know how to read their state and how to manipulate datarefs.

Developers read this forum.

I assume that this may be a bug in my hands not in the plane but I can not get used to how auto-throttle work. Example one During continuous (or late) descent being on final approach with autopilot off and auto-throttle on when I further release flaps it gives too much power and plane starts to level. I try to retain descend gradient but then AT reduces power and that increases vertical speed. I continue to struggle with AT In such way but finally it leads not to calming the plane but to completely destabilizing the approach. What I do now is disengage AT before intercepting G/S. Example two Ok, may be I'm a factor... But on early descents having autopilot on, auto-throttle on, flaps partly out when plane levels to intercept glideslope AT waits until speed reduces much below assigned on MCP and only then starts to slowly add power. Sometimes speed is so low that plane becomes unstable. (Assigned speed is always 10-15 knots above limits.) My question is how to properly deal with auto-throttle, may be I'm doing something wrong?

IXEG are drug dealers! I've tried to switch to FF 757 but failed. It's good, with lot's of neat features that I like but it's too modern. I do not like flying computers. On the other hand old steam planes are not suited to modern reality of RNAV/GNSS navigation. So I consider IXEG 733 to be a perfect balance between warm feeling of old steam cockpit and modern navigation capabilities. That's why I hate IXEG 733 for its underdone state but fly it madly. It's a real drug!

Dataref is not realistic Thanks for wipers clue.

Worked for me.

Yesterday I've crashed... Not the software, but the plane. After it has hit the ground simulator said that there was ice on my wings. My fault, but it happened suddenly. I was flying nicely and in next second I was falling. So I want to ask if there are any visual clues in real world that aircraft starts to ice? Or it is really so unpredictable?

IXEG 737 is incompatible with XSquawkBox Version 1.3.2: http://www.xsquawkbox.net/xsb/2017/04/known-incompatibility-x-plane-11-xsb-1-3-2-and-the-ixeg-733-1-0-x/ Will be anything done with that (in nearest future)?

The only thing we ask you now is to make it not slide all over the apron into the terminals before engines get started. After that you can fine tune it for XP11 for years. BTW, why, when I start a new flight the plane is like "dropped" from about 1 meter onto the apron?

Have read the hole topic put still didn't catch - have anyone fixed inaudible callouts?