CTD help

Moderators: Tony, Sharkku

CTD help

Postby Kilstorm » Mon Oct 08, 2018 9:22 am

see below
Last edited by Kilstorm on Mon Oct 08, 2018 3:35 pm, edited 1 time in total.
Image
Kilstorm
 
Posts: 69
Joined: Wed Jun 08, 2016 12:38 pm

Re: Would FI be causing this external view issue?

Postby Kilstorm » Mon Oct 08, 2018 12:22 pm

Just got a CTD and received this msg of file attached:
Attachments
FI CTD.jpg
FI CTD.jpg (32.64 KiB) Viewed 1314 times
Image
Kilstorm
 
Posts: 69
Joined: Wed Jun 08, 2016 12:38 pm

Re: Would FI be causing this external view issue?

Postby Kilstorm » Mon Oct 08, 2018 12:22 pm

Here is the error file
Attachments
error-20181008T122451.txt
(654.61 KiB) Downloaded 57 times
Image
Kilstorm
 
Posts: 69
Joined: Wed Jun 08, 2016 12:38 pm

Re: CTD help

Postby Badwolfx » Sun Oct 14, 2018 11:34 am

I keep getting the same.. did you find a solution???????????
Badwolfx
 
Posts: 13
Joined: Thu May 17, 2018 12:36 pm

Re: CTD help

Postby Tony » Mon Oct 15, 2018 2:16 am

What windows update have you guys had ? Are you on the latest Nvidia drivers ??
Tony F
Customer Support = contact tony@flyinside-fsx.com
FlyInside Inc.
Tony
 
Posts: 4649
Joined: Sat May 30, 2015 3:20 pm
Location: Rift User

Re: CTD help

Postby Kilstorm » Fri Nov 02, 2018 4:19 pm

Hi Tony. Im now upgrading my drivers to the nvidia 416.34. As far as windows, I think I am up to date. OS 17134.228 ver 1803 Windows 10 pro. Just got the crash again so I am updating my video drivers in hopes that helps. Any other ideas based off the crash report? P3Dv4 and FI use to be a solid platform but now I am getting crashes more often.
Image
Kilstorm
 
Posts: 69
Joined: Wed Jun 08, 2016 12:38 pm

Re: CTD help

Postby Messifan30 » Sat Nov 17, 2018 8:51 am

Dont worry my flyinside is only Crasing every flight, thats normal.
Messifan30
 
Posts: 22
Joined: Sat Jul 07, 2018 11:56 am

Re: CTD help

Postby Goromo » Sat Nov 17, 2018 9:08 am

So here is another post regarding CTD.
This was posted on 8th Oct, today is the 17th November, and still no help from the Dev's. The same as the line 117 Crash. Totally ignored.

Why are these problems being ignored?

Does this mean there is now no support for the P3D product? if so please have the courtesy to advice your PAYING customers accordingly.
System: i7 7700k, @ 5.0ghz, 32gb RAM, GTX 1080, Samsung 960 EVO NVME 500 GB x2, 2TB HDD,Win 10 64 bit
GoFlight Yoke, Saitek TQ, MFG Rudder Pedals, several Goflight modules. Home Cockpit.
VR: Oculus Rift CV1..
SIM: P3D version 4.3
Goromo
 
Posts: 24
Joined: Sun Dec 18, 2016 7:29 am

Re: CTD help

Postby Tony » Sat Nov 17, 2018 10:10 am

These problems are not being ignored. I'll take full responsibility for this as I missed it. Recent holiday followed by another trip away but thats no excuse. It's my job to pass this to the devs, I was supposed to and forgot. I will ensure that they get to see this and go from there. Sorry once again guys.
Tony F
Customer Support = contact tony@flyinside-fsx.com
FlyInside Inc.
Tony
 
Posts: 4649
Joined: Sat May 30, 2015 3:20 pm
Location: Rift User

Re: CTD help

Postby admin » Wed Nov 21, 2018 5:41 pm

Hi All,

Please forgive me for not addressing this sooner. If this was actually one specific bug this would've been fixed a long time ago. Issue is that the -2005270523 bug is very meaningless. It basically means "somewhere in the program, in the last few seconds, something made DirectX give up." We've seen it happen (and fixed it), in bugs with our stereo-rendering system. We've seen it happen with buggy NVIDIA drivers (and seen those cases fixed with updates). It can happen because a different add-on does something wrong (and FlyInside catches the error), and it can happen because we do something wrong which messes up an add-on's behavior. We've had some users run into this due to a damaged Oculus HDMI cable (multiple users over time). That's a long-winded way of saying, that despite all of you seeing the same error message, everyone is quite possibly experiencing a different bug or underlying cause.

If you're interested:
0. Make sure you're up-to-date on drivers, that your PC is stable in general, try turning down any overclocks you aren't 100% confident in.
1. Try disabling add-ons. If the error goes away, shoot me an e-mail (dan@flyinside-fsx.com) letting me know which add-on is related. We can dig in and see if it's fixable.
2. Make a backup of your settings. Try turning down settings, deleting the settings file to get defaults, or simply changing them. If that makes a difference please send me your original Prepar3D.cfg so I can take a look and see if there's some settings combination we aren't compatible with.
3. If you are experiencing these crashes with default settings and no add-ons, please contact me. That's strange but we'll do some deep/detailed debugging with you to try to hunt it down.

Thanks,
Dan
Your friendly neighborhood developer!
Contact Me: dan@flyinside-fsx.com
admin
Site Admin
 
Posts: 2695
Joined: Tue Feb 06, 2007 8:36 am

Next

Return to P3D Bug Reporting Here

Who is online

Users browsing this forum: No registered users and 1 guest