Litjan

Hi Michael, thanks for taking the time and effort to validate this in the full-flight sim! I will check again in our upcoming patch to see if we are good... Cheers, Jan

Yeah, we need to run a solid quality pass on the VNAV - it works ok for standard situations, but once the descents get more intricate (with lots of restrictions, etc.) it doesn´t do so well. The "UNABLE CRZ ALT" warning is usually a sign that you are asking too high a crz alt for the route distance, i.e. the plane can´t make it up and down in time. This may be compounded by restrictions on SID and STAR that force a flatter profile... The "CHECK ALT TGT" message says that your MCP alt is set in the opposite direction of what your FMS expects. So if you are at 5000, your cruise alt is set to 10.000 but you set the MCP alt to 4000, you would get the message ("huh? don´t we need to climb to cruise alt, first? Why do you want to descend already??") Jan

I would think that you were too fast - VNAV will only allow your speed to go 10kts faster than planned - if you (for any reason) are faster than that, it will disconnect (saying: "hey, pilot, I am in over my head. Do something for your salary and get me back on profile, then we can try again"). Once you are back at the (or close to) the planned speed, you can re-enable VNAV. Jan

We will see... Jan

Sure. The VOR is sending out a dual-phase signal, the on-board receiver can detect which part of the "phase" he is on - and hence determine the radial it is on. This in turn allows the pilot to know which way he would have to fly to get TO or FROM the station. So if the detected phase-shift is 180, you must be somewhere "due south" of the station, so flying 360 would take you right to it, while 180 straight from it. https://en.wikipedia.org/wiki/VHF_omnidirectional_range The ILS localizer antenna is creating two overlapping beams, one contains a "fly to right!!" code, one a "fly to left!!" code (simplified). If you are straight in the middle, both infos cancel each other out, and you know you are centered on the LOC. https://en.wikipedia.org/wiki/Instrument_landing_system_localizer However, you (or the plane) have NO idea which way to fly to stay there! Imagine the runway is 36-18. You are ON the LOC. Unless you know that the LOC is running 360 degrees, you will have a hard time staying on it. If you know that its APPROXIMATELY north, you can react to the drift in time - so if you fly 355, you will notice it drift to the right, and can correct. But if you start out flying 270 degrees, you will be in the "fly right!!" zone so deep, that you have no idea how far right you need to go, to get it centered again (280? 290? 330?) You can observe this in the 737. Pick KSEA 34R. Dial 325 into CRS1 and intercept the LOC. The plane will INITIALLY turn to 325, then goes "whoa, this loc is running to the right like crazy, better bank to keep it centered!". Once it tracks it, you will find that its keeping exactly the correct course (to null the drift). If you have a crosswind (but set the CRS correctly), the effect is the same. Plane turns to inbound course, but notices the "drift" away from the LOC and corrects. Hope this explains it, Jan

Thank you, a know bug that will be solved with 1.1. It happens whenever you enter a runway without an approach in the FMS. So RWY09 wont work, but ILS09 would. Cheers, Jan

No. Cheers, Jan

Correct behaviour. Only shows set N1 when the "manual N1" knobs are pulled out to set N1 manually. Cheers, Jan

Thanks for the report - I believe this may be fixed in 1.1 - do me a favour and re-fly the scenario when(ever) the patch comes out... Thanks, Jan

Set the correct inbound CRS. If you need additional help, make sure to watch ALL the tutorial videos, this stuff is well explained there. Happy flying, Jan

We have the patch pretty much ready to go - we need to compile it into an installer and then run a brief beta-test. We can´t really estimate how long this will run, it depends on how much stuff the testers find wrong with it. We have found out that the IXEG will initially not be compatible with XP11 - so it will take a while for us to adapt to XP11 and get our aircraft running with it, as was to be expected. Cheers, Jan

This is normal and not an IXEG problem. Happens with all other aircraft as well. Reason is that runways are not placed correctly in the X-Plane world, sometimes. You need to set the CRS selectors to the correct inbound course, otherwise the plane does not know which track to align to initially - this is the same on other aircraft as well, they just set the course automatically from their database (modern aircraft). The ILS signal contains no course information, only "you are right, you are left". But even if you set the course slightly wrong, the plane will still track the localizer exactly (it will just "think" there is a crosswind). Cheers, Jan

Also noticed that there can be situations where the plane runs out of trimrange when CG is fairly aft and speed is very high. We have to investigate if this is normal or something we need to fix. The trim set for takeoff (green range) has nothing to do with the trim during cruise, so that is not a lead, though. Thanks, Jan

We have fixed a bunch of reasons for crashing with the coming update 1.1. Once that is rolled out, please report again any crashes you see, and we will hopefully fix those more rapidly in a "hotfix" situation! Spaciba, Jan

Thanks for the report, we expect to squash a bunch of these with 1.1 update! Cheers, Jan

Need to try that! But will wait until they support HDR... Thanks for letting us know, Vitaly! Spaciba, Jan

No.

You are right - but it´s not on the one that we portray ;-) Cheers, Jan

Hi sthenion, why don´t you send me a PM with the changes you made, so we can check them out from our side - and then either incorporate a change for everyone, or post this as a choice for advanced users to make. Thanks, Jan

mmerelles is correct - but I am not sure if we will update the oil temp in 1.1 - it is really not a showstopper, but it requires a LOT of research and coding to get right (across all ambient temperatures, airspeeds and engine states)... In a way I feel that providing an accurate engine model is really on X-Plane´s table, not so much on ours. The current bypass engine modelling of X-Plane is rudimentary at best and we had to make quite an intricate coding cast to get N1´s and thrust correct. I will approach Austin in the future (once the dust settled around 11.0) and may work with him to get a good and customizable bypass-engine per default, and that should then yield realistic oil pressure and temperature values as well. Jan

Most definitely

Just do me a favour and re-check your settings for all virus- and anti-spy software. We had instances where people turned off those programs, but then they somehow "revived" themselves... So check with windows defender, avast, anti-vir, etc... This is just to make sure that we are not chasing the wrong rabbit, here. Thanks, Jan

This is what it looked like on our planes:

Its still "processing" - let me know if you still can´t see it in an hour or so... Thanks, Jan