Page 1 of 1

[Bug|Java] The problem of the appearance of 3D in the furnace

Posted: 26 Jul 2018, 01:49
by OvOTecnt
As shown, the furnace in combustion state loses 3D material.
2018-07-26_09.43.33.png

Re: [Bug|Java] The problem of the appearance of 3D in the furnace

Posted: 26 Jul 2018, 10:37 
by HanFox
You are correct. Thanks for the report.

You can fix this by opening the 3D Blocks zip and navigating to /assets/minecraft/models/block and renaming lit_furnace.json to furnace_on.json

The issue has been fixed in the download.

Correct solution to loss of 3D material in furnace under combustion condition

Posted: 27 Jul 2018, 05:06
by OvOTecnt
This problem resolution does not rename lit_furnace.json file to furnace.json (this is my solution in the error reporting comment area).
This is due to the loss of furnace.json in the blockstates folder in PureBDcraft More 3D Blocks MC113.zip, the reason why the loss of 3D is due to combustion is because the furnace under combustion is furnace_on.json in block, not lit_furnace.json in the material package.
So you should copy the furnace of the blockstates folder in the original game material package to the blockstates in the PureBDcraft ***x MC113.zip or the PureBDcraft More 3D Blocks MC113.zip, and change furnace_on in the internal data to lit_furnace and save it.As in the picture.
2018-07-26_09.43.33.png
2018-07-27_12.36.21.png
QQ图片20180727125420.png

Re: Correct solution to loss of 3D material in furnace under combustion condition

Posted: 27 Jul 2018, 08:36
by Sphax
Have you tried re-downloading the 3D Blocks Addon?

Re: [Bug|Java] The problem of the appearance of 3D in the furnace

Posted: 27 Jul 2018, 10:18
by HanFox
As I already stated this issue is already fixed in the download.

However, I'll point out it has nothing to do with the blockstate file.

The issue was solely to do with the fact the model for the active furnace hadn't been renamed with the MC1.13 changes (i.e. it was still lit_furnace instead of furnace_on).

Blockstate files aren't required to be present to change models as Minecraft resourcepacks use a hierarchical loading order (i.e. if a folder is missing in one resourcepack, it will look in the pack below, etc. until it reaches Mojang's "default" pack).