Products Support > GSX Support FSX/P3D
GSX AI Jetway detection
virtuali:
--- Quote from: DLH7LA on September 03, 2020, 11:50:34 am ---Now we are talking, with default AI it connects without any problems
--- End quote ---
Well, at least you should now be convinced the problem ARE THE AI, not GSX.
--- Quote ---So where is the difference to FLAI models?
--- End quote ---
It might be a difference, even a small one, between the SODE internal models database ( which SODE uses when its on its own ), and the data GSX gets from Simconnect.
SODE has a database of generic models, while GSX uses its own data, which is usually way more precise, because it's made for the user airplane, so users can customize very precisely their own airplane for GSX, and this will sent to SODE, which will use it INSTEAD of its own generic database when it's used together with GSX.
While this is clearly better for the user airplane, when AI are used, GSX is not using its own database ( because it refers to specific user airplanes so, a PMDG 737 is NOT the same as an iFly 737 ), it takes data from Simconnect, which means it takes you [Exits], and applies a generic correction, because the data on the [Exits] refers to the CENTER of the door, while the data GSX and SODE normally use are referred to the BASE of the door, which of course is the better approach for service vehicles, while the center might be more useful for jetways, which were the thing the [Exit] data was initially designed for.
SODE has its own database of generic models, and it also applies an offset, and has some correction factors is, which means what you put in the [Exits] section is not used "AS IT IS", neither GSX or SODE will use it as it is, each one will have some correction applied, and your problem might be you are off of JUST enough to make one correction working, but not the other.
I'm sure you should be able to find a value for the [Exits] that works both for GSX and SODE.
DLH7LA:
--- Quote from: virtuali on September 07, 2020, 11:06:57 pm ---SODE has its own database of generic models, and it also applies an offset, and has some correction factors is, which means what you put in the [Exits] section is not used "AS IT IS", neither GSX or SODE will use it as it is, each one will have some correction applied, and your problem might be you are off of JUST enough to make one correction working, but not the other.
I'm sure you should be able to find a value for the [Exits] that works both for GSX and SODE.
--- End quote ---
And there is the problem, I have all [EXITS] correctly adjusted to work with SODE jetways and the way you put it, there is minor adjustment needed to make them connect the GSX jetways. But then I ask you how it comes that not a single GSX jetway starts to randomly connect to ANY aircraft model? If you say it works with other 3rd party AI, where is the difference between them? Im quite sure there is some more data (in the model, in the aircraft.cfg, wherever) GSX needs to move the jetway. Maybe it is because PSXseecon injects the traffic via .bgl and not via AI Traffic? But then again, how come SODE jetways are cabable of identifing the injected traffic but GSX is not?
virtuali:
--- Quote from: DLH7LA on September 09, 2020, 08:13:25 pm ---But then I ask you how it comes that not a single GSX jetway starts to randomly connect to ANY aircraft model?
--- End quote ---
As I've said, with YOUR AI set, after YOUR adjustment. Without checking all of them, one by one, I cannot possibly say.
--- Quote ---If you say it works with other 3rd party AI
--- End quote ---
I don't just "say": I posted a SCREENSHOT showing proof they do, with UT Live.
--- Quote ---where is the difference between them?
--- End quote ---
Not possible to say, without looking at your AI and your changes.
--- Quote ---Im quite sure there is some more data (in the model, in the aircraft.cfg, wherever) GSX needs to move the jetway.
--- End quote ---
No, there isn't. For AI, it ask the sim through Simconnect, which reports data about the exits, which are taking from the [Exits] section of the aircraft.cfg.
--- Quote ---Maybe it is because PSXseecon injects the traffic via .bgl and not via AI Traffic?
--- End quote ---
Exactly like UT Live does.
--- Quote ---But then again, how come SODE jetways are cabable of identifing the injected traffic but GSX is not?
--- End quote ---
It seems you haven't read my previous post carefully enough, which explained the differences. I'll repeat it again: SODE has its own AI database with *its* own correction factors, GSX use Simconnect with *its* own correction factor, which might be slightly different and enough to make a jetway working or not, with YOUR AI set.
DLH7LA:
--- Quote from: virtuali on September 09, 2020, 10:21:28 pm ---As I've said, with YOUR AI set, after YOUR adjustment. Without checking all of them, one by one, I cannot possibly say.
Not possible to say, without looking at your AI and your changes.
--- End quote ---
Here is the link to the models: http://flai.bvartcc.com/
And here is the link to the program that injects them: https://www.lekseecon.nl/ (together with a program called real traffic it reflects basically all flightradar24 movements so there is indeed REAL traffic in my sim)
After I forwarded my adjustments to FLAI and the model developers, they have implemented them in their models so everyone gets the joy of moving SODE jetways, it should be very easy for you to reproduce since my adjustments are in the official installer.
virtuali:
--- Quote from: DLH7LA on September 10, 2020, 10:35:29 am ---After I forwarded my adjustments to FLAI and the model developers, they have implemented them in their models so everyone gets the joy of moving SODE jetways, it should be very easy for you to reproduce since my adjustments are in the official installer.
--- End quote ---
I'll check it out as soon as possible.
Navigation
[0] Message Index
[*] Previous page
Go to full version