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

Crash when switching views

Recommended Posts

Hi,

I get a lot of crashes to desktop with the current version of the 717 and P3Dv4, unfortunately I can't even complete a flight.

This happens randomly while I'm switching from the external view to the internal view (it also happen in the opposite but less).
I got several associated dll crash in the windows event viewer which I never have when flying another aircraft:

- ntdll.dll
- menu.dll
- ai_player.dll
- api.dll
and also a kernelbase.dll

The affected dll seems totally random, I already tried to reproduce this with other aircraft but it never happened.

I am using ASP4 and ASCA as well as Envtex but this doesn't do anything in real time to the sim and some sceneries.
Also using Chaseplane, FSUIPC and PF3 ATC sometimes and it appears that the Multiline FSUIPC display increase the chance of having a CTD during view changes. Many crashes also happened while I was close to the TOD.

Also couldn't this be a simconnect conflict between chaseplane and the 717?

I hope this can help for finding the cause as it seems I'm not the only one.

Edited by kmax59

Share this post


Link to post
Share on other sites

This is an ongoing issue, been around for quite some time. They are working on it. Unfortunately you have to limit the use or not use external views at all for now.

Share this post


Link to post
Share on other sites
1 hour ago, Wispy said:

This is an ongoing issue, been around for quite some time. They are working on it. Unfortunately you have to limit the use or not use external views at all for now.

Thanks Wispy, I didn't experience this until recently. I added some information to my original post, hopefully it could help the TFDI team to find a cause to this

  • Thanks 1

Share this post


Link to post
Share on other sites

It is strange. I had at least 15 flights in with no issues whatsoever switching view on a very regular basis, and now I can't switch them at all without a CTD. I'm not sure what changed, but I miss my 717 now. 

Share this post


Link to post
Share on other sites
4 hours ago, macca22au said:

As I mentioned elsewhere, I fly and enjoy the 717, but only in VC mode and don't change views.   Like everybody I hope that the devs can sort this soon.

I hope so too, but some more detailed report may help them in case they didn't find yet the reason. I'm currently flying the same flight I already flew 6 times, let's see what happens when not switching the views !

Share this post


Link to post
Share on other sites
Does this sort of information help you at all?
 
- <System>
  <Provider Name=".NET Runtime" />
  <EventID Qualifiers="0">1026</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2017-09-08T09:07:28.886057800Z" />
  <EventRecordID>37900</EventRecordID>
  <Channel>Application</Channel>
  <Computer>Ian1939</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0020001, exception address 00007FFA3B9C9E08 Stack:</Data>
  </EventData>
  </Event>

Share this post


Link to post
Share on other sites

No problem ;) It indeed works if I don't switch to external view a moment before TOD and after that until landing. This is surely linked to the systems and the flight plan.
It would be great to get some feedback from the TFDI team about this, especially for such an important issue.

One question:

Does someone tried on P3D v3? Is this happening too on this sim?

 

Here is the kind of error I'm getting on my side, usually getting the same NET runtime error as macca22au just before getting this:

Quote

 

- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2017-09-09T16:30:15.026562000Z" />
  <EventRecordID>412359</EventRecordID>
  <Channel>Application</Channel>
  <Computer>DESKTOP-AH34826</Computer>
  <Security />
  </System>
- <EventData>
  <Data>Prepar3D.exe</Data>
  <Data>4.0.28.21686</Data>
  <Data>594a7255</Data>
  <Data>api.dll</Data>
  <Data>4.0.28.21686</Data>
  <Data>594a7300</Data>
  <Data>c0000005</Data>
  <Data>00000000000155d1</Data>
  <Data>3004</Data>
  <Data>01d32980c15f660d</Data>
  <Data>D:\Prepar3D v4\Prepar3D.exe</Data>
  <Data>D:\Prepar3D v4\api.dll</Data>
  <Data>26e6c816-42de-45c5-af32-2aeac7cc02fc</Data>
  <Data />
  <Data />
  </EventData>
  </Event>

 

 
Edited by kmax59

Share this post


Link to post
Share on other sites

Did a test today without chaseplane, same crash with a similar error log in the windows event viewer, so we can forget about chaseplane being the cause of the CTD.

Share this post


Link to post
Share on other sites

kmax:  have you turned on Hardware Rendering in the Addon Manager.  It has absolutely altered my experience.  Switch views carelessly without CTD.

But being the Dunderhead that I am, I had to read and re-read the instructions given elsewhere in this forum because nothing is quite what it seems.

Open Addon Manager, > Aircraft Sharing > Customise (a box down at the bottom of the page), >Options.  Fooled me, I didn't think the page scrolls, it does in the normal manner.  Find ALLOW HARDWARE RENDER  and Select by ticking the box.  It comes with warnings, but mainly applicable for v3.  A good v4 rig should have no problems at all.

Share this post


Link to post
Share on other sites

Devs:  as you are working on the v4 version why don't you either make this automatic or change the wording at the option to ensure users of v4 take the option.

 

Share this post


Link to post
Share on other sites
4 hours ago, macca22au said:

kmax:  have you turned on Hardware Rendering in the Addon Manager.  It has absolutely altered my experience.  Switch views carelessly without CTD.

But being the Dunderhead that I am, I had to read and re-read the instructions given elsewhere in this forum because nothing is quite what it seems.

Open Addon Manager, > Aircraft Sharing > Customise (a box down at the bottom of the page), >Options.  Fooled me, I didn't think the page scrolls, it does in the normal manner.  Find ALLOW HARDWARE RENDER  and Select by ticking the box.  It comes with warnings, but mainly applicable for v3.  A good v4 rig should have no problems at all.

Thanks for the feedback macca22au, unfortunately I already use Hardware rendering, I also tried without it but it doesn't change anything here for me :(

Share this post


Link to post
Share on other sites

All I can suggest is what I would do:  a root and branch uninstallation of TFDI, clearing out all folders (save your flightplans somewhere else), a redownload of the beta, cross my fingers, reinstall and see how it goes. Surely another version of the beta should almost be ready. 

But given your thoughtful responses in our conversation I would think that you have already done that!

  • Like 1

Share this post


Link to post
Share on other sites

Well, I already did a full aircraft reinstall, but I didn't uninstall the addon manager, that's what I am going to do right now by redownloading the whole thing. Will give you my feedback once completed :-)

Edited by kmax59

Share this post


Link to post
Share on other sites

No luck ! It crashed again after reinstalling :|

EDIT: Same result by not using the Hardware rendering

Edited by kmax59

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