Logo Platform
logo amplifiers simplified

[Bug] Gjallarfire Weapons Module shows with 0% efficiency on short range

Copied to clipboard!
8 years ago
May 23, 2017, 1:36:03 PM

Summary / Title

Gjallarfire Weapons Module (UE quest Laser) shows the wrong efficiency on short range. 


Description

If you equip a ship with the module the tooltip for the module says:


Range Effectiveness: 

Long 100%, Medium 100%, Short 80%


But the Weaponstats show:

Long 100%, Medium 100%, Short 0%

(29 dps, 29 dps, 23 dps)


Steps to Reproduce

1. equip a ship with the modul in the ship design editor


Reproducibility

5/5


Expected Behavior

Range efficiency shows 80% for short range


Version

1.0.3 Preview


Notes

Also shows the wrong range in the Battlescreen/Fleet when you mouse over the ship for a tooltip


Attachments




edit: swapped screenshot for one that shows detailed stats with dps^^

Updated 8 years ago.
0Send private message
0Send private message
8 years ago
May 23, 2017, 5:17:05 PM

Updated to the 1.04 Preview and this bug still existed, so did a bit of digging in the xml configuration files and identified a fix for this.


In your SteamApps/common/EndlessSpace2/Public folder search for the file ModuleDefinitions[Quest].xml and open in a text editor.


The module reward is referenced in relation to the quest, search the text file for ModuleWeaponLaserQuestUE03.  


Around line 125 there are entries for the range penalties, in my file only the Long and Medium range entries were present: 


<AvailableRange RangeName="Long" PenaltyPropertyName="LongRangePenalty"/>
<AvailableRange RangeName="Medium" PenaltyPropertyName="MediumRangePenalty"/>


I added the following line directly beneath these two lines:


<AvailableRange RangeName="Short" PenaltyPropertyName="ShortRangePenalty"/>


And volia, short range laser damage fixed and comes up as expected at 80%.


HTH.


Edit: Found the advanced battle screen was broken in the 1.04 Preview so backed off to 1.03 Preview and confirmed this fix was still valid.

Updated 8 years ago.
0Send private message
8 years ago
May 30, 2017, 5:04:33 AM

I encountered this as well. Tried Koofka's fix, and it worked as described. Thanks koofka!

0Send private message
0Send private message
?

Click here to login

Reply
Comment

Characters : 0
No results
0Send private message