Jump to content

sniper31

Members
  • Content Count

    665
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by sniper31

  1. Well, first of all I am hardly filthy rich nor do I drive a Ferrari. I am retired military, enlisted at that, so that should give you an idea of my income. Why do I enjoy having 1Gb access? Well, there are two adult users in my home that use thier PC's for streaming different shows or movies at the same time as gaming. Also, my live in girlfriend works from home and requires a consistent, efficient internet connection. Further, when we have visitors and they want to stream stuff on thier phones or laptops, it does not affect our bandwidth that much. In summary, there are many reasons, many of which are not just because someone is filthy rich. I have managed my finances well as an adult even though my career was not a high-income career, and now I have enough funds to enjoy my hobbies in retirement. So, for me, it is hardly a 'waste of money'. 🙂
  2. Concur with this. How I started to transition from GA to the Airbus. Previously, I had never flown any passenger jets in any flight sim. These videos helped me learn the Airbus immensely.
  3. It all depends on where you are located. Where I live in Colorado I am paying $65 per month for 1 Gb fiber connection. Each state is different, and also can depend on how close or far you are from more populated areas. There are different taxes in different states etc.
  4. Sorry, I did not buy a 4090 to underclock it just for MSFS. I don't ask much of my 4090 in MSFS running in 1440p with settings at high and medium. Glad that it worked for you, but I really don't think that is the answer for me. The error I get in Event Viewer is always the same for me since this SU13 CTD started for me: AppName FlightSimulator.exe AppVersion 1.34.16.0 AppTimeStamp 00000000 ModuleName FlightSimulator.exe ModuleVersion 1.34.16.0 ModuleTimeStamp 00000000 ExceptionCode c0000005 FaultingOffset 00000000023f9441 ProcessId 0x18d8 ProcessCreationTime 0x1da14d700431f8e AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe IntegratorReportId 37124043-c1b6-49d7-96b0-231872851dac PackageFullName Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe PackageRelativeAppId App As for GPU drivers, that is of course prudent and good information that you posted, but I have already been long aware of that process and fully know how to properly install and uninstall drivers, to include Nvidia GPU drivers. I have tested a range of drivers to try and fix this issue, both older and newer Nvidia drivers. I appreciate the suggestions and attempts at help here guys, but I am starting to repeat myself in this thread as it grows longer. The MSFS reinstall is going to happen. It is even a step in the Zendesk process, albeit one of the last steps, but still, a step. Reinstallation is a valid step in troubleshooting software problems. It's not the first step I would take, and trust me, I have been troubleshooting this CTD problem since the release of SU13. Again, appreciate the attempts at assistance. I am commencing with MSFS reinstall. I will report back in this thread with my progress. Once reinstalled, I will have to do several flights before I can be satisfied that the problem is resolved, or if I get a CTD right off the bat, then, and only then I will look deeper into hardware.
  5. I always have multiplayer turned off as I don't like or use it. As for photogrammetry, I mostly fly with it turned off because the melted trees and buildings look that you sometimes see really bothers me. In any case, while troubleshooting my CTD's I have tried with photogrammetry both on and off. Made no difference, I had the same CTD in either case.
  6. I would accept that theory IF I was having this CTD issue before SU13. But, I have had my 4090 for almost a year now, and I have never had any problems with MSFS crashing to the desktop UNTIL SU13 was installed. Before SU13, I must reiterate again, that I had no stability problems in MSFS. Furthermore, I do not have my 4090 overclocked. It has been a solid card, no overheating issues or excessive fan running or any odd behavior.
  7. I know that is not the cause of mine because I stopped using FSLTL when I first started troubleshooting my CTD's. But, who knows, could be the cause of yours. Flight simming is always a voodoo type of science 😉
  8. Hi, and thanks for the nice comments (name is Landon btw 🙂 ). As for my PSU, it is a SeaSonic Snow Silent 1050W 80 Plus Platinum (like those ratings mean anything anymore). Plenty of juice. And it's the same PSU and PC setup I had before SU13. As for trying the MSFS beta, not the right fit for me to be a beta tester (personal reasons that I won't advertise on here). Besides, I don't have the Steam version of MSFS. But, not a bad suggestion. 🙂
  9. Nvidia drivers are some of the first things I looked at. My current driver is not that old, but not the latest either. As far as I have seen, it is not on the do not use list for MSFS.
  10. Pretty certain. There is always a chance, but my PC is not brand new. It's about 8 months old now. I have updated the BIOS as recommended after I built it because the tech was newer at the time. All the driver's are updated. I have tested and tested the hardware a lot (PC hardware is BIG hobby of mine, as much or more then simming) after putting the system together, as I always do with a new build. No problems ever showed up. I don't ask of MSFS nearly as hard tech wise as I do other games. And like I said above, even in a vanilla state I get a CTD right off the bat. So, I am leaning towards software/MSFS at this point.
  11. I have voted, several days ago 🙂 I just now had another flight CTD, right at the beginning. Nothing extra running or installed. Default everything. Same CTD...always the same. More and more I am thinking that since this CTD started for me with SU13, and it seems to be affecting others but also lots of other simmers are NOT affected, that I am wondering if the download issues many of us had when that update came out maybe caused some data corruption for me. If you all recall, there was a lot of download traffic when that update was released, and many of us were having download timeout issues and it said it would finish but then it wasn't. I mean, at this point I am running out of potential causes, and that seems to be all that's left. So, it's looking like a reinstall might be on my menu tonight or tomorrow.
  12. That looks like the DX12 default scenery tile bleed through issue that has been around for a bit. When you see that, go into external, top down view and then zoom way out. If this is the DX12 issue, then the tile will correct itself for that sim session. Next time you fly you might see it again though, but in a different location. This is a known issue with MSFS and DX12 that has not been addressed successfully yet, but hopefully will be soon.
  13. @MarcG @Sonosusto @andy1252 Guys, thank you for all the words of advice and trying to calm my nerves some, lol. I have slept on it as I said I would, and I am not going to nuke my MSFS install just yet. It's not off the list, but not yet. IF I do nuke it, it will be a systematic uninstall of MSFS and other associated item. Those on AVSIM that have known me for awhile from other sim sites know that I am very tech savvy, and I don't make rash decisions when troubleshooting. I understand the troubleshooting process in regards the PC world, both software and hardware, and I always have notes and checklists going to track my steps and plan my process and ideas. In regards to my SU13 MSFS CTD problem, I have confirmed, reconfirmed and confirmed again that my community folder is empty. I have two Marketplace purchases in MSFS, both FSReborn aircraft, so I have uninstalled those. I don't use FSUIPC, and I have been testing without any addons running. My CTD issue is not the map zoom problem that some of you have experienced. My CTD's always happen while flying. Sometimes right when the flight starts, sometimes after an hour of flying, and sometimes right near the end of my flight. But, always when flying. My MSFS settings are nothing demanding. I run in 1440p with a mix of medium and high settings. The ONLY setting I have in ultra are the volumetric clouds, and when troubleshooting this problem I have dropped them to HIGH. My temps run in the high 40's to low 50's celsius while simming or other gaming. Everything at this point, with my system and setup, is pointing to a problem with MSFS and the SU13. I am sorry, but that is the situation. I don't have a history bashing MSFS, I have been enjoying it since it's release and I look forward to what is in the future with it. I simply think something changed for many os us with SU13 and we are now having these very hard to diagnose CTD issues. But they are happening. When I take everything else out of the equation and all that's left is MSFS and it CTD in a vanilla state, then the next step will be, has to be, a systematic and proper reinstall. I am close to that, but not quite ready to push the button just yet. I long for the days pre SU13 where I could fly in MSFS for hours, flight after flight, in any aircraft, with any scenery and not have any technical problems at all. I will get back to that eventually.
  14. Well, I had a total of ONE successful flight after the USB adjustment, and then on second flight, about halfway into it, CTD. And, I have been using Addon Linker long before SU13, so that is not anything that will matter with this issue. I am about to give up and nuke my entire MSFS install, something I said I would never need to do before SU13 came along. I am going to sleep on it before I do that, but boy, I am getting more and more frustrated. My system runs everything else without issue and at extreme settings. I am running MSFS in 1440p on a 7800X3D and a 4090 I can't even have two stable flights in a row after this last SU.
  15. Well, surprisingly, all of my USB devices in Device Manager has the 'Allow the PC to shut down to save power' box checked, as you suggested might have been the case. I remember checking all of these a while back when you had this problem now that I think about it, and they were NOT checked then. So, as you suggest, some Windows update must have checked them. Now, whether or not those are the cause of MY CTD problems since SU13, time will tell. I would be very happy if this is the solution in my case.
  16. I have had CTD's with SU13 along with a completely empty community folder. Also, I have tried DX12 and DX11 and it still happens. Up until SU13 you would be hard pressed to ever hear me complain about anything in MSFS. Even with the current CTD issues, I still am enjoying MSFS but it is getting very annoying considering how stable it was, for me, before SU13.
  17. Nothing on my system or MSFS install has changed since before SU13, and since installing SU13 I average a CTD about every 3rd or 4th flight. And no, my system is not overclocked and temps average around 45-50c (I have very good cooling). I have been troubleshooting this issue since the release of SU13, working on trying to figure out what the cause could be, every day, and I have had no success.
  18. Okay, confirmed, no Logitech drivers or plugins on my system, but I did indeed have SimLink installed as it is needed for Navigraph charts. Just to check it off though, I uninstalled SimLink, rebooted my PC and launched MSFS. Very first attempt at a flight, in the default Cessna 172, start taxiing, then freeze and CTD. Just like every CTD since I installed SU13, EventViewer says MoApp caused MSFS to crash. So, for me, SimLink had no bearing on my SU13 CTD's. Was a nice thought though.
  19. I'll consider that. I don't have any Logitech devices, so no Logitech plugins. I think I have already uninstalled Simlink awhile ago, but I will double check. Thanks for the suggestion. I get an MSFS CTD since the install of SU13 about every 4-5 flights. Most times it happens when I click to load my flight, or sometimes during flight. It is a very nagging, CTD that does not happen every time, just every so often. Reminds me of the kind of CTD's I would experience in previous sims like P3D and FSX. Ones that are extremely hard to pin down the root cause. Frustrating.
  20. I LOVED ENNK Narvik airport from the FSX/P3D era. One of my top 3 favorite airports. Miss me some Narvik, and I agree it would be great to have a decent or better rendition in MSFS.
  21. Guys, try following the information in this link and see if that helps: MSFS Tutorials | Load a Simbrief flight plan into the G1000 Nxi | Simvol It worked for me with the FSR 500.
  22. Looking forward to exploring this scenery! I am very familiar with this area as I grew up in nearby Temecula. Thanks for another great looking freeware scenery @vbazillio 🙂
  23. Looking pretty darn good @vbazillio, despite your 'amateur skill' 😉 😁
×
×
  • Create New...