Add fog
This commit is contained in:
parent
cfe2f711de
commit
71a034d74c
3 changed files with 34 additions and 12 deletions
11
TODO.txt
11
TODO.txt
|
@ -2,6 +2,7 @@ fuck issue trackers :D
|
|||
|
||||
=========== GENERAL ==============
|
||||
|
||||
- press forward map??? :-D
|
||||
- make some kinda repo for world record runs?
|
||||
- fix the ramp map again due to new physics -- NOW it's almost good but it's
|
||||
still possible to reach the finish at first jump, try to do something about it
|
||||
|
@ -14,7 +15,6 @@ fuck issue trackers :D
|
|||
its velocity by a proportion of car's velocity change (this minus prev.
|
||||
frame), then offset car body by this. However we'll also have to transform
|
||||
inbetween world space and model space.
|
||||
- try to add distance fog?
|
||||
- c99 may impose limit 4095 chars on str literal, gives warning on internal
|
||||
data file, try to somehow hack around it (maybe just convert it to an array in
|
||||
the end?) Maybe this: make a standalone C file with the string in it that
|
||||
|
@ -39,16 +39,17 @@ fuck issue trackers :D
|
|||
|
||||
=========== BUGS =================
|
||||
|
||||
- After adding the non-rotating physics feature, the car now gets funny when
|
||||
turned on the roof, once even shot to the ceiling of the map.
|
||||
- Managed to get the car stuck in non-rotating state, then after a while get
|
||||
it back by crashing. MAY BE FIXED NOW, watch if it still happens
|
||||
- immediately after starting the map countdown seems to be lower (seems to
|
||||
perhaps be caused by nextPhysicsFrameTime, look into it)
|
||||
|
||||
=========== HANDLED ==============
|
||||
|
||||
- should drifting make a sound? NO NEED
|
||||
- Managed to get the car stuck in non-rotating state, then after a while get
|
||||
it back by crashing. MAY BE FIXED NOW, watch if it still happens
|
||||
- After adding the non-rotating physics feature, the car now gets funny when
|
||||
turned on the roof, once even shot to the ceiling of the map.
|
||||
- try to add distance fog?
|
||||
- Consider better input handling in SDL? Currently it just detects presses on
|
||||
the exact frame, so a press can be missed. But how tho? LOOKS FINE, it's
|
||||
only an issue with extremely low FPS, at which point it's unplayable anyway
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue