I had no issues with V1.0, but so far with V1.1 its stuttering horribly in busy areas (Ex. Vatsim KBOS was busy tonight and my performance was horrible, I did several test flights). Never had an issue with V1.0.
Edit: can confirm removing FSLTL V1.1 models and running with only AIG models for model matching and performance is perfectly smooth again, even at busy airports. Something is wrong with FSLTL V1.1 models. They cause an enormous performance hit, V1.0 did not.
Since the update, I’ve flown 3 times and each time, the airport was probably 80% empty. I’ve got IFR at 130, VFR at 2 and Static aircraft at 7. My last flight I flew into KATL. Two terminals didn’t have a single aircraft at the gates, the other 4 were looking normal. What’s going on here?
Don’t forget that you may need to reduce the size of the images like we did as described above. My installation went from 22 gig to 2.5. I assume that would impact your performance.
I have a question about the range impacted by the mod. I see where the minimum you can select is 50 miles (or km, I can’t remember). Anyway, let’s say that I’m starting at Burbank (KBUR) and I want to fly to Dallas. Would it make sense to be able to select two miles as my range because I only care about planes that are within that circle? If I’m flying east, I wouldn’t care about planes spawning at KLAX or any of the other southern California airports. And after I take off, I can always alter the range to be 50 or more so I can pick up the planes as continue flying. Then as I get closer to Dallas, I could again decrease the range to 5 miles or whatever. My assumption is that if I could do that, FSLTL and MSFS would have less planes to deal with, which in theory would reduce the overhead.
It’s just a thought…?
those parked aircraft may start moving if the injector picks an outbound flight with that airline and plane model, so they are not really static.
Yes, highly recommended! I reduced the effects textures to 256 and the aircraft textures to 1024 px. And for those thinking this might be too small: unless you are the type of simmer that taxies along busy international hubs for hours admiring the wealth of nice and crisp liveries, you won’t notice any blurryness on the AI planes. You have to be nearer than say 100 m to see slightly unsharp textures. And this doesn’t happen at 99.5 % of the time.
Reducing the VRAM usage by the AI planes by 90% definately is worth it.
You will find the TextureOptimizer and a detailed description here: https://izn-flightsim.s3.amazonaws.com/textureoptimizer.html
100% absolutely agree.
Having said this I think the vast majority of simmers greatly appreciate the effort being put in here by the devs 
There is always a small minority of users who will always be negative and complain ‘come what may’ for some reason but I think they are just that, a small minority.
Yes, great work here by FSLT.
Thank you 
I have exactly the same issue and I cant reach the website either. Any ideas?
Don’t be discouraged by toxic people guys. Keep up your great work, it’s greatly appreciated here.
Their discord is quite active and they are super helpful, you can ask your question there if you want.
I confirm, I used the tools provided on your link, I reduced the liveries in 2048, my FSTL traffic base file went from 27 GB to 9.65 GB and I don’t see any difference in quality in the simulation.
Seems like we are the only one with this issue in the forum at least.
Have yoy found a solution for this error in the Fs injector installer ?
I don’t use discord and I can’t ask for support there.
Just by chance is your FBW installer up to date? There was an update to the installer very recently. This sounds like a FBW installer issue.
Yeah I have 3.3.3 as well. I just noticed in Settings->Download there is an option to disable version warnings, have you tried that?
You could also try a Settings → Reset Settings and try again. I have no installation issues with the FBW installer. Which also has its own discord. Its worth signing up to getvsupport though.
Also did you remove any old version in Community first?
traffic injector is working properly, even with the new models added, A380 etc.. the issue in my case is that installer doesn’t recognize that injector is installed.
before every single flight I check for very add on updates Fenix A320, PMDG, GSX and FBW installer add ons and apps.
i love seeing all the crisscrossing trails
and then there was this one that apparently forgot something back at the airport 
Thank you for the link, doing it right now and works well. Decrease it to 1024 and will see.
I hace my injextor exe file located outside of community so maybe thats why I dont see this issue? The injector Exe can be relocated anywhere.
