Abstract: Components associated with application entities can be grouped into one or more component groupings. A grouping can include, for example, components that include or specify parameters and settings for a gameplay entity of a gaming application. The grouping of components enables a single component group to be displayed through an editor interface instead of all the individual grouped components, which simplifies the view through the interface. A user can select important parameters to be exposed at the group level, such that those parameters can be accessed and set without having to access and search through the individual grouped components. The grouping can also be saved and used to develop subsequent entities, which can simplify the development process and ensure that necessary components are included for specific entity types.

Abstract: A first content item instance may be played by one or more participants and may be presented by one or more first compute nodes to the one or more participants. Information associated with the first content item instance may be collected. The information may include, for example, game state, user inputs, and other information associated with the first content item instance. The information may be provided as input to a second content item instance executing at one or more second compute nodes. Audio and/or video information output by the second content item instance may then be collected, and data including the collected information may be transmitted to one or more third compute nodes for presentation to spectators. Spectator feedback may be received and provided back to the first content item instance, which may be presented based, at least in part, on the spectator feedback.

Abstract: A first content item instance may be played by one or more participants and may be presented by one or more first compute nodes to the one or more participants. Information associated with the first content item instance may be collected. The information may include, for example, game state, user inputs, and other information associated with the first content item instance. The information may be provided as input to a second content item instance executing at one or more second compute nodes. Audio and/or video information output by the second content item instance may then be collected, and data including the collected information may be transmitted to one or more third compute nodes for presentation to spectators. Spectator feedback may be received and provided back to the first content item instance, which may be presented based, at least in part, on the spectator feedback.

Abstract: A first content item instance may be played by one or more participants and may be presented by one or more first compute nodes to the one or more participants. Information associated with the first content item instance may be collected. The information may include, for example, game state, user inputs, and other information associated with the first content item instance. The information may be provided as input to a second content item instance executing at one or more second compute nodes. Audio and/or video information output by the second content item instance may then be collected, and data including the collected information may be transmitted to one or more third compute nodes for presentation to spectators. Spectator feedback may be received and provided back to the first content item instance, which may be presented based, at least in part, on the spectator feedback.

Abstract: A first content item instance may be played by one or more participants and may be presented by one or more first compute nodes to the one or more participants. Information associated with the first content item instance may be collected. The information may include, for example, game state, user inputs, and other information associated with the first content item instance. The information may be provided as input to a second content item instance executing at one or more second compute nodes. Audio and/or video information output by the second content item instance may then be collected, and data including the collected information may be transmitted to one or more third compute nodes for presentation to spectators. Spectator feedback may be received and provided back to the first content item instance, which may be presented based, at least in part, on the spectator feedback.

Abstract: Art asset rendering systems and methods in which pre-processing is performed in a compilation process. Geometric data are processed in the compilation process with knowledge of associated shading programs. The data are converted into data structures targeted directly to a target hardware platform, and a code stream is assembled that describes the manipulations required to render these data structures. The compiler includes a front end configured to read the geometric data and attributes (an art asset) output from a 3D modeling package and shaders in a platform independent form and perform platform-independent optimizations, and a back end configured to perform platform-specific optimizations and generate platform-targeted data structures and code streams.

Abstract: Art asset rendering systems and methods in which pre-processing is performed in a compilation process. Geometric data are processed in the compilation process with knowledge of associated shading programs. The data are converted into data structures targeted directly to a target hardware platform, and a code stream is assembled that describes the manipulations required to render these data structures. The compiler includes a front end configured to read the geometric data and attributes (an art asset) output from a 3D modeling package and shaders in a platform independent form and perform platform-independent optimizations, and a back end configured to perform platform-specific optimizations and generate platform-targeted data structures and code streams.