UGS - autoupdate from Horde - exception

Development Pipeline & Plugins
, ,
1

Hi,

we are trying to use UGS auto-update from horde feature, but we struggle with excetion thrown when starting UGS/confirming auto update setting window when HordeUrl is specified in Deployment.json.

But when new UGS installation (with specified HordeUrl in Deployment.json) is started. Continu button on Update window is throwing exception (see image exception.png).

I tried to debug this and noticed that in UpdateSettingsWindow.cs is method ConnectBtn_Click that is checking equality of _settings.HordeServer and DeploymentSettings.Instance.HordeUrl and if those two values are equals, then _settings.HordeServer is set to NULL. And when this method continue in execution there is nullcheck that causes the exception. (see code01.png)

And im confused why is this there?

I though its somehow due to update of value in registry, but even _settings.Save() method is nullchecking value and not updating it.

Also i noticed, that when UGS is installed with hordeUrl e.g. http://my.fluffy.horde/ and then is this value in Deployment.json changed to http://my.fluffier.horde/. The change is not propagated to UGS. Its read from setting file, but its overriden by value in registry.

Maybe these two issues are linked together? Not sure but it seems like to me.

Feel free to ask aditional informations

Thanks and regards

Lubos Suk

2

Steps to Reproduce

  1. Build UGS installer with specified default HordeUrl in Deployment.json
  2. Install this UGS on PC (or reset horde registry values)
  3. Run UGS (UpdateSettingsWindow should appear. Or run with -settings argument)
  4. Ensure that Horde radio button is selected and Server field is filled with same url as specified in Deployment.json
  5. Click continue button (exception should apper)
3

Hey Lubos,

I’ve just confirmed this on my end, and internally that this is a known issue. I’ll see if I can try down the bug ticket, and get it added to the public tracker.

Kind regards,

Julian

4

Hey Lubos,

Just following up here - there is an open PR that looks to have addressed this (at least for the local user). This may be a suitable workaround in the interim while the team gets an official fix.

https://github.com/EpicGames/UnrealEngine/pull/12304/files

Kind regards,

Julian

5

Hey Julian,

thanks for the PR, it looks similar to changes we made on our side to hotfix this issue till oficial fix is available.

Thanks and regards,

Lubos