Troubleshooting
FantasticalOptimizations (FOS) supports various OptiFine features, including resource pack extras. However, the implementation differs from mod to mod and some resource packs are accepted in OptiFine even if they are broken, so this page should help you fix some of those issues.
Older versions
Is the resource pack actually built for the version you're running? If not, check for the latest version or use a converter tool like this one or the official one.
Broken paths
If you see this message while activating a resource pack:
Contains broken paths
This means the resource pack maker is using spaces or other non-standard characters in the file or folder names.
If this is the case, the modpack will warn you and allow overriding it, but note that various glitches may occur (miscolored or invisible blocks, lightning issues, broken textures...).
To fix that, please tell the resource pack maker to only use the following characters in file/folder names: a-z0-9._-.
Fullbright
Or "game brightness beyond 100%".
Currently the vanilla resource pack and OptiFine resource pack methods do not work, and neither will work a direct options.txt edit. Instead, just add a specialized mod, such as Methane or other simpler ones.
Fabulously Optimized does not plan to add "fullbright" methods beyond its current dynamic lighting, because it would take away from vanilla gameplay's night vision and may be disallowed on certain servers' rules.
Invisible blocks
This may occur when the pack is using broken paths and is trying to change the models of some blocks, like chests.
Core shaders/incompatible with Sodium
Resource packs may be incompatible with Sodium
Resource packs are incompatible with Sodium
Does the resource pack change the UI beyond usual means (e.g. rearrange HUD elements)?
That means it may depend on core shaders, which are not fully supported on FOS.
Issues and workarounds are tracked on the mod's Discord or GitHub.
Last updated