sp614x / optifine

1.81k stars 418 forks source link

[1.15.2] Incompatibility with Ultimacraft resource pack (pre13). Previously worked on pre12. #3661

Closed ghost closed 3 years ago

ghost commented 4 years ago

Description of Issue

When I try to use the Ultimacraft resource pack, it loads the pack and then unloads it. This only occurs with the latest pre13 1.15.2 version of Optifine, but works with the older pre12 version.

Steps to Reproduce

  1. Apply the Ultimacraft resource pack on OptiFine 1.15.2 HD U G1 pre13.

OptiFine Version

OptiFine 1.15.2 HD U G1 pre13

Installation Method

Used jar in mods folder.

Fabric/Forge Version

Fabric, latest.

OptiFabric Version

optifabric-1.0.0-beta8

Other Installed Mods

Every single mod you have installed, besides OptiFine. Please don't leave anything out, even if you think it has nothing to do with the issue at hand. For long lists of mods, use Pastebin. https://pastebin.com/

Log Files/Crash Reports

Any relevant log files. Drag and drop text files here to upload to GitHub directly, OR upload the complete contents to Pastebin. https://pastebin.com/

You can get logs from .minecraft/logs, and crash reports from .minecraft/crash-reports. Locating your .minecraft folder will depend entirely on your OS. See this page for details: https://minecraft.gamepedia.com/.minecraft

DO NOT directly copy and paste log contents here on GitHub.

F3 Debug Screenshot

image

Prior Testing

If you've installed standalone:

If you've installed using Forge/Fabric:

Additional Information

image This pops up in the corner after attempting to load the resource pack.

lsdxm commented 4 years ago

Same thing happens to me with a bunch of different packs, mostly ones that change the UI. Can't use VanillaTweaks textures, Faithful's dark gui or bread hunger packs and a few others.

Happens with OptiFabric beta8 on MultiMC and also Vanilla launcher, only on pre13. All of these worked fine on pre12.

sp614x commented 4 years ago

Can you post the error log?

KaiAF commented 3 years ago

No reply from the author of the bug report