Products Support > GSX Support FSX/P3D
GSX PBR Update
simtom:
So, I uninstalled everything and disconnected my computer from the internet (for preventing the Live Updater to download anything).
I had no problems with the installation and all the files were still present.
I was also able to register GSX in P3D but as soon as I reconnected to the internet weird stuff started to happen. Whenever I request something from the CTRL + F12 menu Couatl crashed.
virtuali:
--- Quote from: simtom on July 02, 2019, 06:20:16 pm ---So, I uninstalled everything and disconnected my computer from the internet (for preventing the Live Updater to download anything).
--- End quote ---
Which of course is precisely what you should NOT do, since we released some fixes in the meantime
--- Quote ---Whenever I request something from the CTRL + F12 menu Couatl crashed
--- End quote ---
Has it crashed with a suggestion to open the error log ? If yes, open the error log, save it, ZIP it and Attach it to a post.
AFS:
Dear Umberto,
maybe you should tackle the problem from another angle.
It makes no sense now to examine countless systems for possible misbehavior. Smarter would be to make the installer so that it runs everywhere.
I'm also wondering why all the other updates have always been hassle-free and now not at all. Have you changed anything and if so, what?
Since the update obviously has allocation problems with installations that are NOT installed on C: - I'm NOT talking about your computer now - it would be smart to ask for user input instead to use the "full automatic" mode .
For example, the query for which version of the flight simulator should be updated. Here, of course, the registry can be read out and a suggestion made, but the user can change the path according to his own needs.
The same can be done by querying the valid GSX installation path.
Thus, the installer knows exactly what he (files for FSX or P3D4, only legacy or only PBR files) exactly install or update and what is not. The user input is then the basis for the installation or the update.
Errors are then automatically only on the user - in contrast to now.
The problem with different registry entries to perhaps nonexistent simulator installations is then non existent.
I also think it would be wise to put just the new full installation files for downloading on the server instead of this huge live update.
This certainly requires less server time than the live update with such a large amount of files.
If the setup file does the same user queries before installation, nothing can go wrong. This gives users the freedom to decide what they want to install where.
Many software manufacturers do this, e.g. REX, and there is no problem with that.
I would use the live update only for small updates, as before.
Perhaps this option would be more efficient in the long run than having to deal with bugfixes now and all the time.
Maybe you can think about it.
simtom:
--- Quote from: virtuali on July 02, 2019, 06:22:30 pm ---Which of course is precisely what you should NOT do, since we released some fixes in the meantime
--- End quote ---
All right, I'll uninstall it again without disconnecting.
--- Quote ---Has it crashed with a suggestion to open the error log ? If yes, open the error log, save it, ZIP it and Attach it to a post.
--- End quote ---
I'll update you on that after reinstalling (if still occurring).
simtom:
--- Quote ---Has it crashed with a suggestion to open the error log ? If yes, open the error log, save it, ZIP it and Attach it to a post.
--- End quote ---
The crash log isn't very long, this is all I get:
couatl v3.2 (build 4231)
panic log started on Tue Jul 2 18:30:56 2019
problem raised by engine or unspecified addon
{'Airport': 'KSFO', 'User Pos': (37.61067183629535, -122.38701042433878, 6.36775 m, 2.40575 m, 210.28998983289128)}
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version