3D Rendering Engine Object Culling for UI State Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional 3D graphic rendering engines face performance issues due to the rendering of unnecessary objects, as they do not effectively consider the characteristic of user interfaces where the viewpoint is fixed and the displayed objects remain constant, leading to inefficient visibility tests and increased computation.
Innovation Solution
A method and system that extracts and renders only the minimum number of 3D graphic objects necessary for the current state of a user interface by culling objects and generating an object list based on the user interface's state, reducing the number of rendering objects and improving performance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional visibility test techniques are used, then the rendering engine can handle general 3D scenes, but the rendering performance deteriorates due to unnecessary objects being rendered
Solution Approach 1:
The patent performs preliminary action by pre-determining which objects are visible in each user interface state before rendering occurs. The system analyzes the fixed viewpoint characteristic of user interfaces and pre-calculates visible objects for each state, storing this information in advance so that during actual rendering, only the pre-identified visible objects need to be rendered, eliminating unnecessary rendering computations.
Solution Approach 2:
The patent extracts the essential characteristic of user interfaces (fixed viewpoint and predictable state transitions) from the general 3D rendering problem. By identifying and extracting this specific characteristic, the system can apply specialized object selection logic that removes unnecessary objects before rendering, rather than using generic visibility tests that render all objects.
2Loss of time
If all 3D graphic objects are rendered, then the rendering engine maintains simplicity in its operation, but the computation time increases unnecessarily
Solution Approach 1:
The system performs preliminary analysis of user interface states and predetermined which objects are visible before actual rendering occurs. This pre-computation of visible objects for each state allows the rendering system to skip unnecessary objects during execution, reducing rendering time without requiring complex real-time visibility calculations.
Solution Approach 2:
The patent creates a simplified representation or copy of the object selection logic that is specific to user interface states. Instead of implementing complex general visibility testing for all 3D scenes, the system uses a simplified copying approach that applies object selection rules tailored to the fixed viewpoint characteristic of user interfaces, reducing both computation time and complexity.
3Productivity
If conventional visibility tests are applied without considering user interface characteristics, then the system remains universally applicable, but rendering efficiency decreases
Solution Approach 1:
The patent applies local quality by tailoring the object selection logic specifically to user interface scenes with fixed viewpoints, rather than using a one-size-fits-all visibility test. The system identifies the specific characteristics of user interface states and applies optimized rendering logic only to these scenes, improving efficiency for this specific application while maintaining the ability to handle other 3D scenes with appropriate adjustments.
Data Source
AI summary
A method, medium, and system rendering 3-dimensional (3D) graphic objects. According to the 3D rendering method, medium, and system, a minimum number of objects for expressing a current state of a user interface are extracted, and the extracted objects are rendered, thereby enabling the rendering performance of a user interface engine to be improved. Here, according to a method, medium, and system minimizing the number of rendering objects, a minimum number of objects for expressing each state of a user interface are culled, and a list of the culled objects is generated, thereby enabling the minimum number of objects for expressing a current state of a user interface to be extracted using the list of the culled objects.