Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Down/Up Facing Item Frames have incorrect rotations #1727

Open
peytonpeck opened this issue Apr 13, 2021 · 10 comments
Open

Down/Up Facing Item Frames have incorrect rotations #1727

peytonpeck opened this issue Apr 13, 2021 · 10 comments
Labels
status:good-first-issue Community help is wanted for this issue type:bug Incorrect behavior, not working as intended

Comments

@peytonpeck
Copy link

WorldEdit Version

7.2.3

Platform Version

Spigot

Bug Description

When copying, rotating, and pasting a clipboard (or schematic) that contains an upward or downward facing item frame, the item frame has an unexpected rotation behavior (at least to me?)

The behavior can be observed in this image

The block and item frame on the left is the original clipboard, and the right is a rotated version of it. I will point out the item in the item frame does get rotated too.

Expected Behavior

I would expect an item frame pointing up or down, when being rotated horitontally, would remain facing the way it is, but the item in the frame would rotate.

Reproduction Steps

  1. Place an item frame facing up or down
  2. Copy it
  3. Rotate it
  4. Paste it
@peytonpeck peytonpeck added status:pending Pending acceptance or closure. type:bug Incorrect behavior, not working as intended labels Apr 13, 2021
@wizjany
Copy link
Collaborator

wizjany commented Apr 30, 2021

kohlerpop1: Ok last reply but it turns out it is not a visual glitch. After extensive test the only difference between a correct facing item frame after rotation is the yaw changes by 90. A item frame on the east west north south changes the yaw to correctly rotate but the ones on the up and down facing do not need to rotate at all only need to have their relative position moved I dont know how you can fix this but I have declared my findings for you. Good Luck!

@octylFractal octylFractal added status:good-first-issue Community help is wanted for this issue and removed status:pending Pending acceptance or closure. labels Jun 1, 2021
@octylFractal
Copy link
Member

I don't really have time to look at the intricacies of our rotate code, but I'm pretty sure this is an actual bug. Requesting that someone else take a look at it and PR a fix.

@BSBMteam
Copy link

BSBMteam commented Aug 3, 2021

These values set painting rotations in item frames:

ItemRotation: 0b = North
ItemRotation: 1b = East
ItemRotation: 2b = South
ItemRotation: 3b = West
ItemRotation: 4b = North
ItemRotation: 5b = East
ItemRotation: 6b = South

This bug also works on:

WorldEdit Version
Fabric-Official(7.2.6-beta-02+2e45a20)

Platform Version
Fabric 0.11.6-1.17

@octylFractal octylFractal pinned this issue Aug 6, 2021
@peytonpeck
Copy link
Author

Any resolution to this?

@octylFractal
Copy link
Member

Nothing has changed since my last comment. That's the current step.

@peytonpeck
Copy link
Author

Not sure how much I can help... I've never used/built with gradle but I'm sure its not hard to do.

In order to fix it, I imagine we'd just need to make a change here probably by seeing if the original vector is equivalent to one that faces up/down, and if so, only rotate it a certain way. I would test my theory but, like I said, never built with gradle :P

@octylFractal
Copy link
Member

Well it's a good thing we have instructions then, isn't it?

@peytonpeck
Copy link
Author

Indeed... be back in a few minutes 👀

@peytonpeck
Copy link
Author

peytonpeck commented Aug 15, 2021

After playing around for a bit, I've noticed a few things.

  • Upon originally pasting an item frame with a rotation of 90 degrees, the hitbox of the item frame is in the correct spot however the client sees the item frame in the wrong spot. This behavior can be observed here.
  • Upon the chunk unloading and reloading, the client will see the item frame as it should be, as seen here
  • It only seems to fix itself when the chunk is reloaded, and not when a user teleports away or relogs, indicating it is likely server-side.

Question is... why is it doing that...

@aurorasmiles
Copy link
Contributor

aurorasmiles commented May 11, 2024

some observations for this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:good-first-issue Community help is wanted for this issue type:bug Incorrect behavior, not working as intended
Projects
None yet
Development

No branches or pull requests

5 participants