Chris

There's a few tactics you could try. You could throw smoke at the door so they can't shoot out when they open they door. You could camp the door with lots of soldiers facing it at medium range, so you kill the Sebillian with overwatch once it opens the door (if your soldiers have full TU when facing the door they'll probably shoot first). Alternatively, you could put your shield soldier out in front of your other troops and far enough away from everyone else that the Sebillian will probably shoot at him and nobody else would be suppressed (and he might not die due to the shield). Or you could blow the door off with the HEVY or the lasers, and then just shoot into the UFO from a distance. There's quite a few things you could try - just try to avoid getting your whole team suppressed!

This update is only accessible by switching to our Experimental branches (instructions on how to do so here). This is a relatively small update that mostly incorporates localisation fixes - we're planning to push this build onto the main branch in a couple of days if no major issues are encountered by the community. Changes: Updated the localisation files to incorporate the latest batch of translation fixes. This should fix the bulk of the remaining translation issues in the game. Fixed late-game Wraith terror sites sometimes having enemies equipped with Plasma weapons rather than Fusion weapons. Gemini now has 12 starting armour (previously 15). Shielded Plating for interceptors now offers +24 armour (previously 25). Together these two changes prevent the Gemini getting more than 60 Armour, as going above this level breaks the air combat UI. Added more explanation to the tooltips for the concept of damage drop-off on explosions. Improved the tooltips for Flashbang Grenades and Smoke Grenades.

We have now had a reply from NVIDIA, they said they'd take the game into maintenance mode and update the save path - so it sounds like the problem was that they needed to update some settings at their end. However I'm not quite sure what the expected timescale is for this fix. We've not had any further contact from them, but I'm not sure if that means they've already made the change or whether it's still being processed. Might be worth you giving it a test? I'll give you an update if we do get another email from them anyway.

I'm not sure why the saves are being cleared each time you're playing. Presumably GeForce Now is saving to some weird location that Steam Cloud can't find, but we don't know what that location is because you can't access the local folder to tell us. And then I guess it deletes the entire virtual machine when you end your session. There's very little that we as developers can do here. I've reached out to our publishers as they apparently have some kind of relationship with Nvidia to ask them what might be going on here (they emailed them just now), hopefully they'll have some kind of answer in the next few days. It's a bit concerning that nobody can play the game on GeForce Now any more at all; the new save directory is a pretty standard location for Unity games. You might also want to consider some of the options for playing Xenonauts 2 on a Mac? It's not officially supported but we have had reports of people playing on Crossover, and perhaps Whisky and Parallels are also options.

One other thing to consider - if Steam Cloud is active, you should be able to access your saves for Xenonauts 2 using this link: https://store.steampowered.com/account/remotestorageapp/?appid=538030 Hopefully then you can download them to your local machine and put them in the correct folder, and either play locally or let them sync to the correct folder on GeforceNow.

Hmmm. We're really bumping up against the limits of what we can do with those restrictions, unfortunately. Is Steam Cloud active with GeForce now? If so then maybe you can install the game locally and it'll copy the saves to your local machine and you can shuffle them around there? I'm sorry you've been left in this position. We put quite a lot of safeties in place for the save migration process but it seems like Geforce Now is blocking all of them.

This update is only accessible by switching to our Experimental branches (instructions on how to do so here). Another large-ish patch for the previous Experimental build, which seems to be relatively stable so far! We've made a bunch of localisation fixes over the past couple of days and we've now sent our files off for translation - once those are back, we'll release this build onto the public branches! Changes & Bugfixes: Incorporated the fixes made to 7.21.5 and 7.21.6 over the weekend, which will help avoid crashes if users have lots of old Early Access save games in their save directory. Fixed a crash that could occur if picking up items in the tactical inventory from near an area with interactive objective props (Cleaner Desks, Abduction tubes, etc). Fixed melee weapon hit chance information being incorrect in the bottom left "shot calculation" UI element. It now shows the base accuracy of the weapon as (say) 65% rather than the incorrect x1.65 formatting it used before. Fixed an issue where a planned move (the move + shoot action using Ctrl+Shift) could move the soldier onto a teleporter when using a medkit or melee weapon, causing the teleporter to trigger before the action occurred. The teleporter will now not trigger in such situations. Fixed the Alien Plasma Machinegun using the same 2d tile art as the Alien Plasma Rifle. Fixed the Aircraft fuel tooltip still incorrectly talking about aircraft running out of fuel in air combat. Fixed a typo in the Alien Plasma Weapons xenopedia entry. Fixed some more translation issues.

Yeah, we won't be breaking save games again unless there's a large post-release patch for some reason (maybe if we do a free update to accompany some DLC or something). But that won't be happening for a while, if ever.

Your save games won't be gone, but the game is trying to read saves from a different directory now. We can help you find them / move them across if there has been a problem. It's best to create a bug report for it as I don't check these threads very often. If you go to the Main Menu and click the Local Folder button, are there any files in the /Saves/ directory? Often the problem is that there is lots of saves in there, so it takes a 20-30 seconds for the Load Game window to show the full list.

Hi - so in the Steam options for the game, you can set launch arguments. Try this: -localGameFolder="%USERPROFILE%/Documents/My Games/Xenonauts 2/" If that doesn't work, then maybe try switching to the Steam beta branch called "v7.20.4" as that's the older version of the game. That should let you finish your campaign and then you can switch back to the newer version if you want to keep playing.

Thanks. This bug doesn't seem linked to the jetpack itself, it seems to be linked to the fact the unit has 0 TU. If their TU is refreshed then they path normallly. I'll chat to the programmers about it.

Hey - hmmm, I guess it depends how you're getting the game onto GeForce now. Are you putting your games onto GeForce Now via your Steam account? If so we could probably put an older version of the game on a branch for you to play, or maybe you could use the command line arguments to set the updated file path? Let me know what your setup is anyway.

Thanks. This looks like an issue with the game loading files - does it happen if you start a fresh campaign? The issue might also go away if you do a hard reinstall of the game, as it's perhaps caused by a corrupted file:

Thanks. Do you have a controller plugged in, or any other input device? That's often the cause of UI input issues. Although I guess it'd be strange that this happens sometimes and not other times if so!

Another hotfix for v7.21 to address ongoing crashes related to players having old saves in their save directory. This should fully fix the issue, but if not, players can always manually delete old campaigns from their save directory while they wait for another patch (any campaign folder that doesn't have a string of numbers at the end of the name can be deleted). Changelog: Another fix to prevent saves from several years ago causing crashes when scanning the save game folder.