@ACSoft47 There was no missunderstoodning here by me. I was so annoyed from you about this matter, so i did dig up more with this “problem” “we” have. As i said before, it has to be problem with the 3rd party airport you are using and it certainly isnt problem with GAmod. And it is like that i said. So your Simvol version has those “front of terminal” parking spots typed as “Ramp GA medium”, so im not suprised you got GA aircraft spawning there. Even stock MSFS is making those as a GATE. And payware version (pilot experience sim) offcourse made it correctly… as a GATE.
I even contacted the developer of that freeware airport you are using, to change those parameters to be right ones. I just cant do nothing more for you for this matter. GAmod works as it should be.
The “Gate 4” name in the simvol version is the confusing thing here, but it is just a name, what is relevant is the TYPE, and that is “RAMP GA Medium”. You could also call the “RAMP GA Medium” something like “Aircraft Deposit Site 4” instead of “Gate 4”, it would still be a “RAMP GA Medium” for the sim.
Slightly annoying and confusing that you can name each parking spot basically as you wish independent from the actualy TYPE, but thats how it is. Many, many scenery devs do it this way sadly, FSDT was some time even worse just using “RAMP MIL Cargo” as TYPE instead of gate…
@C0rsten, I really don’t understand why you put this matter only on the level “is GAmod guilty or not guilty” ? Or is it the airport author which is guilty ? Or even, maybe the user (me) to use an incorrect addon ! But this is not the problem ! This addon is maybe perfectly correctly defined, with both “Gate & GA ramp medium”. Maybe, in the mind of the author, this configuration want simply to reflect the reality of this airport gates in front of the terminal, mainly gates for commerial flight, but also, alternatively a GA ramp for medium aircraft.
The guilty, if we absolutely need to found one, is the code who choose the spot, which is not able to analyse the whole aircraft spots situation (something probably very complex, apparently because of the freedom to mix everything) at a given moment and return the most appropriate spot. In our example, the free “GA ramp small” only, on the side place. Is this code under your control ? Probably not, this is why I asked if maybe it would be possible to create some kind of exclude spots list by airport. Apparently, you said it is not possible.
Since the beginning I contact you in the meaning to help you and I gave to you the example of this LFKJ by Simvol which was illustrating perfectly this particular case of the mess around these aircraft airport spot definitions. Since the begin of this conversation, I have made more tests on more airports and found, of course, other bad situation when trying to mix these traffic type, by using GAmod along with FS Traffic. I have even contacted FS Traffic guys to question them about this matter. They told me they are aware of the situation and that it is even the reason why their GA feature is delayed.
@ACSoft47 Well, your point of view was whole time, that i need to do something for you to get that airport working. Here is quote from you:
“I thought it might be helpful to you, to use this Simvol LFKJ version 2.6 for tests, because it is obviously problematic with your addon, but apparently correctly designed. It may perhaps help you to improve GAmod.”
You were 100% sure, that airport is correctly designed and i have to make gamod to work with it. Wich is impossible task to me work on, as i said earlier. It is nonsense, that size of that airport that has big terminal, has RAMP_GA_MEDIUM´s front of the terminal.
And why you are saying this: “I choosed the Simvol version and NO this is NOT the same work, author are different.” when i just pointed to you, those are same pictures. So yet again, i dig up more. Author in both are jolouv.
No, I never said that !!! I said “but apparently correctly designed”.
Now, you pretend that both Flightsim.to & Simvol have the same author and what ?!? It is NOT the problem !!!
For the last time, I though you might be interested to test this specific LFKJ addon, to see if maybe, you can avoid this specific problem, which is just one of the numerous problems the GA implementation in MSFS can cause. In brief, if you would be interested to discuss about this matter. It is apparently not the case, so continue to think that GAmod is perfect and that any problems the user may encounter are his personnal fault or the fault of the airport 3rd party.
Sorry, but now, I have enough of this steril conversation. I have already uninstalled GAmod and do not plan to use it later on, not only because of this specific problem, but also because all the other’s problems I also found during my tests and the impossibility to have a constructive dialog with you.
I will wait to see if JustFlight will be able to do better with their own implementation of GA in FS traffic.
I wish you all the best for the future of your GAmod.
Because, in the time I was initially searching an LFKJ addon, it was the only one available on Flightsim.to. But it had multiple problems, so I continued to seach Internet and found the Simvol version, wich I adopted.
So I was trapped by the fact Philppe Louvet decided to switch to Flightsim.to, without to warn his users of the Simvol version that it was not anymore updating his LFKJ on Simvol.
So, I decided to test this Flightsim.to last 2.7.1 version, but as you can see, the problem is still there ! We have small GA aicrafts on “Gate / GA medium” spot, in front of terminal and empty lateral parking spots.
Anyway, thanks a lot, to you to have made me aware of that fact. Now, I know that, if I want to stay up to date with Philppe Louvet addon, I should now follow it on Flightsim.to and forget Simvol !
As written before, the problem is that the parking spots have the “GA” classification, no matter how the dev finally calls it (here “Gate”). The sim only checks if there is a match between the classification and the aircraft.cfg entry, if it is a match, it will place the plane there, no matter how the dev calls the spot. He could easily call it “Big Airliner Parking Spot”, as long as the classification is still “GA medium”, GA planes will end up there. So he needs to adjust his parking spot classification… Sadly, as written before, many scenery devs go this route, reason unknown (might be a remnant of a workaround that worked back in FSX/P3D days)
Yes, and Philppe Louvet did promise to change that for next update of flightsim.to version. I did ask him to do the changes for someone here. “V2.8 is in progress with a new Gendarmerie bulding” he did response to me.
who wants to beta? Final release is atleast one week from here. I need to contact all the model copyright holders, them to give me permissions to add models to GAmod. And light master Nicottine will hopefully do lights to new models next week. But beta i can share!
What I would interested to know, is who choose the spot, where the given aircraft will be placed ? I mean, is it fully the MSFS inside code, without any possibilities for GAmod to interact with that ?
I understand the Gate/GA problem, but my main concern in this case was, why placing a small aircraft on a medium spot, when you still have a lot of free small one, is also something stupid ! But I guess this is certainly done by the old Microsoft code and probably GAmod cannot do anything about that.
Correct.
By using the GA parking spot definition, it prevented the sim’s default GSE from surrounding the user airliner when on stand. This was important to prevent clashes between the default GSE and either GSX or PMDG’s own ground equipment.
