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

Massive Lag in Pattern Terminal #3490

Closed
scotty9090 opened this issue May 11, 2018 · 6 comments
Closed

Massive Lag in Pattern Terminal #3490

scotty9090 opened this issue May 11, 2018 · 6 comments
Labels

Comments

@scotty9090
Copy link

@scotty9090 scotty9090 commented May 11, 2018

Description

When opening the pattern terminal, I get a massive amount of lag, mouse becomes unresponsive, etc. This seems to be somewhat inconsistent and will often start out fine (although a little bit sluggish) and will either remain stable, but often gets worse and worse. At times, it suddenly seems to recover and performance goes back to acceptable levels.

This is the first time in many playthroughs with both AE2 and this pack that I've run into this problem. I've tried breaking replacing the terminal, moving it to different locations on the network - not really sure what else to try so any advice or things I can do to further diagnose the issue would be welcome.

EDIT: All other terminal types are fine - Crafting Terminal, Interface Terminal, etc. I've systematically disconnected every segment of my network with the terminal directly connected to the controller (no P2P) and the problem persists.

EDIT2: Okay it seems to be tied to putting anything in the crafting grid. So if I have a blank workspace performance is fine. As soon as I shift click in, or manually drag items into the pattern terminal grid (to try to encode a pattern) performance starts to suffer. The more items I put in, the worse it gets. I think this likely explains the perceived "inconsistency" that I sighted in my original post.

Environment

I have a fairly average AE2 network setup - nothing extreme and this problem has happened from very early game when my network was really basic.

  • Minecraft Version: 1.12.2
  • AE2 Version: rv5-stable-11
  • Forge Version: 14.23.3.2674
  • Pack: ATM 3 v5.9.5
@yueh
Copy link
Member

@yueh yueh commented May 19, 2018

Nothing we can do without any actual sampling/profiling results.

@mindforger
Copy link
Collaborator

@mindforger mindforger commented May 19, 2018

Try a creative energy cell as power source, you may suffer power outages due to small capacity in your system, always make sure to have enogh powercells installed

@scotty9090
Copy link
Author

@scotty9090 scotty9090 commented May 21, 2018

Can you point me to something that explains how to enable sampling / profiling? I've never done this before and not sure what to do. Is this the vanilla profiler (/debug start)? Or something with Forge?

@Pingger
Copy link

@Pingger Pingger commented May 21, 2018

Opis would be good for thos. Unfortunately it is out of date. Last working version is for 1.7.10

@Buuz135
Copy link

@Buuz135 Buuz135 commented May 22, 2018

It seems to be intense checking in the recipe tree, it happens with both modes (Processing and Crafting)

ae2
ae2_snapshot.zip

@yueh
Copy link
Member

@yueh yueh commented Jun 1, 2018

The cache probably will not be that impressive, as it it will not prevent that many duplicate calls as most ones can still be considered as unique call (or have to). Not comparable to say the changes we could make to a crafting terminal.

The underlying cause is that recipes in minecraft are slow as hell and it seems that forge is fine with it.

@yueh yueh added enhancement and removed awaiting-feedback labels Jun 1, 2018
yueh added a commit that referenced this issue Jun 2, 2018
@yueh yueh closed this Oct 2, 2018
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 27, 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
5 participants