May 5, 20233 yr On 4/17/2023 at 12:35 AM, Ed1 said: while running FSLTL, hm, just another shot in the dark but I flew EDDM-EDDH in the FBW with FSLTL and had the overheat error while descending into Hamburg. Then I flew exactly the same (simbrief flight plan) flight again without FSLTL and just landed fine on RWY05. again, no academic a/b testing but those seeing NO overheat, do you possibly NOT use FSLTL while those running FSLTL may be prone to those nagging overheat errors? Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
May 5, 20233 yr 5 hours ago, DAD said: hm, just another shot in the dark but I flew EDDM-EDDH in the FBW with FSLTL and had the overheat error while descending into Hamburg. Then I flew exactly the same (simbrief flight plan) flight again without FSLTL and just landed fine on RWY05. again, no academic a/b testing but those seeing NO overheat, do you possibly NOT use FSLTL while those running FSLTL may be prone to those nagging overheat errors? Well, for me, I always fly with FSLTL running (along with FSRealistic and GSX) and I have yet to experience any of these overheating error messages. It is rare that I have a CTD of any sort, although once in long while, and I mean a long while, I will have one. But, never two in a row. In my situations when I have had those, a simple PC reboot solves the problem for me. Now, granted, this is but one case so I understand there could be issues for others out there. But, you asked about those who always run FSLTL, so that is why I answered. Normally, I don't like to post that I am not having a problem that others are, because it is not always helpful, although in certain cases such as this when someone asks, I will respond if I have information. AMD Ryzen 9900X3D & ASUS X870E Gaming Plus MB, w/64 Gb GSkill DDR5 RAM, PNY RTX 5090 GPU, lots of SSD's and M.2 drives, HAVN Case, Virpil VPC Panels 2 and 3, Virpil Constellation Alpha Stick, Virpil Rotor TCS Plus w/ Hawk-60 Collective grip, TM TCA Yoke Boeing Edition, TM HOTAS A-10 and F/A-18 Sticks and TM TPR Rudder pedals. Currently on Win11
May 5, 20233 yr Just got this for the first time ever (although I am on a new build). One thing interesting to note, however, is that post-CTD I noticed that the virtual memory was at >95% just before the crash. Related? One thing that is definitive is that it was not due to temps. The CPU was under 60C and the 4090 under 50C. I was using FSHud and FSLTL. Redoing the flight now but just bare-stock MSFS + the Fenix. Richard 7950x3d | 32Gb 6000mHz RAM | 8Tb NVme | RTX 4090 | MSFS | P3D | XP12
May 5, 20233 yr Yesterday I had the overheat warning on my left view client and today onnut server. As both 40 series graphics cards blow their hot air into the case I leave the doors open. Checked the temps on both below 70 degrees Celsius. It’s a MSFS thing I guess. 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
May 5, 20233 yr 6 minutes ago, GSalden said: Checked the temps on both below 70 degrees Celsius. It’s a MSFS thing I guess. Definitely. My 4090 was yawning from boredom when my crash happened. Richard 7950x3d | 32Gb 6000mHz RAM | 8Tb NVme | RTX 4090 | MSFS | P3D | XP12
May 5, 20233 yr Just now, cobalt said: Meaning what exactly? I think he means if you have a gfx driver that's working well for you, keep it. I'm in the process of rebuilding my system...and I haven't quite decided which version nvidia driver I'm going to install on it. On my old rig I have a driver from circa December/January that has worked well for my 3080ti -- but now I have a 4090 and all-new hardware in this new machine... Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
May 5, 20233 yr 30 minutes ago, Mace said: I think he means if you have a gfx driver that's working well for you, keep it. I'm in the process of rebuilding my system...and I haven't quite decided which version nvidia driver I'm going to install on it. On my old rig I have a driver from circa December/January that has worked well for my 3080ti -- but now I have a 4090 and all-new hardware in this new machine... I am on the 531.68 version and it seems to be working ok (despite a GPU-lost the other day)... Absolutely no reason what so ever to always be bleeding edge when it comes to GPU-drivers if it is not explicitly stated in the release notes that MSFS has had some work done on the new version. No. Reason. What. So. Ever. Richard 7950x3d | 32Gb 6000mHz RAM | 8Tb NVme | RTX 4090 | MSFS | P3D | XP12
May 5, 20233 yr On 3/31/2023 at 2:25 AM, bofhlusr said: I have 32 GB of RAM. Nothing is overclocked. The PC is problem free. I have about 1TB of NVMe free space in C:_drive where MSFS Steam version is installed. I've been using the same GTX1070ti graphic card for almost 5 years without problems. I also did a Windows system file integrity check: "SFC /scannow". No problems. I don't use an anti-virus. This is the first error since I started using MSFS in 2021. This might be unrelated, but I'll mention it anyway. I was testing a new joystick (Turtle Beach's Velocity One Flightstick) the day before and couldn't get the touchpad on the joystick to work. Is anyone using this joystick and getting the same error? Doing a restore to a restore point before testing the joystick did not fix the issue. The question is what I should do now. I'd hate having to re-install MSFS since there's no guarantee it'll fix the error. Since I get a CTD now, I don't have access to MSFS, Options. Any suggestion most welcome. @Altenae, did you recover from the error? This is exactly what I started getting just a few days ago. I just started a new topic before I saw this. Cheers, Pete Pete Solov - Lake in the Hills 3CK and Schaumburg Regional 06CProud AOPA Member - PPL 2001Real World Piper Cherokee Pilot
Archived
This topic is now archived and is closed to further replies.