netwalker

Flight description: Route PAJN - PAKT, flight altitude 12 000 feet. Approximately in the middle of the route the flight data aren't no longer updating and do not match (distances to the next waypoint, see picture). The white airplane symbol is moving forward, but the numerical values remain unchanged. Flight aborted.

Thank you for the hint.

On the G1000 MFD, the flight altitude took the value of -1000 ft and could not be changed. (see screenshot). It jumped back to -1000 ft again and again. On a previous flight everything was fine. Thanks

Thanks for the hints, I'll try to repeat the flight with these settings.

I have problems during this flight with reading out the navigation data. I am flying according to the flight plan from KSNA to ZUSED. The flight plan shows: I'm flying to ZUSED, desired Track = 197°, distance to ZUSED 17.4 nm, but the distance is getting bigger and bigger! ? The PFD shows a BRG of 258°, the course is 077°, GPS and AP are on. Something is wrong here, isn't it?

Hello, I don't want searching for the sound error anymore. Today the sound works fine again. I have no explanation for the problem of yesterday. I suspected that ASXP could be cause it by periodically polling the online weather.

I have an annoying noise problem with my newly purchased aircraft. The engine sound is periodically interrupted during the flight. The fps values are ok (about 30 - 35 fps for GTX 1070 TI), so it can't be the problem. I use a good quality audio interface (Presonus Studio 26), and the sound is excellent in all my other planes (also in IXEG). The engine settings are correct I think, I found useful hints for it in youtube tutorials.

Thanks again, the engine start works properly now.

I'll try it with your recommended settings, thank you.

I can't start my new purchased SR22 and after an hour of trying am rather frustrated. I have never had such problems with my (a lot of) other planes. I deleted all inside files in the X-Plane 11/Output/SR22 folder. No chance for a (cold) start. I attached here the new Na_record and Na_state files. NA_Record.txt NA_State.txt

Hi Litjan, sorry for the slightly delayed answer. Unfortunately I also could not reconstruct the error. When programming the FMC I always enter the airways and waypoints at the right place - that's why the error message couldn't come. I also noticed the extremely high takeoff speeds - on the takeoff Ref page when I accepted the proposed V1 value by mouse click the error occurred, if I remember correctly. I suspect two possible sources of error: 1 - in any input field the allowed limits are missing - therefore the calculation algorithm could calculate such unreal high takeoff speeds. 2 - I accidentally forgot to press the EXEC key somewhere. Thanks for your help. Regards netwalker

I experienced more times the following error message (s. screenshot)

After reinstalling and deactivating my virus scanner the problem is solved. Thanks a lot.

Hi Goran, thanks for your early reply. I'll follow your intentions and will report the results.

After successful loading the aircraft is not responsive. Newly installed. The log files are enclosed. Thanks GizmoLog.txt Log.txt

I've been having trouble with the throttle control lately. My joystick throttle controller is not recognized. Before it worked fine and now it works with all other airplanes. The file log.txt is enclosed. I have reinstalled TBM900, and recalibrated the joystick twice. Log.txt

Since I also have problems with the sensitivity of the controls when flying manually, I would like to try to change the values in TBM900_vrconfig.txt carefully. I am aware that the developers are reluctant to see such changes and would never make suggestions in this regard. There is a risk that someone might experiment "idiotically" and later complain about having discovered any "issues". Still, maybe it is worth a try by carefully backing up the original parameters, if you know what you are doing. Here you are: BEGIN_MANIP drag_xy sim/cockpit2/controls/yoke_roll_ratio sim/cockpit2/controls/yoke_pitch_ratio YOKE_MANIP_TRANSLATE -0.318090 0.240970 3.070750 -0.318090 0.240970 3.210750 -0.318090 0.240970 3.140750 0 0 1 69 -69 END_MANIP

As I wrote, at my other planes the sound is/was OK. Nevertheless I tried to change the sound settings a little bit in X-Plane. Suddenly the sound was also there on TMB900 again, so my problem is solved. Thanks for your advice.

Thank you, I'm waiting for the suggestions.

Since the update I don't have sound anymore. Interestingly, the sound of the running turbines is working in tracking mode (at start position on the runway). Inside the cockpit there is no sound anymore. With other planes I have no problems, the sound settings are correct in X-Plane. Version 1.1.9 I had never such issues.

Thank you for the hint, I know this possibility. However, I doubt that this acceleration works well. X-Plane already requires high performance computers at normal speed and higher resolutions. At least for me it has other disadvantages, like wild movements on the screen and the difficult determination of the re-entry point for "normal speed".

Thanks, I'll give it a try. Is it the X-Plane map (shortcut M), or the MFD map? The ToLiss A319 - maybe the best Airbus simulation ever - offers an elegant solution: (see below) Either "jump to the next waypoint" or "jump 100 miles" appears in the window. I often use it to shorten long boring routes and it takes just few seconds. However, it is only possible for straight flight segments with constant heading, which is often the case on long flights.

During long flights it could be quite boring watching the monotonous landscape through the winshield for hours. Would it be possible in future versions to provide a way to shorten the flight between waypoints? I'm thinking of jumps between waypoints or e.g. "forward jumps" of 100 miles? There are other planes which offer this possibility.

No, sometimes I forgot it at first myself, too, but once after seeing the animated fuel leakage, I close the cap every time carefully. Otherwise the fuel inbalance didn't come up during the next flights anymore. I checked the airframe integrity, but all was OK.

I close the fuel cap of the tanks every time, so an open fuel tank cannot be the explanation. Even if a tank had remained open, why did the plane continue using the almost empty left tank after switching to the right almost full tank ?