• 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.
  • 0
cwdefouw

Displays going black during flight

Question

I have had this happen twice on the most recent version as of June 8, (1.0.9.0, I think). During the flight usually at around an hour in, the four leftmost displays suddenly go black, the two rightmost displays stay on with no issues. I can click the black displays and bring up the 2D windows, which display fine, which allows me to continue, but I don't think this should be happening, and I can't imagine it is a problem with my machine as two of the 6 displays do not exhibit the problem. After the first occurrence, I uninstalled the aircraft, downloaded a new copy of the TFDI Addon Manager Installer and reinstalled everything. Had the same problem on the next flight the next day. I did not have this problem before the last update. A screen capture is attached, system specs are below.

Thanks,

Chris DeFouw

System Specs:

Proc: I5 2570K

Graphics: Nvidia GTX970

RAM: 16GB

Conventional HDD

Prepar3d v3.3

 

 

717_DisplayFailure on 6_9_17.JPG

Share this post


Link to post
Share on other sites

98 answers to this question

Recommended Posts

  • 0

I'm having the exact same problem! About an hour in and the 4 left displays go blank but still work in 2D.... No warnings/EICAS messages everything is working fine.

Save P3D, Force Persistence Save and restart P3D and open the flight again and the displays are back.

 

I7 6700K

Nvidia Titan X

32GB RAM

Samsung NVME SSDs

Windows 7 Enterprise X64 and P3D 3.4.18.19475
 

Share this post


Link to post
Share on other sites
  • 0

My occurrences were as follows...

6/8/17 - Flight was KTPA to KATL on the RAGGZ1 arrival to Runway 27R

6/9/17 Following complete uninstall/reinstall of the TFDI Addon Manager and B717 plane...

Flight was KMSP to KMCI on RBA3 arrival to Runway 19R

 

Thanks,

Chris DeFouw

 

Share this post


Link to post
Share on other sites
  • 0

Thanks for letting me know; I'll forward this to the rest of team and we will keep you guys posted. Flight Sim Con happened this weekend so we all appreciate your patience in our delayed response during this time. 

Cheers,

Share this post


Link to post
Share on other sites
  • 0

 KATL to KMDW and KLAX to KSFO when this happened.

Since posting that I had this problem earlier, I have not been able to recreate the problem.

Thanks,

Brett 

Share this post


Link to post
Share on other sites
  • 0
8 minutes ago, turbofandude said:

Do you happen to have a lot of other graphics intensive addons installed, or have your settings particularly high?

FSDT KLAX 

Flightbeam KSFO

Imaginesim KATL

FlyTampa KMDW

ORBX NA

ActiveSky16

All settings nearly maxed out on P3dv4... no performance issues on the aircraft when this happened, just had the left 4 displays go blank. If you opened the displays in 2D they still function normally.

Thanks,

Brett

Share this post


Link to post
Share on other sites
  • 0

Please try reducing your settings slightly - P3D v4 has been a MONSTER on video performance so far, so chances are, it's maxing something out.

Share this post


Link to post
Share on other sites
  • 0

For me, this is occurring on P3Dv3.3. Medium settings, This did not occur before the most recent version upgrade.

Share this post


Link to post
Share on other sites
  • 0

Same problem for me except they did not go black.  They were filled with what looked like vegetation.  Green and black.  I only purchased the plane a few days ago and have the latest updates. 

Edited by kenthom

Share this post


Link to post
Share on other sites
  • 0

Is there anything happening on this problem?   I have attempted several flights at different locations and it continues to happen making the plane unflyable.

Share this post


Link to post
Share on other sites
  • 0

I thought after the update today that possibly this issue was solved but it was not to be.  Forty miles from destination they all turned to a camouflage color.  UGH

Share this post


Link to post
Share on other sites
  • 0

On a flight from KATL to KMSP and around 45min into the flight I lost my left 4 screens like everyone else is reporting. P3D3.4. I noticed they work when there pop-outed.

Edited by Dan Moore

Share this post


Link to post
Share on other sites
  • 0

I also got the same. My first flight today with the 717 on P3DV4 from CYYZ to KMSP. I did it two times and it happened in both. Fortunately the co-pilot displays was working so I was able to land safely.

em353AQ.png

The left screen shows something like broken screen to me (like electrical problem?). The first time it happened at least one more of the other black screens had also the same broken textures. I was also getting some error messages the first time I went to external camera with EZdok referencing some texture files, I'm not sure if its related, I'll screenshot them next time. Also I don't have any weather or ground radar indications...

PS. The plane is beautiful! 

 

 

Edited by Ifikratis

Share this post


Link to post
Share on other sites
  • 0

Next flight also did exactly what lfikratis' screenshot shows...weird yellow blobs at 90 minutes in. Very annoying. Saved and restarted P3Dv3.4 and it's back to working fine.

1st leg was DTW-DCA and this one is ATL-MDW. Interesting that it happened both times a few minutes into the descent.

Edited by and1049

Share this post


Link to post
Share on other sites
  • 0

Same flight... after restarting P3D it was fine... continued the approach and the displays crapped out again on a 10 mile final. This REALLY SUCKS!

IMG_8833.JPG

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Any reply from the developers that they are working on it? Obviously to turn down display settings is not a solution..

I have grounded my 717 until this is fixed.

Edited by Ifikratis

Share this post


Link to post
Share on other sites
  • 0

Also just experienced this with Captain and 2 centre Displays going black during the flight (roughly an hour in) on P3D v4, no CPU or GPU spikes or anything out of the average to indicate why its doing it, the FO side still works fine and 2D pop-ups are working fine?

Share this post


Link to post
Share on other sites
  • 0

The 717 is not the only airplane that can have this happen. We have also have not been able to recreate this. We've also had scenarios where disabling all addons prevented the screens from blacking out, which leads us to believe there is a conflict somewhere. @Ifikratis We reply every time this gets reported (this isn't the first, by far). We will be doing what we can, but it's hard to fix a problem that isn't specific to us and that we don't have.

 

We are working on trying to find a solution, but information is limited.

Share this post


Link to post
Share on other sites
  • 0

Interesting reply.  I only had the plane for a very short time and all worked well.  But I have been adding airports and weather as they became available in V4.  It will be very difficult to pin down what is affecting the panels.  This plane will remain in the hangar until a solution is found.  Frustrating.  

Share this post


Link to post
Share on other sites
  • 0
7 hours ago, turbofandude said:

The 717 is not the only airplane that can have this happen. We have also have not been able to recreate this. We've also had scenarios where disabling all addons prevented the screens from blacking out, which leads us to believe there is a conflict somewhere. @Ifikratis We reply every time this gets reported (this isn't the first, by far). We will be doing what we can, but it's hard to fix a problem that isn't specific to us and that we don't have.

 

We are working on trying to find a solution, but information is limited.

This is the only aircraft I'm having this issue with and all the scenery (flightbeam) and orbx is p3dv4 sdk compatiable, I am only running active sky and vpilot otherwise, gpu and cpu usage is normal within the flight with gpu barely rising about 55/60.

I have been able to replicate this every flight, is there a log I can send you since it's a beta? I also see people reporting the same issue with 3.4 which wasn't in your previous build so it would indicate it's something to do with the aircraft?

 

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