Extreme lag under 1FPS 32 chunk render distance
realflow100 opened this issue · 25 comments
Some information
Operating system: windows 7 pro 64-bit
Java version: java 8 that comes with minecraft launcher
Minecraft version: 1.14.4
Baritone version: 1.14.4
Forge mods (if used): none
Exception, error or logs
none
How to reproduce
#goto bell or crafting_table or stripped_oak_log while having very high render distance like above 16 chunks to 32 chunks lag gets extremely bad under 1FPS
but 16 chunks or less framerate is perfect.
No problem with grass or grass blocks. for some reason only happens on with certain blocks.
Final checklist
- [+] I have included the version of Minecraft I'm running, baritone's version and forge mods (if used).
- [+] I have included logs, exceptions and / or steps to reproduce the issue.
- [ + I have not used any OwO's or UwU's in this issue.
I have this same issue, 1.18, my render distance is set to 16 chunks. If I use mine diamond_ore from the surface from some distance away from the y level of the diamond ore I drop to 1fps. The fps only recovers when I'm within 5 blocks of the ore, then stays stable as it's pathing to each vein.
I'll note this happens with any ore. Redstone, gold, iron, diamond... It even happens when using goto grass from a cave below the surface.
I'd like to add that the game log seems to blame the lag on "root" "root.tick" and "root.tick.textures":
[23/02/2022 00:15:23 AM] [Render thread/INFO] [CHAT] [Baritone] > goto grass
[23/02/2022 00:15:24 AM] [Render thread/WARN] Something's taking too long! 'root.updateDisplay' took aprox 885.9458 ms
[23/02/2022 00:15:24 AM] [Render thread/WARN] Something's taking too long! 'root' took aprox 897.1849 ms
[23/02/2022 00:15:24 AM] [pool-3-thread-61/INFO] [STDOUT]: 787072 movements considered
[23/02/2022 00:15:24 AM] [pool-3-thread-61/INFO] [STDOUT]: Open set size: 13881
[23/02/2022 00:15:25 AM] [pool-3-thread-61/INFO] [STDOUT]: PathNode map size: 49656
[23/02/2022 00:15:25 AM] [pool-3-thread-61/INFO] [STDOUT]: 71552 nodes per second
[23/02/2022 00:15:25 AM] [pool-3-thread-61/INFO] [STDOUT]: Path goes for 50.65570056765576 blocks
[23/02/2022 00:15:25 AM] [Render thread/WARN] Something's taking too long! 'root.tick.textures' took aprox 887.8979 ms
[23/02/2022 00:15:26 AM] [Render thread/WARN] Something's taking too long! 'root.tick.textures' took aprox 872.8968 ms
[23/02/2022 00:15:26 AM] [Render thread/WARN] Something's taking too long! 'root.tick' took aprox 1890.556 ms
[23/02/2022 00:15:26 AM] [Render thread/WARN] Something's taking too long! 'root' took aprox 1902.1013 ms
(ad infinitum)
shut yo skin tone chicken bone google chrome no home flip phone disowned ice cream cone garden gnome extra chromosome metronome dimmadome genome full blown monochrome student loan indiana jones overgrown flintstone x and y hormone friend zone sylvester stallone sierra leone autozone professionally seen silver patrone ching chong ling long suck my ding dong head ass pubg fortnite flip phone remote control autism down syndrome stage four terminal brain cancer o'reilly auto parts silver bronze ash amiibo uv light pen sushi ramen harrison ford gamer bitch ass virgin lamp thermometor lean mean string bean charlie sheen limousine canteen trampoline serpentine antihistamine wolverine submarine unclean nectarine broken gene halloween defective spleen smokescreen james dean putting green tiny peen anti vaccine aquamarine eugene extra green nicotine vaseline jellybean magazine protein lightning-mcqueen vending machine what'chu mean Ocean Man by Ween head ass tf up bitch
my solution work. mark as solved or the others will come
Your solution doesn't work as it will partially break mining. It will mean that baritone will never update what blocks it will mine, so it will mine about 64 blocks and then not mine any more.
What the heck are the responses on this thread, like, this is just trolling...
Reviving a 3yo issue because it's still an issue. Plus you yourself kept just posting troll comments on it so dunno wyta
Why is everyone being so obnoxious and unhelpful? its disgusting seeing this.
I know, right? Actually ridiculous seeing someone tagged as a contributor just trolling in the issue and antagonising people trying to report said issue. Should only be comments on this regarding the issue, whether or not someone else is having it, any additional info, or if any fixes are being done and/or tested.
Should not be posts complaining that people are bumping the issue, when it's being bumped because it's still an issue!
NOPE zero difference. still 0.5FPS with 0.1 of a second of 30FPS then back to 0.5FPS constantly
no good. i set it to 30 and it still lags unplayably. its hard to even do the #stop command because of how bad its lagging.
if I set minegoalupdateinterval to like 50 or something ridiculous it freezes hard every other second for a few seconds then unfreezes for a second and is super laggy and stuttery and then freezes again for a few seconds its super stuttery and laggy still.
any idea why it would lag so much around 32 chunks but not 16 chunks?
I go from smooth 100FPS+ at 16 chunks to under 0FPS at 32 chunks when pathing to certain blocks but ONLY specific blocks.
I have 12GB DDR3 ram
minecraft and OS is installed on 500GB SSD plenty of free space.
GTX 1050 ti 4GB OC graphics card
i5 3570k quad core 3.4ghz CPU up to 3.8Ghz
computer specs is not the problem
I dont know what you mean but around 16 chunks view distance theres no lag when pathing for bells or stripped logs. regardless if they are close to me or miles away.
but around 32 chunks my FPS drops from over 100 to less than 0 if i try to path for bells or stripped logs or other specific blocks
Hey, I have the same problem but it lags even if I have my render distance set on 2. If I click Shift+f3 if says that it lags because of Tick (about 99%) also it may be a problem with 1050 Ti cause I have the same graphics card as him. It also only happens on 1.16 and lags all the time not only when i type a command