Litjan

Thanks for the log - this will help us narrow down on these problems and fix them! Jan

We support LAT/LON as far as they can be found in the FIX database. Jan

The intersect field will take data for a runway intersection takeoff - either the displacement in meters, or the name of the intersection. In the real plane the position of the FMS will update to the runway beginning when you press the TOGA buttons. If you take off from an intersection, this update would be erroneous, since you are not actually at the beginning. So you can enter an intersection value (i.e. 900m) and the updated position will be correct. If the FMS position is being fed GPS data, this update will not be taken into account - so it does not matter if you enter anything or not. The IXEG 737 will always have GPS updating, so entering anything (or nothing) into this field will have no effect. Cheers, Jan

Ok, so it seems to be widespread - I am already on the dev build for the next version - where Nils did some changing of the pointers for the wind-sound... I think it was previously getting the wrong soundsample. At any rate, I am not hearing anything like this on my build, so I would assume that this is fixed for the first "real" update. We are planning to do one more hotfix before that one, though - and this fix will probably not be part of that (only code, no content). Jan

This is excellent advice, and the way I do it - even in the real plane. The electric trim is too sensitive at those speeds. Grab the trim wheel with the mouse-hand and move just a bit. Jan

Hi, I have not noticed this so far - I will try to reproduce it on my end. Do you have the details of your soundchip handy? Thanks, Jan

Hi guys, this is very interesting and I am not sure if this ties in with the general problem of having a limited amount of sound resources at your disposal or if something else is going on. Could you try and do a flight without the VATSIM or PilotEdge plugin installed and see if that helps with the sounds? If so, that would be a great lead... Jan

No, there is no D-TO to my knowledge. Checking the thrust rating on the CDU is essential to avoid having the wrong "max thrust" selected. On my airling, a derated thrust was never used, not sure if other airlines even do that... The effect of R-CLB washes out to 15.000 feet, but I am not sure if the label will change from R-CLB to CLB... something I never consciously watched in 10 years of flying the plane. Simply don´t know and the manual doesn´t state it clearly, either. Jan

Hi Boki, thanks for the report! We will keep working on these crashes - but to find them we need a lot more information - if you want to help, please read the bug reporting guide in the manual, or at least post the gizmo log so we know what the exact nature of your crash was. Thanks, Jan

Or from any other live virus scanner, like Avast, etc. Jan

I am considering it. Jan

No, you can´t cycle like you do in FSX... Jan

Hi Tom, there are different configurations to the gear warning horn, depending on the model used. The one we model can not be silenced at FLAPS 15 if both thrust levers are < 30 deg. Jan

Pilot error , but very understandable. A "derate" is not a "reduced takeoff thrust". Thanks for the report, though - keep ´em coming! Cheers, Jan

We used to have a problem with the fuel resetting to 0 - which in turn would starve your engines... this SHOULD be fixed with 1.0.5... but let´s keep an eye open for that! Jan

To tell you the truth - I have no idea how long they are displayed. I have never seen "the end" - yet they can´t wrap around the world, or you would see them come in from the other side. I think we made them like 1000NM or so - that should suffice for even the laziest air traffic controllers. Jan

I would put some money on the fact that the missed approach is containing a VECTOR... These go on forever. Jan

Hmm, this is very unusual - we have NOT seen any crashes to desktop so far that I can remember, so I would venture to say that something beyond our 737 must be involved... Jan

Because the file type is not supported...anymore . The reason and discussion is here: http://forums.x-pilot.com/forums/topic/10578-105-no-more-airbus-extended-coroute-flp/ Cheers, Jan

Oh no, there are quite a few excuses in the repertoire of an airline pilot. Birds, CB´s, bad LNAV coding...

Hmm, ok - very odd. Do you do consecutive flights - i.e. land, park the plane and then take off again? Jan

Hi Ethan, I am not expert on these logs - they are all just a bunch of characters for me ;-) I would suggest you start the standard bug incompatibility confirmation protocol. Remove all plugins except gizmo and pluginadmin, reboot X-Plane. Then try again. We found out 99%+ of all problems with this approach. Thanks, Jan

Hi, I can´t download the attachment you placed. Can you describe the crash? Was it a gizmo console opening, or X-Plane crashing to desktop, or the whole computer freezing up? Thanks, Jan

You can install aircraft wherever you want to - just navigate to the folder in the aircraft selection dialog. I am sorry, I am out of ideas. Jan

Thanks for the info - I will take a look at that! Jan