Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Large FPS drop using Destruction tool on Max Area
See original GitHub issueAs mentioned in #123 there is a bug / performance issue with the destruction tool when it’s area is set to 16x16x16.
With a Mid -> Pretty Okay gaming PC (GTX 1070, I5, 16GB Ram with 4GB Ram dedicated to MC) and having the max area active on the tool, you will notice an FPS drop of about 90%. It’s something due to how you are highlighting the blocks. I’ve done some messing around and found that it’s this method https://github.com/Direwolf20-MC/BuildingGadgets/blob/master/src/main/java/com/direwolf20/buildinggadgets/tools/ToolRenders.java#L363 that is causing the issue.
A simple fix might be to switch over to using your renderBox method or changing the overlay to large box instead of highlighting each block separately and causing render updates each tick.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
FYI this is a part of the reason it’s still beta. I need to clean this up.
I just tested this. My PC is not great (especially the graphics, as they’re integrated – I don’t even have a dedicated graphics card) and even when rendering all 4096 boxes, my FPS drops to 30 in a flat world.
I also found that rendering all 6 quads has the same effect on FPS as drawing only 1 quad. The solution I implemented was to prevent rendering for blocks with no sides to render (#129). With that, FPS only drops by a few even when set to max range.