Products Support > GSX Support FSX/P3D

GSX PBR Update

<< < (16/30) > >>

AFS:
Dear Umberto,

You misunderstand something here. It's NOT about who is to blame for the mistake.
I only tell you these things so that you can recognize and analyze what goes wrong or could be improved.
I use your software and want it to work and install EVERYWHERE and with EVERYONE.

I noticed some things that make the update problematic and tedious.

1) The installation package "... \ Documents \ GSX_Installer" is only available when the installation has already been completed. This is a big disadvantage because you can not determine WHERE these files are stored.

If someone on his system partition is not enough space for the 1.72 GB he cannot install the software. It does not matter whether the files are cached in a "Temp" folder or in the "Documents" folder. It is only successful if the user still has enough space or if the files "Temp" and / or "Documents" are outsourced and not located on C :.

Suggestion: the better solution for the user would be to first download the GSX_Installer package and be able to determine the location itself. In addition, an installation from a local storage medium often goes much faster (many already have an SSD for P3D in operation) than directly from the internet.


2) The update version, downloading file by file immediately directly from the Web to update on the spot, takes too long in such a large update. It depends too much on the connection speed to the respective time of day (much or little traffic) and took me between 40 minutes and more than 2 hours with the same installation variant.

Even with a "small" update, as we have had it in the past, it takes far too long, as each file is checked, downloaded and installed online during the update.

Suggestion: here, too, would be better in the future, if we could download the update package completely and only then, when installing from a local medium, the verification and the replacement of the files would be done. that would also have the great advantage that in a new installation not every time the often lengthy online update process would have to be made again. it would be much more user friendly.


3) I do not know why there is a "new" GSX_Installer package that does not already contain ALL updates.

But I'm assuming that this is a variant WITHOUT the latest updates and you did not have time to update it because it was important to first publish the new update, and then update the package.


Currently, it is the case that we install the package and then immediately started an "update" to update the files. In addition, this takes a perceived eternity.

Suggestion: if it is only a few, few files, the actual update version is acceptable.
but as soon as it concerns more files - the difference between the "GSX_Installer" installation and the "Update" installation is installed but 2.73 GB - would be a complete "package" for local storage the better option. at least 90% of the software manufacturers do it and that works well and always.


4) which I still unclear, why the update ALWAYS at the beginning of the GSX files deletes.
This is certainly not a "local" problem only on my system - quite some users report here about it - as the update explicitly reads the respective installation path from the registry.

Since an update is indeed carried out over an existing installation, something like that should not happen. the existing files MUST either be preserved, moved and / or updated or deleted AND reinstalled.

As mentioned above, dear Umberto, it is not a criticism but only a user feedback that should help you to fix or avoid problems.


Greetings from Vienna  ::)

urban_fox27:
i had the same problem, i was installing on to my D rive which is where all my P3d stuff is located, i wasn't having any luck.
so i tried to install it on the C drive and it has installed successfully so far,yet to test.

mwyatt:
Hi Virtuali, I have the situation where GSX/GSX2 does not work after the update. See previous posts.
My Net is 4.7.2 and up to date.
My P3Dv4 and GSX/GSX2 are installed on my "F" drive, kept separate from the System Drive.
You are welcome to connect via TV at any time suitable to you. I have it already installed.
My PC is a Dual Boot PC, if that makes any difference to the update.
Look forward to resolving the update failure issue, wherever the problem lies.
Martin.

AFS:
@ mwyatt


Check if the files "__init __. Pye", "GSX Level 2 Control Panel.exe" and "GSX_manual.pdf" exist in the folder "your install directory" \ Addon Manager \ couatl \ GSX "or only folders, where are files.
If this files are not present, you do not need to search any further the error. The GSX files are missing. It is then as I described it in my first contribution.

You can, for the time, being  remedy this with my method, which I described in the first article.

AFS:

--- Quote ---An example, we just found there was a problem with the updater if there were empty registry keys from simulators that were NEVER installed and the problem was caused by... guess what, the famous dangerous P3D Migration Tool, that left empty keys for version of the sim which were never there.
--- End quote ---

That may be so. But this could easily be avoided if the update only p3d4 or fsx refer to and would search only for exactly this key.
Likewise, I think it may be easier to let download a complete update package to the users. These should then be able to select and install the right installation.

It's not like that you, Umberto, have to think for everyone. We can do a little by ourselves.   ;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version