• 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.
kpan24

P3Dv4 CTD when switching views

Recommended Posts

On 2017-6-24 at 6:08 PM, jackscrj said:

My experience with p4d has been a ctd festival. 

I disagree.  My experience is the exact opposite.  P3D v4 has been rock solid for me, except when flying this one specific aircraft where I get a CTD on each flight..  I have done 16 hour B77L long hauls, multiple aerodrome rotations in both the B744 and B77L without quitting/reloading and have yet to encounter a single crash flying "the other" company's V4 aicraft.  

Strangely, my CTD occurs when I'm doing absolutely nothing in the simulator.  I can be at level cruise not touching a thing, not switching views then suddenly the visuals just lock up (sound still plays) then the sim just gives up the ghost and I get my desktop view (ProjectFLY and vPilot then tells me that it lost the sim connection).  There is some combination of software that doesn't play ball with the 717, I'm convinced of it.  The problem is trying to find the culprit as unfortunately my CTD doesn't yield any 717 debug logs or event viewer entries.

Share this post


Link to post
Share on other sites

Where does it saves TFDi error .bmp files? (minidumps files)

Edited by Sanpp

Share this post


Link to post
Share on other sites

Hello all!

I am also affected by this CTD-problem.

I made today 4 flights with the 717 in P3Dv4, and all 4 times the sim crashed. 3 times without a message in the event log, 1 time with the menus.dll as causing dll in the event log.

All 4 times this CTDs appeared after 40-60 mins inflight...

 

I hope there will be a fix soon!

Thank you in advance

Kind regards

Matthias

Share this post


Link to post
Share on other sites

I don't know many times I can say this - P3D v4 has not been stable so far. We're not getting a crash dump from these, it's showing DLLs that we don't use (we don't use menus.dll), and the view switching CTD has, historically, been found to be caused by something else. I'm not going to jump out and take responsibility for this crash and promise a fix when I'm really not even convinced it's our code causing it. If something changes and we're able to pin it down to our code, I'll certainly fix it, but that has not happened yet.

Share this post


Link to post
Share on other sites
15 hours ago, Sanpp said:

Where does it saves TFDi error .bmp files? (minidumps files)

A dialog will open and tell you that it has crashed and where the dump was saved, if one is generated.

  • Like 1

Share this post


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

A dialog will open and tell you that it has crashed and where the dump was saved, if one is generated.

Roger that! Thanks!

Santiago

Share this post


Link to post
Share on other sites

The problem is I can't actually get the program to crash. It just hangs unresponsive. I'll have to try it with the hotfix to see if it changed anything. But I absolutely can say I only have this problem with this aircraft out of all that I have installed. It seems to be very repeatable. Just cycle through exterior and interior views a few times. Sounds like with ezdok or chaseplane, not sure about default camera management. Not saying it's necessarily your code, but maybe some sort of conflict.

Update: Installed the p3dv4 hotfix 1 and have tried switching cameras like crazy and so far I am not seeing any crashes. I think it was a p3d bug

 

Edited by jasonpc
  • Like 1

Share this post


Link to post
Share on other sites
5 hours ago, jasonpc said:

The problem is I can't actually get the program to crash. It just hangs unresponsive. I'll have to try it with the hotfix to see if it changed anything. But I absolutely can say I only have this problem with this aircraft out of all that I have installed. It seems to be very repeatable. Just cycle through exterior and interior views a few times. Sounds like with ezdok or chaseplane, not sure about default camera management. Not saying it's necessarily your code, but maybe some sort of conflict.

Update: Installed the p3dv4 hotfix 1 and have tried switching cameras like crazy and so far I am not seeing any crashes. I think it was a p3d bug

 

Yes. You are not the first to confirm that the patch Lockheed Martin released today fixed this issue for them. This would be the reason I have been saying it's a P3D bug.

  • Like 1

Share this post


Link to post
Share on other sites
10 minutes ago, turbofandude said:

Yes. You are not the first to confirm that the patch Lockheed Martin released today fixed this issue for them. This would be the reason I have been saying it's a P3D bug.

You told them... You told them! lol

Good to know that your issues are gone

  • Like 1

Share this post


Link to post
Share on other sites
7 minutes ago, jackscrj said:

I'm sorry how can you disagree with my experience lol

A logic fail in semantics on my part I guess :)  I meant to disagree, based on my own experience, that P3D v4 is a CTD festival, not your experience of it.

Share this post


Link to post
Share on other sites

I as well am having this issue. Other aircraft on V4.1 I have Zero Problems when it comes to a Crash To Desktop. I just purchased this aircraft yesterday and It has CTD'd over 5 times now. This frequently happens when I switch views. As well as the frames drop a LOT when changing views. I don't use any camera add on, just default. 

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