ME Cable Crash - Tesselating block model
Kuhnmann opened this issue · 11 comments
Hi there
as soon i will click on a ME Cable the Game Crash.
I am not to good in codeing and don't understand the Crash log..
Can anyone help me?
crash-2020-11-06_14.55.05-client.txt
Thank you!
Yeah we should copy over that sprite nevertheless. I even left a FIXME FABRIC heh.
That would be the best solution
It was fixed in OptiFabric v1.8.8 so that or any later version should have you going fine. All the v1.8.x versions work from 1.16.1 to 1.16.4 in case that wasn't clear.
I updated to the latest version 1.8.10 and it still has the same issue.
If you're still getting crashes even with the newest version I'll need the crash report to see what else can be done
Hi yueh - thank you for your respons. it works, but now it just looks boring ;)
Is there a way to have a Optifine work with my config? i love to use a shader...
Thank you!
This is fixed in latest version of Optifabric. Any similar crashes in the future are best reported to the Optifabric github: https://github.com/Chocohead/OptiFabric
Thank you very much! All is working fine - glad that you helped me!
Do note that ME Chests still produce a crash with optifabric, but hopefully that will be solved soon too.
Whilst I've fixed this in OptiFabric, for reference the null
which is passed in here:
should be the sprite from
quad
. There's already a pair of accessor mixins which exist in AE2 which would work to allow it to be accessed (as it is protected field on BakedQuad
):It was fixed in OptiFabric v1.8.8 so that or any later version should have you going fine. All the v1.8.x versions work from 1.16.1 to 1.16.4 in case that wasn't clear.
It was fixed in OptiFabric v1.8.8 so that or any later version should have you going fine. All the v1.8.x versions work from 1.16.1 to 1.16.4 in case that wasn't clear.
I updated to the latest version 1.8.10 and it still has the same issue.