Arndt777

Hello, I would like to join. Thank you very much for this great contribution! Arndt

I am very happy about this tutotial, too. So far, I have started several times to learn the handling of the tool, but wasn't successful. Now, I am going for it again, and so far I am confident to make it although I am not an IT guy. Thank you very much for this huge effort! Regarding the resolution: I have a curved monitor with 3840x1440 resolution. So I can read the GIT windows with some effort (going very close to the screen). Of course I would appreciate, if parts II and III are published in a more reader friendly resolution of the GIT windows. Many thanks again! Arndt

Two times: yes. The unit works great with P3D. You can assign and configure with FSUIPC. But even easier it is with GoFlight's own driver utility. Regards Arndt

I could solve the problem. It was due to a faulty installation of MyTraffic. Arndt

I use P3D v3.2 and My Traffic 6: I don't have any traffic with the new Aerosoft versions of Frankfurt, Tegel and Zurich. The problem persists, whether I disable the respective BGLs inside the MyTraffic scenery folder or not. There have been no problems with the 'old' versions of EDDF, EDDT and LSZH or with other sceneries. The new sceneries of EDDF, EDDT and LSZH all have the AirportController. Could there be any connection? Any other idea how to solve this problem? Best regards Arndt

I have several USB controllers (GoFlight modules, yoke, rudder, Saitek throttle quadrants) and Windows 10 as the operating system. Although doing the power management trick as described in the previous mails, I still had severe problems with my USB controllers. They have not been recognized by Windows 10 at all, or movements of the controllers have been been transmitted to P3D with a time lag or quite jerky. Now I could solve these problems by changed settings in the bios of my Gigabyte GA-Z170X mainboard Legacy USB Support: Disabled USB Mass Storage Driver Support: Disabled TBT USB3.1 Force Power: Enabled. This might be a way for others too, who have problems with their USB controllers under Windows 10. Best regards Arndt

I have two Saitek Throttle quadrants in my configuration. After re-installing Windows 10, the quadrants don't work anymore. I installed the Saitek drivers and the quadrants show up as an USB device, but any movement of the handles is not recognized. Of course I did the energy management trick (manually), but without success. Any ideas? Kind regards Arndt

Ed, thank you for your hint! I made a repair (P3D 3.2.3), but unfortunately there is no improvement. Maybe, I should go for a complete reinstall. Right now, without erasing the contents of the shaders cache, it is impossible to load a flight. Arndt

Thank you for your comments! I was surprised, because I didn't have this problem before. And now it is there, without installing new sceneries etc. Strange! Right now I am already waiting more than four minutes... Only restarting the computer and deleting the shaders cache seems to help. Best regards Arndt

Hello, in the last days I am having the problem, that loading a flight is stopping at 'loading terrain data' at 6%. Then the only solution is to restart the computer. I have no idea concerning the reason for this problem. I haven't intalled any new scenery or software. Is someone able to help? Regards Arndt

Jorge, you have been right!!! I learned, that in Windows 10 it isn't sufficient to deactivate UAC in the system control panel. You have to do it in the registry!!! Once I did that, I was able to activate P3D 3.0. Thank you again, Jorge!

Thank you for your advice, Jorge! UAC is disabled in my setup. I reinstalled P3D 3.0 with right click as an administrator, But unfortunately the problem persists. Has anyone another suggestion? Arndt

Hello, I downloaded and installed P3D 3.0 without problems. Then I tried to activate. After typing in license ID and license password, I got following message: "Error: Registry key could not be opened/created or is missing. (9217)". How can I solve this problem? Additional information: I have Windows 10 installed, and I am running P3D 2.5 without problems. Regards Arndt

Just yesterday, I solved the landing gear issue by completely unchecking the 'detect crashes and damage' option within the realism settings of P3D. You find this hint on page 14 of the manual, too. Many thanks to Rob by RealAir for his prompt advice. Arndt

I had another flight with Nick_N's settings, and I am still very pleased. New for me have been his tips regarding shadow settings and the 60 fps locked. Everything else I know from other guides, too. But the combination of seetings is really effective. Of course, there is shimmering because of the waiver of NI. If I combine Nick_N's settings with 4x Sparse Grid Supersamling from NI, then I still have a 3 to 4 fps advantage in front of my previous settings and great graphics. I will keep these settings.

I have applied Nick_N's tips and recommendations to my P3D installation more or loss completely. The result was a substantial increase in fps (5 - 7 on average), thereas graphic quality and fps stability was equal or even better than my previous setup. I am going on to test, but so far I am very pleased. Arndt

Did you finally receive your items? I am asking, because I consider a new purchase.

I ordered a yoke and rudder pedals over the past two years. I had the same problems with delivery times. Customs is a common excuse. But finally I got my items. Regards Arndt

Hello, I have installed P3D 2.5 (2.5.12943.0). Now I realized, that the controls sensitivity slider is not working or has a minimal effect: Even if you reduce for example airleron sensitivity on the slider to 1, sensitivity is very high. The same is true, if you adjust sensitivity by FSUIPC. Has someone experienced the same problem? Does anyone know a workaround? Kind regards Arndt

Please see what I got from the P3D flight planner. Different from yours.

Here is the screenshot ... So far the cruising altitude is stable and didn't change, even after closing and restarting P3D for sebveral times.

Hello Vaughan, I am not using old plans, but only new one's. They are in the same format as yours. But: nearly all flight plan files do contain as cruising altitude not values like 5000 ft, 5500 ft or 6000 ft (this is my usual cruising altitude), but values like 55 ft, 524 ft and so on. I changed the cruising altitude values in all my flight plan files outside P3D back to my usual cruising altitude and then saved the file. Afterwards I reopened these files within P3D and cruising altitude again has changed to these strange values like 55, 524 and so on. I don't have any idea regarding the source of the problem. Regards Arndt

Hello, I realized a problem with the default flight planner of P3D version 2.4: If I input a specific cruising altitude of for example 6000 ft and save the flight, then this cruise altitude value is getting lost. If I retrieve the flight, then I don’t find the saved cruising altitude, but a fantasy value. This fantasy value never is four digits or above, but two or three digits only. Is this a bug of Prepar3D 2.4, or is this a problem with my installation? Can I take any action? Kind regards Arndt

Hello, since two weeks or so I have problems with the ATC the selected attitude of the flight plan is constantly ignored by ATC, and the given attitude is nonsense; for example: the flight plan contains 6000 ft attitude, ATC is giving me 100 ft sometimes messages are shown in the ATC window, but not read by the controller or messages are read only partially. I already have replaced the ATC sound file (Prepar3D v2/sound/atc) by my backup of the original files. But the problem still persists. Has anyone an idea how to solve this problem? Kind regards Arndt