Search the Community

For some odd reason on my system, the ASOBO updates (at Checking for Updates) will DL just fine at any speed my router can do. But on my system, from the Content Manager, all downloads have to run very slowly at 10Mbits/s or slower or they will hang. Don't know why there is such a difference. Not a big problem because the Content Manger files are all very small vs. the monthly MSFS updates. But something to watch out for if you have problems downloading.

Hi all, Never thought I would be a victim of CTD but recently (started around 2 weeks ago) I have been experiencing P3D hangs after ~4 hours into my flight. The hangs are triggered by mouse clicking, on the PFD, ND, or just looking around with middle wheel. The hangs usually take place when I am about to (or has entered into) descend into my destination. Not too sure whether the hangs are caused by the descend, or the fact that I am approaching the 4 hours mark. Up until 2 weeks ago everything works flawlessly – this is what baffles me the most. Given I have no restore point saved, I have tried formatting my entire hard driver where the P3D is installed, deleting all P3D folders in all the places (AppData/Local, Appdata/Roaming, ProgramData…etc), and performed a clean reinstall for all software. For the first two hangs when it started happen I had these apps running: P3D v3.1 Latest version PMDG 777 FS2Crew v1.7 Latest version ASN FSUIPC v4.949f GSX v1.9 After the formatting and a clean reinstall, the first two hangs I had the same apps running as above, and in the last two hangs I had these: P3D v3.1 FS2Crew v1.7 Latest version ASN FSUIPC v4.949f To be honest I don’t think it was those apps that caused the hangs. I am suspecting it is more like conflicts between P3D/PMDG/Windows Update - because this is as far as I can recall if anything has changed between the hang/no hang situation. I will update my system spec later, but I am running P3D on Win7 SP1. Has anyone experienced the same recently? Really want to practice my landings

Hi all. I had this Splash Screen hanging problem with FSX-S stopping on the initial splash screen and never loading from there. It was resolved by deleting the "logbook.bin" file within the Flight Simulator X folder inside My Doucments. If you want to find out how I am sure this was the solution to the problem in my case, read on. If not rename the logbook.bin file and let FSX create a new one on start up, back it up before deleting it, just in case. After experiencing this hanging on the splash screen error and finding no real help on the www, I decided a complete reinstall from Windows 10 up was in order. Cunningly, I made full system images at every step of the reinstall process using the native Windows backup tool. I installed all of my office programmes etc. first then set about Steam - FSX - FSUIPC - Linda - TrackIr before next setting about the Orbx scenery addons. After I had installed Vector and 4 patches, I decided to go flying as I missed it. A simple flight across 5 miles of the Isle of Wight in the default Piper Cub. Turned off the PC, went to bed, work, home, booted the PC and went to have a quick flight again before commencing the install of Orbx Europe etc. FSX hung up on the splash screen again, Impossible I was gobsmacked! But felt reassured that my painstakingly produced system image's would solve the problem. I set about using the last image created before Vector, taking me back to the full system state just before it was installed. I was even more gobsmacked to find out that even that did not solve the freezing splash screen problem But I realised that the only files that had not been replaced by the system image was in fact the Flight Simulator X files in My Documents folder. I ahd configure the system image file to replaced only drives C - F - G (Windows - Steam - FSX) whereas the My documents folder resided on my D drive and not on the image, the only files inside the Flight Simulator X folder were the Piper Cub flight and the logbook.bin files. I deleted the logbook.bin file attempted to start FSX and all was well again, it worked a treat Game on. Promptly I used the Image of Vectors install state to quickly get back to where I was and the newly created logbook.bin file worked a treat there as well, there was no problem with anything just the logbook.bin file. Reading through some forums I found some great help and advice but none of it worked for me. I only came across 1 thread that indicated deleting the logbook.bin file was an option. But did not believe it. Now I am convinced, blow me down who would have guessed it? on a newly created install Windows 10 up. I hope this helps someone out there, knowledge of this file's corruption when all is newly installed let alone an old installation could save a lot of time and effort, hence the reason to explain how I came to realise this was right for me at least. ALWAYS backup or rename the suspect logbook.bin file before deleting it, you will loose your pilot and flight records in FSX if they are not already lost, but that a welcome exchange in my opinion. That said one could always keep a back up of it so an uncorrupt copy could be copied over, I found the recycle bin is a great place to store these back up files, right up until the time you forget and empty it. Hope this helps someone out, lets go fly. A big thank you to the person who said delete the logbook.bin file, you were right, I am sorry I did not believe you.

So today after creating a new .cfg file and having everything work good... or so I thought... this popped up after my crash. I have no idea what it could be since all the drivers are up to date. Any help would be greatly appreciated. Thanks in advance!!! Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: XAudio2_6.dll, version: 9.28.1886.0, time stamp: 0x4b6b0791 Exception code: 0xc0000005 Fault offset: 0x0002cbef Faulting process id: 0x1c90 Faulting application start time: 0x01d0584630a72017 Faulting application path: C:\FSX\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\XAudio2_6.dll Report Id: bc74dd36-c456-11e4-be9d-902b3457650f Faulting package full name: Faulting package-relative application ID: