I know this sort of thing has plagued the sim, but it is still going on, and this might be one of the worst I’ve seen:
N385Z is a Cirrus SR-22, for which I actually have the Asobo version installed in the sim. An A380 is a bit large for both representing this plane and for this small airport.
This is also happening in SU10, I first noticed it October 4th.
I didn’t make a bug report because uh, I was too distracted by the sim doing other things
I’ve reach the point of bug report fatigue. I’ve written a number of them within betas and outside of betas. Many, if not most, haven’t been addressed.
I wonder if model/livery matching is a server side thing, because I’m sure it was working fine before the 4th. It worked fine after SU10 released and during the SU10 Beta.
The only patch was for the Canada World Update, but I can’t see how that would have broken model matching.
Noticing it while monitoring the live traffic changes, it’s an absolute clownshow of inappropriate models and liveries. It was never this bad, occasionally you may get the odd wrong livery but right airframe or generic thrown in but I’m getting some way out of left field matches happening and it’s a major immersion breaker.
With FSLTL and AIG models installed I know there are multiple good matches available if it actually tried.
Significant regression here in my opinion, hopefully it is just caused by some server side weirdness and will be sorted in time.
I’ve been flying out of KPRB municipal airport (where my screenshot was taken) as my home airport for the year+ I’ve had the sim and I’ve never seen anything like this level of ridiculousness.
Here’s another example of it. That jumbo’s wing has collided with the building.
Again, this is KPRB — a municipal airport. I never saw this sort of thing at this location until SU11 beta. I’d know, because KPRB is my “home” airport and I fly in/out of here most of the time when I fly GA.
I was watching traffic at KATL while getting ready to fly to KDTW and all the flights were matching perfectly (at least 83 aircraft spawned while I was there), model and livery wise. Took off and flew to KDTW, enroute everything matches fine except for a King Air which spawned as a Turkish 737.
Once I started getting close to KDTW, I started seeing lots of mismatching, except for the airlines I saw matching fine at KATL. All the Delta and Skywest flights appeared to be matching fine for example.
Just flew from KDEN to KSLC. At KDEN tons of mismatching except for Southwest. Landed at KSLC, still some mismatching, but just like KATL, a majority (not all) of the Delta, Southwest and Skywest planes seem to be matching fine.
Can anyone anyone else duplicate my findings regarding those airlines?
If you’re using AIG make sure your Delta plans are up to date, as there was a recent change to the ICAO airline code for the Skywest operators for them.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
Yes
Have you disabled/removed all your mods and addons?
No
Brief description of the issue:
Whilst testing our AI fleet with SU11 Beta I have noticed that model matching is potentially worse than previous builds. Giving a specific example, according to flight aware DLH903 should be an A320 Neo, but despite having this aircraft included in our package (icao_type_designator = “A20N” and icao_airline=DLH) The model does not show for this flight.
Provide Screenshot(s)/video(s) of the issue encountered:
It might be fixed now. I sat at LAX for thirty minutes, the only mismatches I saw made sense.
For example A Delta A321Neo spawned with an S7 livery, but that’s because AIG doesn’t have a delta livery yet for A321Neo.
Couple generics spawned, but again they were aircraft models AIG doesn’t have in their library.
I wonder if matching is done server side, would explain how it seems to be fixed without a patch. It would also explain how it broke on SU10 without a patch
Sadly SU11 seems to have totally borked the model-matching
– even with FSLTL and AIG models installed which were displaying perfectly fine in SU10.
Random generics is what we now get at airports with SU11, see screenshot…
We can’t win either way…they’ve borked SimConnect injected traffic (AIG & FSLTL) and the model matching with the in built live traffic is now broken too.
AI in the sim at the moment is the worst its ever been.