Litjan

Hi and thank you for the bug report - I will try to recreate the same thing on my machine so we can fix it! We have possibly not caught it because no one would try to enter PASI on LSK6L before... Cheers, Jan

Happy that you got it to work - as an interesting side-note, there is the chance that the start switches get "stuck" in the GRD position (although I never witnessed this in 10 years of flying 737s) - so the FO has to now call "starter cutout" when they do - and if they don´t he manually moves them back to OFF (just like you did). I have added your request for datarefs to the list, lets see what we can do! Cheers, Jan

Works fine here on XP11.20vr1 - maybe there is a plugin conflict or a hardware switch or lever assigned to "starter"? Cheers, Jan

Will be fixed in next X-Plane beta. Jan

Thanks for everyone´s input - your concerns are duly noted and also shared by me. It pains me every day that I testfly our 737 that it is not complete yet, and I have to be patient and wait for the other team members to have time available as well. I KNOW that our plane is worth 75$ - even in its present state with some aspects unfinished. I find the statement "FMC is nowhere to being really useable" a bit of an exaggeration. I flew the 737 classic around Europe for 10 years and I could have done it easily with the state the FMC is in now. The thing I miss the most is the progress page, its just too convenient to know when you will arrive and how much fuel will be left...holds, pbd, offsets, abeam positions, VNAV descent restrictions - don´t get me wrong, but missing these is not making the FMC "unuseable". I know that many customers can not understand the care and detail we put into simulating the systems (electric, hydraulic, pneumatic, pressurization, ice+rain, flight controls, landing gear,...), the flight-model, sounds, textures, autopilot modes, etc - simply because they don´t care to explore that aspect of the aircraft and/or don´t know the real aircraft to make an educated comparison. Just as Morten said - we are painfully aware of the fact that work remains to be done and are working on improving our product right these days. Cheers and happy landings, Jan

According to Sydney Just from Laminar this will be fixed for the next VR beta. Thanks to Ben Russel for helping out in making the connection with Laminar and bumping the bug with them! Cheers, Jan

Honestly - no. We are a bunch of devs that do this in our free time besides our "real" jobs - the VNAV turned out to be way more complex than expected, and we needed to finally get the plane on sale when we did. The one person in our team that can finish the VNAV (we probably need to rewrite a good chunk of it) is sidetracked by his real business and does not have time to tackle VNAV right now. We ARE planning to finish this, but unfortunately I can not even give you a timeframe. The plane is 75$ and it is incomplete at this point, no doubt about it. Is it already a lot of fun and worth 75$? I personally think so. But if you expect "completeness", don´t buy it (yet). I am part of the IXEG team and love to make a sale, but I won´t lie to you or try to convince you to so something that you will later regret. Thats why we also highlight the shortcomings of our aircraft in this thread, for everyone to see: The list should be up-to-date (will go over it really quick). I am sure the other users did not mean to be condescending - but we have a LOT of people that couldn´t fly their way out of a whorehouse (is this the correct figure of speech? ) without LNAV and VNAV and when people start complaining about lack of fully automated flight the suspicion lies close that these features are sought after for lack of ability to cope with selected modes (or even - gasp - manual flight). Cheers, and all the best, Jan

Only for very simple descents - if using VNAV on more complex arrivals (with restrictions) is important to you, I advise to hold off on purchasing this aircraft. Cheers, Jan

I have never heard of a problem like that - we are using the default dataref for "height above terrain" to trigger the callouts. I suspect a clash with some other plugin you use or some special sort of scenery (which gives a wrong return in radar altitude). Cheers, Jan

I would say: "We are not ruling out making one at one point in time."

I can confirm the displays not working properly with 11.20vr1. I have filed a bug with Laminar Research and hope that they know what may have caused this. Cheers, Jan

Your installation went wrong, gizmo plugin is not running. Try to reinstall and follow the instructions exactly. Good luck, Jan

Hi Niall, there are several possible reasons for this. You can attach your log.txt (you will find it after the incident in the main X-Plane folder) and attach it here, so we can take a look at that. There is the possibility that a plugin you are using is causing this, that is why Ben asked you to try on a clean (or the demo) copy of X-Plane, you can also remove your plugins (just disabling them when in the game is not enough) by temporarily moving them into an extra folder to possibly isolate the problem. Another possibility is that your preferences accidentially set a button or key to "reset aircraft" function - you could check if that happened (scan your key and joystick bindings with the search for "reset"). Cheers, Jan

That you would have to ask my mother .

it´s Friday...again

Yes, I have heard of similiar problems from other users using Spadnext. I never even heard of Spadnext, so I can´t comment on what the incompatibility seems to be. Cheers, Jan

The light values for the landing and taxi lights are accessible in Planemaker, and you can increase and tweak them to your hearts content, I think. The engine values are a custom calculation that we do - the planemaker values have little to do with the thrust output. Jan

In other words - the proper mode for a smooth descent in your situation would be the V/S descent mode. You *could* use FL CHG, but you would need to advance your thrust levers again (after the RETARD-ARM cycle finishes) to add some thrust - that way the plane would descend less steep. Jan

Double check if windows defender is causing the problem, then, please. It re-activates itself sometimes during updates, and that has caused confusion before. Not making edits on the FMC during flight is really the worst solution and would severely hamper the enjoyment of our product... Cheers, Jan

http://forums.x-pilot.com/forums/topic/12240-solution-to-freeze-and-stutter-when-modifying-the-route-in-the-fmc/

Thanks for letting us know and I am happy that it is working for you now! Merry Christmas, Jan

Is it crashing or just gettting very slow?

Lol, and your Captain did not hit you on the head with the weight-control folder???

There are many thousands of users flying version 1.2 in XP11. You and Jolmos are the only ones having problems with the VOR and ILS radios . Jolmos is not an advanced member, he is a member who has had many problems and complaints with the IXEG 737 . I am not saying that our aircraft is without faults, but there are users that have only the problems that everyone has, and there are users that have "all sorts of problems" with our aircraft. http://forums.x-pilot.com/profile/28924-jolmos/content/ If you look at the youtube streams coming in (still), you may observe that no one seems to have problems with getting ILS or VORs to work. Here is an example, posted less than a day ago. https://www.youtube.com/watch?v=hn_yWzQHIa0 I would be the first one to move heaven and hell if our plane had problems receiving ILS and VORs, but in this case the evidence is strongly pointing at you (and maybe Jolmos) having something screwed up on your computers for it not to work. And we can´t patch around that. Jan

Thanks, Craig. I know that this point is hard to believe for the general public - just like the fact that "heavies" are not lumbering monsters that can bank at a maximum of 1 deg/minute, either . Especially since "other" aircraft circumvent this discussion by simply giving the customers what they expect. Cheers, Jan