Quark

Quark

143M Downloads

Animation bug with Pipes on latest Quark release

pelletstove opened this issue ยท 9 comments

commented

When I upgraded to Quark-r1.5-148 and AutoRegLib-1.3-28. Quark Oddities Pipes don't show animations correctly anymore. They seem to still function as expected but the items kinda have this strange stuttering animation near the source until the item leaves the pipe system. Downgrading Quark to the last release seems to clear up the issue.

commented

I saw that this ticket was marked closed so I compiled the latest code to test. Seems like it does show some animation for me now but only for a few sections of pipe, then the animation stops. I recorded a screen capture to illustrate the issue, https://streamable.com/6s4ig

commented

... ugh. Of course.

commented

Tested with the latest Quark-r1.5-149 but still seem to have the same behavior where it only shows the animation for the beginning section of the pipe. I tried with a new world and deleted the quark config but have the same issue.

commented

god. damn. it.

commented

Confirmed the fix works. Thanks!

commented

Still seems to be a problem when the pipes are vertical, unfortunately.
Versions:
Quark-r1.5-155
AutoRegLib-1.3-30
Tested with Forge 14.23.5.2831 and 14.23.5.2838

In all pictures the first two chests are full of sandstone. The redstone blocks arrive in the third chest as expected but the animation doesn't show it.

image
Moving the hopper closer changes where the animation stops, but it's still not right. It should go all the way to the top chest
image
Horizontal appears to work fine
image

commented

That's odd... I can't reproduce

commented

I can still reproduce the issue in the latest version, even with a horizontal setup.
quark pipe animation bug
The problem seems to occur when the item tries to enter an inventory in which is does not fit. It then re-routes, which is however not reflected in the animation. It also does not occur when the full inventory is connected to the same pipe where the item started in.

commented

Can confirm r1.5-162 fixes the issue