Currently, I've implemented a simple Python WebSocket server that returns the agent location and wall locations whenever it's called.
The javascript client creates a new mesh every time it receives the data and draws it on the browser with three.js (THIS IS WRONG)
This should change such that the browser holds one mesh each for all the agents/wall location, and move/redraw that mesh according to the new information coming in from the server.
Plus, maybe a keyboard + drag event based camera work might help with the visualisation.(In that case change the camera to Perspective camera?)
92012a9f28e1590b6008c856d5672c5fefc61b72 uses instanced mesh + server timing to reduce the burden of creating a mesh every frame and rendering it constantly.
Still need to work on redrawing only when the scene changes (window reload, etc.)
Mouse and Keyboard event will come later, but for this issue, I'll close it for now, and will open a different issue in the future regarding the web demo
Currently, I've implemented a simple Python WebSocket server that returns the agent location and wall locations whenever it's called.
The javascript client creates a new mesh every time it receives the data and draws it on the browser with three.js (THIS IS WRONG)
This should change such that the browser holds one mesh each for all the agents/wall location, and move/redraw that mesh according to the new information coming in from the server.
Plus, maybe a keyboard + drag event based camera work might help with the visualisation.(In that case change the camera to Perspective camera?)