Open xal3xhx opened 8 years ago
just a quick update, i left the server running overnight and woke up to the computer off and saying, io:110: Too long without yielding
one more update, after trying to restart the computer, i get it saying reactorcontrol:1118: attempt to index ? (a nil value)
You are missing some information:
BigReactors-0.4.3A
im playing with the skyfactory pack.
nothing was in log file
Having the same problem with it in FTB Infinity 2.4.2 Read some stuff about sleeps being the problem, and that you shouldn't use sleeps. https://www.reddit.com/r/feedthebeast/comments/1awgq6/computer_craft_too_long_without_yielding/
Perhaps a shoving away of sleeps in the source code is the key.
We only have a single reactor and turbine setup, so it shouldn't be too much to handle. I may look into this.
Found another reference....
But there's no usage of sleep in the application, so what could be taking too long to respond?
Looking at the computercraft docs: http://computercraft.info/wiki/Os.startTimer
The wait loop is weird: https://github.com/sandalle/minecraft_bigreactor_control/blob/master/lolmer_bigreactor_monitor_prog.lua#L1378
Maybe this is the problem?
That wait code was a work-around for something at one point. I've only run a few (about four) reactors at once with a few monitors (about 5 :)) for some time and haven't noticed this, but it may depend on how busy the server is (go single-threaded Minecraft, even with Cauldron it's per dimension/world).
@xal3xhx , are those EnderIO Capacitor Banks for your pathway? :)
For our context, we only have 3 monitors, a single turbine and a single reactor. The server has like 2 users, 4 3.0ghz cpus, and 8gb of ram. That should be enough to run a two person setup :)
i have 10 reactors all of them are mostly always online 11 monitors 10 for each reactor and one for a summary. the computer crashes every once and a while saying. reactorcontrol:1670: Too long without yielding. not sure whats going on. i also cant get a debug monitor to work that could just be me not setting it up right tho.