A publisher has a InstaLOD game title license for 150 seats. A publisher has 3 different location 3rd party game developer studio to work on a publisher's game project "A".
A publisher wants to have full remote control on activation and deactivation at 3rd party developer studio. However a publisher will not know whether which activated PC machine at 3rd party developer studio is actually assigned (and working) by their artist.
OR a publisher will not know whether which activated PC machine at 3rd party developer studio is actually assigned has actually not used because that PC user was already left 3rd party studio. Or that PC machine was assigned for not LOD work but other non-LOD related game development work.
In order to have each control over 150 seats, a publisher wants to have 3rd party auth key system. A publisher can generate "3rd party ( or internal team) authentication key with # of possible activation seats number". This key will be used / managed by 3rd party company to decide which their local PC should be activated or should deactivated over the course of their development status. A publisher will have a central control on this key itself. A publisher can activate and deactivate this key if a publisher is no longer use that 3rd party game developer studio. A publisher can deactivate this key then that 3rd party game developer will no longer able to use InstaLOD.
Does anyone has similar problem or has set up similar system?
If InstaLOD has such mechanism already?
Please sign in to leave a comment.