Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-190717

Trader Llama pathfinding can cause significant ticktimes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Awaiting Response
    • None
    • 1.15.2
    • None
    • GEforceGT 650M/PCIe/SSE2
      8GB ram ( 4 GB allowed to minecraft)
      CPu: 8x core I7 intel
      Java : 1.8.0 64b
    • Unconfirmed
    • Performance

      Hello,

      I have noticed that in some chunks of my game , the game "increase drastically" the ms ticks

      the value increase as soon as a switch from a normal chunk to a problematic one. ( always > 140 when there is an issue and always < 50 when there is not)

      As far as i understand, This high value generate several bugs in the impacted chunks : minecart extremely slow and laggy, mining bug ( the mined block reapear for 1 or 2 sec ) , red stone timers are not working etc.. ). general behavior is that the chunks seems very laggy. 

      some chunks are so impacted ( >200 ) that the game is unplayable .

      I saw that there issue have been reported for 1.14 + ( MC-138550) but not for 1.15.2 that is why i post this one.

       

      Edit : map loaded in 1.16 RC1: 

      reduced in intensity : from  >200 => to 70/80 in the impacted chunks

      i have done a new debug report.

      game is playable , however difference is still clearly visible. btw the chunks impacted and those that aren't. ( ms tick value is *2 ) 

      Nb : I checked as i was thinking that it might affects the "most transformed" chunks vs the untouched , but seems not related ( some impacted chunks were not modifed since generation at all) 

       

        1. 2020-06-26_21.13.56.png
          2020-06-26_21.13.56.png
          2.06 MB
        2. 2020-06-26_21.14.19.png
          2020-06-26_21.14.19.png
          1.83 MB
        3. 2020-06-26_21.14.22.png
          2020-06-26_21.14.22.png
          2.03 MB
        4. 2020-06-26_21.14.25.png
          2020-06-26_21.14.25.png
          1.99 MB
        5. 2020-06-26_21.14.37.png
          2020-06-26_21.14.37.png
          537 kB
        6. 2020-06-26_21.14.43.png
          2020-06-26_21.14.43.png
          1.79 MB
        7. bugged chunk 1.png
          bugged chunk 1.png
          864 kB
        8. bugged chunk 2.png
          bugged chunk 2.png
          1.18 MB
        9. debug-report-2020-06-20_17.37.19 1.15.2.zip
          59 kB
        10. debug-report-2020-06-20_18.06.04 1.16 RC1.zip
          54 kB
        11. lama 1.16.1 a.png
          lama 1.16.1 a.png
          2.85 MB
        12. lama 1.16.1 b.png
          lama 1.16.1 b.png
          2.17 MB
        13. lama 1.16.1 c.png
          lama 1.16.1 c.png
          2.64 MB
        14. lama 1.16.1 d.png
          lama 1.16.1 d.png
          2.46 MB
        15. mining lag.png
          mining lag.png
          674 kB
        16. normal chunk 1.png
          normal chunk 1.png
          833 kB
        17. normal chunk 2.png
          normal chunk 2.png
          1.12 MB
        18. profile-results-2020-06-20_17.34.46 debug launched in normal chunk.txt
          120 kB
        19. profile-results-2020-06-20_17.37.08 debug launched in bugged chunk.txt
          131 kB
        20. profile-results-2020-06-20_18.05.50 1.16 RC1.txt
          127 kB
        21. profile-results-2020-06-26_21.40.03.txt
          116 kB

            Unassigned Unassigned
            MGT MGT
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: