Products Support > GSX Support FSX/P3D

GSX turning 77W into 77F cockpit **SOLVED**

<< < (3/10) > >>

virtuali:

--- Quote from: Qantas747 on September 09, 2021, 01:16:55 pm ---Upon further researching all the affected cockpit parts in the PMDG virtual cockpit have the visibility condition "custom_vis_IsFreighter_01" So it seems GSX is triggering that variable when the first container is loaded on the loader machine.
--- End quote ---

I can assure you nothing in GSX triggers that variable. The only PMDG variables used by GSX, are only used to read their status ( to know if doors are opened or closed ), but we never write anything on 3rd party airplanes.

Qantas747:
Okay so why is it when the container goes on the loader, it triggers that variable? Here is another video showing both views. https://drive.google.com/file/d/1Ywzii74miUk6bTg4DZz0Uyn9erUEN8Fu/view?usp=sharing

It clearly has to be GSX causing this.

VHEBN:
Hi Umberto, I can confirm I also have this issue, occuring only with GSX

virtuali:

--- Quote from: Qantas747 on September 09, 2021, 01:51:29 pm ---It clearly has to be GSX causing this.
--- End quote ---

That's not sure. What is sure, is that GSX doesn't contain any reference to that variable anywhere in its code, this is not really open to discussion.

But something like this is still possible with L: variables because, they way they work, they are linked to a numeric ID, which can change during the simulation, usually when the airplane model is changed, which triggers a complete GSX restarts so, it would be impossible to have a conflict between IDs, since all variables used by GSX are being registered again with the sim after a complete restart.

GSX always checks with the sim if an ID is already used, before trying to register one of its own L: variables it needs to write to, but every other add-on should do the same, to prevent these conflicts. We don't do it before *each* write, because we used lots of them for animations, and asking the sim if a variable ID is available continuously would likely cause stuttering in animations and, during those years GSX has been out, we never had any problems of conflicting variables with different names ( which can only be caused by conflicting IDs ).

In fact, so many 3rd party airplanes use a large number of custom variables for visibility or animation, if this was a problem in GSX, it should happen with every airplane, at least those that use custom L: variables.

Qantas747:
Well if it doesn't have anything to do with GSX, why does it occur after I've recently updated your program??? It was working fine and now its not. Sticking your head in the sand and saying no issues here, nothing needs to be fixed is really not the solution here.

Navigation

[0] Message Index

[#] Next page

[*] Previous page