I am using FSLTL for quite some time and have now added the AIG folder to my community folder.
But AIG models do not show up, for example no Emirates A380 at OMDB, just the FSLTL 777s.
In MSFS Content Manager, the AIG Beta folder is showing up as installed in the community folder.
I have toggled all possible switches in the FSLTL config file to troubleshoot this, but I cannot solve this. I have even recreated the AIG manifest.json with a special tool, but no change. I also used the console debug mode, but cannot see anything related to AIG.
I always read “just drop the AIG folder to the community folder and launch the FSLTL injector”. This is what I have done. I am using the latest FSLTL version offered in the FBW installer.
You could try copying the AIG folders (OCI/SimObjects/Airplanes) to the FSLT folder (SimObjects/Airplanes)
Important is COPY not MOVE.
This is what I did a long time ago and it has gone quite well.
Then choose an airport with a lot of movement, preferably at night and just by looking at the type of light on the planes, you will realize the huge difference between AIG and FSTL.
Be aware that some of the gate sizing at default airports means A380’s won’t appear. We have our A380 model coming soon in the FSLTL pack that will size the wing span appropriately to actually fit gates - but for now you might need to manually edit that value in the A380’s flight model cfg
All FAIB model folders in AIG install need to go. Do a search on here for FAIB models not being compatible with FSLTL.
Your install of AIG models will come down to just 20GB. Maybe best to do this to a copy of the folder instead. You do need the layout.json file recompiled with MSFSLayoutGenerator.exe
To check whether FSLTL sees the models, I’d recommend stopping FSLTL, removing the current FSLTL log file, then restart FSLTL. Go back and look at the FSLTL logfile, and at the start it will list out all available models, so there should be FSLTL AND AIG models listed there if it sees the AIG folder properly.
I guess the problem must be that Microsobo does not have the knowhow to solve AI issues. That also explains the many regressions and bugs they introduce each update. They don’t find experts or programmers for the AI Traffic Job. They copied pasted the whole AI System from FSX, because they have no clue about it
I don’t think Asobo is spending much time to trying and fix the AI. I think they have the know-how, and would improve the ai if that was important to the Microsoft bean counters.
About the missing AIG A380s all over the world: it seems real world A380-capable parking spots are not correctly defined in most sim airports, therefore little to no A380s parked.
I found a workaround this by modifying the following files:
aig-aitraffic-oci-beta\SimObjects\Airplanes\AIGAIM_TFS_A380-800_RR\flight_model.cfg
aig-aitraffic-oci-beta\SimObjects\Airplanes\AIGAIM_TFS_A380-800_EA\flight_model.cfg
In the files look for …
[AIRPLANE_GEOMETRY]
wing_area=3892
wing_span=262
… and change the wing_span to 200 and save.
This will allow A380 in heavy parking positions. Sometimes it is a bit tight for the whale, but I don’t care. At least I can see them now … The optical dimensions are not affected by this.
I have not noticed any downsides to this modification, let me know if you see any.
Are you with the FSLTL development team or doing a third-party mod? If with FSLTL, any idea if you will be including the CRJ / ERJ series of jets in this “pack”? Lastly, I know this is a tough one to answer but any feel for a rough timeframe? Getting close? Or sometime in 2023?
As is known P3D is a remake of FSX and the traffic there is not perfect but it is very functional together with ATC. For example, in airports I have the simulator’s own default (P3D) even there the planes land, take off, respect the distances from one plane to another (landing or takeoff) but if they don’t give a frustrate at the height that occurs in real life , ATC and air traffic are one of the things I miss from P3D, FSX and FS9. I don’t understand how a group of “professionals” from Asobo and MSFS can’t make this workable in MSFS where technology is so advanced
FSLTL and AIG friends. Is there any progress working with Asobo on fixing the Simconnect issue? Apart from reporting the issue and providing feedback, have you guys been engaged with their dev team to get this sorted?
This would also indicate that you think we have some way of talking to them directly. We don’t - just the devsupport forum.
We’ve been trying to get it fixed since the first SU11 beta started - but so far there is no useful feedback from Asobo.
I think the Q&A brush off of the topic made it pretty clear you shouldn’t expect anything soon from their end.
So we are continuing to look for workarounds - which is of course a complete waster of actual devloper time as opposed to adding new features.
Ultimately though anything done now is a workaround, this needs Asobo to actually fix the issue properly or at least provide some insight into fixing it.
