Traben-0 / Entity_Model_Features

Other
104 stars 18 forks source link

[Bug - models] "Require base model for variation" is outdated and doesn't work properly (Optifine compatibility) #269

Closed magmamir closed 1 month ago

magmamir commented 2 months ago

Describe the bug
In the latest versions of Optifine, a base model for variations is only required if you don't have a .properties file. So it either need to have a base model or a .properties file to make variations work. In EMF, with the "Require base model - compatibility" option turned on (default settings), variations will only work if you have both, a base model and a .properties file. With the "Require base model - compatibility" option turned off, the base model is not mandatory, but the combination of base_model + variation2 + variation3 still won't work, unlike in Optifine.

To summarize:

In Optifine:

In EMF (with "Require base model" enabled):

In EMF (with "Require base model" disabled):

List and link to broken resourcepacks resources_end_test.zip

Expected behavior and Screenshots Optifine: Optifine EMF: EMF

Versions:

magmamir commented 2 months ago

Checked OptiFine 1.20.1 HD U I6. Variations without base model still work.

magmamir commented 1 month ago

Fixed in 2.2.7 version. Thank you for the fix!