July 4, 20241 yr Author 5 hours ago, Noel said: This must be somewhat recent, no? If so just remove the latest entries in blocks of say 5 at a time to get to the bad guy quickly. Difficult to say, the "issue" with the FSR500 taxi light I recognized some months ago, but as I am not flying that much those days I did not really care about it. Only when seeing that the PMDG 777 landing light had a comparable issue, I wondered if something is broken in my sim... Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
July 4, 20241 yr 1 hour ago, AnkH said: Difficult to say, the "issue" with the FSR500 taxi light I recognized some months ago, but as I am not flying that much those days I did not really care about it. Only when seeing that the PMDG 777 landing light had a comparable issue, I wondered if something is broken in my sim... Did you check with a default aircraft whether it has the same issue? if it does, the next simple step is to disable your community folder and try again. If that still doesn't solve the issue, you know at least that you don't have to sort out which addons are the cause and move to troubleshoot settings Flightsim rig: CPU: AMD 5900x | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking
July 4, 20241 yr Author No, the default Cessna 152 for example does not have this issue. I now disabled everything via AddonLinker, means only payware adns with installers remained and the issue persists. Bummer. Now reinstalling FSR500 to see if it is a borked installation of this plane (even though the 777 should have no issue then). Starts to get strange... if reinstalling FSR500 has no effect, I need to go with an empty community folder, but then, will the FSR500 showing the issue also be gone, no? and the 777. So how could I test it then... Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
July 4, 20241 yr Moderator 5 hours ago, AnkH said: if reinstalling FSR500 has no effect, I need to go with an empty community folder, but then, will the FSR500 showing the issue also be gone, no? and the 777. So how could I test it then... IMHO, you need to START with an empty CF. If problem persists you have eliminated everything in CF. If problem goes away, then issue lies within CF. Unless I missed something you haven't done this - should be first step - determine where the problem lies. Also, I assume you did do a repair install of MSFS correct? RIG#1 - I9 14900K MSI Pro z790 RTX 5070Ti 40" 4K Monitor 3840x2160
July 4, 20241 yr Author With this cumbersome approach I found the causing addon. It was surprisingly the A2A Comanche. Luckily, a simple re-installation of the addon solved the issue. So root cause remains unknown... and it took me more than 2h to get to the point I found A2A addon to be the causing factor. Thanks all for your suggestions! Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
July 4, 20241 yr Yeah, the most efficient way is taking every single addon you have, payware, freeware even liveries completely out of the equation. Addon linker is indispensable for this reason. Then your sim will load rather quickly. Though the root cause, you mention...yeah hard to find that. Glad you were able to fix the issue. Edited July 4, 20241 yr by Sonosusto 7800+4090+64ram Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.
July 5, 20241 yr It might be a cumbersome method but it is the only sure way to troubleshoot an issue caused by an addon. And it only took 2 hours. Great that you could find it and even fix it. Flightsim rig: CPU: AMD 5900x | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking
July 5, 20241 yr Author True, feared it will take longer but with reducing number of addons loaded, the sim of course started up quiet quick. But I was down to four addons before I found the bad guy, the first 450 addons removed had no effect 🙈 Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
Create an account or sign in to comment