If using the standalone "star_trek_setup.exe" file, then the workflow is also very similar being \\Star Trek Online\Live\x86 & \\Star Trek Online\Live\圆4 however the problems also occur that way as well and that's why it's important for all of the Devs at Steam, Arc, and the publisher work together.
Yes, both the Steam & Arc clients do "distribute" / install the GameClient.exe executable in either of the following paths (Steam Paths) \Steam\steamapps\common\Star Trek Online\Star Trek Online\Live\圆4 & \Steam\steamapps\common\Star Trek Online\Star Trek Online\Live\x86 because all you have to do is look in either of those folders or attempt to find those folders during the installation process and you'll notice that they're not installed at all until the installation is about 80% complete, and the following paths for Arc that are \Star Trek Online_en\Star Trek Online\Live\圆4 & \Star Trek Online_en\Star Trek Online\Live\x86 follow the exact same workflow as well. The above being said, is there any particular command line that can be placed in the "Star Trek Online.exe" STO Launcher's command line options that will force the launcher to use the 64-bit variant instead of the 32-bit due to the fact that in Windows 10, at present, only the 64-bit GameClient.exe is the only GameClient.exe file that works reliably? The latter portion with the security token and "Star Trek Online.exe" launcher being necessary is normal behavior for STO, and I'd actually not recommend going outside of that method however it's nearly impossible to tell if "GameClient.exe" from the 圆4 directory is being used by the "Star Trek Online.exe" or the x86 (32-bit) directory is being used by the "Star Trek Online.exe" without attempting to launch one of the GameClient.exe files directly from either the x86 or 圆4 directories.Īt present the GameClient.exe file from the 圆4 directory is the only one that will launch the game fully, and there's some copy of the game files back and forth between the Live and Live\圆4 directories required to get the GameClient.exe to even execute at all because it does require the presence of the local game files. Only the 64-bit GameClient.exe file will launch the game fully at this time however the game will not connect when launching the executable directly because it does need the security token from the launcher. Happy Holidays to all although not so much for those of us using STO on Windows 10. and initially posted there however this is a recent issue that's occurred within the past 24 hours post holiday event patch. Well, I found a 2 year old link on the forums, about a similar issue at URL:
0 kommentar(er)
