Jump to content

Capt Shark

Members
  • Posts

    52
  • Joined

  • Last visited

About Capt Shark

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Capt Shark's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare

Recent Badges

28

Reputation

  1. If I purchased the CRJ 550/700 on the MS Marketplace, do I have to keep it consistent and buy the 900/1000 on the MS Marketplace as well?
  2. In this case I might be the exception. I have a i9 10900K and RTX 3080, 32GB RAM.
  3. For me with the latest sim update and reinstalling the CRJ, the sim will load fine and even the United Express CRJ-550 livery has reappeared. It loads okay and start up from Cold and Dark is fine, taxi, take off and cruise is fine but at the two airports that I've been flying into, I ALWAYS get a CTD when on final approach. It will not capture LOC, nor GS as it did before I had issues. I've been flying the ILS manually and within 3-5nm on final of the runway, I always get the CTD. KDFW 35L and KLAX 25R. I am hoping that this gets resolved soon. Thank you.
  4. @Mathijs Kok, thank you sir! I'm sure you understand our frustrations as well. The majority of us realize that there are a lot of complex issues, but time is money; so to speak. The CRJ has become a favorite of mine, and probably for others as well. Not being able to fly it is disappointing. Rest assured you have our support. Hopefully these issues are resolved soon. Best regards, Mark
  5. Also noticed this which I believe has something to do with the Bravo Throttle set up? Faulting application name: AFC_Bridge.exe, version: 2.1.0.0, time stamp: 0x60049820 Faulting module name: AFC_Bridge.exe, version: 2.1.0.0, time stamp: 0x60049820 Exception code: 0xc0000005 Fault offset: 0x000000000000f9b0 Faulting process id: 0x308c Faulting application start time: 0x01d75c3337a352b4 Faulting application path: C:\Users\Mark\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\AFC_Bridge\bin\AFC_Bridge.exe Faulting module path: C:\Users\Mark\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\community\AFC_Bridge\bin\AFC_Bridge.exe Report Id: bee55d11-dbd9-4dcd-9533-417b53b8e012 Faulting package full name: Faulting package-relative application ID:
  6. Just tried it with the latest 1.0.5. CTD while loading the FBW A32NX. Pulled the CRJ folder out of the OneStore official folder and the FBW A32NX loads and flies fine. Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7 Exception code: 0xc0000005 Fault offset: 0x000000000016ed1a Faulting process id: 0x33a4 Faulting application start time: 0x01d75c32e025c0be Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: d698e32d-f3ef-4a2b-b047-6c51473fe69a Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App
  7. Welcome to the club. Mine always happens on short final. Every time. I posted my Event Viewer data in a different thread. I know the guys are working on this issue, but it's a bummer because the CRJ has become my favorite aircraft to fly.
  8. I'm glad some guys are getting good results. For me, not so much. Had to do a complete re-install, but mine was like 2.36 GB. CTD while loading the aircraft. I removed all the 3rd Party Liveries and am able to start from C&D, taxi and take off, fly the downwind leg, but no LOC nor GS capture on the ILS, followed by a CTD on short final fully configured. There's another thread which I posted on and am watching. Hopefully this gets resolved. The CRJ is my currently my favorite aircraft, so this experience has been disappointing.
  9. I just did a test flight at KDFW from gate 21. Cold and Dark start up to 35L. One lap and on to the ILS35L which did not capture, so manually flew it and suffered a CTD on Final approach, fully configured. Purchased on MSFS Marketplace. Hardware -------- CPU Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz GPU NVIDIA GeForce RTX 3080 (3840 x 2160 x 4294967296 colors) GPU Driver 466.47 RAM 32GB @ 2133MHz Microsoft Windows ----------------- Windows 10 Post October 2020 (20H2) Update / Version 10.0.19043 / 64-bit User Profile and Document Folders --------------------------------- User Profile Location: Environment.GetFolderPath = C:\Users\Mark Volatile Environment\USERPROFILE = C:\Users\Mark Documents Folder: Environment.GetFolderPath = C:\Users\Mark\Documents Shell Folders\Personal = C:\Users\Mark\Documents Microsoft .NET Framework 1.0 - 4.0 ---------------------------------- .NET Framework DF .NET Framework 2.0.50727 Service Pack 2 .NET Framework 3.0 Service Pack 2 .NET Framework 3.5 Service Pack 1 .NET Framework 4 .NET Framework 4.0 Microsoft .NET Framework 4.5+ ----------------------------- .NET Framework 4.7.2 or later (only latest version is shown) Microsoft Flight Simulator (2020) --------------------------------- Microsoft Flight Simulator (Windows Store Edition). Content located at: C:\Users\Mark\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages Microsoft Flight Simulator X & Lockheed Martin Prepar3D ------------------------------------------------------- Prepar3D v4.x not installed Prepar3D v3.x not installed FSX Steam Edition not installed FSX SP2/Acceleration not installed X-Plane 10 & 11 --------------- X-Plane 11 not installed X-Plane 10 not installed Microsoft XAudio2 ----------------- XAudio2_9.dll found: 10.0.19041.1 (WinBuild.160101.0800) XAudio2_8.dll found: 10.0.19041.1 (WinBuild.160101.0800) XAudio2_7.dll found: 9.29 (DXSDK_JUN10.100602-0421) XAudio2_6.dll found: 9.28 (DXSDK_FEB10.100204-0932) XAudio2_5.dll found: 9.27 (DXSDK_AUG09.090904-1620) XAudio2_4.dll found: 9.26 (DXSDK_MAR09.090316-1354) XAudio2_3.dll found: 9.25 (DXSDK_NOV08.081027-0939) XAudio2_2.dll found: 9.24 (DXSDK_AUG08.080731-0600) XAudio2_1.dll found: 9.23 (DXSDK_JUN08.080530-1349) XAudio2_0.dll found: 9.22 (DXSDK_MAR08.080305-1539) Simconnect, SDKs and Visual C++ Redistributables ------------------------------------------------ Microsoft Flight Simulator Plugin - (Version Data: 8.0.313.0) Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2010 x86 Redistributable - 10.0.30319 - (Version Data: 10.0.30319.0) Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0) Microsoft Visual C++ 2019 X64 Additional Runtime - 14.28.29325 - (Version Data: 14.28.29325.0) Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.28.29325 - (Version Data: 14.28.29325.0) Microsoft Visual C++ 2019 X86 Additional Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X86 Minimum Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7 Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7 Exception code: 0xc0000005 Fault offset: 0x000000000016ed1a Faulting process id: 0x3148 Faulting application start time: 0x01d7572d676e63b4 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: e0c0fb36-d06e-4a99-952c-2c6395109f07 Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
  10. Hello All: Same issue as the others. Only one livery for the 550. All the default 700 liveries appear to be fine. I have removed the 3rd Party Liveries as they seem to corrupt the loading of the aircraft. Thanks for looking in to this! Regards, Mark
  11. CTD for me as well. All 3rd Party Liveries removed. For me I am able to do my standard start up, but when flying around the pattern and shooting the ILS, I get a CTD on Final, or minutes in to the flight.
  12. I spoke to soon. I added back two 3rd party liveries for the CRJ700 for United Express. I didn't use it but opted for the Aerosoft American Eagle livery. Took of in the patter at KDFW and when on final approach, suffered a CTD. i'm going to remove them and retry the route. Really frustrating with the CTDs.
  13. Hey Quasiguru, after a couple of CTDs, I gave it a break and came back to it and this time I deleted my Roaming Cache and some pre-cached areas. I also re-checked the Content Manager and another update appeared. I successfully downloaded and installed. Same result and CTDs. Next went in to my Community folder and removed all the 3rd Party Liveries. Tried it again and loaded fine! I just taxied around KATL and all was okay. Only thing missing now is my United Express CRJ 550 livery which I never removed. Any way, it looks like it was the 3rd Party liveries. I'll test it out a little more.
  14. @quasiguru It downloaded and appeared to install okay, but when loading a flight I got a CTD. I did not reboot after the download/install. Well, CTD again. I'm going to delete it again and retry. Wow.
  15. Thanks! I'm in the Content Manager but currently it says NOT INSTALLED. 2.44GB download. It won't let me delete it since it doesn't think it's there, so I'll try to "re-download" and re-install.
×
×
  • Create New...