FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: abueren on October 24, 2020, 07:10:59 pm
-
Hello,
since upgrading to P3dv5 in June, I don't have the jetways connecting to AI-Planes anymore. This happens at FSDT-Airports like KORD or KSDF and at other airports with GSX-level2-Jetways as well. With airports that have normal SODE-Jetways everything is fine. Also in P3dv4, it works fine as exptected. I use TrafficGlobal for both Sim-versions, so the AI-Planes are also the same.
So I would appreciate if you could help me as we've been waiting so long to have this feature and I was really happy when it was introduced in spring.
Thanks
Adrian
-
An user reported if you install SODE in the default folder in C:\Program Files, there might be issues with permissions ( doesn't happen here but, every system is different ), which might affect SODE communication with GSX, which can be affected by Windows permissions.
Try to uninstall it and reinstall in another driver or folder.
-
thanks for the suggestion. Do you really think, this could be the reason? As I wrote, it works perfectly with P3dv4 just not P3dv5. SODE ist of course only installed once. The only difference is, that P3DV4 is installed in G: and P3dv5 in I: If it's because of the installation location of SODE, how come it's working for the one simulator and not the other?
-
I only reported what an user said, I cannot reproduce this and, from GSX point of view, there's absolutely no difference in the way SODE and GSX communicates between P3D 4.5 and P3D 5.
-
ok, I'll give it a try
-
I have made some more tests and now found the issue. It doesn't depend on P3dv4 or v5. If AI is created with the Traffic Slider, it works fine. If you use a tool like VOXATC which sort of injects the traffic based on the traffic-bgls in the sim, it won't work. Of course I don't know if you're familiar with this method of injection that Voxatc uses since it's a third party tool. All I can say is that with regular SODE-Jetways, it works in all cases.
So if there were a solution for this feature in GSX, that would be really awesome.
Best regards
Adrian
-
I have made some more tests and now found the issue. It doesn't depend on P3dv4 or v5. If AI is created with the Traffic Slider, it works fine. If you use a tool like VOXATC which sort of injects the traffic based on the traffic-bgls in the sim, it won't work. Of course I don't know if you're familiar with this method of injection that Voxatc uses since it's a third party tool. All I can say is that with regular SODE-Jetways, it works in all cases.
So if there were a solution for this feature in GSX, that would be really awesome.
Best regards
Adrian
Hello Virtuali,
have you had a chance to look at this yet?
-
Of course I don't know if you're familiar with this method of injection that Voxatc uses since it's a third party tool. All I can say is that with regular SODE-Jetways, it works in all cases.
We are obviously familiar with that method, and we have special code made precisely to handle that case. We tested it with UT Live, and it works with no issue so, there are no reasons why it wouldn't work with another program.
-
Of course I don't know if you're familiar with this method of injection that Voxatc uses since it's a third party tool. All I can say is that with regular SODE-Jetways, it works in all cases.
We are obviously familiar with that method, and we have special code made precisely to handle that case. We tested it with UT Live, and it works with no issue so, there are no reasons why it wouldn't work with another program.
But that's exactly the issue I have...
-
But that's exactly the issue I have...
As I've said, we tested it using UT Live, and it works, and nobody reported otherwise so, if it doesn't work with the *other* product you have, it means it might do something differently, although I can't see how, since creating AI through Simconnect is quite standard and, again, GSX perfectly supports that.
-
Ok , I must say your answer is not satisfactory, because it doesn't help me at all. First you say, you're familiar with addon injecting traffic and then you tell me, the "other tool" does it wrong or something? I would like to repeat again - with SODE jetways it will work, just not with your adapted SODE-mechanism.
So what would you suggest, how can I get help with this if not from FDST?
Maybe there is anybody else here reading this who use VOXATC? Please reply.
-
So what would you suggest, how can I get help with this if not from FDST?
Just dont expect any further support, the sale has been made and the easy reproducable error is not reproducable for the staff :)
http://www.fsdreamteam.com/forum/index.php/topic,24086.msg160114.html#msg160114 (http://www.fsdreamteam.com/forum/index.php/topic,24086.msg160114.html#msg160114)
-
Just dont expect any further support, the sale has been made and the easy reproducable error is not reproducable for the staff
It would have been best if you abstained for this nonsensical comment. We spend quite of bit of time trying to reproduce problems, which is why we ALWAYS reply ( exactly as listed in the thread you linked ) with screenshots showing it's TRUE we cannot replicate it.
With AI, it's just NOT POSSIBLE to test each and every combination of products out there, which especially for AI products, come in very mixed up models made by many different authors following many different standards.
The sure thing is:
- GSX jetways works perfectly fine using default AI traffic, clearly proving GSX supports the standard way of making traffic ( traffic.bgl )
- GSX jetways works perfectly fine using UT Live, clearly proving GSX ALSO supports the non-standard way of making traffic using Simconnect traffic injection.
That's the two ways to create AI traffic, and they are both fully supported.
-
It would have been best if you abstained for this nonsensical comment. We spend quite of bit of time trying to reproduce problems, which is why we ALWAYS reply ( exactly as listed in the thread you linked ) with screenshots showing it's TRUE we cannot replicate it.
And yet there are already two AI products (and just a wild guess, several more where users just dont care enough to complain here) that are not working with GSX AI detection, eventhough SODE works perfectly.
I would not mind (much) if you just stated that its not working (at the moment) but you try to find a solution. But you dont and just say that its
fully supported.
-
And yet there are already two AI products (and just a wild guess, several more where users just dont care enough to complain here) that are not working with GSX AI detection, even though SODE works perfectly.
First, it's just wrong to guess there might be "other" AI products without any evidence. From what has been reported here, first it was said they don't with Traffic Global, they only if VoxATC is creating them with AI injection.
It has been already confirmed several times it surely works fully with default AI traffic and AI injection with UT Live.
I would not mind (much) if you just stated that its not working (at the moment) but you try to find a solution. But you dont and just say that its
"fully supported
I cannot say "it's not working", because it surely does with two of the most common ways to create AI traffic, which use the two known method to create it, either the standard traffic.bgl method or the AI injection.
If there are some other tools that GSX doesn't work with, it must be something strange or unusual about them. About AI injection, there's nothing specific about how GSX works with UT Live.
GSX doesn't know or care it's UT Live creating AI, it SIMPLY respond to standard Simconnect events which are automatically sent by the simulator itself when a new AI is created or destroyed and, when this happens, it TELLS SODE and SODE will animate the jetway on its own.
So, the only possible explanation I have for AI created with AI injection not working with ONE tool ( VoxATC ), but working with another one ( UT Live ) can only be related in the non-working tool doing things differently, perhaps creating AI with a different frequency or density, which might cause a lack of communication between the sim and GSX, so GSX doesn't know the AI is created.
There have been so many documented cases of add-ons not being able to communicate with the sim because of other add-on spamming the sim with too many requests in a short time, resulting in them being dropped, and this is entirely random, you don't get to know who's getting all notifications and who's not so, fact SODE works with that same tool doesn't tell anything, and it might be entirely different depending which other add-ons are installed, since the one causing too much traffic doesn't necessarily have to be the one related to AI. Sometimes, a weather engine can slow down updates for everybody else but, again, the effect of missing notifications is not the same on all add-ons, depending what they do, some might just result in a delayed process, another might skip animations.
-
First, it's just wrong to guess there might be "other" AI products without any evidence. From what has been reported here, first it was said they don't with Traffic Global, they only if VoxATC is creating them with AI injection.
It has been already confirmed several times it surely works fully with default AI traffic and AI injection with UT Live.
So you are just saying it is compatible with AI via .bgl and UT Live, you call this "fully supported" but clearly it is not.
I cannot say "it's not working", because it surely does with two of the most common ways to create AI traffic, which use the two known method to create it, either the standard traffic.bgl method or the AI injection.
[...]
There have been so many documented cases of add-ons not being able to communicate with the sim because of other add-on spamming the sim with too many requests in a short time, resulting in them being dropped, and this is entirely random, you don't get to know who's getting all notifications and who's not so, fact SODE works with that same tool doesn't tell anything, and it might be entirely different depending which other add-ons are installed, since the one causing too much traffic doesn't necessarily have to be the one related to AI. Sometimes, a weather engine can slow down updates for everybody else but, again, the effect of missing notifications is not the same on all add-ons, depending what they do, some might just result in a delayed process, another might skip animations.
And still you call your program "fully supported" concerning AI traffic.
Why cant developers just aknowledge, that their program is not perfect? Basically the whole flightsim community is still there not because of a naked installation of a simulator software but because of the addons and the way they work together (see GSX and FSL, works smoothly most of the times but as soon as there is a bug, the developers blame each other.). Instead they tend to give missleading infos about features in order to raise profit.
-
So you are just saying it is compatible with AI via .bgl and UT Live, you call this "fully supported" but clearly it is not.
IT IS fully supported using standard AI Traffic, and IT IS with one of the most popular traffic utility that does traffic injection.
And still you call your program "fully supported" concerning AI traffic.
Yes, because it is. "Fully supported" means AI work fully.
It doesn't mean they would work with ANY 3rd party non-standard way of creating AIs which in some cases require combinations of products that are not even supposed to work together. You said you use FLAi and PSX, and on FLAi page, they say PSX is not officially supported, and they won't offer any support for it. And you use another commercial product on top of that.
Why cant developers just aknowledge, that their program is not perfect? Basically the whole flightsim community is still there not because of a naked installation of a simulator software but because of the addons and the way they work together (see GSX and FSL, works smoothly most of the times but as soon as there is a bug, the developers blame each other.).
This is also valid for developers of other AI traffic utilities that don't work with GSX, while UT Live is ( can't see why, considering we don't do anything specific to UT Live )
I'm trying to replicate your extremely complex AI setup, which seem to require to install a freeware set of AI, PSX to inject traffic and a commercial product to create Live Traffic that requires a Trial license that I'm waiting to get right now.
Instead they tend to give missleading infos about features in order to raise profit.
This of course doesn't apply to our products, which all come with a TRIAL VERSION, one that can be downloaded FREELY, without requiring a registration of any kind.
-
Hello Umberto,
I realize that it's not possible to support any kind of combination of Add-on-tools for P3D. But yet, of course I would like to make it work somehow.
But coming back to the original point - an "original" SODE-Jetway works correctly with this traffic that VOXATC injects. And if the jetway is managed directly by GSX it doesn't. As I understand, GSX actually uses the mechanisms of SODE to animate the jetways, is this correct? So would it be possible to analyze, what differences might result from this in the way injected traffic is treated?
If this doesn't lead anywhere, is there a way to "convert" GSX-Jetways to a regular SODE-file structure with an XML-File and a Simobject-Folder?
Best regrads
Adrian
-
But coming back to the original point - an "original" SODE-Jetway works correctly with this traffic that VOXATC injects.
GSX works with UT Live that does standard Simconnect AI injection and, as I've said, GSX doesn't know if it's working with UT Live, in only subscribe to standard Simconnect notifications when AI are created or destroyed, no matter who's doing that.
As I understand, GSX actually uses the mechanisms of SODE to animate the jetways, is this correct? So would it be possible to analyze, what differences might result from this in the way injected traffic is treated?
Yes, it's always SODE that animates jetways.
If this doesn't lead anywhere, is there a way to "convert" GSX-Jetways to a regular SODE-file structure with an XML-File and a Simobject-Folder?
It's not possible.
But since are saying they don't work with A ( at least this is what this thread was about, isn't it ), I don't think they jetways are the problem, otherwise they wouldn't work with your airplane too.
I suspect GSX is missing AI notifications from the sim for some reason. I asked for a Trial license for that live traffic product you use, and I'll try to look at it when I get it.