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

LOWW issuing star command freezes the game #768

Closed
georgeenciu opened this issue Dec 22, 2016 · 9 comments
Closed

LOWW issuing star command freezes the game #768

georgeenciu opened this issue Dec 22, 2016 · 9 comments
Labels

Comments

@georgeenciu
Copy link

Hello,

I have the following situation that happened twice already:

  • on LOWW chart AUA241 enters the radar from PESAT with heading 360
  • after issuing the command star ww665.balad3k.loww the game freezes, i can not click on anything, i can not issue any command
    screenshot 2016-12-22 18 00 16
    screenshot 2016-12-22 18 00 22
  • the error keeps appearing
@n8rzz
Copy link
Contributor

n8rzz commented Dec 22, 2016

@georgeenciu @erikquinn quick first pass, the star command is erroring here:
screen shot 2016-12-22 at 1 28 25 pm

which seems odd because there is and entry segment. There is not an exit segment, though. When this fails, the current leg doesn't reset and when it tries to get the waypoints for what it thinks is the current leg, it fails because it doesn't exist.

Will continue investigating...

@n8rzz
Copy link
Contributor

n8rzz commented Dec 22, 2016

the other thing is that, as its written now, the command you included is actually invalid. The correct command should be: star balad.balad3k.loww. here is the definition for that route:

"BALAD3K": {
     "icao": "BALAD3K",
     "name": "Balad three kilo",
     "entryPoints": {
          "BALAD": ["BALAD"]
      },
     "body": [["BALAD", "A100|S250-"], ["WW669", "A60+|S250-"], ["WW665", "A60|S250-"], ["WW663", "A50|S250"], ["WW661", "A50|S250-"], ["WW659", "A50-|S250-"], ["WW657", "A50-|S250-"], ["WW655", "A50-|S250-"], ["WW653", "A50-|S250-"], ["WW652", "A50-|S250-"], ["WW651", "A50-|S250-"], ["WW650", "A50-|S250-"], ["RW11", "A50-|S250-"]],
     "draw": [["BALAD", "WW669", "WW665", "WW663", "WW661", "WW659", "WW657", "WW655", "WW653", "WW652", "WW651", "WW650"]]
},

@n8rzz
Copy link
Contributor

n8rzz commented Dec 22, 2016

even with the corrected command, it will still fail. so there is a legit problem here.

@n8rzz
Copy link
Contributor

n8rzz commented Dec 22, 2016

ultimately this fails because the currentWaypoint has a speed that is null. how that waypoint does not have a speed is a bit of a mystery.

this issue seems to logged already as #730 (n8rzz#138)

@georgeenciu
Copy link
Author

This is odd. I had the same freeze issue, but I could issue commands. I issued the dvs command to a plane I just issued star nerdu.nerdu4k.loww and it unfreeze

@georgeenciu
Copy link
Author

I've retested it and here is what I've got:

  • SXD4026 enters the radar. issuing the sr command it replies XANUT.XANUT1W.LOWW
    atc-1
  • I want to change that to the BALAD3K transition, so I issue: star balad.balad3k.loww
  • the game freezes and the speed and altitude of SXD4026 disappear from the strip
    atc-2
  • the console fills up with the Expected valueToClamp to be a number error
  • issuing dvs will resume the game
    atc-3

@ghost
Copy link

ghost commented Dec 23, 2016

When you enter CAF to an already airborn plane it also freezes, I only played LOWW so far..

@georgeenciu
Copy link
Author

didn't happened to me on cvs

@ghost
Copy link

ghost commented Dec 23, 2016

I meant CAF (cleared as filed)
dvs doesnt resume the game, LOWW running on Chrome

EDIT:
It was a mistake that i entered this command to an already airborn plane, i was confused and choose the wrong one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants