Rendering Data Loading with Sector-Based LOD Version Indexing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of managing rendering data in interactive computer simulations is exacerbated by the large number of small files required for complex computer-generated environments, leading to storage and access issues that hinder real-time scene rendering and restrict file manipulation, development, and update capabilities.

Innovation Solution

A method and system that define a computer-generated environment database with multiple versions, organized into virtual geographical sectors with distinct levels of detail, using content files to quickly identify and load relevant data into memory for real-time access, reducing the need for extensive storage and minimizing network latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the database stores a very large number of small files to represent complex computer-generated environments, then the environment complexity and detail are improved, but the storage and access efficiency deteriorates, and file manipulation becomes restricted

Engineering Contradiction:
Improveenvironment complexityVSAvoidstorage and access efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent segments the large database into multiple versions (v1, v2, v3, etc.) and further divides each version into virtual geographical sectors. This segmentation allows the system to manage and access only the relevant subset of files needed for the current simulation scene, rather than managing all files in the entire database. The content files act as indexes that point to specific files in specific versions, enabling efficient access to segmented data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces content files as intermediary structures that mediate between the application and the large database. These content files contain metadata and pointers to actual data files, allowing the system to quickly identify and access only the necessary files without scanning the entire database. This intermediary layer significantly improves access efficiency while maintaining the ability to manage complex environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If all rendering data files are loaded into memory for real-time access, then the real-time rendering performance is improved, but the memory consumption increases significantly

Engineering Contradiction:
Improvereal-time rendering performanceVSAvoidmemory consumption
Core Design Contradiction:
SpeedVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary rendering data files from the large database and loads them into memory, rather than loading all files. By using content files as indexes to identify which files are needed for the current scene, the system extracts and loads only the relevant subset of data, achieving real-time performance while minimizing memory consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs preliminary actions by pre-organizing the database into versions and sectors with associated content files that contain metadata and file pointers. This preliminary organization allows the system to quickly identify and load only the necessary files into memory when needed, rather than having to process or search through all files at runtime.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If the system maintains multiple versions of the database with multiple levels of detail, then the flexibility for development and updates is improved, but the database size and management complexity increase

Engineering Contradiction:
Improvedevelopment flexibilityVSAvoiddatabase management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the multi-version database into virtual geographical sectors, where each sector has its own content file containing metadata and file pointers. This segmentation reduces the management complexity of multi-version databases by allowing the system to work with smaller, manageable subsets of data from each version, rather than managing the entire multi-version database as a single complex structure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3867778B1Loading rendering data for an interactive computer simulation
Publication Date: 2026.01.28 CAE INC
  • EP3867778B1 patent drawingFigure 1
  • EP3867778B1 patent drawingFigure 2
  • EP3867778B1 patent drawingFigure 3

AI summary

Systems and methods are disclosed for loading rendering data for a scene from a computer generated environment at an interactive computer simulation station. In accordance with one aspect of the present disclosure, a content file is created that defines, for each of a plurality of virtual geographical sectors of a computer generated environment, available levels of detail for the virtual geographical sector and a latest available version that the available levels of detail are contained in. A file associated with an available level of detail in the latest available version is listed in the content file. The content file is loaded into memory during execution of an interactive computer simulation station for real-time access by the interactive computer simulation station to determine which files are available to be loaded for rending of the scene having a target level of detail in a latest available version.