InkPlayCurrent Controller and Agent installers are built for 64-bit Windows.
Operations and support
Compatibility evidence
Know the supported InkPlay environment before installation.
InkPlay currently packages Controller and Agent for 64-bit Windows venue machines. Controller uses Microsoft Edge WebView2, branch components communicate over the local network, and venue-specific Windows policies, games, and launchers should be proven on test PCs.
The Windows Controller launcher hosts the web interface in Edge WebView2.
The Controller installer configures the Local Node service and firewall rule.
Desktop scope
Controller and Agent are Windows-first venue components.
The published installers are named and restricted as win-x64 packages. The current launcher and companion target the Windows 10 generation of APIs, with Windows 10 and Windows 11 x64 as the venue testing scope.
- Use 64-bit Windows for the current Controller and Agent installer path.
- Keep Windows updates, sleep behavior, and venue user permissions under owner or supervisor control.
- Test fullscreen, startup, recovery, taskbar, and policy behavior against the venue Windows image.
Controller requirement
The Controller launcher depends on Microsoft Edge WebView2.
Windows 10 and Windows 11 machines normally include WebView2. The launcher is designed to show a requirement message when the runtime is missing instead of leaving a blank window.
- Verify WebView2 is available on the chosen staff workstation.
- Treat a WebView2 requirement message as a runtime prerequisite, not a branch-data failure.
- Use the official installer and launcher rather than copying partial application folders.
Network scope
Controller, Local Node, Agent PCs, and local mobile flows need reachable branch networking.
The Controller installer registers the Local Node Windows service and a TCP 5245 firewall rule. Player PCs must reach the Local Node over LAN; physical phones testing local flows must use the branch host LAN address, not localhost.
- Keep the Controller host and Agent PCs on a reachable branch LAN.
- Allow the configured Local Node port through venue firewall and network policy.
- For physical-phone LAN tests, keep the phone on reachable Wi-Fi and use the Windows host LAN address.
Venue image testing
Games, launchers, security tools, and Windows policy still require venue testing.
Compatibility is broader than the operating-system label. Anti-cheat, launchers, shared libraries, security policy, antivirus, and shell restrictions can interact differently on each venue image.
- Open the venue’s normal games and launchers after changing Agent policy.
- Test one PC before applying restrictive settings across the floor.
- Keep a safe admin recovery and rollback path for policies that block a required game or launcher.
Helpful guides
Continue with the operator manuals.
Common questions
Compatibility questions, answered clearly.
Which operating systems do the current InkPlay Controller and Agent installers support?
The current public desktop package scope is 64-bit Windows. Windows 10 and Windows 11 x64 are the documented venue testing scope; native macOS and Linux desktop installers are not currently published.
Does Controller require a normal browser tab?
The installed Windows Controller uses a launcher that hosts the existing interface in Microsoft Edge WebView2. If WebView2 is missing, the launcher should show a requirement message.
Will every game and launcher work without testing?
No blanket guarantee is published. Venue games, launchers, anti-cheat tools, Windows policies, and security software should be tested on a small Agent group before floor-wide rollout.
Need help with your venue?
Continue the conversation in the support center.
Choose the branch, describe what is affected, and keep every reply together until the issue is resolved.