FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: dornier on May 31, 2017, 04:03:46 am
-
Hi,
I tried installing GSX with the new installer as of today 5-30-17 and it couldn't install SODE. First it had me uninstall version 1.4.2, which I did. I tried to install GSX and when it got to the SODE install it just sat there for at least 15 minutes and the progress bar only went up to about 1/4 and stopped. I ended the SODE task and GSX finished installing. My question is, how do I fix this? Where can I download the P3D v4 compatible version? Otherwise do I attempt another install after rebooting?
Thanks,
George
-
Piggybacking on dornier's post, I too am having difficulties with the new installer. It told me to uninstall SODE v1.4.2 because it was outdated (even though SODE v1.4.2 seems to be the latest version.) I did so, but it is still telling me to uninstall it. I used the program's uninstaller to uninstall it, so it would have been uninstalled correctly.
(http://i10.photobucket.com/albums/a123/thecohortsska/Capture.jpg)
-
I too am experiencing the same issue. I uninstalled the previous version properly, and now getting the same message.
-
Where did you download a P3Dv4 compatible installer from?
-
I'm having the same issue in FSX.
-
SODE 1.4.2 is NOT the latest version of SODE so, GSX is correct saying your 1.4.2 is outdated, because it is.
The latest version of SODE is 1.5.0, and it's included with the new GSX installer so, if you do as the installer says, and Uninstall SODE 1.4.2, it will install the 1.5.0 version without having to download it separately.
The GSX installer checks the SODE version in the registry so, if you have Uninstalled it properly, the registry should have been cleared so, if you are still seeing that message, it seems something went wrong Uninstalling SODE, so the old registry key for 1.4.2 is still there.
The SODE registry keys might be located here:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\12bPilot\SimObject Display Engine\Version
HKEY_CURRENT_USER\SOFTWARE\12bPilot\SimObject Display Engine\Version
Be sure that both of them are empty, after Uninstalling the existing SODE. If not, remove the Version key.
-
Hi,
So I looked at the registry and it shows 1.5.0. Under version it shows 1.3.0. I also noticed that 1.5.0 and 1.3.0 is in the uninstall option in Windows 10. I'm still running FSX:SE, do I need to have 1.3.0 installed? Since 1.5.0 is installed, how do I run it to register it?
-
So, your issue was that you still had 1.3.0 installed. There's no reason to keep 1.3.0 installed, the 1.5.0 version supports all versions of FSX and P3D
-
Ok, I will uninstall both and try to reinstall GSX again. Thanks, George
-
My question was ignored... where do i download P3Dv4 compatible GSX installer? The website still has old version "Last updated 19-apr-17".
-
My question was ignored... where do i download P3Dv4 compatible GSX installer? The website still has old version "Last updated 19-apr-17".
Please re-read again, carefully, my previous post, which answered your question entirely. I'll quote again the relevant part here:
The latest version of SODE is 1.5.0, and it's included with the new GSX installer so, if you do as the installer says, and Uninstall SODE 1.4.2, it will install the 1.5.0 version without having to download it separately.
-
Define "New". Last updated 19-apr-17 - is not new, its 1.5 months old, its May the 30th today. Be more precise please because the website download section has nothing that says "P3Dv4 compatible".
So, is "Last updated 19-apr-17" the installer i should be using for P3Dv4 or is there another link, if there is then please provide me with it. Thank you.
-
You stil haven't read my reply. I'll quote it, again:
The latest version of SODE is 1.5.0, and it's included with the new GSX installer so, if you do as the installer says, and Uninstall SODE 1.4.2, it will install the 1.5.0 version without having to download it separately.
There's nothing to download, the SODE installer is INSIDE the GSX installer, the only thing you must do, is exactly what the GSX installer is telling you: Uninstall the old version, so the GSX installer will be able to proceed, and install the newest SODE, which is included in it.
-
Thank you. I didnt even try to install using the old installer because of this:
GSX has been compatible with P3D V4 since several months so, yes, we'll released it on May 30th, together with all the other updates.
I was waiting for May 30th release.
Installed successfully.
-
I didnt even try to install using the old installer because of this
Well, it wouldn't work even if you tried, since the old installer surely doesn't recognize P3D V4 and, even if it did, it wouldn't work, because it was only compatible with 32 bit.
I was waiting for May 30th release.
That's exactly what we did: it was released a bit late in the night, so (depending on timezones), we went a bit into May 31th but there's a new GSX installer, and it contains the new SODE installer too, and right now GSX is the only way to install the newest SODE, because Jeffrey was kind enough to send us the installer even before he had a chance to update his site, because the newest version has several features which are crucial to GSX, so we couldn't release it without it.
-
SODE 1.4.2 is NOT the latest version of SODE so, GSX is correct saying your 1.4.2 is outdated, because it is.
The latest version of SODE is 1.5.0, and it's included with the new GSX installer so, if you do as the installer says, and Uninstall SODE 1.4.2, it will install the 1.5.0 version without having to download it separately.
The GSX installer checks the SODE version in the registry so, if you have Uninstalled it properly, the registry should have been cleared so, if you are still seeing that message, it seems something went wrong Uninstalling SODE, so the old registry key for 1.4.2 is still there.
The SODE registry keys might be located here:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\12bPilot\SimObject Display Engine\Version
HKEY_CURRENT_USER\SOFTWARE\12bPilot\SimObject Display Engine\Version
Be sure that both of them are empty, after Uninstalling the existing SODE. If not, remove the Version key.
Oh ok. I must have misread the website. I did indeed have left over registry entries...which I subsequently deleted. GSX installed without issue.
Thank you for your help
-
I,m sorry but where might I find the SODE yo uninstall having the same issue?? :-X
-
I,m sorry but where might I find the SODE yo uninstall having the same issue?? :-X
Like any other Windows program, SODE can be Uninstalled from the Windows Control Panel, under Programs and Features entry, of (if you have the big icons view) the "Programs/Uninstall program" entry.
-
I tried uninstalling just 1.3.0, but SODE 1.5.0 wouldn't install. After uninstalling both 1.3.0 and 1.5.0, GSX installed correctly. During the SODE registration process I almost missed the extra tab for P3D tab. Registered both and they both appear to be working correctly now, thanks.
-
Just for my information - is the GSX download on the websitre the "V4 compatible" one?
I did not find that info anywhere and the date stated on the homepage under the download is rather old....
Thanks in advance :-)
-
Just for my information - is the GSX download on the websitre the "V4 compatible" one? I did not find that info anywhere and the date stated on the homepage under the download is rather old....
Yes, it's updated, we just have to update those buttons too...
-
Checked Registry as you suggested and all are empty
I'm sorry but, it's not possible that, if the registry keys are empty, you would see that message. So, the only possible explanation is that you haven't checked the registry correctly.
Here's the two affected keys that GSX checks for:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\12bPilot\SimObject Display Engine\Version
HKEY_CURRENT_USER\SOFTWARE\12bPilot\SimObject Display Engine\Version
And yes, before posting, I tried it again, just to be sure, by manually emptying both keys and, sure enough, GSX proceeds.
Note that, the registry editing will work only to fool GSX into proceeding with the installation but if SODE is not *really* uninstalled and these are not just leftovers, the SODE installer launched by GSX WILL fail just the same, irregardless how what you did to the registry.
I cannot find any mention of SODE on my computer. Why the new GSX installer can not just overwrite and update the registry and save me this headache is beyond me. Bob
That would be totally useless. If GSX didn't care of the registry, the SODE installer would have told you exactly the same, because it is the SODE installer *itself* that doesn't allow to be installed, if it finds an outdated version.
The obvious reason why the GSX installer check first, is that the SODE installation step is done towards the end of the GSX installation, so it wouldn't have much sense to install 90% of GSX, then having you stuck at the SODE step. So, of course, GSX correctly check this as the first thing it does, so you won't have to lose your time waiting for the GSX installation to almost end, only to discover you cannot install SODE, so GSX won't work with jetways anyway, so you'll be back to square one.
You must uninstall SODE, there are no shortcuts around this.
-
For some reason the new SODE isn't working with my FSX SE. I uninstalled v1.4.2 and I installed the newest GSX installer with SODE 1.5.0. The installation went by just fine with the only exception of Windows Defender being triggered but it didn't say what the problem was. It only said that it was disinfecting a file but the installation continued. After loading up FSX, there was no SODE option in the Add-ons menu and at FSDT airports the jetways didn't work.
-
It only said that it was disinfecting a file but the installation continued. After loading up FSX, there was no SODE option in the Add-ons menu and at FSDT airports the jetways didn't work.
It's likely the antivirus has killed SODE so, of course, the proper solution would be uninstalling it again, and reinstalling it with the antivirus disabled. Then, configure the whole SODE folder (usually Program Files (x86)\12bPilot) to exclude it from antivirus scanning.
-
Thanks, my only problem is that I'm unable to make any changes to Windows Defender even though my profile is Administrator. I'm guessing i'll have to totally disable it.
-
Could some kindly advise me how to properly uninstall SODE 1.4.2 do I just delete the files
thanks
-
Sir,
I deleted SODE, but am not sure where the two keys are located so I can delete them. Can you tell me the path to the two keys so I can ensure they are deleted? I am on Windows 7 64bit.
Thanks,
Dave
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\12bPilot\SimObject Display Engine\Version
HKEY_CURRENT_USER\SOFTWARE\12bPilot\SimObject Display Engine\Version
-
The installer checks both keys, so you must delete both.
However, doing that, you will only allow the GSX installer to continue up to the point it will run the SODE installer so, if the previous SODE installation wasn't made properly, it will be the SODE installed *itself* which will not work. And, it will fail silently, because we start it in "Silent" mode so, you might assume it worked, because the installation completed with no errors, but it hasn't, so if you would be stuck with the previous version, GSX won't work with it, since it *requires* 1.5
The GSX installer obviously checked this at the start, so you wouldn't have to wait for the whole GSX installation to complete, only to find that SODE would fail to install at the end...
There are no shortcuts: you MUST Uninstall SODE properly.
-
I have a similar problem that some of the folks with installing GSX to fsx-steam with GSX not installing because of SODE 1.4.. Since I am not a computer expert I am assuming SimObject Display Engine is SODE. The control panel shows two "Simobject display engines" one at 34mb and one 26.0kb. No version numbers given. Are these the ones that must be uninstall and then install GSX. There are two blocks checked in the initial install shoiuld both be checked. (1)FSX steam edition stand alone mode and (2) FSX steam alone mode. FSX-Steam is the only flight sim installed on computer. I have almost all your scenery installed prior to installing KCLT with no problems. After installing KCLT all updates appeared to execute and moved to addon manager under Program files(86)
-
Uninstall every version of SODE, then install GSX.
-
Thank you for such a quick response. After uninstall SDOEs, GSX installed but no courtl was shown in menu. also my FSDT sceneries are in a "trail mode" plus buildings etc are missing even in the trial mode. Using my code for verification no longer works. Does this mean I may have to uninstall all FSDT sceneries and reinstall again? One final note, during install of KCTL saw message that stated "error 2 running C:/program files (x86) addon manager\tidy.exe which mean system cannot find file specified." Sorry for the mess I appear to have.
Appreciate any help.
-
See if you have the same problem discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,15838.msg113707.html#msg113707
-
Umberto, the problem Ywg256 had was very simiilar to mine. When I manually did the couatl.exe it brought all of my FSDT scenery back. It even asked if I wanted to activate each one. Worked with no problem with FSX-SE.
Thank you,
carl
-
Well Looks like I got to excited thinking the problem was fixed; however, the problem came back this morning when I started it up. No courtl showing up and KCLT has scenery file error in local scenery area 344. Will do some more checking on why it worked and now it doesn't.
-
and KCLT has scenery file error in local scenery area 344. Will do some more checking on why it worked and now it doesn't.
That seems to indicate your scenery.cfg has changed, or you moved files manually after you installed, which will surely create such errors.
It's not very clear what you did with "When I manually did the couatl.exe it brought all of my FSDT scenery back. ". Did what ? You are not supposed to manually do anything to it. The problem listed in that thread, was related only to P3D, and it was only related to a corrupted EXE.XML file.
-
I kept noticing that couatl was never showing up on my screen although there is a folder Couatl. I went to the couatl folder under ADDON manager and double clicked the couatl.application manually and then all the FSDT sceneries worked. Couatl also showed up in my menu for the first time. However for some reason I am back to square one since trying to execute couatl within the folder no longer works. I did move KCLT in the scenery library below all the Orbx stuff. For now I have uninstalled KCLT, re-installed addon manager with all the updates to see if that would help but no couatl. Couatl shows no sign of installing and sceneries are back with no buildings just gates etc under trial basis. Will continue to try and figure this out somehow.
Thank you for your support...
-
As already explained in this same thread, and in so many threads in the forum, if Couatl starts manually, but not automatically, the most likely cause is your EXE.XML file being corrupted by a bugged installer of another product, as explained here:
http://www.fsdreamteam.com/forum/index.php/topic,15838.msg113707.html#msg113707