FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Ray Proudfoot on May 27, 2020, 01:48:35 pm
-
Hi Umberto,
This is the email I sent as this forum was down earlier...
I’m running P3D v3.4 (for FS Labs Concorde) and P3D v4.5 for everything else. GSX is installed for both sims.
This morning I launched the GSX uninstall process via Control Panel – Add/Remove Programs and it asked if I wished to uninstall GSX. There was no option to uninstall for just v3 or v4.
As I didn’t want to touch v4 I chose Cancel. However, the uninstaller then advised three files had been set back to default ones. I’m attaching the three screenshots. This should not have happened. Cancelling the uninstaller should have left things as they are.
The problem now is I don’t know how to rectify the problem with these files. Please advise and also change the uninstaller so this doesn’t happen again.
-
Having a shared folder has the obvious advantage that:
- We don't waste any hard drive space if you have multiple simulators installed, since a lot the files are the same for 32 and 64 bit versions of sim.
- We are fully compliant with LM recommendation of not installing anything in the simulator own folder
However, due to these requirements, it means is not possible to selectively Uninstall for one sim only because the uninstaller, by default, will remove all files it has installed when it originally run, and since most of them are shared, it will remove too much, unless we would individually flag shared or not shared files, which is theoretically possible, but it conflict with the very concept of the Live Update, since the Live Update can add, replace and remove any files after the installation but, since the Uninstaller is created on the fly by the installer when you run the installer, it would be impossible to keep the uninstaller updated with all the future changes.
To fix whatever problem you have, I suggest doing the following:
- Uninstall GSX and every other FSDT product you have
- Reply YES to the question "Do you want to remove the Addon Manager ?"
- Check if you still have an Addon Manager folder and if you have it, remove it manually
- Reinstall GSX and every other FSDT product you have, indicating all the simulators you want to install into. Since you still use P3D V3, you must install both the 32 and the 64 bit version of GSX.
Nothing related to activation will be affected.
-
Ouch! All that work when I backed out of the uninstall process? Why does your program replace files when the user selected NO for the uninstall to continue?
-
I was only replying to a part of your question, why it's not possible to selectively Uninstall from just one sim.
The fact is still doing something is not supposed to do when you press Cancel, is in fact a problem we should fix.
My solution would get you going for sure, while we fix this problem, which would in any case require to re-download all the installers are re-run them again ( as I've said, the uninstaller is created by the installer code, when you run the installer ), and the only thing you'll gain while waiting for fixed installer, is that you'll be able to press Cancel and nothing will happen ( as it should ), but you would still have to do the same complete uninstall/redownload/reinstall.
My solution would work even with the current installers, but you cannot still press Cancel. That would require updated installers for everything.
-
Hi Umberto. The problem only relates to GSX. I’m happy to uninstall both 32 and 64 bit versions of GSX and then reinstall them once you have fixed the problem related to cancelling the uninstall.
Are you saying this action (only with GSX) has affected all my FSDT airports as well? Surely not? If that is the case I respectfully suggest you need to reconsider how these programs are managed.
Anyway, for now I’ll do nothing and see how things transpire. Can you advise where these files that were replaced reside on my system? And just to confirm I have opened the GSX Control Panel and opted to replace the default jetways. I presume that’s okay?
-
Hi Umberto. The problem only relates to GSX. I’m happy to uninstall both 32 and 64 bit versions of GSX and then reinstall them once you have fixed the problem related to cancelling the uninstall.
As I've said, you don't have to wait for us to fix the installer because, the only thing you'll achieve, is that you will be able to Cancel the uninstaller without worrying. And even in that case, you will still have to re-download the installer. My solution, instead, worked with the installer you have, just be sure you don't start the Uninstaller and Cancel it, for the time being.
Are you saying this action (only with GSX) has affected all my FSDT airports as well? Surely not? If that is the case I respectfully suggest you need to reconsider how these programs are managed.
I can't say for sure. I gave you a solution that would surely work, regardless. Otherwise, my answer would have been way more complex to write and to follow, like "If you installed this scenery, but not this one, do this, else do that".
-
Hi Umberto. I shall go ahead and uninstall and reinstall GSX and the Level2 version. I’ll see how the FSDT airports behave before going any further.
-
Hi Umberto. I shall go ahead and uninstall and reinstall GSX and the Level2 version. I’ll see how the FSDT airports behave before going any further.
Yes, I don't think airports would be affected. GSX and GSX Level 2 are just one installation
If you don't do anything, the worse it could happen is you might see the default tow truck which the GSX installer disable. The default jetway model can be disabled/enabled with the GSX Control Panel.
If you reinstall GSX, it would surely disable both the default jetways and tow truck. In any case, we already fixed the problem with the uninstaller on abort, and will appear in the next update (requiring to download all installers, if you really need it)
-
Thanks Umberto. I should explain why I’m doing all this. You may recall I posted a message in February about a problem with FS Labs Concorde CTDing at specific places. It was suggested to me that GSX and / or SODE might be responsible so I uninstalled both then reinstalled them.
The problem disappeared until yesterday even though I had changed nothing on my P3D v3.4 install. So I was looking for a quick way of temporarily removing GSX. I backed out of the uninstall and you know the rest.
It was crashing P3D 4nm from a waypoint around 20 miles WNW of EGCC. Highly unlikely that GSX is responsible but it and SODE were the only things I hadn’t uninstalled.
-
And that's another advantage of our products using the proper P3D add-on.xml method to install: you can temporarily deactivate these add-on, usually for troubleshooting, without having to uninstall anything!
Just to to the Options->Add-ons menu of the sim. There, you can disable an add-on ( only those installed with the add-on.xml method will appear there ), without worrying about uninstalling it.
-
And that's another advantage of our products using the proper P3D add-on.xml method to install: you can temporarily deactivate these add-on, usually for troubleshooting, without having to uninstall anything!
Just to to the Options->Add-ons menu of the sim. There, you can disable an add-on ( only those installed with the add-on.xml method will appear there ), without worrying about uninstalling it.
That was the method I tried back in Feb but the CTDs continued. It was only after I uninstalled it I saw the messages about default files being restored and only then did the crashes stop. So knowing which files are involved and where they are would be extremely helpful as deactivating only leaves those files in place.
Other than that I agree it’s a better method.
-
I have uninstalled GSX and am now installing it for 32-bit P3D. It's an enormous install and looks to be taking well over an hour. And why update ALL my products when I just want GSX installing? Give the user the option to save a load of time.
-
Installing GSX shouldn't take more than 5 minutes.
However, if you install using an OLD installer, the Live Update will have to update all files that has been released after that installer came out. It will surely will be much faster if you download the latest full installer, so the Live Update won't have much left to do.
-
Installing GSX shouldn't take more than 5 minutes.
However, if you install using an OLD installer, the Live Update will have to update all files that has been released after that installer came out. It will surely will be much faster if you download the latest full installer, so the Live Update won't have much left to do.
I downloaded the FSX/P3D 32-bit installer from your site. It took around 40 mins for everything to be updated. Was that the correct way to do it? I didn't opt for Addon Manager to be removed with the GSX uninstall.
-
Please clarify if those 40 minutes ( which is very strange ), was the time to:
- Install GSX
OR
- Live Update GSX
OR
- Live Update other FSDT products that were also outdated
-
Hi Umberto,
It was around 30-40 mins from the time I started the downloaded GSX installer. I never used Live Update. There were something like 372 actions to perform and the message at the top of the installer window did say ALL my FSDT products were being updated. But the vast majority of the time was spent installing GSX and the many vehicles.
-
But the vast majority of the time was spent installing GSX and the many vehicles.
Sorry, but this is still not very clear. With "installing", you mean:
- The ACTUAL installation process, in which files are installed from the installer, all happening locally
OR
- The Live Update process, which might have updated files you didn't had the latest version of ?
-
Umberto, I clearly stated in my last post I was using the downloaded GSX installer. Yes, run locally but the interface showed all files were being downloaded from your site.
I never mentioned the Live Update process. How would that be possible in any case if GSX wasn’t installed?
-
Umberto, I clearly stated in my last post I was using the downloaded GSX installer. Yes, run locally but the interface showed all files were being downloaded from your site.
It wasn't clear at all, and in fact it's even less clear now. But I understand why you are probably confused, I'll try to explain better.
I never mentioned the Live Update process. How would that be possible in any case if GSX wasn’t installed?
Now I see where your confusing came from. You thought I was asking about YOU manually running the FSDT Live Update. That's not what I meant, I thought you realized the INSTALLATION happens in TWO steps:
1) Step one is when the installer copies files from its temporary folder to the destination folder. This happens locally.
2) Step two is when the installer launches the Live Update ( not you ) which does it automatically as the last step of the installation. This is where files are eventually downloaded
I asked which part of the process was slow because, if you run the latest installer, the Live Update wouldn't have much left to do, since there shouldn't be *that* many files still left to update, after running the latest version of the installer.
-
Hello again. I wasn’t aware that Live Update was launched by the downloaded installer. Now that it’s clear it does it was when the status was displayed showing how many processes had completed and how many were remaining. That was what took around 30 mins to complete. And the message at the top of the window said all my installed products were being updated. That I find strange when it was only GSX I had uninstalled. I suppose you have your reasons for doing that. One installer checks everything.
I have a reasonable fast internet connection of 60Mbps and it was via a computer connected via Ethernet. I suppose you could check this yourself by uninstalling and running the relevant GSX installer.
The reason I’m reinstalling is because I run P3D v3 and v4. I have been having CTDs when flying FS Labs Concorde in v3 and after exhausting all other likely sources only GSX and SODE remained. After uninstalling and reinstalling GSX the CTDs stopped so it looks like there is an incompatibility between GSX and the CIVA INS in Concorde because the CTDs only occurred at certain places when the INS was active. If it was switched off the problem never arose.
After 3 months of problem-free flying the CTDs started again so I uninstalled and reinstalled GSX and it cured the problem.
Crazy but true! I suppose it could be SODE since GSX installs that too. I can live with this but it is frustrating and also mysterious why it happens.