GT-OptiFine ore bug

Question

GT-OptiFine ore bug

Crimento opened this issue 3 years ago · 10 comments

Crimento commented 3 years ago

Some (not all) GT ores are generating as "Unknown Ore".

Steps to reproduce:

Use clean Minecraft with Forge
Install GregTech 6 and OptiFine
Find broken ore deposit

Removing OptiFine fixes the issue. Also it doesn't happen on serverside.

Mod versions:
Forge v10.13.4.1614
OptiFine HD U E7
GregTech v6.14.21

Answer 1 · 2021-11-17T14:00:43.000Z

Are those Ores after being harvested still Unknown Ore? Or is that just visual?

Also which Ores specifically? Both Material and the Stone they are inside of please.

Answer 2 · 2021-11-17T14:13:26.000Z

Thanks for fast response.

Selecting it in creative mode gives back unknown ore but mining with pickaxe works as normal ore.
Also exiting world and loading back fixes visuals.

Happens with both vanilla (Stone) and GT stone types (like Blue Schist or Komatite) and different ores (Coal, Tetrahedrite, Galena, Salt, Hematite for example).

Small variants with name "oredict.oreSmallNeutron.name" instead of "Unknown ore" in WAILA are generating too.

Answer 3 · 2021-11-17T15:30:38.000Z

You say it is HBM, but are you 100% sure its not just GT6 and Optifine ? This really sounds like Optifine is screwing up the way GT6 syncs Ores to the Client.

Answer 4 · 2021-11-17T17:02:31.000Z

I though it's HBM because I played a lot of GT before without HBM and never seen this issue
Now after a year I came back to 1.7.10 and tried adding HBM and saw this.

But thanks, it's just Optifine and GT

Answer 5 · 2021-11-17T17:12:01.000Z

Got it.
Lazy Chunk Loading setting breaks ore rendering.

Answer 6 · 2021-11-17T18:03:58.000Z

Good to know, do you happen to have an Optifine Config File with this Setting in it that I can use for the Default Config Pack, to make sure this garbage wont happen? Or are those Settings not in an actual Config File? (I do not use Optifine myself, despite my Computer being a fancy looking passive cooled Celeron Potato)

Answer 7 · 2021-11-18T11:10:42.000Z

Here's my config file (warning, it goes into root folder and not into config).

optionsof.txt

Exact setting that brokes oregen is ofLazyChunkLoading which is now set to false

Answer 8 · 2021-11-18T12:24:23.000Z

from the name of the file i assume it is in the root .minecraft directory, like the vanilla options.txt?

Answer 9 · 2021-11-18T15:04:40.000Z

root .minecraft directory

Yes

Answer 10 · 2021-11-18T15:46:58.000Z

Well, I looked at it, I dont think I can include that one in the Default Config Pack... I will add a Warning on the Install Instructions that Lazy Chunkloading needs to be disabled.