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
The TODO here is to bisect the commits and figure out how this happened?
I just randomly glanced at the number of nodes considered and it was higher than ever before!
This is the log
[18:22:00] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Starting to search for path from BlockPos{x=1368, y=68, z=457} to Goal{x=0,z=0}
[18:22:04] [Thread-224/INFO]: [STDOUT]: 6116433 movements considered
[18:22:04] [Thread-224/INFO]: [STDOUT]: Open set size: 128991
[18:22:04] [Thread-224/INFO]: [STDOUT]: 90486 nodes per second
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Took 4000ms, A* cost coefficient 1.5, 6116433 movements considered
[18:22:04] [Thread-224/INFO]: [STDOUT]: Path goes for 245.63387388550464 blocks
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Static cutoff 272 to 244
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Found path segment from BlockPos{x=1368, y=68, z=457} towards Goal{x=0,z=0}. 361945 nodes considered
SIX MILLION MOVEMENTS IN FOUR SECONDS ON MY LAPTOP?!?!??!
The text was updated successfully, but these errors were encountered:
The TODO here is to bisect the commits and figure out how this happened?
I just randomly glanced at the number of nodes considered and it was higher than ever before!
This is the log
SIX MILLION MOVEMENTS IN FOUR SECONDS ON MY LAPTOP?!?!??!
The text was updated successfully, but these errors were encountered: