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

Blueprint movement gets bad when large height differences occur #2688

Closed
KJeff01 opened this issue May 4, 2022 · 1 comment
Closed

Blueprint movement gets bad when large height differences occur #2688

KJeff01 opened this issue May 4, 2022 · 1 comment
Labels
Bug good first issue A good issue to tackle if you're new to contributing to this project

Comments

@KJeff01
Copy link
Member

KJeff01 commented May 4, 2022

Describe the bug
Possibly since the introduction of interpolation to blueprint movement in #1260, one might occasionally see the movement of the blueprint seriously accelerate and jump around the screen before stopping.

I believe this is due to extreme height differences around slopes when moving the mouse around as you try to place something. One can accidentally order trucks to place structures where you don't want them and also waste time trying to place something somewhere as it flies across the screen.

To Reproduce
Steps to reproduce the behavior:
There are multiple ways to see this but just choose a factory and try to move the blueprint around the start of a cliff, or even take a hardpoint around the drop of a cliff.

An easy example to see this is to try placing a factory around the cliffs North-West of the trucks in the beginning of Alpha campaign.

alphaspot

Expected behavior
Should not have blueprints violently move around the screen.

Your System:

  • OS: Ubuntu MATE 22.04
  • Game version: master / 4.2.7.

Additional context
Function displayBlueprints() in src/display3d.cpp
class ValueTracker in src/animation.h

@KJeff01 KJeff01 added Bug good first issue A good issue to tackle if you're new to contributing to this project labels May 4, 2022
@KJeff01
Copy link
Member Author

KJeff01 commented May 11, 2022

Duplicate of #1578. Didn't notice an older issue already reported this. So closing.

@KJeff01 KJeff01 closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug good first issue A good issue to tackle if you're new to contributing to this project
Projects
None yet
Development

No branches or pull requests

1 participant