mirror of
https://github.com/legop3/MultiRoombaRover.git
synced 2026-09-15 17:12:59 -04:00
2.6 KiB
2.6 KiB
- assign rovers based on battery percentage, give people highest one
- bandwidth savings option for videoplayer invisible disconnecting
- setting to disable replay popups in spectator settings menu
- add admin ui for VIP and private requests instead of only through discord
- add flag in roverd for video aspect ratio
- maybe dont? whats the point anyway? why do we exist at all? is there purpose to life?
- just removing the black bars, doesnt do anything practical for the driver page
- would only actually help for keeping spectate page compact
- maybe just make the spectate videos be fixed width and match the height of the media
- either 4:3 or 16:9
- default is 4:3
- all it does is tell the web UI to make the rover video 16:9 or 4:3 shaped
- web UI should default to 4:3 if that rover doesnt yet have that config yet
- maybe dont? whats the point anyway? why do we exist at all? is there purpose to life?
- fix this:
Jun 18 15:14:18 roombaserver.local node[216731]: /home/daniel/MultiRoombaRover/server/src/services/roverManager/socketHandlers.js:92 Jun 18 15:14:18 roombaserver.local node[216731]: cb({ error: err.message }); Jun 18 15:14:18 roombaserver.local node[216731]: ^ Jun 18 15:14:18 roombaserver.local node[216731]: TypeError: cb is not a function Jun 18 15:14:18 roombaserver.local node[216731]: at Socket.handleRequestControl (/home/daniel/MultiRoombaRover/server/src/services/roverManager/socketHandlers.js:92:9) Jun 18 15:14:18 roombaserver.local node[216731]: at Socket.emit (node:events:519:28) Jun 18 15:14:18 roombaserver.local node[216731]: at Socket.emitUntyped (/home/daniel/MultiRoombaRover/server/node_modules/socket.io/dist/typed-events.js:69:22) Jun 18 15:14:18 roombaserver.local node[216731]: at /home/daniel/MultiRoombaRover/server/node_modules/socket.io/dist/socket.js:697:39 Jun 18 15:14:18 roombaserver.local node[216731]: at process.processTicksAndRejections (node:internal/process/task_queues:85:11) Jun 18 15:14:18 roombaserver.local node[216731]: Node.js v22.20.0 Jun 18 15:14:18 roombaserver.local systemd[1]: multirover.service: Main process exited, code=exited, status=1/FAILURE Jun 18 15:14:18 roombaserver.local systemd[1]: multirover.service: Failed with result 'exit-code'. Jun 18 15:14:18 roombaserver.local systemd[1]: multirover.service: Consumed 55min 11.511s CPU time, 711M memory peak.
relative pipe dreams:
- VPS video forwarding
- get forwarding working with the VPS for in-queue users and spectators
- bandwidth testing
- maybe switch room cams back to real video, with audio?
- RF based positional tracking / room map tab
- chromecast monitor youtube search and speakers