-
Notifications
You must be signed in to change notification settings - Fork 14
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
Builder causes massive lag #90
Comments
What version? The answer is probably going to be that this is unavoidable though. Placing blocks is expensive in Minecraft. There is not much I can do about that |
let me abuse this issue to prove a point on my side. the builder is actually not causing that much lag during normal operation, if its either pump, quarry or builder. we are talking about a ryzen 5950 server here, so please listen carefully:
|
There is a reason that the preview mode is like this. It was initially added to be able to safely build structures while the support blocks made sure that liquids didnt' flow away during building. For the quarry it's less useful to do this though. I have to think about this |
From my experience, the support blocks that the builder places when preview mode is enabled are not transparent, despite their render material. Since these blocks are not fully transparent to the lighting engine, the server has to spend a lot of additional CPU time recalculating lighting, especially if many thousands of these blocks need to be placed. In other words, the root cause is the same as the root cause of much of the server lag that occurs when a player runs the following command: If this is confirmed, then to save on server lag, the preview blocks placed by RFToolsBuilder should be fully transparent (to the lighting engine). Steps to confirm the additional lag is due to lighting updates (click to expand)
|
I will check this out now |
essentially the title - not sure if this was ever addressed. using latest rftoolsbuilder builder causes massive framedrops when building.
The text was updated successfully, but these errors were encountered: