Litjan

Thanks for the feedback, gentlemen! Jan

Thanks for the feedback - we continue to optimize our sound code to have as small a footprint as possible, but if other code is taking up sound resources and there are not enough available it is tough. But your report gives us another idea to test... Thanks, Jan

No, its not Tequila (unfortunately) Jan

Thanks a lot, guys - we have something cooking for you as we type - development continues! Jan

We see some issues with people that have soundcards that can´t play enough sounds and those sound slots are already taken up by other, sound-intensive add-ons... We have also had the odd report where people turned down volumes by accident. Then people got sounds again after rebooting, so there is definitely some vodoo involved, sometimes. Let me know if any of these hints helped you get your sounds back - best regards, Jan

Ah, I see - so basically CH was added to the END of your routing, instead of the first point... I will have to see if I can reproduce that, looks indeed suspicious . Thanks for the report, Tom! Jan

Yep, this has been the bane of Tom´s LEGs page editing efforts - when you add a waypoint to the route that already exists, you will usually "shortcut" to it - but sometimes you don´t want that, especially if that waypoint is like the last point of your route. Many Routes pass the same waypoint twice, once as the IAF, and then as the last waypoint with a hold... We will have to revisit these cases - and I see a solution when we start implementing "derived waypoints" where we need to add a numbering tag to waypoints to keep them apart... Let´s see. Jan

Absolutely - and always has. I suggest reading up on the logic behind that before posting bug reports, though - it is a pretty intricate system. Jan

We will look into A/T tuning in the future - but it is a fine balance between it being too springy and too sluggish. The real autopilot will also over- undershoot the target values on occasion, but it shouldn´t do so by 20kts, that is true. Jan

Hi, hard crashes are usually related to other plugins or scenery installed. A hot candidate in your case is MrX6s San Diego Scenery. It has been causing crashes for many people, and so far he has not been able to figure out why that is... So I would go with that first (just add a _DISABLED to your scenery_packs.ini) and hope that fixes it. Good luck, Jan

Definitely a bug you saw there, Tom - thanks for the report and keep them coming! We will need to proof the FMC outside the "regular use envelope" in the future, like what happens if you do something really odd. We concentrate on getting "normal use" right, first, but are going to field more and more of the oddball stuff in the future. Jan

Correct observation - and known already. It is quite funny that this seems to be quite a job to fix, Nils is usually very quick about these things, but it has been known for a long time (since way before release) and it will just require a lot of time to change. Definitely on the list, tough! Jan

Yes, I am seeing the same issue - and it is indeed more obvious if the framerate is really high - we will look into it. Jan

Yeah, this is completely normal and I have seen it like this (or even worse) in the real airplane many times. IIRC the thrust levers were allowed to be about "one knob apart" at the same N1 and it was still considered to be in limits. And the acceleration in your movie was also fine. Also be aware that "engine age" is random between airplane loads. Jan

No need to apologize at all! This stuff is incredibly complicated and I often refer to my manuals and real pics and vids when trying to figure out how stuff is supposed to work ;-) Cheers, Jan

I would put some money on the guess that all the many payware add-ons you flew did not simulate the 737 - 300/400/500 series? If that is so, then it is easily explained by the fact that these "other" Boeings have an autotune feature that will both set the ILS frequency AND also the inbound course (as read from a database). So no dialing of the inbound course is required. Jan

Hi, During Takeoff, the autothrottle will enter "Thrust Hold" mode at 84kts. It will simply not move the levers anymore. This is going off of IAS, so with a headwind and a rolling take-off you might see that the set N1 is never achieved. You can alleviate this by moving thrust levers to get ca. 40%N1, then release the brakes and push the TO/GA buttons. Also note that the carots on the N1 indication are always at FULL takeoff thrust, but if you set a TASS, this is what the autothrottle will aim for. For the go-around, the correct rollmode is "BLANK" - but the flight-director will give you commands to maintain the "present ground track" at point of TOGA press. For the take-off this should be HDG, though - are you sure that both FD´s are on (this is a prerequisite for the takeoff mode to work). Jan

Here is a link to a movie (220MB) I made with my camera while taxiing on the runway at EGLL (X-Plane 10.50). Can you take a look and tell me if this is similiar to what you see? Thanks, Jan https://dl.dropboxusercontent.com/u/9681692/737%20taxiing%20EGLL.MOV

Absolutely - what you are experiencing sounds completely unacceptable and we are determined to find out why this is. I will make a short movie with my handheld camera (videocapturing software tends to introduce some lagging sometimes) and post it here so you can see how it runs on my system - then we can compare to figure if this is akin to what you see on yours. Jan

We are simulating 10.7. Jan

Hi and thanks for the input. We never used a derated take-off on my airline, so I was not sure how the real behaviour is, and the manual isn´t quite clear on it. If you can provide me with a reference where selecting a "full power-no TASS" takeoff at the TO-1 or TO-2 derate shows R-TO on the TMA, I would be grateful and we will change this in the future. After all, nothing should remind you that this is not the real thing! Thanks, Jan

Hi and thanks for the feedback - I will try to reproduce the fluctuation with lower FPS. We had some problems with that one initially, and maybe we can tweak some more... The Wing-Anti-Ice won´t open on the ground - so you will just see the "bright blue" until you lift off (unless you utilize the ground-test function, but that will only work for a few seconds, then the thermal protection will close it again). Also note that you are not allowed to use the APU for wing-anti-icing - it is placing too much stress on the APU. However, it should operate the valve, I will look into that. Can you send me another screenshot of the valve failing to operate during flight when pressurized by the APU? Thanks, Jan

Yes, plenty of information related to its function occurs. The function is so developed and not a failure. Jan

Ah, yeah, that one. You have to push it to show "fuel used" (it will switch back to fuel flow after a short while). Jan

Hmm, I am not quite sure where the button referred to is located...? Jan