messages and micro services
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- distributed-systems
Research direction
No files, tests, or entry points are named. Start by reviewing the proposed engine-to-service message list and resolving the open questions about timestamps, tick rate, object types, and bandwidth through the mentioned benchmarking. Done would require an agreed message contract and documented benchmark results.
Written by the indexing model from the issue text.
Description
(I forgot rotation on a lot of these...)
from engine:
-updateTimestamp(uint64 time) will be automatically prepended to every block of messages sent, probably an integer of microseconds? or tenths of a millisecond?
-
onCollision(int objA, vec3 objApos, vec3 objAoldSpeed, int objB, vec3 objBpos, vec3 objBoldSpeed, float colForce)
-
onInput(int action)
-
onAIsee(int objID, int seeObjID, vec3 objPos, vec3 objBpos)
-
newObj(int objID, vec3 pos, vec3 speed)
-
deleteObj(int objID)
-
onTick()? what would be a reasonable tickrate for this?
-
onReachTarget(int objID, vec3 pos, vec3 rot)
to engine:
-
moveTowards(vec3 target, float maxSpeed, float maxAccel)
-
moveTowardsPoints(vec3 targets[], vec3 rots[], float maxRotSpeed, float maxSpeed, float maxAccel)
-
moveTowardsObj(int objID, float maxSpeed, float maxAccel)
-
createObj(int modelID, vec3 pos) type? physics objects?
-
deleteObj(int objID)
-
getObjInfo(int objID)
-
bindInput(...)
-
preloadFile(...)
I'll want to do some basic benchmarking to figure out how to design these messages, will bandwidth be much of a concern at all?
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Die4Ever/AsyncGameEngine
-
Better frameworkOpen
Difficulty 5/5 Over a week Newbie friendliness 18/100
Die4Ever/AsyncGameEngine#18 · 2 comments ·
-
Green threadsOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Die4Ever/AsyncGameEngine#15 ·
-
ProxiesOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
Die4Ever/AsyncGameEngine#14 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Die4Ever/AsyncGameEngine#13 ·
-
FramePacer classOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
Die4Ever/AsyncGameEngine#12 · 1 comment ·
All issues in Die4Ever/AsyncGameEngine
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Qiskit/qiskit-aer#2466 ·
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
status:needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
PX4/PX4-Autopilot#29006 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Segfault in pwStreamAddBuffer: createBuffer() returning nullptr is dereferenced (Screencopy.cpp:943)Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100