ivanseidel / ivanseidel/IAMDinosaur
Sensor readings too slow?
- Dominant language
- JavaScript
- Stars
- 2.8k
- Forks
- 533
- PR merge metrics
- No merged PRs in 30d
Description
I left the code running for all night and didn't learn anything. The readings on the sensors seem to be really slow and innacurate, it kinda read it when the cactus has already hit the dinosaur. I'm doing everything as it's explained.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. First reproduce the slow and inaccurate sensor readings using the documented setup, then locate the sensor-reading and update paths while tracing their timing against the cactus collision. Done means readings respond accurately before the dinosaur reaches the cactus, with a regression test or documented reproduction demonstrating the fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100