Is anyone else hearing UPS flights being all called UPS 5 or 5 heavy? I'm assuming this is because on FR24, these flight numbers all start as 5X then flight number, so something like UPS 5X245. I reported it to them a while back, but this doesn't seem to be addressed yet.  

On 10/13/2022 at 8:11 AM, Corsten said:

Well, i am not home atm. I will do some benchmarks later before i will get on to this real time online more. But in theory, there is no fall back system with real time online, but you can make you own with "icao_generic = 1" atribute. Let me explain, choose model that has biggest amount of liveries -) go to that model folder and open aircraft.cfg -) change "icao_generic = 0" to "icao_generic = 1". In future, if livery or model isnt found by real time online, it will fall back that choosed model. But if there isnt livery for it, it will pick random one from that model. This way we should not see Asobos generic models, but if you do... there is "icao_generic = 1" is those models also. I have allways disabled those and used my 3rd party model as a fall back generic. B738 or a320 should work fine as "icao_generic = 1".

I think I have understood most of it. But wouldn't it be better to disable generics in general. If I'd choose B738/A320 as generics, wouldn't it show wrong liveries here and then, for example Ryan Air in Vancouver or Westjet in Salzburg ... And to disable the Asobo generics, where would I find these models?

I just did a flight and I'm sure I started "fsltl" properly. I could see traffic around me both on the MFD and the Aivlasoft Map (It was there)  but I could not physically see it either from the cockpit or using "outside" View. In fact yesterday I had traffic around me and I could physically see it. I run "fsltl-trafficinjector.exe" from my desktop even though I do have both the "base" and "injector" folders setup in the great "Addon Linker" app. Should I be loading the "injector" folder into the "Community" folder? I already do that for the "base" folder. I noticed that the "fsltl" Menu in the MSFS Toolbar was missing as well. Maybe it's just me, a one off or something.

4 hours ago, Nemo said:

I think I have understood most of it. But wouldn't it be better to disable generics in general. If I'd choose B738/A320 as generics, wouldn't it show wrong liveries here and then, for example Ryan Air in Vancouver or Westjet in Salzburg ...

Generics will show even though they're set to off in the menu though. Using Corsten's method there will probably (I'm not 100% sure) not be any generics showing. But - there will be wrong liveries, which IMO is a bit better. 

4 hours ago, Nemo said:

And to disable the Asobo generics, where would I find these models?

They're found in the FSLTL base models folder, if I understand your question correctly. Choose one of the A320 folders, then edit aircraft.cfg -) change "icao_generic = 0" to "icao_generic = 1".

13 minutes ago, TomCYYZ said:

Should I be loading the "injector" folder into the "Community" folder? I already do that for the "base" folder. I noticed that the "fsltl" Menu in the MSFS Toolbar was missing as well. Maybe it's just me, a one off or something.

Could be a one off. You don't need to have the injector folder in community unless you want the toolbar options. 

2 minutes ago, Cpt_Piett said:

Could be a one off. You don't need to have the injector folder in community unless you want the toolbar options. 

Thanks, good to know.

23 minutes ago, TomCYYZ said:

I just did a flight and I'm sure I started "fsltl" properly. I could see traffic around me both on the MFD and the Aivlasoft Map (It was there)  but I could not physically see it either from the cockpit or using "outside" View. In fact yesterday I had traffic around me and I could physically see it. I run "fsltl-trafficinjector.exe" from my desktop even though I do have both the "base" and "injector" folders setup in the great "Addon Linker" app. Should I be loading the "injector" folder into the "Community" folder? I already do that for the "base" folder. I noticed that the "fsltl" Menu in the MSFS Toolbar was missing as well. Maybe it's just me, a one off or something.

This is the dreaded SimObject limit introduced in SU10. I was getting a lot of these and frequently. I was able to get rid of it by removing the extra GSX clutter and not injecting parked aircraft in the injector. 

1 minute ago, Drumcode said:

This is the dreaded SimObject limit introduced in SU10. I was getting a lot of these and frequently. I was able to get rid of it by removing the extra GSX clutter and not injecting parked aircraft in the injector. 

Yes, that limit made SU11 CTD when trying to load the whole GAIST package. 

2 minutes ago, Cpt_Piett said:

Yes, that limit made SU11 CTD when trying to load the whole GAIST package. 

Is there a dedicated thread for getting rid of this stupid limitation? I'll vote. 

16 minutes ago, Drumcode said:

Is there a dedicated thread for getting rid of this stupid limitation? I'll vote. 

Not sure. I would definitely vote though. 

Does anyone know if the sounds are unique to each plane? or do they all use the same sounds? Would love to know.

3 hours ago, Cpt_Piett said:

Yes, that limit made SU11 CTD when trying to load the whole GAIST package. 

That crash isn't happening for everyone. I have the full GAIST package, and the full AIG package (yes everything) and the sim runs fine. So I don't think it has anything to do with that limit.

Edited October 23, 20223 yr by Tuskin38

9 minutes ago, Tuskin38 said:

That crash isn't happening for everyone. I have the full GAIST package, and the full AIG package (yes everything) and the sim runs fine. So I don't think it has anything to do with that limit.

It could still be related though, as I guess the total object count would be dependent on the number of addons. 

I have filed a bug at Zendesk of Asobo.

It appears SU10 has introduced this BS. I am worried about everyone who has not noticed this yet.

I refer to the pics below. Gamebreaking issue.

 

This bug causes following issues:

1) No AI parked at gates of EHAM anymore. They are alle stacked at airport roof. All of them in one.

2) This causes CPU lockup and frame rates drop below 10 fps. Especially when in the vicinity of these AI aircraft.

3) Issue seems to be related to certain airports and AI intensity.

4) Unable to get rid of them. Disabling AI does not remove the models. Stay stuck until the end of the flight.

5) No workarounds, happens to all of the AI-programs -> AIG/FSLTL..

Horrendous issues and again, it worries me no one noticed this. The bug report mess at Asobo does not tell me where my report actually went and if they are going to fix this. It is a bloody mess.

 

Well, it is not solved...

Are they serious with bug reports or joking around?

Closed, within a few hours. Can someone explain this?

Edited October 23, 20223 yr by Piotr007
mess

3 hours ago, Piotr007 said:

I have filed a bug at Zendesk of Asobo.

It appears SU10 has introduced this BS. I am worried about everyone who has not noticed this yet.

I refer to the pics below. Gamebreaking issue.

Closed, within a few hours. Can someone explain this?

I suspect the mention of FSLTL may have led to them classing it as an "addon issue" and not an FS2020  issue and simply closing the ticket.... Or the issue is resolved is SU11?

Edited October 23, 20223 yr by Vel

4 hours ago, Piotr007 said:

I have filed a bug at Zendesk of Asobo.

It appears SU10 has introduced this BS. I am worried about everyone who has not noticed this yet.

I refer to the pics below. Gamebreaking issue.

 

 

This bug causes following issues:

1) No AI parked at gates of EHAM anymore. They are alle stacked at airport roof. All of them in one.

2) This causes CPU lockup and frame rates drop below 10 fps. Especially when in the vicinity of these AI aircraft.

3) Issue seems to be related to certain airports and AI intensity.

4) Unable to get rid of them. Disabling AI does not remove the models. Stay stuck until the end of the flight.

5) No workarounds, happens to all of the AI-programs -> AIG/FSLTL..

Horrendous issues and again, it worries me no one noticed this. The bug report mess at Asobo does not tell me where my report actually went and if they are going to fix this. It is a bloody mess.

 

Well, it is not solved...

Are they serious with bug reports or joking around?

 

 

Closed, within a few hours. Can someone explain this?

Zendesk is just catch & dispatch. Solved means it has been handled by Zendesk and forwarded to the correct group.