seems like support selectively replies to posts, rather than do them in order. yawn.
I don't know what you are trying to say but, have you ever heard words like "time zones" or "it's Sunday and we ARE still replying" ? You posted on Sunday early afternoon, and are already complaining you haven't still haven't got an answer only 4 hours later, when under ANY REASONABLE standard, you should AT LEAST allow 24 BUSINESS hours to get any reply, from any kind of support ?
it prompts a message stating there is an issue with my simobjects.cfg file
It's not very clear what's gave you that message. From your subject, it might seem this message came from SODE installer ? Assuming this is what you meant by adding SODE to the subject, considering GSX simply start the SODE installer in the same way as you might have done separately, with any other product that use SODE so, this is not even a GSX support question to begin with.
If SODE says your simobjects.cfg file has a problem, then yes, your simobjects.cfg DOES have a problem.
However, note that GSX or any other FSDT product DO NOT USE the simobject.cfg AT ALL! The simobject.cfg file normally lists all the folders where default objects can be found. Yes
, it IS possible for 3rd party developers to add their own paths to it, but we don't use that method. More precisely, we used it only with P3D up to 3.3, since from P3D 3.4 and above, the add-on.xml method has been introduced so, all our products in any version higher than 3.4 ( which of course included P3D 4 and 5 ) DO NOT use the simobjects.cfg file anymore.
However, it's possible SODE WILL use it for its own use or for other products that use SODE objects, but not FSDT ones.
This is to say, if you are "sure" your simobjects.cfg is fine, even if the SODE installer or the SODE Platform Manager says it doesn't exists ( this is what says in the lines you posted, which surely are from SODE ), this might indicate a more general problem with your overall P3D installation, like corrupted registry keys, for example.
That WILL of course affect GSX and every FSDT product, even if we don't use the simobject.cfg file, fact it's not found, seems that something's clearly wrong with your P3D install.
A common source of problems like that is the usage of FSX Migration tools, which change the registry keys to allow to install legacy products with outdated installers that don't recognize P3D. These tools might have not be used correctly, or might have not restored the registry correctly after doing their job, or you might have uninstalled them before the correct registry keys could be restored, leaving you stuck with wrong registry keys.
I'm giving this explanation based on your report that you think your simbjects.cfg files are fine. Since I don't have any reason to doubt you, then the ONLY explanation left why SODE can't find them, is the simulator registry keys wrong.
And if the simulator registry keys are wrong, this will surely screw up GSX and any FSDT product, and the FSDT Updater too, since all they rely on the registry keys pointing to the correct installation.
So, again, while the simobject.cfg file issue won't DIRECTLY affect GSX ( we don't use that file ), it's an indication of something wrong in your P3D installation.
