MC-85394Spawning 'crit' particle with speed >100 causes a extreme lagspike
Just type in this command:
/execute @p ~ ~ ~ particle crit ~ ~ ~ 10 10 10 100
and Minecraft will get stuck like one second.
Usually the speed value was not allowed to go higher than 1
Created Issue:
Spawning 'crit' particle with speed >100 causes a extreme lagspike
Just type in this command:
/execute @p ~ ~ ~ particle crit ~ ~ ~ 10 10 10 100
and Minecraft will get stuck like one second.
Usually the speed value was not allowed to go higher than 1
Changed Description:
Just type in this command:
/execute @p ~ ~ ~ particle crit ~ ~ ~ 10 10 10 100
and Minecraft will get stuck like one second.
Usually the speed value was not allowed to go higher than 1Just type in this command:
/execute @p ~ ~ ~ particle crit ~ ~ ~ 10 10 10 100and Minecraft will get stuck like one second.
Usually the speed value was not allowed to go higher than 1
Added Affects Versions: 15w44b
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
Added Affects Versions: 1.12.1
Added Affects Versions: 17w43b
Added Affects Versions: 17w46a
Can confirm.
Yeah if you try /particle dragonbreath ~ ~1 ~ 1 1 1 0 10000, and change the '0' to a '1' and then a '10', you will see the different lag tiers, I guess you could say.
In response to Talon2863:
Thats because you are spawning 10000 dragonbreath particles which will cause lag unless you have a super-powerful computer.
My computer's decently powerful and it gets no lag when I spawn the 10,000 particles at 0 speed (thanks to dinnerbone). However when I spawn them in at 10 speed, I get about 1 frame a second. And the poster says it happens even with a small amount of particles (100) at 10 speed.
Can confirm for MC 1.12.1.
Seems to have gotten better in 17w46a, but still causes a spike when the speed is set to 10000 (100 isn't noticeable though)
This issue has been fixed in 1.13.1.
Probably actually was fixed in 17w45a; there was a pretty big particle refactor then. I'm not sure why I didn't mark it as fixed then (I commented about it, albeit for 46a since I don't think I'd looked at the particle stuff yet). Going to do a quick test for it and then resolve for that.