Rendering pipeline for electronic games
An electronic gaming device provides a rendering pipeline for an electronic game. The rendering pipeline includes a client component and a native component of the rendering pipeline, where the client component is configured to: initiate a rendering operations pipe between the client component and the native component; convert display commands from a source language of the electronic game into rendering operations of an intermediate rendering language; and transmit the rendering operations through the rendering operations pipe to the native component. The native component is configured to: receive the rendering operations via the rendering operations pipe; translate the rendering operations from the intermediate rendering language into rendering operations of the native component; and perform the rendering operations of the native component on the display device.
1. An electronic gaming device providing a rendering pipeline for an electronic game, the electronic gaming device comprising:
at least one memory device storing a native component of the rendering pipeline;
at least one display device upon which video output of the electronic game is rendered; and
at least one processor configured to execute the native component, wherein the native component, when executed on the at least one processor, is configured to:
receive rendering operations in an intermediate language via the rendering pipeline from a client component, wherein the rendering operations are converted from display commands in a source language by the client component;
translate the rendering operations from the intermediate language into rendering operations of the native component; and
perform the rendering operations of the native component on the at least one display device.
2. The electronic gaming device of claim 1 , wherein the at least one processor is further configured to execute the client component that converts display commands in the source language to rendering options in the intermediate language.
3. The electronic gaming device of claim 1 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of the electronic game.
4. The electronic gaming device of claim 1 , wherein the source language of the electronic game is one of JavaScript and Typescript, wherein the client component includes a java virtual machine that executes the electronic game.
5. The electronic gaming device of claim 4 , wherein the client component is configured to create a WebView object and execute source code of the electronic game via offscreen WebKit rendering in the WebView object.
6. The electronic gaming device of claim 1 , wherein the client component is configured to transmit asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.
7. The electronic gaming device of claim 1 , wherein at least some of the rendering operations of the intermediate language include an operation type, a node identifier, and model data.
8. The electronic gaming device of claim 1 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to transmit the rendering operations to the native component through the rendering pipeline.
9. A method for providing a rendering pipeline for an electronic game on an electronic gaming device, the electronic gaming device including a memory device storing the electronic game and a native component of the rendering pipeline, the electronic gaming device also including a display device upon which video output of the electronic game is rendered and at least one processor configured to execute the native component, the method comprising:
receiving rendering operations in an intermediate language via the rendering pipeline from a client component, wherein the rendering operations are converted from display commands in a source language by the client component;
translating the rendering operations from the intermediate language into rendering operations of the native component; and
performing the rendering operations of the native component on the display device.
10. The method of claim 9 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of the electronic game.
11. The method of claim 9 , wherein the source language of the electronic game is one of JavaScript and Typescript, wherein the client component includes a java virtual machine that executes the electronic game.
12. The method of claim 11 , wherein the client component is configured to create a WebView object and execute source code of the electronic game via offscreen WebKit rendering in the WebView object.
13. The method of claim 9 , wherein the client component is configured to transmit asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.
14. The method of claim 9 , wherein at least some of the rendering operations of the intermediate language include an operation type, a node identifier, and model data.
15. The method of claim 9 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to transmit the rendering operations to the native component through the rendering pipeline.
16. A non-transitory computer-readable medium storing instructions that, when executed by a processor of an electronic gaming device, cause the processor to:
receive, at a native component, rendering operations in an intermediate language via a rendering pipeline from a client component, wherein the rendering operations are converted from display commands in a source language by the client component;
translate the rendering operations from the intermediate language into rendering operations of the native component; and
perform the rendering operations of the native component on a display device.
17. The non-transitory computer-readable medium of claim 16 , wherein the client component includes a virtual machine that is configured to perform just-in-time compilation and execution of an electronic game.
18. The non-transitory computer-readable medium of claim 16 , wherein the client component is configured to transmit asset loading operations to the native component, wherein the native component is configured to load assets identified by the asset loading operations.
19. The non-transitory computer-readable medium of claim 16 , wherein at least some of the rendering operations of the intermediate language include an operation type, a node identifier, and model data.
20. The non-transitory computer-readable medium of claim 16 , wherein a heartbeat is established between the native component and the client component, wherein the client component uses the heartbeat as timing for when to transmit the rendering operations to the native component through the rendering pipeline.