one of my gunners has 0 view range

[MajorFreak]

playing latest LW, although modded from midcampaign

 

mods (using mod manager)

Additional Species by amaciel81

Alien Stats Exposed by amaciel81

Campaign Summary by tracktwo

Enhanced Tactical Info by spazmojones

Show Country Name by spazmojones

UFO interception tweak by spazmojones

 

mods (manually installed into mod manager's game subdirectory)

engine.upk

Mesh's LW Tweaks by Mesh2007

 

==========

 

the gunner in question has items that differ from the gunner squadmate (without the LOS issue): Targeting Module vs Armor Piercing Ammo (both have alloy jacketed rounds for the LMG)

the gunner in question is two ranks below the other, but same perk choices

 

***

 

A reload fixed the problem, yet anyone else noticed this bug?

[dubiousintent]

Very odd. Given a reload fixed the issue, it's most likely just a "glitch". (That is: something caused a bit or two to flip in memory. Not enough to crash the game, but enough to cause "weird things". Might be an indicator of overheating or failing memory, might be a power dip/surge, might be cosmic rays, "might be ..." etc. Common explanation is "gremlins" :tongue: .) Annoying but not much anyone can do if it can't be replicated. (I realize that is what you are asking: "has any one else had the issue?" The above is for novice lurkers. Read on, please.)

 

Standard boilerplate response follows:

 

Long War bug reports should be posted in the appropriate Beta Feedback thread in the "Long War" download page "forum section" for a quick response. (The LW Team has stated they don't check the main forum at all anymore for problems. Really, the dev team is the most likely to be able to help with a LW issue but anyone else who can also will be there.) You may also find that the answer is already known and posted in that section.

 

Be sure to read the "Readme" and "Detailed Troubleshooting" documents included with the LW download before reporting bugs. They need all the information requested there (including which OS platform: Windows, Linux, OS/X, ARM/IOS, etc.) to be able to help. If they can't reproduce the problem, they can't fix it. You increase your odds of getting help by re-reading included documentation and following instructions on reporting bugs, and then documenting what you have already tried ... in detail. Short "it's broke" reports simply generate requests for more detail; wasting time. Better too much detail than not enough.

-Dubious-

Edited October 17, 2015 by dubiousintent