RainWarrior

The item posted in the description of that video works fine. What forge version are you using, and can you show the model?

The item posted in the description of that video works fine. What forge version are you using, and can you show the model?

Yes, please try build #1730, this issue should be fixed there. Thanks for reporting!

Please try build 1726, this issue should be fixed there

In NiceModel.handleBakeEvent, change DefaultVertexFormats.BLOCK to ITEM.

1) lighting system needs correct normals to be specified to generate the correct AO shadowing data; you're using very old hard-coded code to generate the vertex data, which doesn't do that - if you want to generate the model like this, look at custom model loaders that are in forge. 2) retexturing like this can be accomplished more easily - get cube model from the registry (ModelLoaderRegistry.getModel(new ResourceLocation("block/cube_all"), or something similar), or make a json model with 2 layers, which would be more appropriate for this; cast to IRetexturableModel (with checking), and call retexture. Look at uses of IRetexturableModel in forge for examples.

This is the expected behavior. This happened in 1.7, and still happens in 1.8 vanilla.

Please try build 1577 or later , the issue should be fixed, thanks for reporting.

Please try build 1551 or later, another item-related performance issue was fixed.

Nevertheless, please try build 1553 or later, it should fix your issue. In the future, try not to use getItemCameraTransforms, it can't always return the correct transformation.

I assume the inner model for your lantern is a normal vanilla model - build 1529 fixed loading of perspective transformations for them, now they implement IPerspectiveAwareModel too, instead of relying on getItemCameraTransforms, so you need to use that. cast inner model to the IPerspectiveAwareModel, call handlePerspective, and return Pair.of(LanternOn, <second element of the result of inner model's handle perspective here>). Vanilla models should have correct value in getItemCameraTransforms again in the next build, when possible (not using Forge Blockstate Json).

Please try build 1547+, it contains some performance improvements that should help with the FPS. It doesn't show up on the site right now due to a Jenkins derp, but that build exists, and will show up eventually

Thanks for the information To get the max FPS above the 60 mark (your display refresh rate), you need to turn off v-sync in the options too.

Can you please check as much of the cases specified below, and report your performance: 1a) vanilla 1.8 (that exact version, not 1.8.x), smooth lighting: maximum 1b) same, smooth lighting: off 2a) forge 1.8 pre-1523 build, smooth lighting: maximum 2b) same, smooth lighting: off 3a) forge post-1523 build, smooth lighting: maximum 3b) same, smooth lighting: off 4a) forge post-1523 build with forge rendering pipeline turned off (can be found under Minecraft Forge general mod settings in the main menu), smooth lighting: maximum 4b) same, smooth lighting: off

Thanks for the report, it's always best to know about it Sadly, this issue arises due to the furnace block being marked opaque in the code, so the renderer treats its insides as dark; Here's what happens with that furnace with vanilla lighting: As you can see, even vanilla renderer isn't lighting it up correctly; forge renderer behaviour is slightly different, but I think it's acceptable, since there are no holey models for opaque blocks in vanilla, and vanilla renderer renders them incorrectly too.

Fixed in builds 1532+, thanks for reporting

Please try with build 1525+, when it's available, it should fix this issue.

Please try build 1484, the issue should hopefully be fixed.

ItemModelMesher.getItemModel(ItemStack) actually is the place that calls the ISmartItemModel hook. As for perspective - default perspective (without additional perspective transformations) is what's used for entities, so you should make your default model be the one used for in-world entity.

Please try the latest build (1308) and see if the error is fixed.