Robert_LH

I think I noticed this as well, if we are talking about the same thing. In my case the aircraft were just hovering/swaying sideways across the tarmac and through buildings with high speed. Kind of uncontrolled and eratic. I only saw this thread now, so no log text. Next time I‘m seeing it I will try to post it here.

Nico, I think I found the mistake with the radius. Some gates had a too wide radius. I have edited it again and checked thouroughly and now the collision issue is solved. I`m sending you the updated park_airport file again, if that is alright with you. Sorry for the mix up.

Edited/updated answer. See below :)

Hi kiek, as already mentioned in the above message, here is a full log text example. Again there seems to be a conflict although the parking stands are wide enough and are used like this in real life too. GATE A3 : no static parking for UAL124, static aircraft THY8FW* is adjacent at GATE A1, possibly colliding GATE A9 : no static parking for DKH1657, static aircraft PGT1191* is adjacent at GATE A11, possibly colliding I think this maybe the reason for missing aircraft. It would be great if you could have a look into this. My log text LGAV

Hi Nico, I`m going gto try this. I actually just checked the log file as well after missing some flights which should be there. GATE A7 : no static parking for BAW630, static aircraft UAE3TK* is adjacent at GATE A9, possibly colliding GATE A9 : no static parking for UAE3TK, static aircraft AIZ213* is adjacent at GATE A11, possibly colliding Could this maybe be the reason why I see less traffic than expected, even if "Auto Park" works as intended? Is there a way to change this behaviour, so that all aircraft show up?

Hi Nico, it`s me again. ;-) I have been playing and experimenting around with the new version 15.5.0 at my favourite airport LGAV: I really enjoy both accurate parking stand allocation as well as populated airports. So I tried different settings. I noticed of course that with "RT Parked only" I get the most realistic parking as it is actually happening in real life right now but not that many aircraft at the airport (as written in the documetation). When I check the Auto Park Function I get a well populated airport (the amount I put in target %) but unfortunately at the same time I`m losing a lot of the real life RT parked aircraft, which is a shame because it kind of kills the immersion a little bit again. (There was a message at the bottom, for example: "Parking Adjustments: 10 to be removed, 16 to be added"...sadly some of the 10 removed were very nice and accurate RT parked aircraft) Therefore I was wondering if there is a mode to inject all the RT Parked Traffic first and keep it visible (as a priority, kind of) and then fill up the remaining empty stands to the desired target % with Auto Park? I used your PSXT Tutor for more information and this is the quoted result: "No there is no dedicated mode for that. The two modes follow different strategies: -RT Parked Only: uses exclusively the parked aircraft data provided by RealTraffic -Auto Park: PSXT decides on its own which combination of RT Parked data and airport-file data should be used to achieve the configured Target % value. There is no documentation stating that all RT Parked aircraft will always be preserved. If your goal is: “All RT Parked aircraft should remain visible, and only the missing stands should be filled using airport-file data.” then that would effectively be a third mode, which is not described in the current documentation. For LGAV, I would therefore recommend: If real-world accuracy is your highest priority → RT Parked Only If a well-populated airport is more important → Auto Park If Auto Park removes RT Parked aircraft even though sufficient parking stands are still available, that may be something Nico would want to review or refine. The release notes do not explicitly state that Auto Park must always give priority to RT Parked aircraft. They only state that the various data sources are combined to achieve the configured Target % as effectively as possible. Therefore, your expectation — “RT Parked Only plus airport-file aircraft added on top” — is perfectly understandable, but it does not appear to be exactly how the current Auto Park logic is implemented. So Nico, do you think it would be possible to refine this function? Or is this too difficult to achieve? Kind regards Robert

Hi kiek, thanks for your reply. I think I missed this part among all the instructions/suggestions. My bad.... ;) I`m going to edit the stand data now and send it to you as a zip file. Regards

Hi kiek, I already consulted your fantastic AI tutor and would like to get your opinion as well if you don`t mind.... As the title says I would like to permanently edit/change the type and radius of gates and stands in the "park airport" file. The reason is the following: I`m flying a lot out of LGAV/Athens and the airport in real life has a really nice widebody aircraft line-up in the morning between Gates A01 and A13. Unfortunately I noticed that some of these gates were never occupied by widebody aircraft when using PSXT. They were either completely empty or populated by smaller aircraft which was not correct for that time of the day. So I had a look into the "park airport" file and noticed that some of theses gates where a widebody jet should be had a typestr="GATE_MEDIUM" and a small radius, for example radius="19.0", meaning that the small radius rejected the correct large aircraft from showing up. I experimented a bit and manually edited the park airport file and gate stand to typestr="GATE_HEAVY" and also edited the radius to a larger radius="30.0" or even radius="40.0" and suddenly each time the correct widebody jets were sitting at the gate, like in real life. When I exited MSFS however or switched to a different airport all changes were overwritten once I got back to LGAV. So I used your AI tutor to ask how to permanently overwrite the file and the program said that this is not supposed to be done. The workaround it suggested to me was to create a complete handmade LGAV file in order to replace the archived version to keep it from overwriting. But it also mentioned that this would mean I no longer receive any archive updates.... That´s why I´m writing to you here. What would your suggestion be? Is there another possibility to solve this issue? Kind regards Robert

Please ignore, edited after irrelevant entry.

I think that‘s the reason for my misunderstanding on my part. Somehow I thought there was a similar airline concept as well…

That would be great as I‘m away from home for work a couple of days. So in order to stick to the above example of the Norwegian flight: I noticed this on a particular flight on May 21st, Flight D8 2901 (Callsign NSZ2901) departing from Barcelona LEBL to Helsinki EFHK, around 10:30 a.m. local time BCN. (~8:30 am UTC) For me it turned into a Tui 737 in matching depth 7 or disappeared completely in matching depth 3.

What I don‘t really understand about the matching logic is the following: I have over 8000 liveries installed, all coming from AIG, FSLTL und JustFlight. Why does the matching mechanism go to a complete different airline or model, even if I have a similar model/livery in my installed packages? For example: I tried playing around with the matching depth as you guys suggested. There was supposed to be a Norwegian Air Sweden Boeing 737 taxiing for take off. I switched the matching depth to 2 and 3 in order to experiment a bit and the aircraft disappeared in the sim because it apparently didn‘t find the correct livery for this particular flight. As I really want to see all available traffic around me, I switched the maching depth back up to 7. Now the aircraft appeared again but in a Tui Livery, which was obviously incorrect and spoiled the immersion. So my question is: If PSXT in this case did‘t find a matching Norwegian Air Sweden livery, why didn‘t it alternatively come up with a normal Norwegian Air livery for the 737(which livery I definitely have as for example the airport Oslo is full of Norwegian planes when I load it up). I think there is not even a difference in the appearance between the two operators other than the slightly different official name and the airline code. And even if this is not possible for some reason, why didn‘t it at least show up as a white paint when I’m using matching depth 4 (as written in den Manual, if I understand the mechanism correctly), instead of disappearing completely? Then the aircraft would at least be visible as traffic, even if just in a generic white livery. Can you maybe shine any light on this?

Hi kiek, I think its a misunderstanding. I read the FAQs but the problem seems to be different and something I have never seen before. I would like to share an observation with you for a specific flight, again at LIRF, Rome. It was Easyjet flight U2 2992/EJU95ZU from FCO to FRA. The flight is operated by an Airbus A319. However the flight showed up at the gate as an all-white Boeing 737. It started taxiing out and then on the taxiway it suddenly became the correct model A319 and the correct livery Easyjet and continued taxiing to take off. I checked the log file again and this is what the original flight at the gate looked like: EJU95ZU_ FCO->FRA EJU B736 =6= JustFlight_AI_737-7_White If I had any missing models, how could it change to the correct model all of a sudden during taxi?

Hi kiek, but ITA only has a pure Airbus fleet. Why would these aircraft show up in the sim as 737 of Malawi Airlines or United Airlines?

Or this log text here. The wrong liveries/aircraft always show up with e Boeing 736 ITY348_ ITY B736 =6= AIGAIM_Malawian Airlines Boeing 737-700WL ITY1383_ FCO->GOA ITY B736 =6= FSLTL_B737_GNJ-Hercules Jet-STUB