Kaiii3

not needed, but can not harm to enable it 😉

correct - flightplans are updated on a regular basis by the AIG Team 🙂

good to know that the design as its issues with smaller screens.....

yeah. For those not on the forum: There is a Link to PayPal on our homepage as well: https://www.alpha-india.net/

Thanks Ray, it is not just the servers, those are actual by far the cheapest on our bill. The raw-data is far more expensive to get and we use regular 100% of the donations to conver a big part of those yearly payments, while the Team internally covers the rest. The ammount we pay has drastically increased over the last years (like with every other service world-wide). In fact we might start looking around at different data-providers to see if we can find a btter plan that covers our needs at a lower price. At the moment we had a 1 time pay for all the data-plan, this makes it very expensive but it is a "fire and forget", no need to think about the number of airlines to update. Provider like FR24 or FA provide their API on a request basis, we would have pay for each request/response making it far more unpredicable in the long run.

Should be active now 🙂

Jay is still testing some stuff

just to keep you updated: AIGs report is send to ASOBO

Test-Package for ASOBO will be delivered to them next week so we can get a feedback on what is the issue.

The Sim still ignores "valid" LODs on our models. We have checked with SU4Beta and are preparing a test-case for ASOBO at the moment to replicate the issues.

Models are 2020 native and build in 2020 by our developer (he has no 2024). Weitere saw those missing wheels/ignored LoDs already in 2020 so I am not sure if this is actual a 2024 only issue.... When I am back home I will collect some data and forward that to ASOBO

No idea, Jay (our 3d-design guy) is still on 2020 and we have actual all no cluewhy the SDK values are fine but the Sim rrsultis different.

Fun fact: AIG models are designed within 2020 LOD Limits and have 5 LoD. Sadly the Sim ignores those and culls the wheels (those are part of the LoDs, so it sees the Sim is fa strikter then its SDK limits)

Report via our Forum or Discord, there are the guys that might can fix this 🙂

how big is the parking-spot in the scenery?

If you use AIGTC with FSHud, you only need to enable external in FSHud ans FSHud in AIGTC

On the "main" OCI page the orange box will be removed if it is already enabled, since you have already the recommended settings. If you want to disable it again you have to go via the Settings-Page as shown in a few posts above.

not if the airports is designed according to SDK 😉 There might be around 0,5% of strange parkings with the smaller regional airplanes that end up in GA stands that are actual set to a to big-size in the Sim

well, the issue was introduced in one of the "performance" updates by ASOBO...

correct, ASOBO is informed and made already first improvements on LODs in SU3. Sadly those did not had any impact on AI models.... At AIG we are aware of the issue but have so far no clue how to workaround it, while mantain fully SDK guidelines. Our main modeller has not yet moved to FS2024, but is planning to do this later this year. Maybe at that point we have more luck with workarounds or tell ASOBO what needs to be changed. And before some asks: The provided LODs of each airplane have the wheels included - it is just the Sim that ignores the LOD files and cuts them anyway....

1) Make a backup to be sure no data is lost (save the aig-aitraffic-oci package) 2) Remove the old folder 3) Start AIM 4) Setup OCI again 5) Move the baclup content (besides manifest.json and layout.json) back to the location 6) AIM should pick up OCI again

There has been no modelupdate from AIG this year - so all changes you see are all within the Sim itself and caused by ASOBO

regarding the LOD's: All AIG mdoels have at least 5 LODs so they are developed according to the SDK. But it seems that the game is "overriding" those LODs with its own calculations. This results in the "removal" of small objects (mainly the gears). We have ideas for workarounds but those will definatly have an impact on the overall performance... Lets hope ASOBO comes up with a fix and I am sure Jay is testing different solutions/workarounds at the same time as well 🙂

Regarding any public information I suggest to watch the FSExpo Video from 2024. Jörg showed there some 3rd party involvment 😉

There are several over at flightsim.to at the moment we do not provide a VMR file, but this might change.