Hi!
My laptop doesn't have the best hardware for games and as a result, I'm always on the lookout for optimisation mods, usually using the mod pack fabulously optimised as a reference point.
I started using this mod and discovered that single chest models don't render. The same goes for ender chests. They do not show up in the crafting book, crafting result, inventory and when place down.
Then, following your advice from CurseForge, you said it may be resource pack related, i removed my main resource pack and it fixed the issue. Trouble is, i use a fair few packs. :/
I have attached some screen shots of the issue, followed by what happens when my resource pack is removed and a copy of selectedpacks.txt from my vanilla tweaks resource pack

Selected Packs.txt

Well, one of your resource packs is overwriting /resources/assets/minecraft/blockstats/chest.json (and ender_chest.json). If you don't want to figure out which pack does that you could make this mod's resources folder a resource pack and set it to highest priority in your game.

Ah thanks for responding so quick. Makes sense though I feel like it would be beneficial to you and your mod if I did find out which pack it had issues with, then you could mark incompatibility with it. Let me know if you want me to do so. Thanks

But actually up looking through the entire resorce pack folder i was unable to find a chest.json or an ender_chest.json I will still try what you said regardless

Although saying that i have found the issue. It seems that your mod is incompatible with Proper Break Particles from the vanilla tweaks library. I looked through my pack and i found only 1 set of chest based files and each one had link to proper break particles and removing it has shown that it does fix hte issue. If you would like to mark incompatability and close this issue that would be fine

Oh okay well nevermind, Thanks for the help. And great mod i can already see the improvement

I added a note on the cf page. I don't think you can mark mods as incompatible with specific resource packs and it wouldn't even make much sense to do that in the first place, since the user can just remove the conflicting blockstate definitions from the resource pack.