FlightFactor B777 / B757 / B767 / A350 /A320
Forum for the B777 Worldliner Professional/Extended, the B757 Pro, B767, A350, A320
174 topics in this forum
-
Pinned topics
-
- 11 replies
- 9323 views
-
- 2 replies
- 7022 views
-
- 1 reply
- 3539 views
-
- 0 replies
- 2827 views
-
- 1 reply
- 5255 views
-
Topics
-
- 1 reply
- 136 views
-
- 0 replies
- 122 views
-
- 1 reply
- 227 views
-
- 1 reply
- 212 views
-
- 3 replies
- 344 views
-
- 0 replies
- 200 views
-
- 1 reply
- 253 views
-
- 0 replies
- 299 views
-
- 0 replies
- 262 views
-
- 2 replies
- 314 views
-
- 6 replies
- 380 views
-
- 1 reply
- 369 views
-
- 2 replies
- 535 views
-
- 1 reply
- 406 views
-
- 2 replies
- 819 views
-
- 3 replies
- 937 views
-
- 9 replies
- 853 views
-
- 4 replies
- 2391 views
-
- 4 replies
- 928 views
-
- 0 replies
- 634 views
-
Posts
-
well... disabling the mesh (temporarily) could be a way to track down the problem. But you are right, it's much more easy to blame the product to be faulty. -
By Hans Hartmann · Posted
4K doesn't require an expensive graphics card. I've used a GTX 1070 with two 4K monitors (se 7680x2160) for years and framerate was OK all the time. FSX fully supports 4K and so do all add-ons that run directly in FSX like aircraft and scenery. -
-
Danke für deine Antwort. Hatte im englisch sprachigem Forum hier jemanden gefunden mit dem gleichen Problem. Der hat von PMDG den OC Installer bekommen. Hatte die angeschrieben, ebenfalls den Installer bekommen und alles funktioniert. Aerosoft bietet die 737 für P3d V4 an, steht auch so in den Systemvoraussetzungen, dann sollte man auch die Updates bereit stellen um V4 kompatibel zu bleiben wenn Lockheed Martin den Sim updatet.
-
By DaveCT2003 · Posted
Okay, well I would have much preferred you do what I suggested, but we can work around that too. What I'll need you to do is delete the following files: 1. The Prepar3d.cfg file, located in the C:\Users\[YOUR USERNAME]\AppData\Roaming\Lockheed Martin\Prepar3D v4 folder. 2. The "Standard" files located in the C:\Users\[YOUR USERNAME]\AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls folder. 3. If you have ever used FSUIPC to set any control bind for any aircraft, please delete the FSUIPC.cfg file, which would be located in the Modules inside your main P3D folder. The deleted files will all be rebuilt when you start P3D up, but you'll have to adjust your P3D settings and control binds when you start P3D back up. This is the least intrusive way to troubleshoot this issue your having, which is a system issue as reverse thrust worst fine for me and others whether it's triggered by a key or a switch. The next possibility is that one of your C++ redistributables got whacked, or maybe even DirectX. But looking at those things is a more intrusive, so let's stick to the more simple stuff for now.
-