Products Support > GSX Support FSX/P3D
GSX turning 77W into 77F cockpit **SOLVED**
Qantas747:
Hi Umberto,
Thank you for your explanation and investigation into this issue. I appreciate it. I have quoted your reply to my PMDG forum thread and will await for their reply. I'll keep you updated. Thanks again
virtuali:
--- Quote from: Qantas747 on September 10, 2021, 02:22:12 pm ---I appreciate it. I have quoted your reply to my PMDG forum thread and will await for their reply. I'll keep you updated.
--- End quote ---
I've read their reply and, as expected, they are continuing to repeat the problem "must be GSX", just because it happened only after our update, without providing any evidence, like I did.
I think I gave a reasonable enough explanation why it never happened before: we added a couple of variables ( all using FSDT_xxxx names, of course ) more in this version, so maybe now their number it's enough to expose a conflict that could always have happened.
The explanation those errors can be ignored, because they use "custom coding the sim does not understand" doesn't make any sense. The log clearly recognized what the code was doing, and it was a call to an API the sim clearly knows about it, which is used to read an L: variable from the panel system, and the sim said those calls failed.
If they really used "custom coding" to read ALL their L: variables, why the sim is logging failures for just 7 of them, out of the hundreds the panel likely use ?
I think I've gathered enough evidence indicating that, the main reason of the problem starts with those failures, and it was only by chance that, a new version of GSX exposed it because we increased the number of L: variable we use, but that error could have happened before, and I wouldn't be so cavalier telling users to ignore the errors.
I could only guess what PMDG would say IF GSX had so many errors logged, when in fact it has none, and it use lots of L: variables, has *thousands* of multi-livery object variations, yet is completely clean of any errors.
Instead, their plane is able to generate 888 errors using always the same 7 variables in a very short time ( and we don't even know how many more are really happening in the sim, because the log stops after 1000 errors! ), yet for some reason, it's GSX's that must change its errorlog-free code.
If I were them, I would worry about having so many errors (regardless of GSX) and would try to get rid of them, if only for possible performance reasons because, even if the log in the sim stops after 1000 errors, who knows how much more costly in cpu time is having constant errors happening, regardless if they are logged or not...
virtuali:
Hello, we found a workaround for this problem.
I still think it might be best if the airplane fixed its errors with those variables but, since it doesn't seem it's going to be fixed, we found a way to fix from our side. Get the update as usual.
Qantas747:
Hi Umberto,
Thank you for solving the issue and releasing an update very quickly.
Captain Kevin:
--- Quote from: virtuali on September 10, 2021, 06:34:01 pm ---Hello, we found a workaround for this problem.
I still think it might be best if the airplane fixed its errors with those variables but, since it doesn't seem it's going to be fixed, we found a way to fix from our side. Get the update as usual.
--- End quote ---
Not that it really makes a difference, but I'm just curious as to what you ended up doing to solve the issue.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version