FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: heidjer1 on August 28, 2024, 05:47:40 pm
-
When containers are unloaded on my Fenix A320, they are initially compressed during transport onto the loader.
Then they suddenly pop up to their actual size.
What's going wrong here?
-
Is there anyone who knows a solution?
Unloading containers looks terrible.
-
The problem doesn't happen and nobody ever reported it before. It looks like a video driver issue, because we don't have any way to control objects scaling in realtime, and it wouldn't make any sense to do it even if we could.
-
As you can clearly see, the loader moves much too high to the cargo hold opening. As a result, the container does not initially move on the loader, but through it.
That looks very strange.
If I manually select the cargo loader in the GSX settings, then it moves to the correct position and this strange behavior does not occur.
Any ideas?
-
Is there no one who would like to say something about this problem?
-
Is there no one who would like to say something about this problem?
I see that it is there, yes. What is it that you would like for me to say about it.
-
Doesn't happen here.
A possible reason is, sometimes Simconnect "pauses" for a few seconds, because of too many apps sending too much traffic to it, so it misses updates, only to recover later. Some developers reported pauses up to 30 seconds, in which the sim just stop replying. This might be the reason why the platform animation didn't work correctly, because the simulator stopped replying to GSX commands for a while.
-
Hi Umberto,
I have never noticed any pauses. I only fly the Fenix A320. Regardless of the airport, this error always occurs and only when the standard "ANY TYPE" is set in the GSX settings for the front and rear baggage loader and GSX decides to use the cargo loader at the parking position.
If, however, I manually set the "CARGO LOADER" in the GSX settings, then everything is OK and the loader always moves to the right height.
I don't think that has anything to do with pausing Simconnect.
-
I don't think that has anything to do with pausing Simconnect.
Simconnect issues are the only thing that can explains that, because the platform and cargo are raised together, by sending Simconnect commands to both so, either they are both right, or they should be both wrong. If they lose sync between each other, the only possible explanation is the sim missed some commands we sent.
Regardless of the airport, this error always occurs and only when the standard "ANY TYPE" is set in the GSX settings for the front and rear baggage loader and GSX decides to use the cargo loader at the parking position. If, however, I manually set the "CARGO LOADER" in the GSX settings, then everything is OK and the loader always moves to the right height.
GSX doesn't decide anything, the airplane profile decide which loader the airplane will use, but it can be overridden by the airport profile, by setting a type explicitly. However, once a loader has been "decided", it will work just the same as if it was set explicitly.
-
GSX doesn't decide anything, the airplane profile decide which loader the airplane will use, but it can be overridden by the airport profile, by setting a type explicitly. However, once a loader has been "decided", it will work just the same as if it was set explicitly.
The fact is, if the airplane profile decides which loader is used, this error occurs.
If the loader is explicitly selected in the airport profile, then the error does not occur.
This can be reproduced at any time and the error occurs at all airports, at every gate and at any time.
-
Simconnect issues are the only thing that can explains that, because the platform and cargo are raised together, by sending Simconnect commands to both so, either they are both right, or they should be both wrong. If they lose sync between each other, the only possible explanation is the sim missed some commands we sent.
The error really has nothing to do with the platform being lifted together with the container.
The loader consists of two independent platforms.
The first platform (the one at the cargo hold door) moves much too high in the event of an error. This causes the container to roll through the first platform.
The container only appears correctly on the second platform and is then lowered. (Clearly visible in the photos).
Perhaps the developers should take a look at this error.
Regards,
Hans-Jürgen
-
Attached are two short videos that clearly show the error.
Does GSX want to continue to bury its head in the sand and pretend that this error lies somewhere else but with GSX?
https://youtu.be/X2KBr7frf98 (https://youtu.be/X2KBr7frf98)
https://youtu.be/ZMjIEugS424 (https://youtu.be/ZMjIEugS424)
-
Will I get a statement and will this obvious error be investigated further?
Or is the arrogance of the administrators just too great?
-
On the pictures I see, you have to configure the aircraft file to lower the height of the bottom of the cargodoor.
-
Will I get a statement and will this obvious error be investigated further?
Or is the arrogance of the administrators just too great?
Virtuali responded to you already and all you’ve done is dispute him. He is the developer by the way.
What more do you want him to say?
-
None of you have dealt with this problem at all, including virtuali.
Every professional must notice that there are differences between the loader selected by the airport profile and the manual assignment.
This has nothing to do with configuring the height of the cargo door.
If you can read, you have a clear advantage.
-
Then change the load to regular conveyors. Unless you’re flying a cargo plane.
Problem solved.
-
It is interesting how ignorantly obvious errors in the GSX project are dealt with.
It is a shame that the developers brush aside legitimate indications of simple problems like this.
Everyone can reproduce the anomalies I described without much effort.
For me, these developers have disqualified themselves.
-
It is a shame that the developers brush aside legitimate indications of simple problems like this.
I wouldn't really say they brushed it aside. Umberto gave you an explanation as to why it might be happening. You just don't like the answer.
Everyone can reproduce the anomalies I described without much effort.
And yet you are the only person I have seen report this issue.
-
I wouldn't really say they brushed it aside. Umberto gave you an explanation as to why it might be happening. You just don't like the answer.
Umberto's answer unfortunately misses the point. The only thing I'm looking for is an explanation as to why the cargo loader starts up differently in the two states I described.
And yet you are the only person I have seen report this issue.
That may be true, but it doesn't mean that the problem doesn't exist at all.
Umberto only needs 20 minutes to reproduce the situation.
-
Umberto's answer unfortunately misses the point. The only thing I'm looking for is an explanation as to why the cargo loader starts up differently in the two states I described.
Not sure what other explanation you think he's going to give.
That may be true, but it doesn't mean that the problem doesn't exist at all.
There was never a point where I said the problem doesn't exist because I can see it in the screenshots. But if, as you say, everyone can reproduce the anomalies you described without much effort, somebody else would have seen it and reported it a long time ago, and that hasn't happened. You're the first person I have seen report this, so clearly it's not as easy to reproduce as you make it out to be.
Umberto only needs 20 minutes to reproduce the situation.
He tried. He said it didn't happen on his end. I'm not sure what more you think he can do. He mentioned in his first response that it could be a video driver issue, so what graphics card are you running.
-
Umberto's answer unfortunately misses the point. The only thing I'm looking for is an explanation as to why the cargo loader starts up differently in the two states I described.
Not sure what other explanation you think he's going to give.
That may be true, but it doesn't mean that the problem doesn't exist at all.
There was never a point where I said the problem doesn't exist because I can see it in the screenshots. But if, as you say, everyone can reproduce the anomalies you described without much effort, somebody else would have seen it and reported it a long time ago, and that hasn't happened. You're the first person I have seen report this, so clearly it's not as easy to reproduce as you make it out to be.
Umberto only needs 20 minutes to reproduce the situation.
He tried. He said it didn't happen on his end. I'm not sure what more you think he can do. He mentioned in his first response that it could be a video driver issue, so what graphics card are you running.
Right!? It’s like, “ it could be this”.
He responds “no,I don’t think so. Now give me an answer dammit!”
-
Right!? It’s like, “ it could be this”.
He responds “no,I don’t think so. Now give me an answer dammit!”
Oh, we have a very funny bird here.