You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Simple Storage Network (SSN)'s cables cause an unusually high amount of frame lag compared to that of Applied Energistics 2 (AE2) and Refined Storage (RS) when in view.
Images:
Below is a comparison of debug info (with the frame time graph shown) with a solid cube of cables in view.
The first image has AE2's cables in it, and the second image has SSN's cables in it. Notice the high drop in FPS and spike in frame times given SSN's cables.
I did this same test with RS in place of AE2 and had similar results.
(This wasn't a perfectly controlled test: the cubes aren't the exact same size (notice the leftover AE2 cables near the bottom left) and the time of day had changed. However, I think that these two screenshots exemplify the problem. If you would like me to repeat the test more precisely, I can.)
The text was updated successfully, but these errors were encountered:
Minecraft Version: 1.12.2
Forge Version: 14.23.5.2859
Mod Version: 1.8.3
Single Player or Server: Both
Problem:
Simple Storage Network (SSN)'s cables cause an unusually high amount of frame lag compared to that of Applied Energistics 2 (AE2) and Refined Storage (RS) when in view.
Images:
Below is a comparison of debug info (with the frame time graph shown) with a solid cube of cables in view.
The first image has AE2's cables in it, and the second image has SSN's cables in it. Notice the high drop in FPS and spike in frame times given SSN's cables.
I did this same test with RS in place of AE2 and had similar results.
(This wasn't a perfectly controlled test: the cubes aren't the exact same size (notice the leftover AE2 cables near the bottom left) and the time of day had changed. However, I think that these two screenshots exemplify the problem. If you would like me to repeat the test more precisely, I can.)
The text was updated successfully, but these errors were encountered: