Needs a few testers to try new alpha version of updater

[Moon Wizard]

I've been working on a brand new updater that works with some other site changes to allow Steam products to be registered directly on our site, which means it should work for Linux/Mac users as well.

I'm looking for a few people that have Steam purchases (and some that have Steam on Mac) to give the new updater a try in order to test some configurations in the wild. This should not have any impact on your data, as it just handles file updates for DLC. Just to be safe, I always recommend making a copy of your data (in this case, FG data directory) before working with alpha/beta versions of any software.

If you can help us with the testing, just switch your mode to Dev in the FG Settings and Update. This will load a new settings/updater app. In the Settings, instead of a Check Steam for Updates button, there is a "Link Account to Steam" button instead. Just click on there to link your Steam account, and then perform an Update normally. You will only ever need to link your Steam account once on our site, and the update system will automatically update to get any new Steam purchases each time you run the updater.

Please post here if you are able to give it a try, and let me know if it went through without issues or if you encountered any errors.

Thanks in advance,
JPG

[Moon Wizard]

Also, my guess is that if you use AVG, you will have to make an exception. As soon as I get feedback, make any changes and we're ready to move to beta, I'll submit to their whitelisting service.

Regards,
JPG

[Mortar]

Worked for me running Win10. Even made a test purchase through Steam and the updater pulled it no problem without having to have Steam running (I originally purchased both a regular and ultimate license through Steam)

During the initial update to the Dev the PF Core rules took a long time to complete, it seemed to hang about 3/4 of the way through for about 10-15 seconds before completing the file update. After linking my Steam purchases, it was DGA075 that hung (but it wasn't actually updated - 13 Apr 17 @ 11:13pm is the date/time stamp)

Will our Steam purchases be reflected in the FG store?

[Moon Wizard]

I believe that some of the updates that Doug has been making to fix the PF Core Rules are also in the Dev channel, which is why they took a bit.

I believe that the places where the updater is unable to update the progress bar are more noticeable in this version (i.e. saving large files), because the progress bar actually updates more frequently than the older updater. However, it is one thing that I want to keep an eye on (performance). The updater is using a new networking library that should be more resilient to network issues, but it does seem to be just a tad slower.

The Steam purchases will not be reflected in the FG store (as far as I know), though Doug is looking at using the new information to help with shuttling Paizo purchases to the Paizo store in the near term. He might look at adding a third party orders view at some point.

The Steam purchases will automatically update as long as you are using the new updater, or if you go back to the Steam account link page and choose to re-sync (even when using the old updater).

Regards,
JPG

[Mortar]

Other than the two spots I mentioned previously the whole update process seemed to go faster. I have never timed it so can only give my subjective opinion about it.

[Mortar]

So much nicer not having to have Steam running to update.

[Moon Wizard]

Just pushed a minor update to fix a couple permissions issues. Let me know if you run into any issues after updating Dev again, and try to change between modes. (i.e. Live/Test/Dev)

Thanks,
JPG

[Mortar]

Going from Live to Dev had this message HandleFile: An exception occurred during a WebClient request crop up four times.

[Teufelhunde87]

Going to give this a try! I have both Steam and Store purchases on a Windows PC. Backing up now.

[Moon Wizard]

Just updated the Dev build to use a version that should have slightly better error messages when those errors occur.

Regards,
JPG

[Mortar]

Updated one client, had a couple more weirdness happen. Ran the update three times.

[Mortar]

Crazy, don't remember posting that last post. Tried on my main rig, both Live to Dev, and Test to Dev. Getting an "Unable to update one file. Please Contact Fantasy Grounds support". PM'd an enhanced log file to you MW.

[Moon Wizard]

Mortar,

There is a bug in the current updater preventing it from saving the new updater executable, as you can see in the last set of logs you sent. Make sure not to post your logs with enhanced updating to the forums, as they contain you license key.

You'll need to delete the UpdaterEngine.exe file in the FG app folder, and run the installer from our web site for Dev mode to get it back to Dev mode.

Regards,
JPG

[Moon Wizard]

Just posted another new version of the updater. In order to get everything working back and forth between versions as expected, I also had to rev the client slightly. So, this will be v3.3.1.

There will be no ruleset or functionality changes in v3.3.1.

Regards,
JPG

[Mortani]

Tested on two different Windows 10 installs. Update worked without steam loaded. Was able to go back to Live without issue.

[Moon Wizard]

Thanks, Mortani. I was hoping the last updates had smoothed the path for changing between modes, and it looks like it has.

JPG

[Mortar]

My desktop had no issues at all moving back and forth between modes. My laptop, for whatever reason would not start the updater at all the launcher. Updated manually and it has no issues at all now.

[Moon Wizard]

Just pushed minor update to attempt support for opening Steam Account Link URL in Settings under Mac/Linux wrappers.

Cheers,
JPG

[Mortar]

Windows Defender is flagging FGUpdaterengine.exe and deleting it.

edit - Windows Defender dislikes the file so bad it won't even let me add it as an exclusion.

[Mortar]

Two totally different things happening.

First, Windows Defender is catching FGUpdateEngine.exe as a trojan, and won't let me allow it through the firewall.

Second, upon starting the update process once the av/firewall is shut off the next issue is centered around the file UpdaterEngine.exe. The updater opens, and stays open for a few seconds once the process begins. Once it closes, the error window opens saying that the update process can't be completed as the file "FGUpdaterEngine.exe" is missing. The original file "UpdaterEngine.exe" gets deleted in the process.

Bringing the UpdaterEngine.exe from another computer and placing it in the FG program folder, then renaming it to FGUpdaterEngine.exe will allow the update to happen. If you roll back from the newest updater "FGUpdaterEngine.exe" the old one is recreated.

It results in a weirdly funny situation once you combine the two. With Defender and AV on, FGUpdaterEngine.exe is immediately flagged and gone, start the update process FG is blocked from downloading the new updater, in the process of the update FG deletes the old update file and boom....update stops.

[Matticus]

Having the same problems

[LordEntrails]

Having the same problems
I think a little more info would be helpful.
What anti-virus are you using? Have you been able to whitelist FG? Have you tried disabled your A/V while you do the update? ...?