• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
richcam427

(1.0.9.15) Blue displays!

Recommended Posts

Yeah, I'm not sure how to describe this one. My displays look like fish tanks now.

I just installed the 1.0.9.15 update in P3D v4. Happened about 40-45 minutes into my flight. The popup displays work normally.

*Also reported in the bug system*

Image1.jpg

Edited by richcam427

Share this post


Link to post
Share on other sites

Well, this certainly is a different Blue Screen of Death. We're actually aware of this issue and believe it is a P3D bug.

Share this post


Link to post
Share on other sites
2 hours ago, gamesyns said:

We're actually aware of this issue and believe it is a P3D bug.

Have LM confirmed this to be a big on their end?   Between this and the multi-GPU RealLight and TrueGlass issues... it's VERY frustrating and disappointing.  Thanks for continuing to bird dog these issues guys!

Share this post


Link to post
Share on other sites

I am having the same issue. And I just installed P3DV4 on a clean upgrade to Windows10. I did a few hops around Hawaii with no issue, now climbing out of MSP for SFO, I get a similar problem, but my screens are black. Otherwise, exactly as reported above. Weird.....

 

Scott

Share this post


Link to post
Share on other sites
12 hours ago, skyymann said:

I am having the same issue. And I just installed P3DV4 on a clean upgrade to Windows10. I did a few hops around Hawaii with no issue, now climbing out of MSP for SFO, I get a similar problem, but my screens are black. Otherwise, exactly as reported above. Weird.....

 

Scott

Unfortunately, I had grounded my 717 for the same reason.  I'll have to try it again with the new 1.0.9.19.

Share this post


Link to post
Share on other sites
23 minutes ago, CaptKornDog said:

I'll have to try it again with the new 1.0.9.19.

No difference for me with 1.0.9.19. Sorry to say.

Share this post


Link to post
Share on other sites
On 12/25/2017 at 9:27 PM, skyymann said:

I can confirm that. Couldnt even get from ATL to SAV without the screens blanking. Crap....

 

Scott

 

Dang! :(

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now