Quote:
Originally Posted by Dowly
I assume your MS redists are in somewhat updated condition? Steam usually checks for these and updates them if necessary. Has Steam done this when you first start any new game?
|
Latest Steam buys were DLCs for Assetto Corsa and Fallout 4, just weeks ago. Flawless procedures.
Latest game installation was Combat Mission: Shock Force with all addons, just a few days ago. It checked for DirX, Flawless procedure. Cannot say wqhether the DirX was blocked due to my settings or not - point is - the WU settings were not changed by the installer.
As I said earlier, I could imagine that Steam handles "Betas" somewhat differently, due to the often constant updating of Betas required. But if Apex nor got officially released, it is not Beta anymore, does not fall under that regime then.
Problem was not that installation of Apex Beta once may knocked onto Microsoft servers. It did install, and functional, I test-played the island a little bit, for half an hour, it all was there and worked. Problem was that as long as the Apex Beta was present, it reactivated WU again every time I switched it off and rebooted the system in the next day, even when no download of a new Beta was happening.
I probably must simply download all that stuff
once again and see how it works. I wanted to avoid the risk of doing that in vein, it costs an awful lot of time, since you cannot trust in simply copying over the game folder from am image - it already could be affected by this problem, if there is some. I also wanted to minimise the risk to my Windows of getting hit by something W10-related when that WU toggle gets activated. I noticed last autumn that MS is incredibly quick on using a hole in defences against W10-related software, open the door just a tiny bit for a second, and they immediately try to squeeze a foot in there.
Again my queston: can ArmA3 be installed in any way without having all bought DLC automatically getting installed as well? If there is such a switch, I am not aware of it.