FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Driver8 on November 22, 2014, 01:42:31 pm
-
Hello, have an odd little problem with GSX since the last update. I am getting the "GSX Set parking brakes immediately!" message when i shouldn't be :) During the couple of flights I've flown since the most recent GSX update, when i first load FSX in free flight, and whenever i return to the sim from saving or something like that, i'll get the "BONG!" noise and parking brake message flash by once VERY quickly (so quick, in fact, i had to save a flight like 3 times, and have my eyes locked on the screen where i knew the message would pop up when i returned to the sim in order to even confirm it was the GSX message :) ).
I haven't done a "full investigation" yet, but i know that i can reproduce it by going to the save screen and returning to the sim. I've had it happen now in the Aerosoft A321, and in the PMDG 737-800 - just flown those two planes since this started, so i can't say if those are the only aircraft i get the message with or not yet. Didn't matter if i was on the ground or in the air, and when first loading the sim it happens right away, before i even have the chance to call for GSX services.
Now, in fairness, this really doesn't seem to affect anything whatsoever - it was just a bit unnerving having the "BONG" warning noise there when i wasn't expecting it, until i finally managed to catch what the message said and knew it wasn't something else going wrong :) Just thought I'd mention it though because i see one other person in one of the A320 threads seems to be getting this too.
--------- BUZZ
-
i have the same problem...this message appears casually with any type of flight.....
-
Interesting! I have experienced the same thing with PMDG 777 and the Airbus when starting a flight. The green bar comes up so quickly at the top of the screen, I am not able to ascertain which product was complaining. I chalked it up to me, the user. :-)
This issue actually started right after the last update.
Regards,
Miro
-
I noticed the same problem on my initial flight of the new iFly 747-400. I thought it was something that I had done, but now I'm starting to wonder.
-
Same here! I often start a flight and have to save it to open it later and resume my flight. I'm getting a "Bong" sound when reopening my flight. I fly the default Lear 45. "OK stop laughing at me but I like flying the Default Lear45. Anyways, I'm experiencing the same thing and it started just after the last update. :-\
Matthew
-
Same issue with me. Anytime I enter another mode, such as checking the map or entering FS Recorder, I get the Bong sound when I return to FSX. There's also the message about the brakes, but it's very brief. I also don't think it's interfering with anything, as my planes appear to perform normally.
-
Noticed the same here.
-
Same problem Here. Just started after update. Happens in almost any plane.
-
same here, I get the sound and brief message on FSX screan no matter which plane on random instances and every time in the air
-
I can't reproduce the problem.
First, the last update changed only ONE thing: it added the correct ParkingBrakes code to JUST the latest versions of Aerosoft A321/A320, because their airplane folder name has changed in later releases, so GSX didn't recognize those airplane correctly.
NOTHING else has changed in the entire GSX code, and nothing has changed in the Parking Brakes handling, EXCEPT it now works with all Aerosoft variants.
If you are not in an Aerosoft Airbus variant, the Parking brakes handling is exactly the same as it always was since GSX has been released, which simply checks the official Simconnect FSX variable that holds the Parking brakes, and nothing else.
As I've said, I can't reproduce the problem, either with any default airplane or with an Aerosoft Airbus, and I tried doing the same ( going to Save flight and going back to the sim ), but I can't see it.
The only possible explanation I can find, is either:
- Another add-on IS setting the FSX Parking brakes variable, even for a very brief moment. It might be a problem with joystick assignments, maybe a joystick not properly calibrated is sending random braking commands.
However, the parking brakes are not checked if the Sim is not on ground, which of course is checked using the standard FSX Sim On ground variable so, if this is happening while flying, the only possible explanation is that even that variable is not set properly.
So, maybe, there's a problem with GSX communicating with FSX, so variables cannot be updated correctly or they are read with wrong values. This MIGHT be caused by another addon that is sending too many commands to Simconnect, to GSX cannot communicate for FSX properly, because the communication channel is flooded with requests by something else.
BTW, GSX is checking for the Parking Brakes and if the Sim is on Ground only once every 4 seconds, which is the lowest possible update speed, so it's surely not flooding FSX with requests.
-
After the last update, I have this same issue as well. I get this BONG error message imediatley after the scenery loads up. And I will also get it in mid flight. I also see the gsx parking brake error message flash quick when I hear the BONG error message in mid flight. A good way to reproduce this issue is to use the latest version of GSX, start a flight, I used the NGX in FSX, and select a menu screen that will take you out of the scenery such as Display, and select cancel. You should then hear the BONG sound when the scenery come back up. I can reproduce this error everytime using those procedures.
-
As I've said in my previous message, I cannot reproduce the problem. This is what I did:
- I uninstalled GSX entirely
- I reinstalled it using the current installer that is posted online now.
- Selected the PMDG 737 NGX
- Selected a menu like Display or Save flight, selected Cancel, no BOING or any message coming up.
Tried both with Parking Brakes on and off, no change, works in both cases. Tried with a default airplane too, nothing.
-
I see this is a widespread problem brought about by the Live Update. I'm having this problem, too. The only change that was made between not observing vs. observing the problem was the installation of this latest Live Update. The problem can be triggered by opening the AccuFeel menu (which I have been doing lately to turn it off as it interferes with the A320/A321).
-
As I've said, nothing in the Live Update could affect an airplane other than the Aerosoft A321, which wasn't previously recognized, and now it is. Reinstalling GSX is exactly like applying a Live Update, because the files downloaded are exactly the same, coming from the same place and installed in the same way.
The rest of the code that handles parking brakes in GSX hasn't been changed in months, and GSX is not trying too detect parking brakes while flying, unless the FSX variable for the Sim on Ground is being (wrongly) set by another add-on but this shouldn't happen everywhere, you must ALSO be inside an airport AND not flying, in order for GSX to do anything or even starting to check for parking brakes.
And ss I've said, I can't reproduce it in any way. Could you please indicate sure reproduction steps, using a DEFAULT airplane on a DEFAULT scenery ?
-
+1 same problem here, so far on every flight with the CS 707, QualityWings Avro, Simcheck A300 in the last 2 or 3 days. All flights start with the 'boing' noise when the AC is loaded at a gate. Is there a way to roll back to the prior GSX version?
-
Is there a way to roll back to the prior GSX version?
That's not a way to fix things. As I've said in my previous message, I would like to have a reproduction case, using a DEFAULT airplane and a DEFAULT scenery, indicating the airplane, the scenery and the gate used.
It's not use that I ask for this, and I keep getting examples using all sort of 3rd party products instead.
I'm NOT SAYING you must use GSX with a default airplane and a default scenery only, I'm saying that in order to understand your issue, I need to exclude all possible interference from other add-ons so, please, try to help me because, as I've said, I cannot reproduce the problem, not with a default airplane, but not even with the PMDG NGX, which I happen to have installed.
-
I was able to reproduce the BONG error sound using the default FSX Cessna. Default scenery used was KLAN - KFNT. System information Windows 7 64bit, NVIDIA Surround with 3 27in monitors, Active Sky Next on a separate computer networked. I would get this error when returning from a menu screen, as other user have reported. No issues prior to the last GSX update. Not sure if this is related, but I also noticed that the backcolor on all the message windows in FSX is now transparent. Such as the GSX parking brake message, Parking Brake Message etc. etc. I noticed this also after the last GSX update. Just curious if anyone else have the same.
-
I was able to reproduce the BONG error sound using the default FSX Cessna. Default scenery used was KLAN - KFNT.
Tried the Cessna too, at KLAN and of course, no message or sound whatsoever. You haven't indicated any reproduction steps, do you mean you just open a menu and then cancel it, and you see the message and the sound ? Did that of course, but it doesn't happen.
Not sure if this is related, but I also noticed that the backcolor on all the message windows in FSX is now transparent. Such as the GSX parking brake message, Parking Brake Message etc. etc. I noticed this also after the last GSX update
They are always been like this, semi-transparent. They become opaque ONLY if you manually undock the message window by right-clicking on it when it's on screen.
This is a standard FSX behavior, so it's not possible it happened after a GSX update.
Perhaps it's a conflict caused by another running program. Are you able to momentarily turn off EVERYTHING that starts with FSX and try it again ?
-
Using the Cessna, I did not get the message upon load like many other post have indicated. However I did get the error BONG about 15min after departing KLAN. In this scenario, I did not need to access the menu screen to trigger it, it just automatically executed the BONG sound with the quick message flash.
Are you using the latest NVIDIA drivers? I mention this because I'm back tracking all changes made to my system before I noticed this issue. The only changes I made last week was updating to the latest GSX, and also updating to the latest NVIDIA drivers. Prior to that there was no issue.
There's something we're missing hear. Before I found this post, I assumed it must have been just my system, but there's far to many people with the similar problem. Not saying that GSX is at fault, just noticed the issue after the update.
I will look into the docking of my messages, when I load FS next time.
Since the new update is only applicable to the Aerosoft A320/A321, I'm going to uninstall it and see what happens. I will report back later after a few more test.
-
I think I may have found the condition in which the bong is present. Anytime there is a location change from the start up point, you will get the error bong. This also happens with the default Airbus.
For example, I have my FSX always starting up at the same airport/gate because I fly the same route often. The odd time that I decide to change my plans (i.e. different Airport, Gate or even active runway), I will get the bong. Perhaps, that issue always existed and I never noticed it as I never deviated from my start up? I would think others would have experienced sooner. I do not hear the error bong if I do not make any changes to my startup location.
Hopefully our friends at GSX will be able to recreate that condition on their systems and identify the root cause!
Regards,
Miro
-
For example, I have my FSX always starting up at the same airport/gate because I fly the same route often. The odd time that I decide to change my plans (i.e. different Airport, Gate or even active runway), I will get the bong.
I did this too, because I had a startup flight saved at one place, but I moved it to another place to replicate the situation described by another user, and no, it doesn't make any difference, because I can't see any message or any sound in both cases.
In my last reply, I asked if it was possible for anyone having this issue, to momentarily disable EVERY other add-on that starts with FSX. It would be helpful if someone would try that and report back.
-
Okay, I may have more information. ;D
My startup flight did not have Parking Brakes on. I loaded the startup flight, applied the parking brakes, and re-saved it. I restarted FSX, changed to the PMDG 777 aircraft and different gate and I didn't experience the bong. Perhaps this only occurs if the startup flight does not have the parking brakes applied? Just a thought.
Regards.
-
ditto since last live update. nothing has been changed on my system. happens with different aircraft and at no particular time.
ken
-
Perhaps this only occurs if the startup flight does not have the parking brakes applied? Just a thought.
YES, you got it!
My startup flight was saved with parking brakes on, but as soon as I created a new one without parking brakes, I get the message and the sound ONLY if I select an airplane, either a different one or even the same I was flying.
I'm quite puzzled, because that seem to be entirely unrelated to the latest update, since it's a part of the code that has been there for ages...
But at least, being able to reproduce it, should lead to a fix soon. Still cannot reproduce it by simply opening/closing an FSX menu, as others have reported.
-
I see that it looks like this could be related to saved startup flight conditions and the parking brake setting loaded in that situation. I've never saved a startup flight - my Free Flight in FSX still comes up with the MS defaults. I then select the aircraft, start location, time of day, load a flight plan and maybe edit fuel (depending on whether or not the aircraft i fly uses it's own in-sim fuel loader). Since the Free Flight menu with MS defaults starts with a situation already in-flight, could that possibly shed some light on why i get the message when i save with the ";" key mid-flight and then get the alert when returning to the sim from the save screen?
--------- BUZZ
-
Yes. I believe so. Try to create a start up flight at an airport using the Cesna for example. Ensure that your brake is on and save the flight. Exit FSX, then restart. I tested it and the bong went away. :-)
I am sure GSX will come up with a fix.
-
I am not using a start up flight here. just starting FSX with default select flight screen. My aircrafts though (PMDG) are all startup without FSX parking brake but only with "chocks"
-
I've never saved a startup flight - my Free Flight in FSX still comes up with the MS defaults.
The MS default flight it's just another saved flight, the only difference is that MS created it, not you and, since it's not saved with parking brakes on, it still consistent with that finding. As I've said, I was able to reproduce it this way, so it's 100% sure it's related to the parking brakes conditions on the startup flight.
Now, we can work on a fix.
-
Great! So happy were making progress. It happens to me in the dfault Lear45 as I resume my flight in in free flight mode and save the default Lear 45 in mid flight so of course my park brake is not on.
Glad they are working on a fix.
Matthew
-
The very best solution would be to uninstall GSX first and then reinstall the full version. At times just installing the update causes failures, particularly with FS running as is appropriate with almost any program. Even though it says it will over write and no need to shut down, with scenery updates it's always best to do a full install. FS Dream Team really should offer the full install with every update as they did with 1.9. It would just make things so much simpler and would I'm sure avoid 99.9% of all the issues in the forum. Just my thoughts. I have always used the full install whenever scenery was involved and have to date not had any problems. Now if I could only teach myself how to configure the components of the program to meet my personal needs such as where the vehicles park and move etc, I would surely be smokin'......hope this note helps you...
-
At times just installing the update causes failures, particularly with FS running as is appropriate with almost any program. Even though it says it will over write and no need to shut down, with scenery updates it's always best to do a full install.
You are confusing Minor Updates with Major Updates. Minor Updates ARE 100% safe to apply while FSX is running, this is a fact.
THIS one we just released, it's NOT a Minor Update, it's a Major Updated, which CANNOT be applied while FSX is running, the Live Update doesn't even let you the option to do that. It tells to quit from FSX and download the Stand-Alone Addon Manager.
But there's an additional difference. THIS latest update ALSO require to update the vehicles IN ADDITION to the Stand-Alone Addon Manager, and this information is in the update release notes, it was on the email we sent about the update, and it's also on the forum thread of the update announcement.
However, if one fails to read that, or simply forget to install the vehicles, he'll have troubles like missing vehicles or such.
In THIS case, the full installer will surely fix everything.
But it's wrong to suggest to "always" use the Full installer, just because someone might have forgot to read the instructions about THIS specific update, which was made in 2-steps, both to be done with FSX CLOSED (and there's no way you could not do it this way), and it's wrong to suggest a Minor Update might be "unreliable", just because it doesn't require to restart FSX, because it's not.
Sceneries DO require an FSX restart, but it's wrong to assume that, just because it's best to restart FSX to update a scenery, it would be automatically the same for an update of the GSX code, because they are entirely different, with the main difference that, FSX itself, doesn't know ANYTHING of the GSX code, because it's a file that has a meaning only for Couatl.exe.
A Minor Update, the one that can be applied without restarting FSX, downloads ONLY Python code that runs under the Couatl.exe interpreter, which is a *separate* .exe, so it doesn't make any difference if FSX is running or not, and it's totally safe to restart Couatl.exe when FSX is running, to the point that we even have a menu option to do just that which can be called at any time, and that's what the Minor Update does, at the end of the installation.
-
This was happend to me also after the update, with the Airbus X A320. It was like GSX doesn't recognize the wheel chocks, and I have to push parking brake even if the weel chocks was not removed. BUT... I download the full installer,then uninstall GSX, and install all from begining, and by the miracle the message has gone. Everything works perfect, airbus X, pmdg 737 ngx, default plane, no message. And I know it's a pain in the ass, but I allways restart the computer after I install an add-on even if isn't necessary, because in this way I am shure that all from cache is removed, specially if I uninstall same software first. Rebot every time the pc. I've seen problems with modifieng simple file like Aircraft.cfg like adding a line and working just in case after restarting the pc. For someone works, for someone doesn't. There are dozen of Windows version and not all the computer works the same way. But of course, I am talking just IMO.
-
This was happend to me also after the update, with the Airbus X A320. It was like GSX doesn't recognize the wheel chocks, and I have to push parking brake even if the weel chocks was not removed. BUT... I download the full installer,then uninstall GSX, and install all from begining, and by the miracle the message has gone.
This doesn't have anything to do with the update. There WAS a bug, which we solved, and we have updated the files belonging to the GSX code and this SAME files are downloaded, regardless if you apply a Minor Update while FSX is running OR if you reinstalled the full installer.
What likely happened, is that you have applied the Live Update just before we uploaded the bug-fixed version, so you got the bugged version, then in the time it took to download the full installer, uninstall GSX and reinstall it, we updated the files so you got the bug-free version, so you were mislead thinking the Update had a problem.
And I know it's a pain in the ass, but I allways restart the computer after I install an add-on even if isn't necessary, because in this way I am shure that all from cache is removed, specially if I uninstall same software first. Rebot every time the pc. I've seen problems with modifieng simple file like Aircraft.cfg
This doesn't apply to the files belonging to a GSX Minor update.
As I've said, you might have a point, if are discussing files that BELONGS to FSX and ARE used by FSX. An FSX restart and sometimes a Windows restart might be needed, but not all files that belongs to Couatl, which are the only one updated during a Minor Update, and Couatl can be restarted at any time, and it will use the updated files. FSX won't even notice this.
-
My point was that depends of many factors the install of add-ons on FSX. For ex. I have FSX installed in C/FSX and not on C/program files x86. Many user don't follow this simple rule even if is strongly recomanded by major software like REX or PMDG or Aerosoft, and I think you agree with this also.
It was a specific case when PMDG releas his 747 and some users has the black gauges on cockpit. The solution was to add a line on aircraft.cfg, for some works but for somone else works only if they has to reboot the pc. What I wanna tell is that not all the configuration are the same, even with minor or major bug with the release of new versions not allways the installation can go to a good end.
FSX is a simulation that was made many years ago and Microsoft didn't offer any support after (but you know this better then me), so sometimes is very hard to find the problems even if they are more easy or hard to resolve. I has told what happend to me in my case, and was a coincidence why I have downloaded the full installer, because was seems to me that not all the vehicles where updated, that's way. What remains is that for me is now all function perfect with GSX. I didn't say that this is a solution for everybody, and didn't say that was something wrong with the update or something else from GSX. Just wanna say that sometimes is very hard to identify the problems, because I thing that in 90% of case the problems comes from us, and not from software house. You are professionist in you're job and when you make a software you test and work for you because you respect some basic rules, wich many of us doesn't even have the idea that exist. :D
-
My point was that depends of many factors the install of add-ons on FSX. For ex. I have FSX installed in C/FSX and not on C/program files x86. Many user don't follow this simple rule even if is strongly recomanded by major software like REX or PMDG or Aerosoft, and I think you agree with this also.
Again, this is entirely unrelated TO US.
Those software developers tells you this, because what you need to update, is some file USED BY FSX, like the aircraft.cfg, the scenery.cfg, some scenery textures, , or anything else that FSX MIGHT USE.
As I've said, this DOES NOT apply to our Minor Update, that updates ONLY things that FSX DOESN'T USE
It was a specific case when PMDG releas his 747 and some users has the black gauges on cockpit. The solution was to add a line on aircraft.cfg, for some works but for somone else works only if they has to reboot the pc.
That confirms what I've said: the aircraft.cfg IS a file read by FSX, so it might require an FSX restart.
I told you why what you were experienced happened: you were just caught in the middle of our own upload and, because the time it took to restart your system got you the right version, so you are now convinced the Live Update somehow failed because "FSX was running" or "I should restart".
-
Wrong. I am not convince of this, I was only telling what happend to me. And thank you, I understand very well, no need to explain every time.
Again: "I didn't say that this is a solution for everybody, and didn't say that was something wrong with the update or something else from GSX" and I NEVER said that the live update somehow failed for me. Live update finished ok and I repeat the only reason for I have downloaded the full installer is that I have the "sensation" that the vehicles didn't update (maybe you didn't read in previous my post).
As a matter a fact, I don't have any problem with GSX, so IMO I am doing the things right, I don't want to give a solution in this case, far away from me, because it's not my problem and I'm not even capable of this. Anyway tnx , I don't wanna waiste you more precious time.
-
Wrong.
"Wrong" what ?? What I've said is the fact, it's not really opened to negotiations or opinions. You used the "other developers" suggestions as some kind of evidence, but I told you precisely why this might be valid in some cases, but doesn't apply to THIS specific case, the Minor Live Update.
The Major Update, which is what we had with GSX 1.9, it's not even under discussion here, because that one TELLS YOU to Exit from FSX, because that one DOES update stuff that is USED BY FSX. But NOT the vehicles...
I NEVER said that the live update somehow failed for me. Live update finished ok
And again, I NEVER said you said this...Live Update finished ok, but it's NOT supposed to update vehicles. We wouldn't tell "download the vehicles update installers" in the release notes and in the forum announcement thread, if the Live Update was supposed to handle the whole update on its own.
That's the reason why, since some might find "complex" having to apply 2 separate updates, we also say that the FULL GSX installer would work fine too.
and I repeat the only reason for I have downloaded the full installer is that I have the "sensation" that the vehicles didn't update (maybe you didn't read in previous my post).
And that's NORMAL.
The Live Update is NOT supposed to update vehicles. How else you think we said to apply the MAJOR Update AND download and install the Vehicle update too ? Because the Live Update WON'T update the vehicles!
As a matter a fact, I don't have any problem with GSX, so IMO I am doing the things right, I don't want to give a solution in this case, far away from me, because it's not my problem and I'm not even capable of this.
And that's why I have clarified the issue, because you suggested that a Live Update that doesn't restart FSX might not work, which is factually wrong, and I don't want to have anyone using the program in the wrong way, because it read a "post on FSDT site saying so"
1) The MINOR Update IS 100% safe to apply without restarting FSX.
2) The "Brakes" bug fix CAN be fixed with a Minor Updated, but if it didnt' work FOR YOU, but worked after a full reinstall, it was JUST because when you ran the Minor Update, the bug-fixed version was not up yet. By the time you restarted FSX and downloaded and installed the full installer, it was, so you were mislead thinking the problem (even in YOUR case) had something to do with the fact you applied an update without restarting, which wasn't the case.
Is a bit complicated to explain, because the method the Live Update uses to understand if YOU need an Update, it's linked between the time on your system and the time on the online update server, and there are two servers running in parallel located in two different countries and time zones, so it IS perfectly possible that you might just got in the middle of an update, and still got the previous version, while someone else (or even you, if you tried again later with the same procedure) would get the new one.
I won't even try to mention the fact we are running an anti-spam and anti-DDOS service in the middle, so the server you are contacting is not even the same we are *really* running on, but there's a network of worldwide servers that will proxy your files, depending on your location, and will prevent service interruption in case a server might go down.
Please, you have to trust this: if I gave you that explanation, it's because IT'S POSSIBLE to happen, but please stop hinting something wrong happened to you *because* you haven't restarted FSX.
3) What we had with the 1.9 update was a MAJOR UPDATE instead. This one CANNOT be applied without exiting from FSX, the program won't even let you do that.
4) What we had with the 1.9 update wasn't JUST a MAJOR UPDATE, it was a MAJOR UPDATE + VEHICLES UPDATE. You cannot have the program working correctly if you don't do BOTH.
5) If you find this cumbersome and difficult to understand, you don't HAVE to do it. Just download and install the latest Full installer, and be done with it. Someone that does NOT find this difficult, might still appreciate the OPTION to do it with a smaller download, since there IS a choice.