Big Reactors

Big Reactors

11M Downloads

Reactors consuming fuel even when chunk is not loaded in SMP

fusionnrg opened this issue ยท 7 comments

commented

I've noticed on my SMP server that Big Reactors are consuming fuel and wasting power even when the chunk that it is located in is not loaded. I've seen issues like this with multiblock power generation in the past. Is there anything you can do to stop this waste of fuel and power?

commented

Without proof/screenshots, I'm afraid there's nothing I can do for you.

I'd find it exceptionally hard to believe that the chunk is truly unloaded,
as reactor fuel in 0.2 is logically located in individual block
tile-entities. If the chunk is actually unloaded, the reactor would be
unable to modify the unloaded blocks.

If your reactor is near spawn, that could be the source of your problems -
there's a large area around spawn that never unloads. I believe it's a 9-
or 11-chunk radius by default.

On Tue, Feb 11, 2014 at 6:57 PM, fusionnrg [email protected] wrote:

I've noticed on my SMP server that Big Reactors are consuming fuel and
wasting power even when the chunk that it is located in is not loaded. I've
seen issues like this with multiblock power generation in the past. Is
there anything you can do to stop this waste of fuel and power?

Reply to this email directly or view it on GitHubhttps://github.com//issues/99
.

commented

I have run tests in creative mode as well and verifying the chunks were not
loaded with opis. Fuel is still consumed and power is buffered while I
transport to a myst age. I will run further tests tonight when i get home
from work and further document.

On Tue, Feb 11, 2014 at 1:09 PM, Mr. E. Beef [email protected]:

Without proof/screenshots, I'm afraid there's nothing I can do for you.

I'd find it exceptionally hard to believe that the chunk is truly unloaded,
as reactor fuel in 0.2 is logically located in individual block
tile-entities. If the chunk is actually unloaded, the reactor would be
unable to modify the unloaded blocks.

If your reactor is near spawn, that could be the source of your problems -
there's a large area around spawn that never unloads. I believe it's a 9-
or 11-chunk radius by default.

On Tue, Feb 11, 2014 at 6:57 PM, fusionnrg [email protected]
wrote:

I've noticed on my SMP server that Big Reactors are consuming fuel and
wasting power even when the chunk that it is located in is not loaded.
I've
seen issues like this with multiblock power generation in the past. Is
there anything you can do to stop this waste of fuel and power?

Reply to this email directly or view it on GitHub<
https://github.com/erogenousbeef/BigReactors/issues/99>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-34785583
.

commented

If you can construct a creative world documenting this, I'd be glad to take
a look.

Please include as few other mods as possible to eliminate the possibility
of a crossmod interaction.
On Feb 11, 2014 7:48 PM, "fusionnrg" [email protected] wrote:

I have run tests in creative mode as well and verifying the chunks were not
loaded with opis. Fuel is still consumed and power is buffered while I
transport to a myst age. I will run further tests tonight when i get home
from work and further document.

On Tue, Feb 11, 2014 at 1:09 PM, Mr. E. Beef <[email protected]

wrote:

Without proof/screenshots, I'm afraid there's nothing I can do for you.

I'd find it exceptionally hard to believe that the chunk is truly
unloaded,
as reactor fuel in 0.2 is logically located in individual block
tile-entities. If the chunk is actually unloaded, the reactor would be
unable to modify the unloaded blocks.

If your reactor is near spawn, that could be the source of your problems

there's a large area around spawn that never unloads. I believe it's a 9-
or 11-chunk radius by default.

On Tue, Feb 11, 2014 at 6:57 PM, fusionnrg [email protected]
wrote:

I've noticed on my SMP server that Big Reactors are consuming fuel and
wasting power even when the chunk that it is located in is not loaded.
I've
seen issues like this with multiblock power generation in the past. Is
there anything you can do to stop this waste of fuel and power?

Reply to this email directly or view it on GitHub<
https://github.com/erogenousbeef/BigReactors/issues/99>
.

Reply to this email directly or view it on GitHub<
#99 (comment)

.

Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-34790236
.

commented

E.... can I call you E? Big E? Mr.Beef?

So so I stripped all the mods out of FTB techworld 2 and enabled only
mystcraft and Big reactors. I built the reactor, , set up the linking
books, activated the reactor and immediately went into the myst world,
completely unloading the entire Overworld. . I remained there for approx 9
minutes and returned to find the reactor buffer approx half full-ish I took
two screenshots one right after turning the reactor on, the other
immediately after returning from the myst world. They are attached, you
should be able to verify the bug now. The screenshots are also time stamped

On Tue, Feb 11, 2014 at 2:00 PM, Mr. E. Beef [email protected]:

If you can construct a creative world documenting this, I'd be glad to take
a look.

Please include as few other mods as possible to eliminate the possibility
of a crossmod interaction.

On Feb 11, 2014 7:48 PM, "fusionnrg" [email protected] wrote:

I have run tests in creative mode as well and verifying the chunks were
not
loaded with opis. Fuel is still consumed and power is buffered while I
transport to a myst age. I will run further tests tonight when i get home
from work and further document.

On Tue, Feb 11, 2014 at 1:09 PM, Mr. E. Beef <[email protected]

wrote:

Without proof/screenshots, I'm afraid there's nothing I can do for you.

I'd find it exceptionally hard to believe that the chunk is truly
unloaded,
as reactor fuel in 0.2 is logically located in individual block
tile-entities. If the chunk is actually unloaded, the reactor would be
unable to modify the unloaded blocks.

If your reactor is near spawn, that could be the source of your

problems

there's a large area around spawn that never unloads. I believe it's a
9-
or 11-chunk radius by default.

On Tue, Feb 11, 2014 at 6:57 PM, fusionnrg [email protected]
wrote:

I've noticed on my SMP server that Big Reactors are consuming fuel
and
wasting power even when the chunk that it is located in is not
loaded.
I've
seen issues like this with multiblock power generation in the past.
Is
there anything you can do to stop this waste of fuel and power?

Reply to this email directly or view it on GitHub<
https://github.com/erogenousbeef/BigReactors/issues/99>
.

Reply to this email directly or view it on GitHub<

#99 (comment)

.

Reply to this email directly or view it on GitHub<
#99 (comment)

.

Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-34791724
.

commented

Hmm, the screenshots don't seem to have attached properly. Based on your description, it should be possible to reproduce this without Mystcraft involved - simply fly/walk about 200 coordinates away from the reactor. That should place you further than the default distance at which players keep chunks loaded.

I'm a bit slammed with my day job, so I can't dig further into this today.

commented

NO big deal I certainly do not expect immediate results, I simply opened
the ticket to make you aware of the issue to resolve in future releases. I
simply used Myst to insure minimal time in a loaded chunk to illustrate the
issue.

Again Great mod, Keep up the good work.

On Wed, Feb 12, 2014 at 4:28 PM, Mr. E. Beef [email protected]:

Hmm, the screenshots don't seem to have attached properly. Based on your
description, it should be possible to reproduce this without Mystcraft
involved - simply fly/walk about 200 coordinates away from the reactor.
That should place you further than the default distance at which players
keep chunks loaded.

I'm a bit slammed with my day job, so I can't dig further into this today.

Reply to this email directly or view it on GitHubhttps://github.com//issues/99#issuecomment-34919980
.

commented

No updates since 0.3.0, closing. Please reopen if this is still an issue.