December 7, 20241 yr On 12/5/2024 at 5:31 AM, intheshadow said: Not sure what they talk. I'm using it myself and it's perfectly fine. Using fsltlt models and realtraffic. Sounds are messed up but I turn them down anyway. Lights need fixing, as can't be seen in distance. Not sure why so much hate. yeah I tangled with it on another thread and finally blocked it. Seems to be rarely right, but never in doubt. i7-6700k • Gigabyte GA-Z170X-UD5 • 32GB DDR4 2666 • EVGA FTW ULTRA RTX3080 12GB
December 8, 20241 yr On 12/3/2024 at 7:01 AM, jarmstro said: I got a CTD eith the FSLTL injector. Same Ed Windows 11 PRO-AMD RYZEN 9 9950X3D-MSI MAG X870E TOMAHAWK-NVIDIA RTX 5080 16GB-64GB GSKILL 6000-2TB NVMe-1050PSU- It goes to Eleven! Si ATC. IRL Pilot C152 - C172SP - PA-28-181 Archer II - Piper PA-28 Cherokee - Evektor Harmony - AOPA# 09053717 https://www.flightventuresaviationacademy.com/ https://www.pcflyers.org/
December 8, 20241 yr On 12/5/2024 at 3:46 AM, AnkH said: No hate, just clarifying facts. PSXT needs AI models from whatever source, without AI model, it would be completetly useless. So yes, the PSXT guy can basically call PSXT fully MSFS2024 compatible, but the AI models his software needs are not, at least not those from FSLTL and AIG. It is then rather unfair that people put FSLTL and AIG in a "bad" light, because they did not yet manage to make their stuff MSFS2024 ready but PSXT already did. It is just not the same, and this needs clarification. I don't think anyone is putting AIG or FSLTL in bad light. It's not their fault the planes aren't fully compatible. Nor is it PSXT fault that his program works. Until Asobo fixes issues these developers could not anticipate, we all must be patient.
December 8, 20241 yr 3 hours ago, knich said: I don't think anyone is putting AIG or FSLTL in bad light. Yeah, but here in this thread it was explicitly asked, what AIG and FSLTL do not get together because PSXTis already compatible. That is why I jumped in to put things into perspective. Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
April 2, 20251 yr My injector seems to default to this community path (mine is on a different drive in reality): C:\Users\userid\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\community\ Anyone know of a workaround Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
May 18, 20251 yr I have to manually make the right path everytime launching, even though its installed in right folder. Anyone knows how to fix this? i9 RTX 4090 64gb ram
Create an account or sign in to comment