Abstract: Resource processing, such as shader translation, during run time of an application on an emulated platform, can be performed asynchronously from emulation of the application. One or more server computers can be configured to perform such processing remotely from the computers executing the emulation. The one or more server computers can receive resources for processing from multiple computers. The one or more server computers aggregate the resources received from the multiple computers for different applications and process those resources. For example, multiple shaders, discovered from multiple different emulations of an application on multiple computers, are translated and organized by the one or more server computers. The translated shaders can be packaged as an update to the application and redistributed to the computers using the application. Such an update can be installed on the computers as a set of translated shaders for use in the emulation of the application.

Abstract: Resource processing during run time can be performed asynchronously from emulation of an application by a central processing unit. For example, an emulator can include a main processing thread that performs emulation processes. In response to encountering a shader, or other resource, to be processed, the emulator can invoke a separate asynchronous thread to perform such processing. Processed resources, such as translated shaders and generated textures, can be stored in a cache. In response to a command that uses a resource, such as a draw command that invokes a shader or other resource, the emulator can use the processed resource in the cache. If the processed resource is not in the cache, the emulator can skip processing the command that uses the resource. If processed resources can be obtained from other sources and loaded in the cache, processing of resources by the emulator can be eliminated.

Abstract: Resource processing, such as shader translation, during run time of an application on an emulated platform, can be performed asynchronously from emulation of the application. One or more server computers can be configured to perform such processing remotely from the computers executing the emulation. The one or more server computers can receive resources for processing from multiple computers. The one or more server computers aggregate the resources received from the multiple computers for different applications and process those resources. For example, multiple shaders, discovered from multiple different emulations of an application on multiple computers, are translated and organized by the one or more server computers. The translated shaders can be packaged as an update to the application and redistributed to the computers using the application. Such an update can be installed on the computers as a set of translated shaders for use in the emulation of the application.

Abstract: Resource processing during run time can be performed asynchronously from emulation of an application by a central processing unit. For example, an emulator can include a main processing thread that performs emulation processes. In response to encountering a shader, or other resource, to be processed, the emulator can invoke a separate asynchronous thread to perform such processing. Processed resources, such as translated shaders and generated textures, can be stored in a cache. In response to a command that uses a resource, such as a draw command that invokes a shader or other resource, the emulator can use the processed resource in the cache. If the processed resource is not in the cache, the emulator can skip processing the command that uses the resource. If processed resources can be obtained from other sources and loaded in the cache, processing of resources by the emulator can be eliminated.

Abstract: Embodiments that relate to systems and methods for grouping players into a multiplayer game session are provided. In one embodiment, a first match request for a multiplayer game session is received and includes one or more requested player attributes. A plurality of other match requests are received, with one being a second match request including one or more requested player attributes. The first and second match requests are matched based on the requested player attributes. A notification of the match is sent to a client device of the first requesting player, with the notification configured to be received while the client device runs a user session different from the multiplayer game session. The notification includes a selectable element configured to instantiate the multiplayer game session on the client device in place of a user session when the selectable element is selected.

Abstract: Embodiments that relate to systems and methods for grouping players into a multiplayer game session are provided. In one embodiment, a first match request for a multiplayer game session is received and includes one or more requested player attributes. A plurality of other match requests are received, with one being a second match request including one or more requested player attributes. The first and second match requests are matched based on the requested player attributes. A notification of the match is sent to a client device of the first requesting player, with the notification configured to be received while the client device runs a user session different from the multiplayer game session. The notification includes a selectable element configured to instantiate the multiplayer game session on the client device in place of a user session when the selectable element is selected.

Abstract: A progressive stall timer is disclosed. For example, in one disclosed embodiment, a participant in an online turn-based social experience is provided with a time interval in which to take an action in a current turn. If the participant does not take an action in the current turn during the time interval, then the participant is provided a shortened time interval during which to take an action in a later turn. In this manner, the negative impact a stalling participant has on the experience is reduced each time the participant stalls.

Abstract: A progressive stall timer is disclosed. For example, in one disclosed embodiment, a participant in an online turn-based social experience is provided with a time interval in which to take an action in a current turn. If the participant does not take an action in the current turn during the time interval, then the participant is provided a shortened time interval during which to take an action in a later turn. In this manner, the negative impact a stalling participant has on the experience is reduced each time the participant stalls.

Abstract: Key-limited use applications are maintained at a central service where the central service can receive requests from a remote computing device for access to the key-limited use applications. The key-limited use applications include publicly available portions and a locked portions accessible with a key. The central service can provide a key to the remote computing device associated with a key-limited use application for complete access. The key can be stored in a memory device associated with the remote computing device. A digital signature can be assigned to the key to prevent operation of the key in a second computing device. Unauthorized or unlicensed computing devices are prevented from using the applications.

Abstract: A game or other software program is made accessible for execution by clients on a peer-peer network only after a plurality of verifications are made to ensure that control of the software is maintained. With a request sent to a server to access the software, a client includes a nonce and an ID of the user. The server digitally signs a portion of a ticket that is returned to the client, which includes the nonce, a time stamp, and the ID. The ticket is required to access the software. The clients are required to exchange the tickets, verify the digital signature on the portion of each ticket, and use the information therein to confirm that the tickets are current, issued by the correct server, issued to the proper users, and received from the users who are intended to execute the software.