Graphics Asset Rendering and Caching via Parameter-Based Descriptions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software applications face inefficiencies in rendering and caching graphics assets, leading to increased file sizes and communication bandwidth usage due to the need for multiple incarnations of graphics assets to accommodate various computing devices, which results in higher traffic latency and storage requirements.
Innovation Solution
The method involves downloading graphics assets in a non-rendered form, using asset code that specifies rendering instructions and characteristics, allowing the receiving device to render and store them based on its specific characteristics, thereby reducing the need for multiple incarnations and optimizing file size and transmission efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple incarnations of graphics assets are downloaded to accommodate various computing devices, then adaptability is improved, but file size and storage requirements increase
Solution Approach 1:
The patent applies parameter changes by transforming graphics assets from pre-rendered binary formats to a parameter-based description format. Instead of storing multiple rendered versions for different devices, the system stores a single description that specifies rendering parameters (resolution, color depth, format) and uses a renderer to generate the appropriate version dynamically. This resolves the contradiction by maintaining adaptability through parameter specification while reducing file size by eliminating redundant rendered copies.
Solution Approach 2:
The patent uses a virtual copying mechanism where the same graphics asset description is rendered to different output formats as needed. Rather than physically copying multiple versions of the asset, the system creates a single description that can be virtually copied into multiple rendered versions on-demand. This maintains adaptability across devices while minimizing actual storage requirements.
2Adaptability or versatility
If multiple incarnations of graphics assets are stored for different devices, then adaptability is improved, but communication bandwidth usage increases
Solution Approach 1:
The system transmits only the parameter description of the graphics asset rather than multiple pre-rendered versions. The description includes information about the asset's properties (geometry, materials, textures) and the desired rendering parameters, allowing the receiving device to generate the appropriate version locally. This dramatically reduces bandwidth usage compared to transmitting multiple full-resolution rendered assets.
Solution Approach 2:
The system performs preliminary rendering on the sender's device and caches the rendered versions locally, so that when data needs to be transmitted, only the lightweight parameter descriptions are sent rather than the full rendered assets. This preliminary action reduces subsequent communication bandwidth requirements while maintaining adaptability.
3Quantity of substance
If graphics assets are rendered and cached on-demand, then storage requirements are reduced, but rendering time and processing overhead increase
Solution Approach 1:
The system performs preliminary rendering of graphics assets and caches the rendered versions in a local storage structure (such as a frame buffer or texture cache). When the same asset needs to be displayed again, the system retrieves the pre-rendered version from cache rather than re-rendering it. This preliminary action reduces subsequent rendering time and processing overhead while maintaining low storage requirements through efficient caching strategies.
Solution Approach 2:
The rendering system includes self-service mechanisms where the renderer automatically manages its own cache, determining which assets to pre-render and how to organize them for optimal retrieval. The system monitors usage patterns and automatically adjusts its caching behavior to minimize both storage usage and rendering time, resolving the contradiction between these two parameters.
Data Source
AI summary
Various embodiments are generally directed to techniques for downloading graphics assets of a software application in a form in which they are rendered as needed on a computing device based on its characteristics and then stored therein for later use. A computer-implemented method includes determining whether a requested graphics asset is stored in a storage of a computing device, retrieving the graphics asset from the storage when the graphics asset is stored in the storage, rendering the graphics asset when the graphics asset is not stored in the storage, and visually presenting the graphics asset on a display of the computing device. Other embodiments are described and claimed.


