Axstarz

19 hours ago, XyFreak said:

I just realized that timers had a drifting problem since forever by the looks of it:
Even since before the commit that broke things, if a timer called something that let time pass (i know this is bad anyways but it CAN happen), it would actually fully delay the deadline of successive timers (instead of just delaying the timer once).

Here's another patch

--- C:\Games\MultiMC\instances\Draconic Computers 1.12\.minecraft\saves\BRGC\opencomputers\a201b7a4-e2fd-4565-8b4b-79a6993a7e62\lib\event.lua.bak
+++ C:\Games\MultiMC\instances\Draconic Computers 1.12\.minecraft\saves\BRGC\opencomputers\a201b7a4-e2fd-4565-8b4b-79a6993a7e62\lib\event.lua
@@ -62,7 +63,11 @@
       -- nil keys match anything
       if (handler.key == nil or handler.key == signal) or current_time >= handler.timeout then
         handler.times = handler.times - 1
-        handler.timeout = current_time + handler.interval
+        -- we need to make sure the timer doesn't drift but at the same time doesn't get rescheduled
+        -- immediately if it's execution had been delayed significantly (>= handler.interval * 2).
+        repeat
+          handler.timeout = handler.timeout + handler.interval
+        until handler.timeout > current_time + handler.timeout
         -- we have to remove handlers before making the callback in case of timers that pull
         -- and we have to check handlers[id] == handler because callbacks may have unregistered things
         if handler.times <= 0 and handlers[id] == handler then

Hey @XyFreak I'm a noob in LUA an OP so what i have to do to solve that problem ?

Edit: I dont know why but IT'S WORKING 

Thank you very much for your work

Okay thank you very much :) this is an important problem because, I see that the program don't work because All the program is not actualising.

To see that, I launch your program with a passive reactor I consume energy and when I "update the screen" the heat at 1000° and go down because the program stop it (I can't screen sorry:) 

32 minutes ago, XyFreak said:

I do not have a solution for this issue - the gui is using a timer to redraw stuff - if it suddenly stops drawning then i don't think there's anything wrong with the program. In order for me to test things out I need you to tell me the version of OC, ER and propably your forge version as well.

Okay.I have create an another modpack to see if is my modpack and,on the other modpack i have the problem.I using the last version of ER(0.4.5.65) and for OC i also use the last version(1.7.4.153) for Forge, i have the 14.23.5.5.2815.

Thank for your program

PS: I see that when i press "enter" continuous, the screen is actualising i that can help you

Hi @XyFreak

It's my first post in this topic

And sorry for my bad english (hello from France)

I have the same issue of @CygnusiaX1.

The screen has a static image.

There is a solution and it is just me ?