Repository: pyfa-org/Pyfa

Issue #1081: Projecting Linked Guidance Disruptors yields wrong result
Created: 2017-03-29T15:51:10Z
Submit a bug report bug report or feature request
Bug Report
Expected behavior:
Missile range should show 94km * (1-0.381)^2 = 36km
Actual behavior:
Missile range is 94km * (1-0.309)^2 = 45km
30.9% is the GD strengh without link
Detailed steps to reproduce:
Apply Proteus Links to Crucifier.
Project Crucifier onto Caracal
Fits involved in EFT format (Edit > To Clipboard > EFT):
[Crucifier, Crucifier fit]

[Empty Low slot]
[Empty Low slot]
[Empty Low slot]

Guidance Disruptor II, Missile Range Disruption Script
[Empty Med slot]
[Empty Med slot]
[Empty Med slot]

[Empty High slot]
[Empty High slot]

[Empty Rig slot]
[Empty Rig slot]
[Empty Rig slot]

[Caracal, Caracal fit]

[Empty Low slot]
[Empty Low slot]
[Empty Low slot]
[Empty Low slot]

[Empty Med slot]
[Empty Med slot]
[Empty Med slot]
[Empty Med slot]
[Empty Med slot]
Heavy Missile Launcher II, Caldari Navy Scourge Heavy Missile
[Empty High slot]
[Empty High slot]
[Empty High slot]
[Empty High slot]

[Empty Rig slot]
[Empty Rig slot]
[Empty Rig slot]

[Proteus, Boost]

[Empty Low slot]
[Empty Low slot]
[Empty Low slot]
[Empty Low slot]
[Empty Low slot]

[Empty Med slot]
[Empty Med slot]
[Empty Med slot]
[Empty Med slot]

Information Command Burst II, Electronic Hardening Charge
Information Command Burst II, Sensor Optimization Charge
Information Command Burst II, Electronic Superiority Charge
[Empty High slot]
[Empty High slot]
[Empty High slot]
[Empty High slot]

Medium Command Processor I
Medium Command Processor I
[Empty Rig slot]

Proteus Engineering - Augmented Capacitor Reservoir
Proteus Defensive - Warfare Processor
Proteus Offensive - Dissonic Encoding Platform
Proteus Propulsion - Gravitational Capacitor
Proteus Electronics - Dissolution Sequencer


Information Command Mindlink

Release or development git branch? Please note the release version or commit hash:
1.28.1 Stable
Operating system and version (eg: Windows 10, OS X 10.9, OS X 10.11, Ubuntu 16.10):
Windows 7
Other relevant information:

Duplicate issue #1125: Command Bursts which increase Remote Repair Speed are not applied when projecting the boosted fit onto another one.
Created: 2017-04-14T10:16:56Z
Bug Report
When projecting a boosted Logi fit onto another ship, the Remote Rep boosts don't get applied. They show up on the effect column on the logi fit, but the projected reps don't change.
Expected behavior:
Applying the Rapid Repair Boost to a Logi should increase the EHP/s on a ship that has the boosted Logi projected to it.
Actual behavior:
The projected EHP/s stays the same, no matter if the Logi ship is boosted or not.
Detailed steps to reproduce:

Create a boosting fit, for example a Brutix, with a Armor Command Burst. Use the Rapid Repair Charge.
Create a Logi fit, e.g. an Oneiros with 4 t2 Large reps. Withh All Skills V each repper reps 85.3/s. Applying the Link, one repper reps now 100/s. This works fine.
Create a third fit where you want to test the EHP/s gained.
Project the Logi fit onto the new ship. The EHP/s stays exactly the same, no matter if you turn the link on the logi on or off.

Fits involved in EFT format (Edit > To Clipboard > EFT):
Any fit using Command Bursts with the Rapid Repair Charge and fits that use Remote Repair Modules.
Release or development git branch? Please note the release version or commit hash:
Both with the 2017.03.13 (release) fork and the current official release build (1.28.1)
Operating system and version (eg: Windows 10, OS X 10.9, OS X 10.11, Ubuntu 16.10):
Windows 10
Other relevant information:

Closing comment (2017-04-15T03:32:13Z): Can confirm, seems to be a duplicate of #1081. A release will be out in the next couple of weeks with the fix.