Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Chris

  1. On 6/6/2023 at 10:47 AM, anarchy_79 said:

    I appreciate your well thought out and long answer, I got a lot out from it, thank you. Yeah I always forget to use grenades, and in either case everyone is so heavily shielded that they can't carry much of anything beyond their standard gear anyway. I prioritize TU always, I find that without everyone having good TU nothing really works. 

    The only point you make that I don't understand is #5, what is sell cost decline? Sales of what? The stuff I find on missions? 

    Oh, also, one thing I don't get about smoke grenades- if I throw it at an enemy and it hits them dead center, they are engulfed in smoke, and will suffer accuracy penalties or w/e. Question is, if I throw the grenade halfway between my squad and the enemy, does it work exactly the same, so that for instance one might smoke grenade oneself to make the squad harder to hit? 

    Also I'm having problems with assault on fixed positions, like the UFO, where I know there's aliens barricaded in there with overwatch and whatnot, and I lose at least one squad member per UFO breach no matter how I twist and turn it.

    Lastly, if you will, please give a brief overview of how to properly use explosives when breaching a building. What are those satchel charges that every soldier comes equipped with by default, how do you use them? For what?

    Again, thanks for taking the time! :)

    I think the satchel charges are actually borderline overpowered, and I guess it's interesting that their use isn't intuitive to an inexperienced player.

    They do damage to a target and can blow up the cover they are hiding behind, making them much easier to hit and finish off. They're also great for taking out a wall if you need to create line of fire to an enemy that's currently hidden, or just to make a hole in a wall to save TU so your soldiers don't have to walk a long way to get to a door or something. I think they can also take out the doors on a UFO, which can make attacking it easier.

  2. This is the fifth hotfix for V27 and should be the last. This update does not break save games.


    • Added artwork for the Quantum Teleportation and Mentarch Interrogation research projects.
    • Added updated research text for various research projects, including Alenium Explosives, UFO Hull Plating and Observer UFO.
    • Fixed a crash that occurs when you try to start an Alien Base mission.
    • Fixed most types of dead enemy units standing up in a T-pose if you loaded a save game.
    • Explosions that don't inflict damage (e.g. smoke grenades, flashbangs, etc) no longer destroy items on the ground.
    • Like 1
  3. On 6/3/2023 at 12:39 PM, CaptainSPrice said:

    Soldier won't do anykind reaction fire towards aliens or friendlies while being in berserk state. It's like when berserk status appear camera moves towards alien and reverse back towards soldier.


    after berserk state: 



    user_soldier_after_berserk_state-45.json 2.36 MB · 0 downloads user_soldier_before_berserk_state-46.json 2.36 MB · 0 downloads

    Thanks. Yeah, I can reproduce this. We'll take a look and get it fixed.

  4. 23 hours ago, CaptainSPrice said:

    Alien Plasma Cell visual/animation how is it look like:


    Now compere to Alien Small Plasma Cell in terms of visuals:


    It's like someone edited it in Paint and made that thing smaller - no idea how else to describe it. Be honest that visual looks poor.


    user_alien_small_plasma_cell_visualanimation_vs_alien_plasma_cell_bug_or_intended-54.json 2.93 MB · 0 downloads

    Yeah, that's the finished art. It meant to look like a smaller version of the larger clip. If you don't like it then that's fair enough, but it's not a bug :)

  5. On 6/3/2023 at 8:22 PM, CaptainSPrice said:

    Thanks. Yeah, this is a weird bug that has been around for a while but we've not yet been able to fix. 

    Sometimes certain objects that are normally destroyed correctly just don't get destroyed visually. But we don't know what caused it, or why. Do you remember what weapon hit it and what you were doing at the time?

  6. On 6/3/2023 at 12:14 AM, CaptainSPrice said:

    When i try move to build base between Russian and North US

    Russia Side:


    US side(construction new base right top screen selected):


    When i move map a little to the right side I can now see build base icon on US side:


    But now on russian side:


    Posting save below:

    user_select_base_building_on_map_bugged-40.json 705.74 kB · 0 downloads

    Thanks. Yeah, this is a known issue but hopefully we'll find time to fix it before Early Access!

  7. On 6/3/2023 at 7:25 PM, monopoly59 said:

    My Skyhawk got attacked by a fighter on the way back from a crash site mission and was shot down. Immediately after confirming the results, the game crashed.

    I have provided a save from when it was intercepted (48) and one from slightly before (47). The Log is the most recent one from when I loaded the crash save to check to see if it was the right one, so it should apply.

    auto_strategy_before_intercept-48.json 565.57 kB · 0 downloads output_log.txt 15.66 kB · 0 downloads auto_strategy_after_combat-47.json 561.58 kB · 0 downloads

    Thanks. Yeah, this is a bug I discovered myself when testing V27 on the Experimental branch so it should be fixed after the next update!

  8. @maxm222 Thanks for the feedback. I'm glad you've found V27.4 enjoyable - although something would have gone quite badly wrong if it wasn't the best version of the game so far! :)

    The civilian AI is still incredibly basic, as we've not done any work on AI for a couple of years now and it's something we're planning to address fully in Early Access. I'm certainly willing to change up terror missions a little so they have more of a timer, but it's something we need to consider carefully - I'm not sure whether players would like lots of missions having a timed element, rather than just some of them. XCOM2 certainly got a frosty reception when it tried that.

    As for the dialogue, yeah, again this is something I'm willing to listen to feedback on. But I think I'll need to get quite a lot of opinions on it before I start making any changes.

    The logic of the conversation is that both the Commander (you) and the Operations Director are stood around the command table in the command room of your base when this is happening, but I can see how some of the lines could be confusing if you didn't already know that. I guess the "Get in" line could be tweaked to say "Your soldiers need to get in" to make it more obvious what the setup is. Would that have made it less confusing for you?

  9. Hello everyone - May is now over so it's time for our monthly update to explain the progress we've made.

    Early Access Launch Date:
    The first thing to mention is we now have a date for our Early Access launch. I don't know exactly when it will be revealed because our marketing partners Hooded Horse are handling the announcement, but we're just focused on getting the game as good as possible for that date (which is really not that far away)!

    Please be aware that the Early Access version of the game is going to cut off after about 60-70% of the full campaign. This is still a big chunk of the game - depending on how quickly you play tactical missions, you could easily spend 10-15 hours playing a campaign before you hit that point. Ultimately we had to make a decision between spending our time working on polish and bugfixes that affect the whole game, or fixing various issues (and adding some missing content) that only relate to the final section of the game.

    In the end we thought people would prefer to play a 15+ hour chunk of Xenonauts 2 that would hopefully leave them impressed and keen to play the final game, rather than release the entire campaign in a less polished state that they might enjoy less. We will be adding back the removed content during Early Access, once we've had a chance to test it and polish it up to the standards of the rest of the game.

    Current Goals:
    Our current goal is to make sure the playable parts of the game are as enjoyable as possible. One important goal is to ensure all the research text and art in the playable sections is ready, so I've been working hard on that (along with a number of illustrators). We're also working on lots of bugfixes and usability improvements, and adding little quality-of-life features requested by the community - e.g. you can now rotate soldiers when arranging them inside the dropship on the strategy layer. If there's any time left over, we'll try and add some new maps too.

    We're not going to be making any further large changes to the game until after the Early Access launch, as we want to avoid introducing new bugs. It's always important to have the game as stable as possible on launch!

    Completed Work:
    Now I've discussed our future plans, I'll quickly summarise the work we did last month in the space I have left:

    • We released Closed Beta build V27 onto the Experimental branch, along with four hotfixes that fixed a LOT of bugs. We'll be hotfixing a few more issues this week and then hopefully releasing it on the Steam / GOG main branch.
    • More work on the translation.
    • As mentioned above, quite a lot of work on the research text / research artwork.
    • We did some more work on the new Geoscape icons.
    • We fixed the memory leaks in the game, which were causing performance issues and eventual crashes if you played the game for an extended session. This involved upgrading a copy of our codebase into the most recent version of Unity (as the version we're using is so old it doesn't have the tools required to easily find memory leaks), which is good news - after the Early Access launch, we'll probably upgrade the main project to this new version of Unity too. This should improve performance and compatibility, as well as making the lives of the developers easier.

    There's a few more smaller things we worked on that probably aren't worth talking about, as this post is already rather long. That's all I have for this month, so thanks for reading the post and I'll make another post once our release date is announced!

    • Like 1
  10. On 5/29/2023 at 4:45 PM, Sander Bouwhuis said:

    I can remember playing X1 many years ago and being excited that the gameplay resembled the original X-Com. Other X-Com clones had hateful things like enemies spawning in per group. Also, the newer clones removed strategy by only allowing 1 move and 1 action per turn. I was also excited to hear there was an X2 in the making, but that excitement has waned quite a bit over the years. I recently saw a Youtube video, and it looks like X2 is 90% the same as X1.

    Is there a specific reason why X2 is taking so long? Even longer than creating X1 from scratch?

    The main reason is that there's not much we can actually re-use from Xenonauts 1 in Xenonauts 2, other than ideas - and ideas aren't really the time consuming part of development. 

    What that means is that creating X2 from scratch takes longer than creating X1 from scratch, because it's a larger game overall as it contains every feature from the first game plus a bunch more stuff we've added, and because it's a higher quality product and it takes a lot more time to produce something that is higher quality than something that is medium quality.

    Also, we spent a good couple of years working on a vision of Xenonauts 2 that was quite different to the final form of the game (lots of it described on our Kickstarter page) that just turned out not to be much fun to play. So we either had the choice of putting out a bad game, or changing the design to something better and throwing away a load of work.

    It's a sequel in the style of a Civilization sequel - it's not a fundamentally different story or set of mechanics, it's the same basic formula with a bunch of upgrades. Evolution rather than revolution. You'll have to decide for yourself whether the game is enough of a change from X1 to be worth buying, but I personally think it's a big upgrade over X1 (although I own quite a few different Civilization games so maybe I'm biased).

    • Like 1
  11. On 5/25/2023 at 12:41 AM, CaptainSPrice said:

    Thanks. Yeah, something strange is happening here. It shouldn't be possible to gain more than +2 in an attribute per battle, so you're correct that something is going wrong here. I'll take a look.

    As for the slow stat gain, it's because of diminishing returns. You can only get 2000 points of progress in each stat per battle (no matter how long the battle is), and at the start of the game it is 1000 progress points to level up a stat. But after you have +5 in a stat, you need 1250 points to level up so you can't level up twice per mission (unless you have left over points from a previous mission).

    Once you have +15 in a stat, you then need 3000 points per level up so it's not even possible to level up purely based on a single mission (unless you have left over points from a previous mission). It goes all the way up to 5000 points per level above +30 in a stat. I might tweak the numbers to make this work a little better, but overall the mechanic seems to be working fine - it makes farming stats very difficult beyond a certain point, and your soldiers already have very high stats.

  12. On 5/24/2023 at 11:38 PM, CaptainSPrice said:

    Thanks. Does the crash always happen when you reload the smoke launcher then? I can't reproduce it from the save, and the logs don't contain any errors either - which is really strange.

    I'm wondering if this crash is actually from a memory leak, as that can cause the game to close unexpectedly. If so, this crash would be fixed in the next major update (but probably not hotfix).

  13. On 5/26/2023 at 10:15 AM, brualex said:

    It loads the tactical battle till ca. 90%, then it crashes to the desktop.

    Did try to assign less soldiers, but that didn't help.


    output.zip 80.67 kB · 0 downloads

    user_cr-76.zip 2.18 MB · 1 download


    On 5/27/2023 at 12:51 AM, DangerBoy said:

    exactly the same issue


    2023-05-26 16:49:11,644 [FATAL] (F:\Jenkins\workspace\X2 (Build)\release-0.78.x\Assets\Code\Screens\XenonautsMain.cs:938) 
    System.ArgumentNullException: Argument cannot be null.
    Parameter name: source
      at System.Linq.Check.Source (System.Object source) [0x00000] in <filename unknown>:0 
      at System.Linq.Enumerable.Any[Entity] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 
      at Xenonauts.GroundCombat.GroundCombatLogicSystem.<MoveCameraToCentreOnSelectedCombatantAndEquipWeapons>m__21 () [0x000a0] in F:\Jenkins\workspace\X2 (Build)\release-0.78.x\Assets\Code\Screens\GroundCombat\Systems\GroundCombatLogicSystem.cs:823 
      at Artitas.Components.PromiseEventExtensions+<AddPromise>c__AnonStorey0.<>m__1 () [0x00007] in F:\Jenkins\workspace\X2 (Build)\release-0.78.x\Assets\Code\Libraries\Artitas\Artitas.Core\Code\Systems\DelayedTaskSystem.cs:84 
      at RSG.Promise+<>c__DisplayClass53_0.<Then>b__0 () [0x00000] in <filename unknown>:0 
      at RSG.Promise.InvokeResolveHandler (System.Action callback, IRejectable rejectable) [0x00000] in <filename unknown>:0 

    2023-05-26 16:49:11,649 [FATAL] (F:\Jenkins\workspace\X2 (Build)\release-0.78.x\Assets\Code\Screens\XenonautsMain.cs:720) 
    Exception in Unity lifecycle, marked as handled: ArgumentNullException: [INITIAL CRASH] - Argument cannot be null.
    Parameter name: source
    Parameter name: source 
     System.Linq.Check.Source (System.Object source)
    System.Linq.Enumerable.Any[Entity] (IEnumerable`1 source)
    Xenonauts.GroundCombat.GroundCombatLogicSystem.<MoveCameraToCentreOnSelectedCombatantAndEquipWeapons>m__21 () (at F:/Jenkins/workspace/X2 (Build)/release-0.78.x/Assets/Code/Screens/GroundCombat/Systems/GroundCombatLogicSystem.cs:823)
    Artitas.Components.PromiseEventExtensions+<AddPromise>c__AnonStorey0.<>m__1 () (at F:/Jenkins/workspace/X2 (Build)/release-0.78.x/Assets/Code/Libraries/Artitas/Artitas.Core/Code/Systems/DelayedTaskSystem.cs:84)
    RSG.Promise+<>c__DisplayClass53_0.<Then>b__0 ()
    RSG.Promise.InvokeResolveHandler (System.Action callback, IRejectable rejectable)
    Common.Logging.UnityLogAppender:Append(LoggingEvent) (at F:/Jenkins/workspace/X2 (Build)/release-0.78.x/Assets/Code/Libraries/Common/Code/Debug/Logging/UnityLogAppender.cs:43)
    log4net.Appender.AppenderSkeleton:DoAppend(LoggingEvent) (at c:/log4net/tags/1.2.15RC1/src/Appender/AppenderSkeleton.cs:317)
    log4net.Util.AppenderAttachedImpl:AppendLoopOnAppenders(LoggingEvent) (at c:/log4net/tags/1.2.15RC1/src/Util/AppenderAttachedImpl.cs:92)
    log4net.Repository.Hierarchy.Logger:CallAppenders(LoggingEvent) (at c:/log4net/tags/1.2.15RC1/src/Repository/Hierarchy/Logger.cs:576)
    log4net.Repository.Hierarchy.Logger:ForcedLog(Type, Level, Object, Exception) (at c:/log4net/tags/1.2.15RC1/src/Repository/Hierarchy/Logger.cs:688)
    log4net.Repository.Hierarchy.Logger:Log(Type, Level, Object, Exception) (at c:/log4net/tags/1.2.15RC1/src/Repository/Hierarchy/Logger.cs:428)
    log4net.Core.LogImpl:Fatal(Object, Exception) (at c:/log4net/tags/1.2.15RC1/src/Core/LogImpl.cs:983)
    Xenonauts.XenonautsMain:OnApplicationQuit() (at F:/Jenkins/workspace/X2 (Build)/release-0.78.x/Assets/Code/Screens/XenonautsMain.cs:938)


    On 5/29/2023 at 1:54 PM, Alienkiller said:

    Yeah, I can announce that. Have the same CTD.

    Thanks. Yeah, I can reproduce this - we'll get it fixed and put out a hotfix.

    • Like 1
  14. 16 hours ago, CaptainSPrice said:

    Overweighted character before medkit removal - look numbers 117/101


    After medkit removed from inventory into ground - numbers still 117/101


    When i remove different item: 


    user_overweight_soldier_medkit_removal_numbers_bug-31.json 2.17 MB · 0 downloads

    Thanks. That's weird, I can't reproduce this in the save game. If I try recreating the loadout in your screenshot then drop the medikit, it works fine.

    If you're able to reproduce the bug again please let me know and I'll take another look.

  15. 16 hours ago, CaptainSPrice said:

    I am using 3 exploits that help me at the moment identify issues in the game. I was using them since Patch 16

    1. Bravery boost exploit/abuse

    2. Ground attack 0% hit exploit/abuse

    3. Character rotation time units exploit/abuse

    What you think guys?

    Hey - yeah, it's good to post them. Can you just post a thread on the General forums though about exploits? It's not technically a bug so we shouldn't post it here.

    I'll give it a read and consider what fixes we might need to make.

  • Create New...