Litjan

Hi, I think we have seen this problem crop up in alot of departures - let´s see if Tom has the fix for that for 1.0.5 - if not, then it´s on the list for sure! Jan

Hi Kyrre, that does indeed look a little off - thanks for the report! Yes, the 006 means that the lowest elevation shown (the black area) should have nothing higher than 600 feet. Note that we don´t show man-made objects like buildings, just terrain. Jan

Your KLAX looks ugly! Why don´t you have at least the default KLAX showing? Is your X-Plane updated to 10.45?? Jan

Yay!

Thank you, Jean - this is indeed peculiar and we will follow up on it! Jan

Not at all. Just toggle reverse and use your pedals to brake as needed. Jan

Hi Tchou, no, the models I fly don´t have brake to vacate - and I think there were some issues with that function on the 380s, too, so it was/is not used for a while. I don´t know about the later Boeing models. I have a brake-to-vacate built into my head, though . With a little practice you can judge which turnoff would be good to catch, and then I override the autobrake to smoothly slow down to reach taxi-speed just as I get to it. Jan

Yeah, this one crops up all the time. Modern aircraft (even Boeing) will read the ILS front course from the FMC database and set up the AP to follow it upon LOC capture. On the 737, the FMC is not linked to the NAV radios in any way. You have to set up both the frequency and the ILS front course. Front course information is not transmitted by the ILS, just a "fly left, fly right" information. So when the LOC is captured, the plane has NO IDEA where to turn initially, to keep the needles centered. It needs the ILS course to be able to turn onto it. After it does, it will adjust for drift (due to wind, for example). If you set up a SLIGHTLY wrong inbound course, the AP will able to compensate for that (it is the same as having a crosswind), but if the front course is grossly wrong, the AP will turn away from the LOC initially and totally run off it before it has a chance to adjust. This is exactly like it is in the real plane (take it from someone who had to overpower the AP more than once because the plane turned away from the airport on LOC capture, because he forgot to set the inbound course ) Jan

Hi, and thanks for the list. #1 known, #2 known, #3 you might be seeing the pulse-charging of the battery charger cycle, #4 intentional, #5 might be a bug, thanks!, #6 that is not quite working correctly yet and will be changed, #7 intentional, #8 intentional, #9 will try to recreate! Thanks, Jan

That is not quite right, Tchou. In your defense it is hard to judge from the outside how much reverse is being used, and also some pilots will still use reverse more than idle at a lower level. Engines will also switch to a higher N1 idle value when reverse thrust is activated, so it sounds like the pilots are increasing (reverse) thrust levels, this counts as idle reverse, though. Most airports in Europe limit the use of thrust reversers to idle, only. Airlines have also found out that using idle only saves fuel and engine life, however break heating over a certain temperature (risk of brake-disc oxidization) is also an issue. For safety reasons full use of reverse thrust is always allowed, but be prepared for having to answer questions if you do so. Also bear in mind that full reverse N1 is not as high as takeoff N1´s. On Airbus planes, N1 won´t go higher than ca. 70% at full reverse thrust, for example. Jan

You really can´t with the mouse - if this is needed to float your boat, you need to assign a keypress or button... Jan

Thats the way its coded. Sometimes a STAR may have an AT restriction, so in this case just having the STAR may work... in other cases it won´t. Jan

Probably! Thanks for reporting! Jan

Yes - as you can also put in your own "numbers" from the scratchpad into the V-speeds, the FMS thinks you want to put the string "FILE SAVED" into the V-speed and rejects that. Only when the scratchpad is empty does the FMS know that you are trying to simply "accept" the suggested speeds. Jan

Hi Tim, every report helps - and it´s always good to know about these things to keep our eyes open for stuff like this. We naturally concentrate on stuff that is reproducable or being reported by many people - these are the easier and more important "bug-targets". But we still like about the odd stuff that happens, so thanks! Jan

Yeah, we are pretty much not able to do anything about this. I, for example, always have what some may call "micro-stutters" when flying X-Plane, even when using default planes. You can see the sim pause ever so slightly when loading in new trees, buildings, or other scenery objects. I have frame-rates of >50 mostly, and you can "feel" the dip to 30s when this happens. We do have some calculations running every few seconds, and this will also drop your framerate down a bit every few seconds. I guess everyone has a different sensibility when it comes to this, and also possibly your system setup (number of background tasks, memory speed, texture resolution, etc...) could have an effect on that. It is on our long-term list to spread out background calculation a bit more - but for now I can only suggest trying to tweak your system load (look for background, memory intensive processes). Sorry for not having more immediate help available, Jan Here you can see the graphical display of my framerate, sitting in EGLL: I have a base framerate of 40 fps, and every 4.5s my framerate dips to 30. I don´t really perceive this as stuttering on my machine, though...

Well, if you are VRAM limited (trying to show more textures than can fit into your GPU´s memory), then yes, a new GPU with more VRAM will help. But so would probably a lower tier GPU (if it had more VRAM)... Jan

Correct - and usually a modern GPU is yawning and stretching it´s arms while rendering X-Plane - while the CPU is huffing and puffing. The whole simulator is still woefully CPU-bound, even though the team at Laminar has added a lot of stuff for the GPU to do (HDR, for example). However XP10 is still pretty much a legacy, single-core-use simulator that will largely depend on your single-CPU performance in most cases. When I upgraded from a GTX 770 to a 970 I have not gained a single frame per second... Jan

Thanks a lot, Jojo!

This is what we read in your post above - now english is not my first language (and it is neither for Morten), and maybe you ment something else - but to me this does not jibe at all with: So please forgive us when we get defensive when we THINK that someone says that he has zero interest in our product because it doesn´t offer all lighting when not in HDR mode. We put a lot of effort and time into this plane, more than we will ever get even remotely reimbursed for monetarily, so it DOES hurt to read something like this. Jan

Oh, don´t be sorry - I am here anyway . But yeah, go ahead and watch a few of those and it should answer quite a few questions you have! Easier than me explaining everything here in the forums . Jan

User error - you need to regain control of your thrust levers as mentioned and shown on the tutorial videos. Please watch them for how to do that. Jan

I think the debug output was broken (to some extent) in 1.0.4... Jan

This is not (yet) implemented. Jan

When the overspeed protection kicks in, it will try to "nail" the speed to just below the maximum speed. So if you have set 150, but are almost busting the speed limit of 195, the speed cursor will "jump" to the new speed - and the autothrottle will work to maintain this new, higher speed. You need to dial the speed down to 15 kts below this to get out of the overspeed protection and regain control... Jan