Mekanism

Mekanism

111M Downloads

Integeroverflow at Induxtion Matrix when using RF-API

Iarinu opened this issue ยท 1 comments

commented

When using an Induction Matrix, containing enough Induction Providers and connecting it via Cryoteum Fluxduct or anything else transferring unlimited RF/Tick you seem to run into an integer overflow.
If you check the transfer rate with an external tool like WAILA or a PowerMonitor you see that the RF/t transfered constantly jumping from negative to positive and back. (see screen shots attached)
The only impact I discovered so far is, that block with an charge-speed limit charges immediately the second the value gets negative. But since the RF-API isn't supposed to handle negative transfer values I bet there are many more strange side effects which could happen.
An easy way to fix this would be to limit the maximal I/O to the maximum possible with the RF/API, when any kind of RF transferring pipe is connected.

Tested with latest version 9.0.3.277 at MC 1.7.10 with forge 10.13.4.1614-1.7.10

Additional informations can/will be provided if requested

All those screenshots are taken in around 5 seconds.
2016-07-04_12 41 09
2016-07-04_12 41 10
2016-07-04_12 41 10_2
2016-07-04_12 41 11
2016-07-04_12 41 11_2

commented

Yes, it's true that the Induction Matrix shows some wonky numbers, but I assure you everything is working fine within mod integration. I cap out at Integer.MAX_VALUE when outputting just as you suggest.