liam-m / sepr-mqv-2 Goto Github PK

When an aircraft leaves the airspace, display its score by its exit point, which gradually fades (decrease alpha until it's 0)

Sub-task for #3

Mechanism decided by @Matidy

Each aircraft has a base score:

• 100 in easy
• 200 in medium
• 300 in hard.

There is a value 'x' which is equal to:

• base_score / 100 in easy
• base_score / 200 in medium
• base_score / 300 in hard

(of course these are all 1 at the moment. This is for if we decide to change base score in future)

There is a value 'y', which is initially 0. This is increased by 'x' every time an aircraft leaves the airspace.

There is a global multiplier, which is based on y:

• 1 when 0 <= y < 10
• 2 when 10 <= y < 40
• 3 when 40 <= y < 80
• 4 when 80 <= y < 130
• 5 when y >= 130

There is a global score, initially 0. Every time an aircraft leaves the airspace, the global score is increased by (multiplier * base_score * x)

did it already - this is just to keep track of what we changed

• Don't allow a plane to be manually controlled while it's landing
• Remove an aircraft if it hits very low altitude (100)

Currently when an aircraft's destination is the airport and it is selected clicking causes the aircraft to change its bearing so it wont land. I think the left mouse does too many things and im not sure the bearing changing works well since the main method of control should be routing the plane through the airspace

We should all attempt to produce good documentation as a selling point for the next assessment, good documentation means:

1. Sensible variable names
2. High level descriptions of methods and their parameters
3. Optimised code with clear logical sections

• Methods in Aircraft
• Buttons in GUI
• Support in flight plans - entry point or exit point can be the airport
• "There must be suitable constraints on how many landings and takeoffs can happen simultaneously"

• Combined entry & exit point
• Airport in GUI

Sub-task for #2

The airport is located near the centre of the airspace. The player should have more than enough time to redirect a new plane entering the airspace before it crashes/almost crashes into a plane waiting to land.

As the background image currently has the airport on the right, a new image will have to be made at some point (@aljidy, @Matidy).

• Decide mechanism and implement
• Display score in GUI

Aircraft will continue to try to reach a waypoint even if their turning speed means they'll never reach it.

Particularly an issue if you make a plane circle it's exit point as control is removed everytime you exit the airspace.

Aircraft is very large and potentially unmanageable. Refactor out flight plan and associated methods/attributes into its own class.

Make sure that an aircraft isn't spawned at an entry point if:

• There is an aircraft in the final stage of its flight plan heading towards that point
• That aircraft is <250 away - this number should be adjusted but I think it's a good starting point

Instead, make it spawn at a different entry point. If none of them is available, make it spawn at the airport. If the airport is full and no entry point is available, don't spawn anything.

Modify createAircraft() in Demo for this.

The aircraft will start turning towards the old manual target bearing as soon as you re enter manual control.

All of the other entry / exit points have a label with their name on. Display 'Mosbear Airport' just above it.

When an aircraft leaves the airspace on manual control mode, it reverts back to auto control mode to be guided back to it's flight path. Once back in the airspace it reverts back to manual mode and if the user doesn't take quick drastic action it can get stuck in this loop.

Suggested Fix
Once the plane comes back into the airspace it should remain on auto control as opposed to reverting back to manual control.

Do we want to add keyboard controls for everything? I think particularly we could do with changing the control altitude as scroll wheel is a fairly clunky way to do it.

I don't think it'll really be possible to change flight plans using keyboard but it could probably be used for everything else.

Sub-task for #1

• Method in Aircraft - if an aircraft has been spawned at the airport but hasn't been instructed to take off yet. This will make it go into an active state in the airspace. See UI/UX document or ask @Matidy for more details of how this should work
• Button in GUI to make the waiting aircraft take off (see UI/UX document)
• Make sure that there are correct constraints on how many aircraft can land/take off simultaneously

Plane positions continue to be calculated when you move the menu. Everything else freezes. Plane position is not calculated correctly while moving the menu.

Make it so that planes don't get lower alpha as they change altitude - just make it so they become smaller

The selected aircraft's flight path should be highlighted as it is currently.

The aircraft you're hovering over's flight path should be highlighted with half alpha.

See below for example - yellow lines (going the wrong direction too - maybe negative length?). May be because something is static?

Sub-task for #1 (requires #2)

When an aircraft is ready to land but the ATCO hasn't sent the land command, the aircraft will circle the airport at a certain radius. Of course, this only applies to aircraft that have the airport as their destination. This behaviour may change based on UX decisions so we'll wait for those to be finalised before implementing this.

Sub-task for #1

• Method in Aircraft - if an aircraft is ready to land at the airport but hasn't been instructed to yet. This will make it land. See UI/UX document or ask @Matidy for more details of how this should work
• Button in GUI to make the waiting aircraft land (see UI/UX document)
• Make sure that there are correct constraints on how many aircraft can land/take off simultaneously

Offset has to be applied to mouse handlers in order for the mouse to line up with GUI elements in game and the only other solution is to mess with lwjgl which at this point is far too messy, the offsets should be in variables and their presence should be documented and explained

Sub-task for #3

See UI/UX document/ask @Matidy if you're not sure where it should be displayed. Ask @jacob135135 if you're not sure how to retrieve the current score

When attempting to issue the land command the player picks up the flight path as if to modify.

Display what used to be called control altitude above where it says how many planes are currently in the air.

I think it should be called either 'view altitude' or 'highlighted altitude' and its main use is just so you can see which planes are in danger of colliding.

• Change the airport image to the new one @aljidy has made
• Add isMouseOverAirport() and isMouseOverHangar() into Airport that check rectangles (probably best to check if if x >= left and x <= right and y <= top and y >= bottom)
• Draw a rectangle around the airport / hangar if clickable (planes waiting, not busy) - same colour as the indication below
• Make mousePressed() in Demo call take off and landing if the hangar/airport is pressed
• Add an indication on top of the airport and hangar showing how many planes waiting to land/take off that varies colour:
  • Grey = no planes waiting
  • Yellow = plane(s) waiting
  • Red = plane(s) waiting too long (hangar only)

The increase to the plane spawn rate based on multiplier isn’t enough (should also be scaled by difficulty due to the planes moving faster).

Ideally there will be at least 10 aircraft in the airspace at some points

I think it'd be good to have a settings/config file (e.g. in XML or something) to make it easier to change values like aircraft speeds, collision radius and entry/exit point positions. Rather than having to go to several different classes to change these they could all be found in one place.

Then we could find a library to read in the information from the file and stick these into the relevant classes at initialisation. If a value isn't in there then it could either throw an error or go to a default value.

What do we think of this?

Part of #5

• Max aircraft = current multiplier (e.g. x7 => maxaircraft = 7)
  • make sure this doesn’t make anything unusual happen when the multiplier decreases (e.g. aircraft disappearing)
• Spawn rate should be set so the number of aircraft is generally between maxaircraft bounds (e.g. at x5 there should be 3-5 aircraft on average, at 7x between 5-7 etc.)

If you start a game, press escape and start a new one a do it a few times, planes will crash immediately as you start a game

This is just a reminder for you

We can get some extra marks for adding further features or behaviours. These need to be fully explained and justified in the deliverables and must not violate the requirements for the game.

Anyone got any ideas for these?