LAG FPS Drops when the drawers are focused
Crosus97 opened this issue ยท 4 comments
when the drawers are focused on the screen, the FPS drops almost half of the FPS
I've experimented with my team on my instance of the server on Project Ozone 3 (v3.4.4), and a huge chunk of client lag was proven to come from Drawer Controller itself. When you remove it, I get 50% more framerate, and when I add it back, then a third of my framerate goes down immediately.
This is happening because all the items on the face of the drawers are being rendered in realtime. When the drawers are outside of the field of view, those don't get rendered. It depends somewhat on the complexity of the items/blocks being stored as well.
I'd have to look into the possibility of rendering multiple icons to a texture that might be able to speed up rendering, though even that might have limits (good way to test would be to fill all the slots with simple items, like saplings, which each render as a single quad).
The mod includes an item (and corresponding button) called the "concealment key" which when applied to a drawer or controller, will hide or show all the labels. Not ideal, but you could use it to hide labels to prevent your game slowing when doing other things.
This will be a great solution, if you can do it tell me pls
I'd have to look into the possibility of rendering multiple icons to a texture that might be able to speed up rendering, though even that might have limits (good way to test would be to fill all the slots with simple items, like saplings, which each render as a single quad).
but this solution is so tedius
The mod includes an item (and corresponding button) called the "concealment key" which when applied to a drawer or controller, will hide or show all the labels. Not ideal, but you could use it to hide labels to prevent your game slowing when doing other things.
Hi, sorry a bit late but I'm having the same issue in Minecraft 1.16.4 with Storage Drawers 8.2.1. Is the concealment key removed or hidden? I was searching it in JEI, hoping to have a temporary solution, but with no luck.
Edit: ah, this is reported in issue 844.