List view
- No due date•0/1 issues closed
- No due date•4/5 issues closed
- No due date•10/11 issues closed
- No due date•1/1 issues closed
- No due date•2/6 issues closed
- No due date•1/2 issues closed
- No due date•3/5 issues closed
- No due date•1/7 issues closed
- No due date•1/2 issues closed
- No due date•0/21 issues closed
- No due date•1/4 issues closed
- No due date•4/16 issues closed
Support for WebGL: - this milestone is targeted to Release Pro 1.0 One of the requirements for WebGL support is to have a proxy in between driver and instrumented game, as in webgl the game cannot act as a server. AltUnity Proxy Docs: https://docs.google.com/spreadsheets/d/1jBxgh5grTFKvBcelOOnKiZyP-fzdFOGtvc71C1jdGyI/edit#gid=2048524270 ------------------------------------ AltUnity Proxy Usecases: - Multiple Clients ( multiple licenses ) - One instrumented Game - One Driver - Multiple Drivers connecting to same game - Multiple instrumented games connecting to the same proxy - Multiple instances of the same instrumented game 1. Multiple Clients ( multiple licenses ) - in this case the proxy requires a licence_key parameter, upon connection of a game to the proxy, which uniquely identifes a client 2. One instrumented Game - One Driver 3. Multiple Drivers connecting to same game - the proxy keeps track of the commands sent by one driver and forward responses only to the driver that initiated the command 4. Multiple instrumented games connecting to the same proxy - in altunitytester the client can specify game name upon instrumentation - the proxy has the ability to differentiate between games - the client(license owner) has the ability to uniquely identify each instrumented game in order to match tests to the game they wanted - the proxy could expose a discover api to allow the driver to identify to which game he wants to connect." 5. Multiple instances of the same instrumented game -TBD
Overdue by 2 year(s)•Due by December 31, 2022•10/12 issues closed