Ecks
March 16th, 2020, 01:13
The FGU Updater detects if another instance of Fantasy Grounds is running and displays an error message that says it will continue after all instances of FG are closed. However, the updater appears to continue anyways, albeit at a much slower rate.
To recreate:
Launch FGU
Launch a second instance of FGU
Run the updater in either FGU instance
Wait ~10 seconds
In the background behind the error message, the updater progress bar shows the update going through and updating packages. Update progress appears to be much slower compared with the normal behavior (note: my install is currently up to date, so there is nothing to download).
Close the other instance of FGU. The updater error message will disappear as expected, and the update will continue at normal rate.
The FGU Updater also detects FG Classic as a running instance of Fantasy Grounds. I didn't expect these to conflict, but this may be working as designed. I have both FGC and FGU installed using the default directories. Similar to the above issue, the updater will actually continue (slowly) in the background. The error is cleared once FGC is closed.
To recreate:
Launch FGC
Launch FGU
Click 'Check For Updates' in FGU
FGU shows an error message that Fantasy Grounds is currently running. The updater (slowly) begins running in the background.
Close FGC. The error message in FGU goes away and the update continues, now at the (faster) expected rate.
Environment:
Windows 10
New installation of FGU (14-May 2020)
Default data directories
FGU data directory: AppData/Roaming/SmiteWorks/Fantasy Grounds
FGC data directory: AppData/Roaming/Fantasy Grounds
To recreate:
Launch FGU
Launch a second instance of FGU
Run the updater in either FGU instance
Wait ~10 seconds
In the background behind the error message, the updater progress bar shows the update going through and updating packages. Update progress appears to be much slower compared with the normal behavior (note: my install is currently up to date, so there is nothing to download).
Close the other instance of FGU. The updater error message will disappear as expected, and the update will continue at normal rate.
The FGU Updater also detects FG Classic as a running instance of Fantasy Grounds. I didn't expect these to conflict, but this may be working as designed. I have both FGC and FGU installed using the default directories. Similar to the above issue, the updater will actually continue (slowly) in the background. The error is cleared once FGC is closed.
To recreate:
Launch FGC
Launch FGU
Click 'Check For Updates' in FGU
FGU shows an error message that Fantasy Grounds is currently running. The updater (slowly) begins running in the background.
Close FGC. The error message in FGU goes away and the update continues, now at the (faster) expected rate.
Environment:
Windows 10
New installation of FGU (14-May 2020)
Default data directories
FGU data directory: AppData/Roaming/SmiteWorks/Fantasy Grounds
FGC data directory: AppData/Roaming/Fantasy Grounds