Simple Traffic
-
Posts
50 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Posts posted by Simple Traffic
-
-
On 8/6/2022 at 12:25 PM, Skypat said:
what did you change between 1.2.1 and 1.2.2 ? (apart adding skins)
1.2.2 only adds new livery texture files and new offline AI flight plan files - there are no other changes. Parking codes were added previously in 1.2.1.
On 8/10/2022 at 2:20 PM, Skypat said:a free(!) product like "aig-aitraffic-oci-beta" liveries works fine at EBBR or others airports with "ground aircraft density" slider above 0 and ALL planes have random liveries (no problem) but there are from AIG mod folder's liveries not default asobo's.
Some other AI traffic add-ons modify or delete protected internal MSFS files in order to block default MSFS AI models and liveries. Our policy with ST is never to modify internal MSFS files - we will only ever add new files. The upside is system stability because this way ST operates within the rules of the SDK and MSFS Marketplace. The downside is that default liveries may sometimes still appear alongside ST liveries in certain (rare) circumstances.
On 8/8/2022 at 10:05 PM, RogePete said:But maybe there's a way to turn off the stock livieres at all, so the sim at least chooses any real / Simple Traffic livery instead of the stock ones. That was the question.
You can minimise the selection of non-optimised and non-ST aircraft as AI (airborne and ground) by using the following recommended sim settings:
OPTIONS - GENERAL OPTIONS - TRAFFIC - AI AND MULTIPLAYER TRAFFIC DETAIL - USE GENERIC AIRCRAFT MODELS (AI TRAFFIC): ON
OPTIONS - GENERAL OPTIONS - TRAFFIC - AI AND MULTIPLAYER TRAFFIC DETAIL - USE GENERIC AIRCRAFT MODELS (MULTIPLAYER): ONTo completely block the selection of a particular aircraft as AI (airborne or ground), in addition to the above setting, it is also necessary to modify the config files belonging to that aircraft. We do not recommend this and it is not supported, so you do so at your own risk. Locate the other aircraft's package folder and edit the aircraft.cfg file to apply the following config setting:
icao_generic=0
For example, to block the sim from using the default A320 NEO as AI (which is the default aircraft appearing in your screenshots), edit its aircraft.cfg file located here :
\Official\[...]\asobo-aircraft-a320-neo\SimObjects\AirPlanes\Asobo_A320_NEO\aircraft.cfg
Be sure to take a backup, and note that manual edits to official internal files will be automatically overwritten during sim updates.
More info available in the SDK here: SDK: Additional Config Information
On 8/10/2022 at 5:45 PM, RogePete said:maybe it's an issue with the airports and how their gates and parking positions are coded.
The sim will place AI aircraft in airport parking spots where the parking code matches the aircraft atc_parking_code, or where either the airport parking code or the aircraft atc_parking_code are blank. ST aircraft all have standard airline ICAO codes ('AAL', 'BAW', etc) defined as their atc_parking_code. In this case, according to your observation in Little Nav Map, the airport parking codes are neither blank nor standardised airline ICAO codes, so the sim will only place aircraft with an atc_parking_code which is either blank or ',,,,,' in those parking spots.
-
2
-
-
17 hours ago, fenflame said:
Part of this observation is the multiple calls to AI traffic that they are below or above assigned altitudes.
If I remove ST everything goes back to normal with much less radio chatter.Hi fenflame
AI piloting and ATC comms are controlled by the sim, not by Simple Traffic. Please see this MSFS forum post for details relating to this issue, and to vote for fix: AI traffic repeatedly being told to expedite - Bugs & Issues / ATC & NAVAIDs - Microsoft Flight Simulator Forums
-
1
-
-
Also, the widest parking spots at the default EGNX airport are only 92 feet wide, which isn't wide enough for airliners to park in (whether Simple Traffic or stock sim MSFS airliners). The width of the parking spots is defined internally within the sim, so unfortunately not something we can influence.
If you're using an add-on version of the airport which has the parking width defined to be wide enough, then you should see some Simple Traffic planes there too.
-
2
-
-
Thanks for all the suggestions so far everybody. We'll add as many of these as we can in the next update!
-
3
-
Major (strange...) Bug since 1.2.2 (not present in 1.2.1)
in Simple Traffic
Posted
The FLIGHTSIM.0 default entries are there by design. They are not the MSFS default multicolour liveries, but custom ST blank liveries.
In the early days of ST, the sim's internal model-matching logic would automatically 'fall-back' to the default non-coded FLIGHTSIM.0 variation for any real-time AI flight whose ICAO airline code did not match any of the coded livery variations included in ST. This was a good system, because many would agree that a blank livery is preferable to a random incorrect livery. Unfortunately, Asobo subsequently changed the internal model-matching logic, so that it now selects a random livery for any non-matches.
We've left the blank FLIGHTSIM.0 entries in place in the hope that Asobo may one day change that model-matching logic back to the way it was before, as per another ST user's poll here:
https://forums.flightsimulator.com/t/on-line-ai-model-matching-for-not-recognised-lcao-codes/466509
No, in this case the sim is not selecting the FLIGHTSIM.0 entry for those problem parking spots. In fact, according to the screenshots provided, the sim is not selecting an ST aircraft at all for those problem parking spots, because the models in those spots are all non-ST A320 Neos (smaller size and rounded nose).
Currently, the only time FLIGHTSIM.0 entries come into play is when the sim's model-matching logic selects an ST model and then makes a random livery selection across all of its livery variations (including FLIGHTSIM.0), so there is no reason to take them out.