Mekanism

Mekanism

111M Downloads

Tesselating Block in World

gdude2002 opened this issue ยท 0 comments

commented

This is relevant to #3764.

I brought this issue up with the Multipart guys, and they explained that while it's a valid bug for them, and they have fixed it in an experimental build, Mekanism is going to have to implement their change. Here's a log from IRC:

14:03:00 <amadornes> I know what the problem with rendering is
14:03:04 <amadornes> I've known for a while
14:03:10 <amadornes> and it's fixed in the latest experimental
14:03:34 <amadornes> if mekanism wanted it fixed, they would've probably moved to exp a while ago
14:03:48 <amadornes> it's not in a normal release yet because I'm making more changes for 2.0
14:03:58 <amadornes> like reworked networking

[ ... ]

14:48:20 <g> amadornes, if it's in experimental, can I build that or grab it from a CI to test?
14:48:23 <g> or is that a horrible idea
14:48:40 <amadornes> maven.amadornes.com
14:48:45 <amadornes> latest exp has it :P
14:48:50 <amadornes> and no, it's not a horrible idea
14:48:52 <amadornes> but
14:48:59 <g> can't guarantee it'll work right, ofc
14:49:00 <amadornes> it's something on mek's side now
14:49:03 <g> alright
14:49:09 <g> I'll see what happens and bring it up with them
14:49:10 <g> thanks
14:49:30 <amadornes> the patch I added gives you a new getActual/ExtendedState method
14:49:34 <amadornes> with the world and pos
14:49:38 <amadornes> which use the chunk cache
14:49:45 <amadornes> instead of the regular world and pos
14:49:54 <amadornes> but that needs to be implemented on their end
14:50:04 <amadornes> by default it just goes back to the old method
14:50:08 <g> ah right, so that probably won't change anything for us
14:50:13 <g> until they implement it
14:50:18 <amadornes> yup
14:50:35 <g> hm, okay

Is a possible fix forthcoming as a result of this?