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

getCouplerYaw returns incorrect position if two trains are offset #490

Open
4 tasks done
anatawa12 opened this issue Jul 6, 2022 · 0 comments
Open
4 tasks done
Assignees
Labels
bug Something isn't working in fixRTM Comp::RTM Component: RTM

Comments

@anatawa12
Copy link
Member

Before submitting a bug, please make sure following checks.

  • You have finished loading all model packs before login to world/server.
  • You're using the latest stable, snapshot, or daily-snapshot version of fixRTM.
  • You're using correct version of RTM and NGTLib for your fixRTM.
  • You couldn't find same bag in the issues.

Descrive the bug

Original message from Marat_Madiev

not such a critical bug but when 2 trains offset (they do it at the beginning of the curve) the function entity.getCouplerYaw() stops connecting coupler

s

To Reproduce

see image

Expected Behavior

see image

Actual Behavior

see image

OS

N/A

Minecraft Forge Version

N/A

fixRTM Version

N/A(should be latest)

Other Mods

No response

@anatawa12 anatawa12 added the bug Something isn't working in fixRTM label Jul 6, 2022
@anatawa12 anatawa12 self-assigned this Jul 6, 2022
@anatawa12 anatawa12 added the needs-triage The issues without maintainer's check label Jul 6, 2022
@anatawa12 anatawa12 added the Comp::RTM Component: RTM label Nov 1, 2022
@anatawa12 anatawa12 removed the needs-triage The issues without maintainer's check label Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working in fixRTM Comp::RTM Component: RTM
Projects
None yet
Development

No branches or pull requests

1 participant