If the consolidated Game Launcher starts up and logs into your account automatically before the secondary library’s drive has been connected and its volume mounted, then the secondary library might not be correctly recognised once it has been connected, and your consolidated Game Launcher might treat the games stored in that library as “not installed”. What causes my secondary library not to be recognised? If your consolidated Game Launcher is installed on an internal drive (usually the C: drive by default on Windows) but has the option to store secondary Game Libraries on other drives, this could result in the games in the secondary library not always being recognised as installed, even though the game files are still present on the secondary volume and have not been changed. The software and its games will only launch if the Dock is connected, and the volume with the game files consistently receives the same letter from the operating system. If you do use a consolidated Game Launcher such as Steam, Origin, etc to install games, one option is to install this software (and any downloaded games) directly on the desired drive such as the Dock’s internal HDD, or an added NVMe. “E:”) when it’s connected, then there should never be an issue starting the game.
not using a consolidated Game Launcher such as Steam, Origin, the Epic Game Store, GOG, etc) then as long as that drive (with the installed game) consistently receives the same drive letter from your operating system (e.g. If you install a game to the Dock’s Internal HDD or the added NVMe or a connected USB drive using a stand-alone installer (i.e. This article shares some important information on the logistics of having games installed on an external drive, such as the FireCuda Gaming Dock’s internal HDD, an added NVMe SSD, or a USB drive connected to the Dock.
0 kommentar(er)
