Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Oswald1953's Achievements


Rookie (2/12)

  • Collaborator Rare
  • Week One Done
  • One Month Later
  • One Year In
  • First Post

Recent Badges



  1. As Claude said. It's a function that is accessed from an CDU menu. Gives you a list of the waypoints remaining in the flight. Choose one and press reposition. The plane relocates to that waypoint at the time of day the plane would have arrived there and sets fuel accordingly. Use it all the time to skip across large bodies of water. Even better than PMDG's auto time compression. Well worth the effort.
  2. Jump Ahead function that's in the QW 787 is great. Would be really nice to have on the MD-11.
  3. Thanks but that's just good business. Unfortunately we wait pending what will hopefully be a positive result from Lockheed Martin at some unknown future date. There's obviously something in this plane design that's different from all others and triggers this apparent bug. The "fix" they refer to in the knowledge-base is not viable. A second window, regardless of it's size has a severe negative impact on frame-rate which has been reported throughout this thread. So now like you and all the other customers being impacted, the plane continues to sit in the hanger.
  4. When asked recently "So what is it with the 717 that triggers this swizzle bug and why can't something be done to the 717 to avoid it?" The answer received included "If we were to fix it, it would involve a huge change to the exterior and interior models, something that we do not have the ability to carry out at the moment with our ongoing projects and other involvements, especially when LM have acknowledged it is on their side and not ours" This would suggest that TFDi could in fact rework the model to fix this instead of waiting for Lockheed Martin to get around to it at some future date. I can't really see Lockheed Martin having an incentive to jump on this anytime soon seeing that no other plane exhibits this behavior. I don't know about your experience, but it's now been more than a year since I bought this product and have yet to complete a flight without a view change CTD. If TFDi can't get a solid commitment from Lockheed Martin they need to get on with reworking the model instead, in spite of "ongoing projects and other involvements". Unfortunately from time to time in our business we've had to dip into the slush fund and/or rework project timelines to rectify issues that impacted customers even though we could have legitimately pointed the finger at others.
  5. Well let's hope LM doesn't drag this out and is able to come up with a solution in short order. Just seems odd to me that this bug, whatever it is, seems to affect this plane only. If LM can sort it out then fair enough.
  6. That's interesting considering this bug is not only affecting your paying customers, but theirs as well, seeing the problem lies with them. I can't speak for others but I haven't been able to fly the plane since I bought it nearly a year ago.
  7. Thanks Collin. Hopefully they can sort something out for us sooner than later. Been a long time since we've been able to fly the plane.
  8. I've not read about any other plane with this specific issue. If true wouldn't it be easier to tweak the plane coding to avoid the bug?
  9. Firstly I must say the overall 717 package is excellent and it's my go to plane for most flights 1000nm or less. That said I've had the same CTD problem when changing views as many others and experienced gauge issues when setting Sparse Grid Supersampling in Nvidia Inspector to stop shimmering. I'm running Prepar3d 4.5 with no unrelated programs/addons and up until a week ago was also running Windows 10. My rig is not new but has for the most part more than enough grunt. I was getting all kinds of other various fltsim issues in addition to those related to the 717. The other day I happened to notice while browsing through the PMDG Operations Center that they are still recommending Windows 7 x64. So I thought hmmm... I slapped another hard drive into the rig and set about reconstructing the sim from scratch under Windows 7 x64 SP1 with ALL updates. I set P3DV4 exactly as before (the .cfg file untouched) and all the same addons set as they were before. Then I played around with Nvidia Inspector with the following result: Antialiasing - Behavior Flags: None Antialiasing - Mode: Enhance the application setting Antialiasing - Setting: 4x [4x Multisampling] Note: Set The same in P3D Antialiasing - Transparency Supersampling: 4x Sparse Grid Supesampling Toggle FXAA on or off: On Note: Set The same in P3D Anisotropic filtering mode: User-defined / Off Anisotropic filtering setting: 8x Note: Set The same in P3D Texture filtering - Negative LOD bias: Clamp The result now is no more changing view CTD's over 6 flights so far of varying distances and no more SGSS gauge issues and no more shimmering. There is no noticeable impact on frame rate. Also of note is that nearly all my other various fltsim related issues have disappeared. Even the little rotating plane when selecting a plane in P3D has no more jaggies. For reference here is a list of my addons/other related programs: PMDG 737/747/777 FSBuild Radar Contact Ultimate Terrain USA/Canada Addon Organizer Little NavMap Active Sky Active Sky Cloud Art Latest Navigraph Airacs Will reinstall Ultimate Traffic and a few selected airports later when I'm satisfied the Fltsim is stable. As for my rig (don't laugh - it's a beast): Intel Core 2 QX9770 running at 3.8Ghz, XFX 790i Ultra motherboard, 8Gb DDR3 1600 RAM, 1000 Watt Power Supply and a Aorus Gtx 1080ti Extreme graphics card with the version 432.36 driver, 24 Inch Samsung monitor set at 60Hz and 1920x1080 That's it. So far, so good. Just thought I'd share my results in case it's of any help to others.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.