Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage Bus disturbed by ME Level Emitter after restart #2043

Closed
bmario opened this issue Dec 9, 2015 · 5 comments
Closed

Storage Bus disturbed by ME Level Emitter after restart #2043

bmario opened this issue Dec 9, 2015 · 5 comments

Comments

@bmario
Copy link

@bmario bmario commented Dec 9, 2015

I recently came across a bug in rv2-stable-10 on my server.
However I can reproduce the bug with only AE2 installed in Single Player modus.
The problem only occurs after a reboot or new session in Single Player.

The problem is, that an ME Storage Bus does not seems to be working, when there is an ME Level Emitter with a Fuzzy Card in it installed on the same network.

This is my setup:
The ME network comprises the Storage Bus, an Energy Cell, an Terminal, and the ME Level Emitter.
2015-12-09_15 12 54

A Chest with an adjacent ME Storage Bus in default settings.
2015-12-09_15 27 11

In the Chest is an diamond pickaxe.
2015-12-09_15 20 53

And the ME Level Emitter is configured to emit a signal if there is below 1 diamond pickaxes present, with a Fuzzy Card present.
2015-12-09_15 22 31

So in theory, the level emitter shouldn't emit a redstone signal and the terminal should show the pickaxe. But after a restart (for single player, go into main menu), the terminal don't show the pickaxe and there is a redstone signal.
However, after a slight change to the Network, e.g., take away the energ cell, it works again like intended.

*edit: I forgot to mention the forge Versions:
Forge Version on my server: 1448
Forge Version on Client: 1291, 1448 and 1403, all three are affected

@bmario
Copy link
Author

@bmario bmario commented Dec 9, 2015

rv3-alpha-10 is also affected.

@yueh
Copy link
Member

@yueh yueh commented Dec 9, 2015

Interesting.

Should be fixed with #2032.

@yueh yueh added the type-bug label Dec 9, 2015
@bmario
Copy link
Author

@bmario bmario commented Dec 9, 2015

Any chance for a fix to rv2?

Or do you have an idea for a workaround?

@yueh
Copy link
Member

@yueh yueh commented Dec 9, 2015

No idea what actually causes this. Just noticed that the pickaxe is not missing from the terminal with the PR, but the level emitter still behaving incorrectly as the cache was updated in the wrong order.

No idea about rv2, need to at how much work backporting would need. And it is more or less the blocking issue for rv3 beta/stable.

@yueh yueh added this to the rv3 - 1.7.10 milestone Dec 9, 2015
@yueh yueh added the state-fixed label Dec 10, 2015
@bmario
Copy link
Author

@bmario bmario commented Dec 20, 2015

I found a somewhat usable workaround for rv2 on my server, haven't tested it for another build. Adding an ME Controller has a positive effect. However, it sometimes occur nonetheless. Tho, I felt like sharing, it may help someone else.

yueh added a commit to yueh/Applied-Energistics-2 that referenced this issue Dec 27, 2015
… the correct order.

This is loosely based on AppliedEnergistics#2032 and should prevent any duplicated event,
but still does a refresh the whole cache due to potentially issues with
some inventories.

It also ensures that storage buses will not announce a CellArrayUpdate
before they are fully initialized, thus no longer causing them to return
null during an update.

Fixes AppliedEnergistics#2403
@yueh yueh closed this in 38e7e57 Jan 5, 2016
yueh added a commit that referenced this issue Jan 5, 2016
Fixes #2043: Storage buses updates should happen in the correct order.
yueh added a commit that referenced this issue Jan 9, 2016
This is loosely based on #2032 and should prevent any duplicated event,
but still does a refresh the whole cache due to potentially issues with
some inventories.

It also ensures that storage buses will not announce a CellArrayUpdate
before they are fully initialized, thus no longer causing them to return
null during an update.

Fixes #2403
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.