makes absolutly no sense

Does this fix the issue that you can sometimes run into where an enemy you can target is no longer visible anymore once you blow up the cover he was hiding behind? If anything, shouldn't it be the other way around? I run into this the most often with squadsight where my snipers have a shot on an enemy that is in either half cover or full cover, so I grenade them to blow up that cover and give my sniper a better shot and now I can't see them at all. WTF?

@RealityMachina Official ruling: WOTC compatible? (Sorry to pester you across multiple comment sections, but your mods are the shit and I want every single one I can possibly use.)

This works for WOTC I take it?

So is this already included in LW2, since you mentioned them?

It gets really irritating that not only does Advent do it, but your soldiers love shooting through solid walls. I don't know if it's just an engine limitation or lazy coding by Firaxis, but I seriously wonder why even put walls in the game at all if you can just shoot through all of them. And not just shoot, but SEE through them, too. I've had all sorts of wacky situations where there is absolutely ZERO chance I should be able to see an alien, but there he is. And then he takes a shot at me through the corner he's standing in, hitting my soldier on the other side of a solid wall.

Im a little puzzled why multicore map generation would cause this problem :O

love it, still am working <3

I had an advent MEC unit jump onto the roof of the building I was in...and then shoot through it grenade launchering 2 of my squad to vahalla, and seriously injuring another who died shortly after....Hopefully this fixes that bullshit...no damage to the roof by the way...

It is hard to notice sometimes. maybe 1/20 shots fired do I actually see something strange. It's just that this time it was very noticeable. I guess I can just ignore it and enjoy the game for now.

@Morcaster:
Is that a visualisation / animation bug or a genuine line-of-sight gameplay bug?

And I don't know what else to do, Morcaster. I very, very really get the bug and I don't use this .ini tweak.

My dude shot though a 10 foot concrete wall and still killed some dude like 40 feet away from the wall. I really want to fix this.

@Dragon32 what if EnableThreadedWorldDataBuild is already true and you're still getting silly lines?

Not included in WoTC but this mod should work fine with WoTC:
Steam\SteamApps\common\XCOM 2\XCom2-WarOfTheChosen\XComGame\Config\DefaultGameCore.ini

[XComGame.XComWorldData]
EnableThreadedWorldDataBuild=true

This is a pretty simple mod: one line of code, as you can see in the title graphic. It just disables the utilization of multiple cores when the map is generated. It may not need an update for WotC, but I'm no expert. It may even be encorporated into it.

WOTC version?

Anyone tested this with WotC yet? Because as good as vanilla xcom 2 is, it was a MAJOR step backwards from xcom 1 in terms of common sense lines of sight.

I might try this. I was two missions into LW2 when a whole mess of wierd LOS absurdity happened. One agent was able to target through ceiling and wall at an angle but an enemy hidding behind 1/2 cover along the side of the same building's face was invisible to the rest of the squad on the ground around them.

my game worked perfect before, then i got long war and suddenly enemies shoot through walls and cover..... so yea.... game was perfect with line of sight before until long war "fixed" it lol

@Lux Manifestus:
Compare date of last XCOM 2 patch (November 2016) against date this mod was released (January 2017). No.

Has this been patched out yet?

Ok thanks!

It's been on in LW since 1.0, so at this point if it hasn't done anything for you, it won't do anything in the future.

Was this fixed with 1.3??

@=[NK]= Col. Jack O'Neil:
Seem to remember zdiff =3 is equal to a builiding floor in elevation, anything less than that is like the soldier's standing on a bench or something.

You can actually add in zdiff 2.. I've changed the values so zdiff 1, 2 and 3 give 5, 10 and 15 aim/ def respectively :)

@ZotaOTT[RU]:
Get -bg-'s "Enemy Unknown Aim Rolls". Read the Description, and then look at:
Config\XComAimRoll.ini

Configure for LW2

And then tweak this line:
+HEIGHT_MODIFIER=(ZDiff=3, OffenseBonus=20, DefenseBonus=0) ; LW2: Set OffenseBonus to 10

As an option I propose) to reduce accuracy when shooting from the ground and increase the protection of the ceiling) How to do this?

@ZotaOTT[RU]
This simply changes a single INI value from true to false. Really can't see this breaking LW2. Particularly as:
NOTE: Long War 2 has this change by default

LW2 does not work

Well, sometimes they have a line you can't see, but it sounds funky.

I have the mod enabled and still my soldier (who was tucked in a room deep in a building with no vision on any aliens) got shot through not one, but two full, high cover walls with a prisoner cell inbetween and killed in the process... Well played Advent, well played.

I don't really think the game has issues with multi-threading, any more than most other games do, but I'm not sure. It's just a rough game system-wise.

Thats certainly an intersting cause for this problem. I really hope firaxis fixes thissince the multithreading makes the load times so much faster.

I have an SSD and it still takes minutes to load. (An NVME SSD running Windows 10, even). Sometimes it just depends. LW2 definately takes longer to load than Vanilla XC2.

This tweak doesn't seem to work fully, because I've seen some people still have aliens seeing through walls and closed doors.

It's funny but for me this change reduce a lot the loading time, now it only takes a few seconds (I have SSD), before it could take near a minute.

I can confirm that the tweak is in. Source: LW2's incluided XComGameCore.ini (It's at the very bottom)

Definitely the source of the super long load times of LW2.

Well, then try adding the mod? JohnnyLump's comment on the Pavonis forums sort of implied it was, that's all I was going by.

Peerles Girl i can confirm that it's not in LW2 at all...i got fucked up by getting shot through ceillings and walls multiple times

I have to give this a try now, that is one of the most simply frustrating things I have come across thus far in the game.

I would ASSUME the mod works with LW2, but it may already be part of LW2, though I don't imagine installing it would hurt anything. This was posted over on Pavonis Interactive's LW2 forums: http://www.pavonisinteractive.com/phpBB3/viewtopic.php?f=15&t=23380

Does this work with LW2?

THAKNYOUTHANKYOUTHANKYOUTHANKYOUTHAKNYKYRBAKJESFOIEFJF GHJHJ,Mio> opmi?po? ?.L./op@{po~['-0['-



Thanks.

@Draconis Aetherius Xan Di
The setting's value is the same as it's always been. The ability to change the setting value via INI was added in patch 7. As I understand it.

Also. Yay! More dragon avatars.

Hang on, this setting was added in patch 7, the most recent one, right? I've been having this glitch since I started playing the game, and I preordered it. I have 175+ hours clocked on it. Admittedly, I don't know much about programming or modding, can anyone explain this to me? This couldn't be the real problem if I experienced it before patch 7 right? Or did the patch only enable an option and the actual function was always being carried out?

@Galdis:
Way I read it is that the INI option was added in the November 2016 patch (patch #7, the most recent one) but its value was set to True.
There hasn't been an official patch since so, without this mod it'll still be set to True.
You can check your own value in your Documents folder's GameCore.ini

@kylehayman361:
If by "they" you mean Firaxis rather than some shadowy Illuminati group then let me counter that with a question: Has your game been updated since the patch which added this INI line?

they set it to false yet?

Either way it will set that line of code to false.
Also for those worried about performance issues I play it on my laptop and havent noticed any significantly longer load times, but it already took about 30 seconds to a minute to load.

@RealityMachina Can you or anyone else confirm if the newest patch actually fixed this? OP is obviously a saint for making the mod but I don't want to subscribe and cause some conflict with the recent patch.