4024 replies to this topic

[faffler]

In response to post #61587892. #61591282, #61591372, #61592347, #61593527 are all replies on the same post.

Spoiler

faffler wrote: I've noticed that pods on UFO missions (crashed or landed) no longer start patrolling towards XCOM after you activate the command pod. This is really noticeable on the bigger UFO maps where pods will remain completely static in some corner of the map until you walk up to them.

Was this behavior something that ended up getting axed as a result of all the pod activation changes?

szmind wrote: That might be related to my "prevent double move" fix. I worried it could stop aliens patrolling. I am curious if aliens patrol AT ALL in last versions of Rebalance. If they do - the issue is not related to my fix then. On the other hand I think that "hunting last lurker" was always an issue on larger maps - wasn't it?

faffler wrote: I'll try to pay close attention to alien pod behavior as I play more. I only slowly noticed that this was happening as I played my most recent campaign. Pods do seem to be very static right now on UFO missions at least.

Hunting the last pod down could be an issue on some of the big maps, but it was definitely a lot faster in LW 1.0 when the command pod was dead. On one landed abductor in Rebalance v1.18.9 I had two unactivated pods that sat indefinitely at the far edge of the map after every other alien was dead.

faffler wrote: I messed around a bit on a landed raider. I passed ~20 turns without any of the pods (3 left at the time) moving at all. I then activated one pod and ran away to the other side of the map. Hunt mode didn't activate at all, the other 2 unactivated pods remained static.

Here is a save from the mission: https://drive.google.com/open?id=1xbKlzz9_fCxNdSMakousV3f0THHXjd3i

szmind wrote: So - I think it is my debugger's fault (hmm, in that case 'bugger' would be more suitable :) ). 80% sure it does prevent pods from moving. I have implemented a fix. Try it out with your save. I have currently pure LW installed cause I am working with AzXeus on larger project to get rid of pseudo code at all :)

Fix is here - just overwrite the LWDebugger.u in CookedPCConsole with this one. Pods should get moving with "double move" still prevented.
https://drive.google.com/file/d/1qRXQQsa1t8fD8PEdH_T9Ie-fGKfpNeX2/view

Awesome, updating that file immediately got pods patrolling again. Thanks for the quick fix!

[zazuza7]

In response to post #61578352. #61584092, #61594237, #61601762 are all replies on the same post.

Spoiler

zazuza7 wrote: Reconnaissance ability description in-game is wrong. It states that it gives 2 battle scanners while it actually gives 3.

With save scum off after Reloading a save once I got a different outcome of my shot(a miss instead of a hit) and then it didn't change anymore.
I think it is 2nd time I experienced this. I'm pretty confident that moving and shooting with my soldier was my first action of the turn. Any thoughts on what I could've messed up or is that a bug?

Ucross wrote: Thanks for the report on Reconnaissance - it's fixed in the next version.

Save scum is pretty deep coding that I can't really touch so unfortunately I don't know much about why it wouldn't act as intended.

zazuza7 wrote: I'm not sure if you understood what I meant so I'll try to write more clearly.
With save scum OFF I rarely get different outcomes(I think I should always get the same outcome) out of my shots(while I believe my action order is the same).

bturner1 wrote: This, unfortunately, is how it has always behaved for me. If you reload, the first result is different but then subsequent reloads match. It's definitely not a Rebalance bug. I should add that I don't reload like this very often (only after the game does something buggy or I misclick). My theory is that, in certain conditions, there is something about the in-memory game state that doesn't get saved correctly (or, more likely, the game state is incorrect in some way but gets corrected during the save). Therefore, the reloads gives a slightly different, albeit consistent, game state. It may only happen like this in certain buggy situations. For example, I remember trying to get a save to demonstrating strange behavior with teleporting pods, but the pods would always behave differently after the first reload (but consistently with subsequent reloads).

It seems that my problem is the same of bturner1.
I also noticed that autosave doesn't always make a save at the beggining of the turn, not sure what causes that.

[Ucross]

In response to post #61587892. #61591282, #61591372, #61592347, #61593527, #61605107 are all replies on the same post.

Spoiler

faffler wrote: I've noticed that pods on UFO missions (crashed or landed) no longer start patrolling towards XCOM after you activate the command pod. This is really noticeable on the bigger UFO maps where pods will remain completely static in some corner of the map until you walk up to them.

Was this behavior something that ended up getting axed as a result of all the pod activation changes?

szmind wrote: That might be related to my "prevent double move" fix. I worried it could stop aliens patrolling. I am curious if aliens patrol AT ALL in last versions of Rebalance. If they do - the issue is not related to my fix then. On the other hand I think that "hunting last lurker" was always an issue on larger maps - wasn't it?

faffler wrote: I'll try to pay close attention to alien pod behavior as I play more. I only slowly noticed that this was happening as I played my most recent campaign. Pods do seem to be very static right now on UFO missions at least.

Hunting the last pod down could be an issue on some of the big maps, but it was definitely a lot faster in LW 1.0 when the command pod was dead. On one landed abductor in Rebalance v1.18.9 I had two unactivated pods that sat indefinitely at the far edge of the map after every other alien was dead.

faffler wrote: I messed around a bit on a landed raider. I passed ~20 turns without any of the pods (3 left at the time) moving at all. I then activated one pod and ran away to the other side of the map. Hunt mode didn't activate at all, the other 2 unactivated pods remained static.

Here is a save from the mission: https://drive.google.com/open?id=1xbKlzz9_fCxNdSMakousV3f0THHXjd3i

szmind wrote: So - I think it is my debugger's fault (hmm, in that case 'bugger' would be more suitable :) ). 80% sure it does prevent pods from moving. I have implemented a fix. Try it out with your save. I have currently pure LW installed cause I am working with AzXeus on larger project to get rid of pseudo code at all :)

Fix is here - just overwrite the LWDebugger.u in CookedPCConsole with this one. Pods should get moving with "double move" still prevented.
https://drive.google.com/file/d/1qRXQQsa1t8fD8PEdH_T9Ie-fGKfpNeX2/view

faffler wrote: Awesome, updating that file immediately got pods patrolling again. Thanks for the quick fix!

Thanks sz. Added to next version as a bug fix.

[Lafiir]

Download in folder Config contains "CampaignSummary.txt" which is unnecessary and should be deleted.

DefaultGameCore.ini
391: "BalanceMods_Normal=(eType=eChar_Outsider, iCritHit=900 ..." is duplicated (should be iCritHit=1200)

XComGame.int
2673: Alloy SHIV "hard cover" should be "partial cover"
3465: m_strBonusTxt[ePerk_ReaperRounds] should mention it only affects beam and pulse
5899: m_aInventorySummary[eItemInfo_ChitinPlating] should be +2 hit points
5901: m_aInventorySummary[eItemInfo_ReaperRounds] see above
5913: m_aInventorySummary[16] Plasma Stellerator gives +2 damage
5922: m_aInventorySummary[25] should be +5 (for KSM)
5933: m_aInventorySummary[36] should be +5 (for Flamethrower)

Nexus Description Page:
"SHIV autocannon ammo reduced to 2 (from 3)" to "Reduce early game strength". Either remove it, or revert autocannons and MEC minigun back to 2 ammo if that's still relevant.
Not a bug, but maybe put the "INT" folder in Download in a "Localization" sub-folder. This way all can be copied to "XCom-Enemy-Unknown\XEW\XComGame"; combining steps 2-4 for a simpler installation.

Edited by Lafiir, 07 July 2018 - 01:50 AM.

[Ucross]

In response to post #61613267.

Spoiler

Lafiir wrote: Download in folder Config contains "CampaignSummary.txt" which is unnecessary and should be deleted.

DefaultGameCore.ini
391: "BalanceMods_Normal=(eType=eChar_Outsider, iCritHit=900 ..." is duplicated (should be iCritHit=1200)

XComGame.int
2673: Alloy SHIV "hard cover" should be "partial cover"
3465: m_strBonusTxt[ePerk_ReaperRounds] should mention it only affects beam and pulse
5899: m_aInventorySummary[eItemInfo_ChitinPlating] should be +2 hit points
5901: m_aInventorySummary[eItemInfo_ReaperRounds] see above
5913: m_aInventorySummary[16] Plasma Stellerator gives +2 damage
5922: m_aInventorySummary[25] should be +5 (for KSM)
5933: m_aInventorySummary[36] should be +5 (for Flamethrower)

Nexus Description Page:
"SHIV autocannon ammo reduced to 2 (from 3)" to "Reduce early game strength". Either remove it, or revert autocannons and MEC minigun back to 2 ammo if that's still relevant.
Not a bug, but maybe put the "INT" folder in Download in a "Localization" sub-folder. This way all can be copied to "XCom-Enemy-Unknown\XEW\XComGame"; combining steps 2-4 for a simpler installation.

Awesome stuff. Did it all. Thanks so much.

[szmind]

In response to post #61578352. #61584092, #61594237, #61601762, #61607267 are all replies on the same post.

Spoiler

zazuza7 wrote: Reconnaissance ability description in-game is wrong. It states that it gives 2 battle scanners while it actually gives 3.

With save scum off after Reloading a save once I got a different outcome of my shot(a miss instead of a hit) and then it didn't change anymore.
I think it is 2nd time I experienced this. I'm pretty confident that moving and shooting with my soldier was my first action of the turn. Any thoughts on what I could've messed up or is that a bug?

Ucross wrote: Thanks for the report on Reconnaissance - it's fixed in the next version.

Save scum is pretty deep coding that I can't really touch so unfortunately I don't know much about why it wouldn't act as intended.

zazuza7 wrote: I'm not sure if you understood what I meant so I'll try to write more clearly.
With save scum OFF I rarely get different outcomes(I think I should always get the same outcome) out of my shots(while I believe my action order is the same).

bturner1 wrote: This, unfortunately, is how it has always behaved for me. If you reload, the first result is different but then subsequent reloads match. It's definitely not a Rebalance bug. I should add that I don't reload like this very often (only after the game does something buggy or I misclick). My theory is that, in certain conditions, there is something about the in-memory game state that doesn't get saved correctly (or, more likely, the game state is incorrect in some way but gets corrected during the save). Therefore, the reloads gives a slightly different, albeit consistent, game state. It may only happen like this in certain buggy situations. For example, I remember trying to get a save to demonstrating strange behavior with teleporting pods, but the pods would always behave differently after the first reload (but consistently with subsequent reloads).

zazuza7 wrote: It seems that my problem is the same of bturner1.
I also noticed that autosave doesn't always make a save at the beggining of the turn, not sure what causes that.

Hey guys. Concernig that "first reload" issue. Does that occur with EVERY first reload on a mission? I suspect it is not. It is probably "first reload" after updating to new version of Rebalance. Cause your save from older version has random seed generated by older version. When you reload for the first time - the game makes a check and discovers that "sth changed" and proceeds with debug procedure which regenerates random seed. From now on the save holds random seed from "current version".

Also - if you load a downloaded save you will probably get different result than a player who actually uploaded the save :))

And autosave - it has always been skipping a turn from time to time, in vanilla, Long War, ever. As far as I remmember. Kind of - "Save Scum Preventer Lite".

Edited by szmind, 07 July 2018 - 10:20 AM.

[zazuza7]

In response to post #61578352. #61584092, #61594237, #61601762, #61607267, #61622242 are all replies on the same post.

Spoiler

zazuza7 wrote: Reconnaissance ability description in-game is wrong. It states that it gives 2 battle scanners while it actually gives 3.

With save scum off after Reloading a save once I got a different outcome of my shot(a miss instead of a hit) and then it didn't change anymore.
I think it is 2nd time I experienced this. I'm pretty confident that moving and shooting with my soldier was my first action of the turn. Any thoughts on what I could've messed up or is that a bug?

Ucross wrote: Thanks for the report on Reconnaissance - it's fixed in the next version.

Save scum is pretty deep coding that I can't really touch so unfortunately I don't know much about why it wouldn't act as intended.

zazuza7 wrote: I'm not sure if you understood what I meant so I'll try to write more clearly.
With save scum OFF I rarely get different outcomes(I think I should always get the same outcome) out of my shots(while I believe my action order is the same).

bturner1 wrote: This, unfortunately, is how it has always behaved for me. If you reload, the first result is different but then subsequent reloads match. It's definitely not a Rebalance bug. I should add that I don't reload like this very often (only after the game does something buggy or I misclick). My theory is that, in certain conditions, there is something about the in-memory game state that doesn't get saved correctly (or, more likely, the game state is incorrect in some way but gets corrected during the save). Therefore, the reloads gives a slightly different, albeit consistent, game state. It may only happen like this in certain buggy situations. For example, I remember trying to get a save to demonstrating strange behavior with teleporting pods, but the pods would always behave differently after the first reload (but consistently with subsequent reloads).

zazuza7 wrote: It seems that my problem is the same of bturner1.
I also noticed that autosave doesn't always make a save at the beggining of the turn, not sure what causes that.

szmind wrote: Hey guys. Concernig that "first reload" issue. Does that occur with EVERY first reload on a mission? I suspect it is not. It is probably "first reload" after updating to new version of Rebalance. Cause your save from older version has random seed generated by older version. When you reload for the first time - the game makes a check and discovers that "sth changed" and proceeds with debug procedure which regenerates random seed. From now on the save holds random seed from "current version".

Also - if you load a downloaded save you will probably get different result than a player who actually uploaded the save :))

And autosave - it has always been skipping a turn from time to time, in vanilla, Long War, ever. As far as I remmember. Kind of - "Save Scum Preventer Lite".

Hello, szmind. I think the issue is happening each time I first try to reload (probably)every turn. And it was happening to me on a campaign which I started after Installing 1.18.9 and I didn't have it updated to a new version of rebalance yet.

[bturner1]

In response to post #61578352. #61584092, #61594237, #61601762, #61607267, #61622242, #61623192 are all replies on the same post.

Spoiler

zazuza7 wrote: Reconnaissance ability description in-game is wrong. It states that it gives 2 battle scanners while it actually gives 3.

With save scum off after Reloading a save once I got a different outcome of my shot(a miss instead of a hit) and then it didn't change anymore.
I think it is 2nd time I experienced this. I'm pretty confident that moving and shooting with my soldier was my first action of the turn. Any thoughts on what I could've messed up or is that a bug?

Ucross wrote: Thanks for the report on Reconnaissance - it's fixed in the next version.

Save scum is pretty deep coding that I can't really touch so unfortunately I don't know much about why it wouldn't act as intended.

zazuza7 wrote: I'm not sure if you understood what I meant so I'll try to write more clearly.
With save scum OFF I rarely get different outcomes(I think I should always get the same outcome) out of my shots(while I believe my action order is the same).

bturner1 wrote: This, unfortunately, is how it has always behaved for me. If you reload, the first result is different but then subsequent reloads match. It's definitely not a Rebalance bug. I should add that I don't reload like this very often (only after the game does something buggy or I misclick). My theory is that, in certain conditions, there is something about the in-memory game state that doesn't get saved correctly (or, more likely, the game state is incorrect in some way but gets corrected during the save). Therefore, the reloads gives a slightly different, albeit consistent, game state. It may only happen like this in certain buggy situations. For example, I remember trying to get a save to demonstrating strange behavior with teleporting pods, but the pods would always behave differently after the first reload (but consistently with subsequent reloads).

zazuza7 wrote: It seems that my problem is the same of bturner1.
I also noticed that autosave doesn't always make a save at the beggining of the turn, not sure what causes that.

szmind wrote: Hey guys. Concernig that "first reload" issue. Does that occur with EVERY first reload on a mission? I suspect it is not. It is probably "first reload" after updating to new version of Rebalance. Cause your save from older version has random seed generated by older version. When you reload for the first time - the game makes a check and discovers that "sth changed" and proceeds with debug procedure which regenerates random seed. From now on the save holds random seed from "current version".

Also - if you load a downloaded save you will probably get different result than a player who actually uploaded the save :))

And autosave - it has always been skipping a turn from time to time, in vanilla, Long War, ever. As far as I remmember. Kind of - "Save Scum Preventer Lite".

zazuza7 wrote: Hello, szmind. I think the issue is happening each time I first try to reload (probably)every turn. And it was happening to me on a campaign which I started after Installing 1.18.9 and I didn't have it updated to a new version of rebalance yet.

Pretty sure it happens every time...

Just did a test. Loaded a previous in-mission save. Moved a soldier to activate a pod. Made a new save.

Moved a soldier to a notable location. Took a 44% shot with shotgun. Hit and dead. [Moved a different soldier to a notable location. Took a 30 something percent shot and missed.]

Reloaded game. Moved same soldier to first notable location. Took same 44% shot with shotgun. Missed.

Reloaded game and repeated, three more times - all misses.

Save Scum is off. Entire game was played with 1.18.10. It's always been like this for me. I just assumed it was like this for other people as well.

Edited by bturner1, 07 July 2018 - 02:59 PM.

[szmind]

In response to post #61578352. #61584092, #61594237, #61601762, #61607267, #61622242, #61623192, #61627677 are all replies on the same post.

Spoiler

zazuza7 wrote: Reconnaissance ability description in-game is wrong. It states that it gives 2 battle scanners while it actually gives 3.

With save scum off after Reloading a save once I got a different outcome of my shot(a miss instead of a hit) and then it didn't change anymore.
I think it is 2nd time I experienced this. I'm pretty confident that moving and shooting with my soldier was my first action of the turn. Any thoughts on what I could've messed up or is that a bug?

Ucross wrote: Thanks for the report on Reconnaissance - it's fixed in the next version.

Save scum is pretty deep coding that I can't really touch so unfortunately I don't know much about why it wouldn't act as intended.

zazuza7 wrote: I'm not sure if you understood what I meant so I'll try to write more clearly.
With save scum OFF I rarely get different outcomes(I think I should always get the same outcome) out of my shots(while I believe my action order is the same).

bturner1 wrote: This, unfortunately, is how it has always behaved for me. If you reload, the first result is different but then subsequent reloads match. It's definitely not a Rebalance bug. I should add that I don't reload like this very often (only after the game does something buggy or I misclick). My theory is that, in certain conditions, there is something about the in-memory game state that doesn't get saved correctly (or, more likely, the game state is incorrect in some way but gets corrected during the save). Therefore, the reloads gives a slightly different, albeit consistent, game state. It may only happen like this in certain buggy situations. For example, I remember trying to get a save to demonstrating strange behavior with teleporting pods, but the pods would always behave differently after the first reload (but consistently with subsequent reloads).

zazuza7 wrote: It seems that my problem is the same of bturner1.
I also noticed that autosave doesn't always make a save at the beggining of the turn, not sure what causes that.

szmind wrote: Hey guys. Concernig that "first reload" issue. Does that occur with EVERY first reload on a mission? I suspect it is not. It is probably "first reload" after updating to new version of Rebalance. Cause your save from older version has random seed generated by older version. When you reload for the first time - the game makes a check and discovers that "sth changed" and proceeds with debug procedure which regenerates random seed. From now on the save holds random seed from "current version".

Also - if you load a downloaded save you will probably get different result than a player who actually uploaded the save :))

And autosave - it has always been skipping a turn from time to time, in vanilla, Long War, ever. As far as I remmember. Kind of - "Save Scum Preventer Lite".

zazuza7 wrote: Hello, szmind. I think the issue is happening each time I first try to reload (probably)every turn. And it was happening to me on a campaign which I started after Installing 1.18.9 and I didn't have it updated to a new version of rebalance yet.

bturner1 wrote: Pretty sure it happens every time...

Just did a test. Loaded a previous in-mission save. Moved a soldier to activate a pod. Made a new save.

Moved a soldier to a notable location. Took a 44% shot with shotgun. Hit and dead. [Moved a different soldier to a notable location. Took a 30 something percent shot and missed.]

Reloaded game. Moved same soldier to first notable location. Took same 44% shot with shotgun. Missed.

Reloaded game and repeated, three more times - all misses.

Save Scum is off. Entire game was played with 1.18.10. It's always been like this for me. I just assumed it was like this for other people as well.

Interesting. If you are determined - you can check kind of ID of random seed within a log file. It is located by default in C:\Users\[UserName]\Documents\My Games\XCOM - Enemy Within\XComGame\Logs. Sort it by time to get the latest on top (the very last is just Launch.log). Search for "SetRandomSeeds".

[faffler]

EXALT Heavy mobility is currently lower than intended. I'm speculating that this is because of the SAW/launcher penalties being applied to them.

https://imgur.com/a/i1geFaR

DGC.ini
40 Mobility=12
44 Mobility=13

^brings heavy mobility up to what I assume is intended (I tested this in game, regular/elite appear to receive -3/-4 mobility respectively)

I would encourage buffing their mobility to something higher like 11, as AI 'cover units' seem to struggle with moving around the map when their mobility is too low. At 8/9 mobility heavies frequently end up standing out of cover, or are unwilling to move forward.

edit: looking at the screenshots I'm noticing elite heavies have lower aim than regular ones. It seems like regulars get a SAW and elites get a LMG, so you might want to buff elite heavy aim by 10 to account for this.

Edited by faffler, 08 July 2018 - 11:25 AM.