Power Drain Beams leave you with less power than you started with, in every configuration EXCEPT Drain + Cannon (including no support computer)
Description
Details
- Commits
- Restricted Diffusion Commit
- Task Type
- Bug
- Affected Gamemode(s)
- Single and Multi
- Reproducible
- Yes
- Last tested (version)
- 0.19439 (Dev)
- Category
- Engine
- First occurrence (version)
- 0.19228
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
Event Timeline
Drain Beam + Cannon gives a constant energy supply to power the Beam
single Drain Beam consumes more power than it supplies (even though it states otherwise in the structure info)
This is an intended function to avoid abuse as "power supply reversal"
All beams need a power penalty to not bypass the power calculation curve.
The idea on power drain beams is to keep the power of the target down, and not to leech from the energy.
Thought so too - but it looks like the beam cannon combo is then abusing that by powering itself
Bug was due to inaccuracies in beam power consumption.
All power consumption values have now been changed to be per tick to give an accurate representation on how much power is consumed with how many ticks done
Found more power related issues with support tools so I'm going to put it in this task:
Tests below are from standalone computers, they had no support/slave.
Power supply beam:
- the power consumed is incorrect when you're hitting a target (it's fine if you don't). It's in total the normal base consumption + the power supplied.
So if I have a beam that supplies 480 000 and consumes 600 000. I'll supply 480 000 to my target but consume 480 000 + 600 000 my self.
Power drain beam:
- in most cases, its power consumption is incredibly high. The first tick seems to be OK as far as I can see, the 4 after that experience increased power usage. In my example it should have consumed 24 000 per tick, but it did 67 754 702 for the remaining 4 ticks. This issue seems to depend on how much power storage or current power your target has but I have yet to find the exact reason. The power use per second number displayed next to your power capacity bar on your HUD is showing the number that it should be.
- the power drain is lower than it should be, should be 48 000 per tick, but it was 9600. Seems to me that the <DrainPerHit>120</DrainPerHit> is total power drained, and not per tick as you expect from the other weapons/support tools. Could be that the drain per hit is just divided by the amount of ticks in the burst.
Shield drain beam:
- the power consumed is the similar to the power drain beam issue. My beam should have consumed 120 000 (24 000 per tick) but it only did 24 000 in total, 4800 per tick. The power use per second number displayed next to your power capacity bar on your HUD is showing the number that it should be.
Shield supply beam:
- appears to be fine, i'm wondering if it's intended that it drains your own shield too? You basically transfer your own shields to another ship, but you have to pay a large power price for it.
added 2 config options for power supply and 2 for power drain because it was adding/subtracting the power taken/given from the giver/taker. shield supply needs the config options checked.
Power supply and drain work fine now. The added config options also do what they are supposed to do. I've also checked out 3 randomly chosen combo weapons, 1 at 100% and 2 at 50%. Correct power usage, drained and supplied.
Shield supply and drain also work but they don't have those added config options. Putting in queue since they need those config options the most.
-QA Testing-
Fix confirmed: those config options got added at some point, checked it out now and also reconfirmed the previous fixes. Everything mentioned in here works like it should now.
v 0.198.223#20160627_191803
I just tried 1 Shield Drain + 1 Beam (so 100% efficiency)
It said 60 drain
0.5 ticks
600 energy
But actually it does only 30 drain per tick, reach 1200e/s power consumption on the HUD and often miss 1 tick so does 4 hits instead 5. Result = 120~150 shield drained instead of 300.