Bug affects versions from 1.8 through...
------
Button not pressed the textures are:
"north": { "uv": [ 5, 14, 11, 16 ], "texture": "#texture" },
"south": { "uv": [ 5, 14, 11, 16 ], "texture": "#texture" },
"west": { "uv": [ 6, 14, 10, 16 ], "texture": "#texture" },
"east": { "uv": [ 6, 14, 10, 16 ], "texture": "#texture" }However when pressed they change to:
"north": { "uv": [ 5, 15, 11, 16 ], "texture": "#texture" },
"south": { "uv": [ 5, 15, 11, 16 ], "texture": "#texture" },
"west": { "uv": [ 6, 15, 10, 16 ], "texture": "#texture" },
"east": { "uv": [ 6, 15, 10, 16 ], "texture": "#texture" }This causes the impression the button is pressed but the texture has jumped, the front sides of the button changes to the back sides texture when it's pressed.
Example: Wall, back px 1, front px 2, Air
W12A < button not pushed
W1A < button pushed default 1.8+ mc (looks weird)
W2A < what it now looks like with this fix (outer texture moves in towards wall for duration of press event)
The fix is to change the texture on the pressed button to:
"north": { "uv": [ 5, 14, 11, 15 ], "texture": "#texture" },
"south": { "uv": [ 5, 14, 11, 15 ], "texture": "#texture" },
"west": { "uv": [ 6, 14, 10, 15 ], "texture": "#texture" },
"east": { "uv": [ 6, 14, 10, 15 ], "texture": "#texture" }And the front edge texture moves towards the wall when the button is pressed and out as the button returns to normal.
Hope this is a simple bug to fix... (See attached.)
Linked issues
Attachments
Comments 8
In time order,
2015-10-12_19.30.17.png <- Unpressed Buttons
2015-10-12_19.30.37.png <- Current buttons pressed note the side texture.
2015-10-12_19.31.11.png <- Corrected version front texture moves closer.
The original has the near block texture jumping forward to remain visible, whereas with this suggested fix, it looks like the button actually moves as the near block texture seems to go into the block.
I did try searching, oh and mine does include the fixed: button_pressed.json
Which should make fixing it easier, failing that it could even be added as a resource pack hotfix.
Found it: MC-8522.
@@unknown: I will copy your fix to that ticket.
Erm, yes but...
Did pre 1.8 use .json models? If not it would have to be a .obj fix for the earlier versions and the .json from 1.8
Glad to of helped.
@unknown, I made you the reporter of MC-8522, now you can edit that ticket as you like.
Please attach screenshots of the wrong and fixed versions.