Port state setting sandbox#111
Conversation
Add new debug rendering controls
|
Immediate thoughts:
|
Remove (BOT) & (SCRIPT) suffixes
|
Speaking of Performance Monitor setting in #114, once the setting can be adjusted in the sandbox, its start value should of course match that in the MatchConfig. Just a note. |
|
Tried it out and found a few things: If no match has been started this session, the Sandbox page will just say "Connecting..." forever when you try to connect. We should probably indicate that it needs a running match to work. We could for instance add a small message like "waiting for match info..." underneath. Or is that too indirect? The rendering of the arena is pointless while "Watch Game" is off. I think we should draw some instructions on top of the arena rendering in that case. For example: "Enable 'Watch Game' to drag and drop objects around." The first time I dragged a bot, I got this error and disconnected. On reconnect, things were working. Dragging the players/ball around while "Freeze game" is active does not move the players/ball in the game until "Freeze game" is disabled. Is this a core/API issue? The save/load state does not save/load the angular velocity of the ball - this becomes clear if you save a kickoff state. Found RLBot/core#167 when toggling bot rendering. |









Behavior is extremely similarly to the old v4 sandbox. Uses a canvas, updates at 20hz, can drag objects around.
Add new debug rendering controls and compact UI layout.
"Connecting to RLBotServer..." only happens while it's waiting for a match config.
Everything is reset and the connection gets closed when the user clicks out of the sandbox. Reconnecting with rlbot v5 is super duper fast so it's not an issue and we save on all the processing that would've been happening for no reason.