Litjan

I think that should not be a problem - if you run out of activations just shoot the team at X-Aviation a mail, and they usually don´t ask twice about it - unless you went through 50 or so already ;-) Jan

Thanks for the report and the log! Jan

Ok, very interested in how you got the .84 - if you could create a short movie of what happened, that would be very helpful! And no, the VNAV should stay on the current path and plane, until you execute. Of course you could have a VNAV DISCONNECT while MODifying the current plan, if the plane gets too fast, for example. Jan

It is in the email from X-Aviation, alerting you to the 1.0.2 update Jan

Did you read the threads above? I think an upgrade for your OS might be the only cure... Jan

No, it shouldnt! Can you make a video for me? Thanks, Jan

No. Look at tutorial #4 for information on how it should look like. If you don´t want to fly it in LNAV, use the full rose or expanded rose mode with the correct radial dialed in. The "diamond" only shows for ILS approaches. Jan

Here are some threads that might help you as well: http://forums.x-pilot.com/forums/topic/9207-sporadic-fps-problems/?page=2#comment-99205 http://forums.x-pilot.com/forums/topic/9178-massive-sudden-lag/#comment-100342 http://forums.x-pilot.com/forums/topic/9465-fps-crashes/#comment-100120 Jan

Ok - thanks for the initial feedback - I would like to see the effect kick in - so maybe take off, get LNAV and VNAV going, then start rolling the tape. Do the "direct-to" waypoint thing, so you capture the effect of the frames getting bad. If you can, EXECute, so the frames go back to normal... then stop the movie and post it afterwards? Thanks, Jan

Crap - ok, can you give me the sequence of what you are doing? Ideally a short movie? I would really like to get this one fixed for everyone! Thanks, Jan

Thanks for the feedback, Jailer! And no, its not solved, we just "mass locked" those threads, because people kept posting their stuff there and we were worried that we might not see them... Jan

Wow, thanks for putting all this research into this! I think the intended behaviour for the fuel is "always start with the amount the user sets up once" - so the guy that always wants to start with 5000kgs doesn´t have to drag the sliders everytime he starts X-Plane. Setting the "current fuel on exit" would defeat that purpose... I personally think that we might want to revert to the old "fixed" system for the fuel - and maybe tell users how to edit the value in the prefs.txt... Jan

Hi and thanks for the great report - yes, initialization is a total pain in the rear! It is all dependent on what is being called first, I don´t understand much about it, but you can even assign a button to "reboot" gizmo - so maybe just clicking that once the sim ran for one second is your best bet for now. We will continue to improve this aspect, but it is a total can of worms, from what I heard... Jan

Yes, that would have suprised me. It must be a problem with your computer not having enough computational capacity to run the calculations during the MOD phase...so something is stopping it from calculating well. Do me a favour. Spawn at TXKF. Output the framerate on screen. Plan a flight to KJFK, pick any STAR and approach, then fly direct to the first waypoint of the approach. Now start taping a video (CTRL-space, iirc) in X-Plane, then do the MOD thing (shortcut to the second waypoint) and then post the movie here or on youtube. I think we need to see what is going on to be able to guess the problem. Did you check on the other possible culprits? Virus scanner? What OS are you running? Is it the latest and newest OS? Jan

Hi Franz, I see the same thing on some STARs and transitions... we will need to start "tuning" the VNAV calculation process over the next weeks - for now we concentrate on clearing the crashing... Jan

Hi Tom, always good feeback from you! I think you are right, using a button will not trigger the disarm light... I get this a lot now that I am testflying on my laptop... Will check that out. The "USING RESERVE FUEL" message isn´t implemented yet - but on the list! Cheers, Jan

Have to check the real page, but could be! Jan

You are right. It is on the list! Jan

Ok - in this case it should stay - we will take a look at that! Nevertheless, even with the switch in GRD it should work... (just no pre-pressurization on ground). Let me know if you see the AUTO FAIL light again without doing something that might trigger it (power failures, resetting the plane, having window open during flight, etc.) Jan

They are in the X-Plane 10\Output\preferences folder. You probably only need to remove the X-plane.prf file (move it somewhere else and see if this helps!) Jan

Thanks for the report, Philip - let us know how the thing with the lights goes! Jan

Well, you can not have both at the same time - but if the speedbrake is not assigned to an axis, the buttons should work... If all else fails, you may need to delete your X-Plane preferences, I think the button assignments can get messed up (we had a lot of users saying that B is assigned both to brakes and to the rotating beacon...) Jan

That is very good news! We (Nils) worked hard to get our sounds to be more economical, and it is still possible that people with crappy sound-chips may have some problems. So we are especially happy to hear that this improved for you! Jan

Can I get a pic of this with the whole instrument panel (also the MCP) showing, please? Jan

Thanks for the report - skipping a waypoint due to too much distance while passing... Its on the bug list! Vielen Dank, Jan