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

Aerospace movement envelope doesn't update when accelerating or decelerating in movement phase. #5053

Closed
HoneySkull opened this issue Jan 14, 2024 · 0 comments · Fixed by #5054
Labels
Aerospace GUI User Interface

Comments

@HoneySkull
Copy link
Collaborator

Environment

Starting MegaMek v0.49.18-SNAPSHOT
Build Date: N/A
Today: 2024-01-13
Origin Project: MegaMek
Java Vendor: Eclipse Adoptium
Java Version: 11.0.20.1
Platform: Windows 11 10.0 (amd64)
System Locale: en_US
Total memory available to MegaMek: 4 GB

Description

During the movement phase, when accelerating or decelerating with Aerospace units, the movement envelope is static to the initial crafts velocity at the beginning of the turn. If a fighter starts the movement phase with velocity=1, a movement envelope shows the possible movement. However, if the craft starts the movement phase with velocity=0 and you hit the accelerate button, the move envelope stays on velocity zero.

This is the behavior in v0.49.18-SNAPSHOT, as well as in the stable 0.48.0 - not sure if this ever worked.

Initial velocity of zero:
image

Accelerate to velocity = 1:
image

When the fighter starts the movement phase with velocity 1:
image

NOTE: Not sure what the weirdness is with the left side of the movement envelope, but that's a different issue.

HammerGS added a commit that referenced this issue Jan 17, 2024
Fixes #5053 Update Aero movement envelope when accelerating or decelerating.
HammerGS added a commit that referenced this issue Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Aerospace GUI User Interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants