ikbensiep / lofigame Goto Github PK

• some kind of entities that can be run into and bounced around.
• make the marshal npcs
• make marshals approach the player when off track

• #7
• #8
• #9
• #10
• #11
  • (title screen)
  • player settings/home [name, number, choose team] @ garage
  • choose event (in competition or single track day)
  • (if track day: choose world, else: next event in competition)
  • enter world @ trailer
    • choose next session
    • drive [to pitbox, pitlane exit, racetrack, pitbox]
    • #22
    • choose next session / exit event @ trailer
  • #19

• display laptimes
• navigation: back to main menu / go to next session

• #12
• #13
• #14
• (if track day: choose world, else: next event in competition)
• #15
  • #16
  • drive [to pitbox, pitlane exit, racetrack, pitbox]
  • #17
  • #18
• #19

• Investigate if a (much) smaller version of the track layout can be generated, used as a light brackground-image over a dark background-color and scaled up to match the world's dimensions. With a bit of luck this could give you some "free" irregularities because of upscaling pixels.

• After this, investigate if the graphics in the #elevated layer can be duplicated and used as an inverted mask, to block out lights on building corners etc.

• Implement day/night cycle by animating either this entire layer's opacity, or only the background color

----8<--------8<-------8<--------8<--------8<----

previously, in this issue:

This super simple effect can add dramatic night time lighting:

1. create an element to cover the entire world (ie, ::after)
2. add a dark (blue) background color and add a repeating background-image with a radial gradient
3. set this (pseudo) element's mix-blend-mode to multiply

Yields:

Not bad.

However, to have light around the complex shapes of a racetrack, a repeating pattern won't do.

https://github.com/ikbensiep/game1/blob/main/js/sfx-engine.js

Sometimes, an input release may not be captured which you'll notice by the car sometimes going straight when you wanted to turn, or it may keep turning when you've clearly released the arrow key(s).

It is my hunch that this is because we're capturing key up and down events and handling those by storing pressed keys in an array. Because of the possibility of frame drop, we might sometimes not capture a keydown or keyup event.

Is there a solution where we capture input on a separate thread or something?

Should probably suspend gamepad from inputhandler somehow when Game UI used.

Curious how far a couple of autofocus attributes etc get you there.

Decide how the game should respond.

Currently when all waypoints on all available paths have been hit, the routine will start over at the first path, creating an endless loop.

Need to find out:

• how to break out of this loop and let the player roam free
• setting up the next objective / create "win" condition

This is the splash / greeter screen that'll be displayed while the game loads.

(Can be placeholder with just LFO industries logo for now.)

When loading is complete, fade to #13

• Figure out a way to make 3 timing sectors per racetrack.
• #38

This could be done by adding separate sector <path>s or by repurposing the waypoints found in path#racetrack.

Discuss.

• create new career
  • driver name
  • driver number
  • team (starts as privateer / amateur), determines car base config.
• continue career
  • browse events
  • trophy case (ie, personal lap records per venue)
  • team / car settings