Unity support for Netflix Games
TechnicalComments
The standardized wrapper argument is a pipe dream. More layers between the player and the engine usually equals more lag, not less. Why add more bloat?
Better stream management could allow smaller indie studios to reach the Netflix audience without needing to optimize for ten different hardware configurations.
I wonder about the cross-platform part... does this mean they're automating the UI scaling for different screen sizes... or is it more about the input mappings?
If we imagine the simplified development includes a standardized input wrapper, it might actually reduce the friction for devs to support multiple controllers. Would that benefit outweigh the latency concerns for the average user?
To clarify the cloud-native aspect, this likely refers to the decoupling of the simulation tick from the render loop. It allows the server to maintain the game state independently of the client's frame rate, which is standard in high-end multiplayer architecture.
Most people are playing these on tablets or mid-range TVs with spotty Wi-Fi. If the optimization is just for high-end server clusters, it won't matter when the packet loss hits on a home router.
is this just better bitrate management?
Cloud-native often implies server-side simulation. That typically increases the round-trip time for player input unless they have implemented aggressive prediction algorithms.