HGL
afraid-scarlet
Xcom 2 can't move soldiers
As mentioned in another post [https://discord.com/channels/812703221789097985/1400490513685024870] I have the same issue. I've installed XCOM2 from GOG and it is able to start. After switch the to controller settings I've started the tutorial and can move the red cross to the position where the solider should walk. Unfortunately it is then not possible to confirm the position by pressing the A button as showed.
As mentioned in another post I've tried to install the vncrun2022 but there is already showed "Installed components: vcrun2022". I decided to install the vncrun2015 because if I type vncrun in the search bar it just shows me vcrun2003 to 2019 only, so I have no Install button for the 2022 version.
Anyhow, it is not possible to move the soldiers in the tutorial mission. Meanwhile I've skipped the tutorial mission to figure out if the problem is just there but unfortunately the problem persists also in the main mission.
https://0x0.st/KSq9.log
Solution:Jump to solution
Please follow these instructions on using GE-Proton:
1. Head to the Wine Manager in Heroic, click the "GE-Proton" tab, and install "GE-Proton-Latest"
2. Head to the settings for your game(s) (icon on game card in library). In the "Wine Version" dropdown, select "Proton - GE-Proton-latest"
3. Rename your Wineprefix (path is shown in game settings), e.g. from
current-name to current-name_bak. To clarify: Rename the actual folder on your hard drive, do not change the option in the game settings.
Note: This will make game-specific configuration data (e.g. in-game settings or save files) unavailable. If this is an issue, let us know & we'll help you restore them.15 Replies
afraid-scarletOP•5w ago
I've started the game now with -nostartupmovies -allowconsole because I read that there is a teleport option. The soldiers can be teleport by console command TTC, but it looks like they are under the map and it is also not possible to move them or interact with the environment.
afraid-scarletOP•5w ago
Did a little AI digging with the pictures and the blog posts and could solve the issue. Tutorial mission and general game works both now.
Here is the summary (every setting without "":
1. xcom2 as GOG game
2. install game with "Wine Version - Proton -GE-Proton-latest"
3. bind "WinePrefix folder" to the installation folder not the general prefix folder
4. "Select an alternative EXE to run" and choose "<installpath>/XCOM2/Binaries/Win64/Xcom2.exe"
4.1. [Gaming Mode] Start the Game
4.2. If you stuck with missing controller choose the Layout "GamePad with Joystick/precision camera/aimprecision"
4.2.1. In game navigate with the trackpad to options, confirm always with L3 (could be that you need to press B to get back if credits video is played), and set input device to gamepad. Now you have XBOX gamepad in game
5. [Optional] "Game Arguments (To run after the command)" -nostartupmovies -allowconsole
5.1. ~ starts/quits console, command TTC is to teleport the unit to the place where you place the cursor
6. [In Desktop Mode] - download the Visual C++ Redistributable Packages for Visual Studio 2013 from here https://www.microsoft.com/en-us/download/details.aspx?id=40784
6.1. just the vcredist_x64.exe an save it in your download folder
7. Start Heroic and go to settings of XCOM2
8. On the Wine Tab scroll down and click "RUN EXE ON PREFIX" and choose the downloaded file to install it
9. Confirm the agreement in popup window and click install
10. Switch to Gaming Mode
11. Run XCOM
Hope this helps another lost soul to beat the aliens 😉
Can be marked as solved.
Microsoft Store - Download Center
Download Visual C++ Redistributable Packages for Visual Studio 2013...
The Visual C++ Redistributable Packages install run-time components that are required to run C++ applications that are built by using Visual Studio 2013. For an updated version of these redistributable packages, see KB 3138367.
bind "WinePrefix folder" to the installation folder not the general prefix folderNever ever do that please
"Select an alternative EXE to run" and choose "<installpath>/XCOM2/Binaries/Win64/Xcom2.exe"This is already the default EXE, so setting this option won't do anything VCRun 2022 includes VCRun 2013, so installing 2013 shouldn't have done anything
afraid-scarletOP•5w ago
Ok, could you explain why rebind the prefix should not be done?
About the EXE, this is strange because before I did that, the game was not able to start.
Regarding the VCRun2022 package, it is true that this should provide a backward compatibility, but the problem still persists if you not install the VCRun2013.
I'm looking forward for the explanation
Ok, could you explain why rebind the prefix should not be done?You want your prefix in a dedicated folder. Mixing it with the game files will be messy if you ever need to recreate it
About the EXE, this is strange because before I did that, the game was not able to start.Huh, I thought that EXE would've been the default, but apparently it isn't. Instead the default is
Launcher/ModLauncher.exe
Perhaps we should override that then
I'll try reproducing your issue in a bit, downloading the game at the moment
Yeah I can't reproduce this at all. The game just works
We already have the executable override I was referencing above (I was only looking at the game manifest itself, but the override is applied "after"), so that step won't do anything
Ah, I see what might've been the issue here. You're on the GOG version of the game, I was looking at the Epic one. Let me try with the GOG versionNope, also can't reproduce the issue on GOG. The primary play task for this game launches
Binaries/Win64/XCom2.exe. We auto-install vcrun2022 to fix the input issue with thisgenetic-orange•4w ago
Just want to chime in and say I have the same problem with the GOG version, cannot get the soldiers to move in either tutorial or regular mission.
Linux Mint 22.1, latest Heroic, GE-Proton8-3, vcrun2022 is installed.
The only thing that strikes me is that the log contains thousands of lines of "GetEndPoint called on an invalid path" once the level starts, see attached log (that is from only a few seconds inside the tutorial).
genetic-orange•4w ago
Follow-up: Just installed vcrun2013 alongside vcrun2022 that was already installed using winetricks (need to disable umu-launcher to be able to launch the winetricks GUI), and after that the game works fine.
So it seems you do need vcrun2013 either way.
I still get the "GetEndPoint called on an invalid path" when I play with logs, so it seems that is not related.
You are on an ancient version of GE-Proton there. Please update
Solution
Please follow these instructions on using GE-Proton:
1. Head to the Wine Manager in Heroic, click the "GE-Proton" tab, and install "GE-Proton-Latest"
2. Head to the settings for your game(s) (icon on game card in library). In the "Wine Version" dropdown, select "Proton - GE-Proton-latest"
3. Rename your Wineprefix (path is shown in game settings), e.g. from
current-name to current-name_bak. To clarify: Rename the actual folder on your hard drive, do not change the option in the game settings.
Note: This will make game-specific configuration data (e.g. in-game settings or save files) unavailable. If this is an issue, let us know & we'll help you restore them.genetic-orange•4w ago
That is the only version I can consistently get Windows games to run on on my hardware, sorry.
Well, something's wrong with your system configuration then. You don't "fix" this by just not updating, newer GE-Proton versions contain fixes for many issues, this one perhaps included
genetic-orange•4w ago
Believe me, I've tried but most Proton versions (Valve or GE) just make the games freeze on startup, and this is the one that works most of the time. I had the same behaviour over various Linux distributions and hardware, I have no idea why either. But I don't see why I should not use a 2 year old Proton with a 10 year old game as long as it works.
Anyway, that's not the point here I believe. The issue is that vcrun2022 alone is not sufficient to make this game work, you need vcrun2013.
See that's the thing, I didn't need to install vcrun2013; the game worked with just 2022. This difference may be due to the different Proton version
I can't confirm which version OP used since their log expired
afraid-scarletOP•4w ago
It was Proton Latest but I can check the version later.
It must have been GE-Proton10-19 or 20.