All Activity

Thanks.

What most likely happened on the second crash site map was that the dockyard maps had an equal amount of times used, which meant the second crash site map got randomized, it was just a bit of bad RNG that it ended up choosing the same map. Map 1 - 34 Map 2 - 34 Map 3 - 33 + 1(from the first crash site) = 34 so now it randomizes for the second crash site and it just so happened it chose map 3 again. We could add a way to make sure that the last chosen map doesn't get picked again, but again two consecutive maps in the same biome shouldn't be happening often, and even then there's only a 1/3 chance of it happening.

Heavy Servitor looks properly intimidating, good work! Could the cooldown between evasive rolls be a proper stat? Or something that's moddable? It feels like varying the cooldown length would be another good way to differentiate between different airframes.

Looking forward to Milestone 6...

Air combat - make sure its ALWAYS optional. Even commander difficulty always optional. Game balance pass - it is about 3 month late and on top you made no mentions about it for 6th milestone release. Game will need another 2 - 3 balance passes before release, but there is not enough time left. One balance pass takes 1-2 months. That is most pressing issue.

I don't want to sound diificult, but why isn't the game picking the least used map on the second crash site then? I mean if you have such a system implemented, shouldn't the map that was played just 10 minutes ago be diaregarded from the random map pool? Edit: but yeah, as you said, it's a rare thing and if it needs lots of work to fix it, I'm sure you have more pressing issues to work on.

Thanks! Appreciate you going through the trouble to find the saves. I tested it and yeah it's basically just the randomisation of the maps causing the same map to appear twice (the game picking the least used map, then randomizing the next one). We won't make any changes for now as this should be a relatively rare thing, but I'll take note of this just in case this case gets brought up again (which might mean it's happening more frequently that it should)

Noticed that you've accidentally made a duplicate post, but we've basically made a bunch of fixes that should prevent stuff like this from happening again once the next patch (5.39) comes out.

Thanks for the report! We've made a bunch of safeguards that should prevent crashes like these happening once 5.39 is out. Said patch should be hopefully out today, if not before this week ends.

Excellent!

bug_report_2025-07-02-18h37_wn_5.38.1_unhandled_exception_0.zip crash_info.html crash_info.json

bug_report_2025-07-02-18h37_wn_5.38.1_unhandled_exception_0.zip crash_info.html crash_info.json

Nice update! Well done!

Not sure what happened. Played last night. Today went to go load my game. All my saves are gone and deleted. Any help?

Hello everyone - it's time for our monthly development update! Read on to see what we've been working on in June... New Assets: I mentioned last month that the main focus of Milestone 6 was adding new content to the game, and we continued to add new assets to the game this month. The first of these is the new 3d model for the alien Heavy Servitor unit (which can be seen above), which I think is a nice addition to the game and much more distinct from the basic Servitor than previously. This means we've now added unique 3d models for all of the new alien unit variants added in Milestone 5. Various other new assets were added too: The illustrations for the final cinematic is now complete, and the cinematic is now being put together by the animation team that made the intro cinematic. We added a proper background to the UOO-1 Sabotage mission. The platforms that make up this level were previously floating in empty space, but are now contained within the (fairly elaborate) hull of an alien space station. Work has continued on the new Soviet Town terror biome, which we're hoping to have finished in the coming month. Inventory tile artwork was added for the Alien Bio-Rifle weapon given to the Mantids in Milestone 5. Corpse / stunned inventory art for the new Heavy Mentarch was also added. Air Combat Refresh The biggest code changes this month were to the air combat section of the game, which has had a major interface facelift and several usability improvements. We've only completed part of this visual refresh so far, but next month we'll be updating the background, the battlefield UI and the various combatants with sharper and more attractive replacement graphics to finish the job. The gameplay changes so far have mostly involved adding extra information to the UI - for example, the Evasive Roll buttons now show a cooldown bar overlay so players no longer have to guess how long until the ability is available again. The weapon tiles also show a reload progress bar for similar reasons. We've also made minor tweaks to the control system so it's easier to select aircraft and give them orders. Next month we'll be making some actual mechanical changes, like refining the way speed / acceleration work and switching the interceptor retreat mechanic back to how it used to work in older versions of the game (where aircraft had to reach the edge of the battlefield to retreat). Once all that is done, we'll finally be able to start implementing the air combat section of the tutorial. Launch Aircraft Panel Prior to starting on the air combat, we also made some quick improvements to the Launch Aircraft panel. Hovering over an aircraft in the list now shows a pop-up panel on the left that shows additional information on that aircraft, including its full loadout of weapons and equipment and exact values for HP / Armour / Fuel. If the aircraft is a dropship, it instead shows all the soldiers assigned to it. We made some improvements to the aircraft selection logic here, too - previously this was a bit clunky, and potentially confusing for newer players. Shroud Fixes: Community bug reports for Milestone 5 were much less frequent in June than in previous months, which allowed us to shift our attention towards some long-standing issues with the shroud system in tactical missions. Anyone who has played the game will have encountered these - ranging from objects like cursors / fire + smoke / weapoon projectiles all incorrectly drawing underneath shrouded areas, to more subtle things like us being unable to reveal the rear side of doors in alien base maps. We're hoping to have fixes for some of these issues in the next week or two. However, these are quite thorny problems and there's always a chance it'll take longer! Modding Documentation: The updated Xenonauts 2 modding documentation can be found here: https://github.com/GoldhawkInteractive/X2-Modding/ Again, it's worth mentioning that the average player will struggle to mod the game until we finish the mod tools, which we'll probably start work on after Milestone 6 releases. The documentation will be most useful for C# coders want to do code injection, or intrepid pioneers with a very high tolerance for manually editing JSON files that were never intended to be readable by humans. Milestone 6 Stability Test: Finally, we're planning a stability test for Milestone 6 on the Experimental branch this month - most likely between the 7th-11th July. There's still quite a bit of work to do before Milestone 6 is finished (both in terms of adding content and doing a balance pass), but we'd like to start finding and fixing any major crash bugs while we work towards a "proper" test build for Milestone 6. As always, thanks for reading the update. We'll be back with another at the end of July!

I've always suggested doing this like you.,But the problem is that AI knows where you are.,But you don't know where he's in.,As long as you enter his range, whether he sees you or not,There's a high probability that the next round will suddenly appear and give you a shot.,I'm not dissatisfied with the game mode, but this perspective AI does reduce people's game experience.,After all, even a hardcore game should work gameplay.,If it's just a hardcore, what's the difference between it and reality?

1. tactic advice : keep free TU on the end of turn so you COULD shoot AI somehow sees your free TU as danger, so it is much more careful to attack you. Then if it does, you can win the encounter. After a while, you get a experience, how interruption EXACTLY works (carefully reading tooltips helps), so you can use the game rules to your advantage. Otherwise speaking do not run like headless chicken. 2. it is war. It means you kill them an they kill you. who stands on the end wins. Thats how it works since first ape used a stick as weapon. Get use to it. It is NOT Holywood war = where 5 gifted super heroes save the world by massacre thousands aliens while one soldier get a flash would on his biceps and second soldier gets broken heart. 3. stop QQuing and turn Iron man ON.

This was my proposal in discord: https://discord.com/channels/702822278148390983/1286692960171458670 where if your soldier reaches COL rank and a bunch of other conditions, you'd get a capstone ability.

ok, here you go. There's a save before the first crash site (geoscape), a save from the last turn of the first crash site (tactical), a save just before the second crash site (geoscape) and a save from the first turn of the second crash site. (tactical). Hope this helps. user_before_first_destroyer-2.json user_last_turn_of_first_destroyer-3.json user_before_second_destroyer-4.json user_first_turn_of_secord_destroyer-5.json

Hey Skitso, thanks as always for the reports! Do you still have the geoscape save for this? Ideally if you have both saves before and after the UFOs were shot down, that'd be great. As for the sebillian crew thing, we're changing a bunch of stuff for milestone 6, but basically the the first scout spawns a guaranteed mantid crew while the first destroyer is guaranteed to be a sebillian spawn, we're changing some of those guaranteed ufo crew spawns (not sure if we're changing the first scout ufo, but the first destroyer will be changed) so that should help with the crew spawning the same alien type all the time. I've tested this a bit as well on 5.28 and 27 to make sure and was able to get a psyon ufo crew on both cases in around the first 5 ufos (scouts and destroyers), so I think it should be working properly. Was this not the case on your playthrough? EDIT: Took a look at the dockyard maps(there are currently 3 for the small crash site per biome) and it looks like it was setup correctly. What most likely happened here is that the game picked the least used map for said biome and then randomized the next crash site map(if the maps were all used the same amount of times, it will randomize the next one) which coincidentally gave the same map.

Hello there, thanks for the bug report! Can you send us the log file so we can see why the game is not loading properly? You can usually find this by going to Documents\My Games\Xenonauts 2\Logs, you should see a .log file named "output" (note that this is different from the files named "output.log". Can you attach said file here so we can give it a look?

Thanks for taking the time to post a bug report! Yeah, this map has a spawn node that was misplaced inside the battleship UFO's hull. We've made a fix for this but it won't be out until milestone 6. As for the game having no sound, does restarting the game restore audio? And is this the first time this happened for you?

The Psyon is running around the battleship between walls unable to be targeted or killed. bug_report_2025-06-30-07h15_gc_5.38.1_user_f11_1.zip also no sound even after reloading the game, previously had sound.

The gameplay is good. I prefer thinking about the whole map over the x-com reboot's series of mini encounters. Don't rush to move all your units off the plane. It provides excellent cover. When I have very experienced units I avoid moving them out of it until I have swept the area they are moving into. I usually have at least two low value units with shields to take point and act as mobile cover if one of the better units is left exposed. If they stay alive long enough to improve, they get a different loadout and graduate from being scouts/mobile cover. Robots are also ok for exploring ahead. Injured/damaged/shieldless units fall back.

I shot 2 destroyers down back to back and both generated same crash site maps. Are there even more than 1 dock map for destroyers available currently, or is there a bug? (also, why I'm not surprised both were against sebillians? ;)) auto_groundcombat_turn_1_start-120.json