Litjan

jolmos, are you describing the headshake option? We try to emulate the turbulence and unstable air that is prevalent at lower altitudes... and as Pinky Ponk correctly said, if you don´t like that, you can turn it off (Deselect "Enable camera shaking". Cheers, Jan

Sorry to hear this! Have you checked that your "failures" are set to NONE? The default is a certain amount of failures in X-Plane, this includes locking of flight-controls, iirc. Cheers, Jan

Yes, you can also deliberately duck under the glideslope and crash the plane into some forest. That will also get you out of APP mode! Jan

Well, don´t hope for them to come from us . As a matter of fact, don´t expect to ever get the same performance framerate-wise in XP11 that you had in XP10, but that should be obvious. Cheers, Jan

Thanks - we will keep investigating, but of course I wouldn´t object if Laminar just fixed it on their side ;-) I do get some autothrottle problems (slow reaction, not setting correct power, hunting back and forth...). Do you see any of that? Cheers, Jan

Agree with you, Tony - it is pretty usable for a public beta and I really like it, too! Cheers, Jan

VNAV works ok for basic flights - it starts having issues when the vertical parameters are getting complicated, like many speed and/or altitude restrictions... We plan to overhaul and improve on that in the future. 1.1 will not have any fixes regarding VNAV, beyond curing whatever gizmo-soft-crashes were caused by it. Jan

Not a promise, but I think we MAY get rid of the gizmo error on startup with one of the next XP11 betas...it is due to some dataref change that Laminar did. I also have some inconsistencies with the pop-out menus, I often can´t access the XP11 toolbar (on top edge), but haven´t found out what is causing it. There are some other minor items, but I think we will be able to conquer those soon after starting the port. Jan

Hi Tony, I don´t think it´s an IXEG problem...many users report that sort of thing with all sorts of aircraft, I expect those problems to get ironed out in further XP11 betas... Cheers Jan

The plan is to apply the new XP11 features wherever they are appropriate and warranted. It would surprise me if that would exclude the cockpit. Jan

I just got something in my eye! Thanks for sharing! Jan

Yes, our current asessment of the porting process is: Fairly quick (with a bit of Laminar´s assistance in getting some dataref´s straightened out) making it "work" in XP11. A little bit longer to really take advantage of XP11´s new shaders. We need to update the material´s properties, shaders, etc. Here is a quick view of how things CAN look in XP11 (varying levels of "shinyness"): Jan

The VNAV SPD DES is in effect a FL CHG descent - the plane will simply descend with idle power and stay exactly at the specified speed. The difference to FL CHG is that it will level off to honour altitude restrictions (I think) , and it will also honour speed restrictions (like slowing to 240kts below 10.000 feet). So it is a bit more comfortable and less error-prone. I am not very familiar with the SPD descent, since I have never ever used it in the real aircraft. Cheers, Jan

mmerelles is right - in addition there will be an INOP label on the logo lights when winglets are enabled in version 1.1. Jan

No, this won´t make 1.1, sorry. Cheers, Jan

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