Jump to content

Flightfascination

Members
  • Posts

    17
  • Joined

  • Last visited

About Flightfascination

Recent Profile Visitors

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

Flightfascination's Achievements

Newbie

Newbie (1/14)

  • Dedicated Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

12

Reputation

  1. Fair enough Mathijs. I myself was surprised, but very happy, when my below spec computer was even able to load MSFS at all (tested first with XBox Game Pass before actually purchasing). I was happy enough to be in the "cheap seats", vs in the front row, and I know that it's just a matter of time before my luck runs out.....maybe Direct X 12 will be the end of the show. I guess it was just a point of logic that if I could use MSFS, and had no issues with any aircraft to date, that it would have to be some big change that Asobo would make to MSFS that would be the issue, and not an aircraft. In the end, in my opinion, MSFS is the future, and I do enjoy the CRJ, Aerosoft did a great job. So hopefully, my luck will hold out a little longer with MSFS so that I can fly the CRJ 900/1000 (purchased direct from Aerosoft), before the next issue happens. Otherwise, it looks like I'll be upgrading sooner than planned.
  2. Ok, now things are starting to make sense in that Asobo has made recent changes to how they are processing files in the MSFS Marketplace. Lesson learned, in my specific case, I'll avoid the MSFS Marketplace for WASM based aircraft.
  3. The facts in my case: 1) CPU Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz 2) Initial CRJ purchase from MSFS Marketplace and first update, no CTD issues. All subsequent updates from the MSFS Marketplace resulted in CTDs. 3) Then I re-purchased the CRJ directly from Aerosoft and no more CTDs. 4) Same CPU and I assume the same WASM modules.
  4. Just sent to Hans via PM.
  5. All, If you look back at the beginning of this thread, you will see that I was one of the earlier posters. I mention this because at that time, the CTD’s that were being reported were consistent in that they wouldn’t allow MSFS to either get to the start screen, or if you managed to get that far, then the CTD would occur when you tried to choose the CRJ in the hanger, or if you were lucky and got that far, then the CTD occurred when you entered the World Map screen. This was always my case and I was never even able to fly the CRJ. Everyone else was reporting the exact same scenarios. The only solution was to remove the CRJ folder, in my case from the MSFS\Official\OneStore folder. Hans Hartmann, who is a key developer for the CRJ, and who you see throughout this thread, mentioned that the issue seems to be with the update file that we download from the in sim Market Place and that due to the encryption that Asobo adds to that file, Aerosoft is unable the verify where the problem/s are occurring within that file. Once I saw this feedback from Hans, and because I was getting frustrated with not being able to fly the CRJ, I decided to prove his point. So I re-purchased the CRJ, but this time direct from the Aerosoft store. Now I can report that the CRJ works as it did before the fatal updates in the in sim Market Place. And as an aside, I say the following for Aerosoft’s benefit (Mathijs Kok), that the United CRJ 550 livery is also available (this from an unrelated thread where some people who bought the CRJ from the in sim Market Place were unable to see the United livery). So, nothing has changed on my computer, no setting changes, no upgrades, no antivirus turned off (except I always disable the built-in Win 10 antivirus during the install phase only). The only difference is that with the in sim Market Place CRJ update I was getting consistent CTD’s, and with newly purchased Aerosoft store update, no more CTD’s and I’m now flying the CRJ again. So what can I conclude, simply, and not surprisingly, that Hans was right. There is an issue with the in sim Market Place update file and until such time as Asobo and Aerosoft can figure out where the specific error/s are within the encrypted update file, then it seems that trying to look any further, will lead to more dead-ends. I have been absent from this thread since re-purchasing the CRJ directly from Aerosoft, but I now felt that I needed to re-engage, as I see others trying to solve the CTD issue in various ways (which I did as well at the beginning), but still hitting a brick wall. I’m not saying that to solve the issue, people should go out and re-purchase the CRJ directly from Aerosoft, that’s an expensive solution. But if you are patient, unlike me, then I’m sure that Hans will soon “crack the code”, in collaboration with Asobo. As he posted last Friday, “Unfortunately, we won't get any any news on this before Monday. I wish I could help you, but from all I can see here, the CTD happens while the CRJ is decrypted and loaded. Since I don't have access to the MSFS source code, I can't even check out the crash dumps myself and have to rely on Asobo's help with this. I'm sorry for this, but there's nothing I can do.”
  6. Fernando, first you will want to launch MSFS to get a fresh “Error’ entry in the “Event Viewer”, as there can be many other error messages that are not related to MSFS. Once this is done, right-click on the Windows icon in the bottom left corner, then left-click “Event Viewer”, then expand “Custom Views” and then click on “Administrative Events” and you will see a picture like Mopperle posted above. Your cut and paste should look something like what I have at the bottom of my post above.
  7. TenPatrol, traffic variety was already at Ultra, and still CTD. Thanks for the suggestion though.
  8. Thank you Aerosoft team for looking into this issue.
  9. Mopperle, yes I did get that latest update (it was strictly an update to the Asobo 787). Here is the cut and paste from the Aerosoft Version info 1.1.0 that you requested (along with the event log directly below it): Hardware -------- CPU Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GPU NVIDIA GeForce GTX 670 (1920 x 1080 x 4294967296 colors) GPU Driver 456.71 RAM 8GB @ MHz Microsoft Windows ----------------- Windows 10 20H2 October 2020 Update / Version 10.0.19042 / 64-bit User Profile and Document Folders --------------------------------- User Profile Location: Environment.GetFolderPath = C:\Users\Dave Volatile Environment\USERPROFILE = C:\Users\Dave Documents Folder: Environment.GetFolderPath = C:\Users\Dave\Documents Shell Folders\Personal = C:\Users\Dave\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: J:\MSFS 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 (10.0.61637.0 (FSX-Xpack.20070926-1421)) found at: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ X-Plane 10 & 11 --------------- X-Plane 11 not installed X-Plane 10 not installed Microsoft XAudio2 ----------------- XAudio2_9.dll found: 10.0.19041.320 (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 X - (Version Data: 10.0.60905.0) Microsoft Flight Simulator X: Acceleration - (Version Data: 10.0.61637.0) Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.56336.0) Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.61001.0) Microsoft Visual C++ 2005 Redistributable (x64) - (Version Data: 8.0.61000.0) Microsoft Visual C++ 2005 Redistributable (x64) - (Version Data: 8.0.56336.0) Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 - (Version Data: 9.0.30729.0) Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0) Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0) Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0) Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.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.40664 - (Version Data: 12.0.40664.0) Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.40664 - (Version Data: 12.0.40664.0) Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.40664 - (Version Data: 12.0.40664.0) Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.40664 - (Version Data: 12.0.40664.0) Microsoft Visual C++ 2019 X64 Additional Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.25.28508 - (Version Data: 14.25.28508.0) Microsoft Visual C++ 2019 X86 Additional Runtime - 14.28.29913 - (Version Data: 14.28.29913.0) Microsoft Visual C++ 2019 X86 Minimum Runtime - 14.28.29913 - (Version Data: 14.28.29913.0) Here is the cut and paste info from the event log: Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc000001d Fault offset: 0x00000266de342995 Faulting process ID: 0x40dc Faulting application start time: 0x01d75634c8cf067b Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: unknown Report ID: 432fd4b5-ca6f-4089-8d75-a9ebba8c931d Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Thank you
  10. Mathijs Kok Could you please let us know if this post is in the correct forum for support/a response, as there are now 7 of us who cannot use the CRJ without a CTD. Thank you.
  11. By now it’s clear that the 4 or 5 people that have posted here continue to experience the CTD issues, even after either a complete re-install of MSFS, emptying their Community folders, clearing their “m” files, etc, or various different combinations thereof. So something else is still causing the CTD issue. Unlike the throttle issue that was causing problems for so many, the CTD issue seems to be more isolated, at least until more people continue to update to the latest version (the last 2 versions, 1.0.2.0 and 1.0.4.0, had the same CTD effect). In order to try and aid the developers with trouble shooting the problem, and until they step in to this discussion, I’m looking beyond the immediate suspected issues and trying to dig a bit deeper. Something changed between update 1.0.0.1 (that last worked for us), and the ones that followed. But which improved items in those updates might be the culprit/s. Listed amongst the updated items are, “Adapted GS Hold to custom GS” and “Custom Glideslope Hold”. Could something in this “Custom” implementation be conflicting with something in the specific computer setups that the 4 or 5 of us have. Something beyond the MSFS install. I’m thinking, graphic cards, Win OS version, FSUIPC7 (which I disabled during the MSFS start-up sequence but still had the CTD). It could be a shot in the dark, but anything that helps eliminate possibilities for the developers is worth a try. So here are the specs for my computer: -NVIDIA Geoforce GTX 670 2 GB VRAM (yes, below MSFS min specs, but it’s worked fine so far, but maybe the recent update to the CRJ pushed it over the edge), -Win 10 Home 20H2, -Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, -8 GB RAM DDR3, and -FSUIPC7 installed. Hopefully we will hear from the developers soon enough, and get a solution and be able to get back into the wonderful CRJ.
  12. Pilotskcx, thanks for the feedback, but I have no third party liveries and my Community folder is completely empty. I would have to disagree that it appears to not be an Aerosoft issue, as I'm CTD when I'm trying to change from an already selected aircraft to the CRJ, while I'm still in the hanger, which is before you get to World Map where you choose the airport. Further, if I re-launch MSFS after the CTD and go directly to the World Map, bypassing the hanger, the CRJ is displayed as the selected aircraft (upper left corner), as that's the last aircraft that I last tried to choose while in the hanger (before the CTD), and that simple fact that it's there in the World Map, will cause a CTD, and that's before I've had a chance to select a departure airport. So I tried another tactic. I re-started MSFS, went directly into the hanger and loaded an Asobo aircraft, went into the World Map and then tried to change the aircraft to the CRJ from there and while holding my breath, it seemed to work. So I selected an airport (CYOW) and hit the Fly Now button, thinking that I had found success, but seconds later, I got the CTD. Now as a result, MSFS won't even startup and CTD, which is the same issue that was brought up at the beginning of this thread. Now, the only way I can get MSFS to start without CTD, is to remove the "aerosoft-crj" folder from the MSFS\Official\OneStore directory. And if I add it back in, MSFS CTD. The CRJ is conflicting with something, somewhere, it's just a question of what and where. Even though it doesn't appear to be a wide spread issue, I hope that the devs will find a fix, as it's not a question of a missing a certain functionality in the CRJ, I can no longer fly the CRJ period. I hope that I've provided enough feedback/clues as to where the problem might lie and am ready to provide as much feedback as is required to solve the issue. Thank you
  13. Sorry, the post titled "My throttle doesn't work after Update 1.0.0.3" is under the "Controllers, thrust levers, hardware panels" Forum.
  14. I'm not sure how to link to other posts, but you can read about the 'm" files and those under the "Work" folder by going to the post titled "My throttle doesn't work after Update 1.0.0.3" under the General Discussion Forum. I just tried deleting all of the files under the "Work" folder, but MSFS still CTD whenever I try to load the CRJ from the hanger (with either the 550 or 700).
  15. I bought the CRJ from the in sim Marketplace, not directly from Aerosoft, so there is no uninstaller as far as I know. And there is no way to un-install the CRJ via Windows (as far as I can tell). I did however, remove the "aerosoft-crj" folder from the MSFS\Official\OneStore directory before installing update 3. The "m" files are not deleted automatically, so I did that manually, as I mentioned above. Just in case it helps in the troubleshooting, I purchased MSFS in the Microsoft Store.
×
×
  • Create New...