Handheld Model Loading for Head-Mounted Displays
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for developing virtual reality applications require developers to re-adapt Software Development Kits (SDKs) and modify game or application logic when users switch to handheld devices with different shapes and styles, leading to increased development costs and mismatched virtual and real-world device models.
Innovation Solution
A model loading method and apparatus for head-mounted display devices that determine the type of a connected handheld device, obtain corresponding model resource data, generate a handheld model based on this data, and load it into the virtual scene, allowing for seamless adaptation without requiring SDK re-adaptation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If developers use pre-built handheld models in SDK for virtual reality applications, then the application can be developed and uploaded to application store, but the model cannot be modified when users switch to different handheld devices, leading to mismatch between virtual model and real device
Solution Approach 1:
The system pre-establishes a mapping relationship between handheld device types and model resource data in advance. When a user connects a handheld device, the system automatically identifies the device type and retrieves the corresponding pre-stored model data, eliminating the need for real-time SDK re-adaptation and enabling immediate compatibility with different device types.
Solution Approach 2:
The system creates a universal mapping mechanism that can accommodate multiple types of handheld devices through a single SDK framework. By establishing general mapping relationships between device types and model resources, the system achieves multi-device compatibility without requiring separate adaptation processes for each device type.
2Adaptability or versatility
If developers re-adapt SDK and modify game logic to match new handheld devices, then the model can match the real device, but development costs and time will be increased
Solution Approach 1:
The system pre-establishes a mapping relationship between handheld device types and model resource data in advance. When a user connects a handheld device, the system automatically identifies the device type and retrieves the corresponding pre-stored model data, eliminating the need for real-time SDK re-adaptation and enabling immediate compatibility with different device types.
Solution Approach 2:
The system uses pre-built model resource data that serves as templates or copies for different handheld device types. Instead of creating new models from scratch for each device, the system retrieves and applies appropriate pre-existing model data, significantly reducing the time and effort required for adaptation.
3Ease of manufacture
If the handheld model is pre-built into SDK, then the application can be developed once and uploaded to application store, but it cannot be modified when users use handheld devices with other shapes and styles
Solution Approach 1:
The system pre-establishes a mapping relationship between handheld device types and model resource data in advance. When a user connects a handheld device, the system automatically identifies the device type and retrieves the corresponding pre-stored model data, eliminating the need for real-time SDK re-adaptation and enabling immediate compatibility with different device types.
Solution Approach 2:
The system introduces a mapping relationship as an intermediary layer between the fixed SDK and variable handheld devices. This mapping mechanism acts as a mediator that translates between the pre-built SDK models and the actual diverse handheld devices, enabling flexibility without modifying the core SDK structure.
Data Source
AI summary
The present disclosure discloses a model loading method and apparatus for a head-mounted display device and a head-mounted display device. The method includes: obtaining a type of a target handheld device, in which the target handheld device is a handheld device connected to a current application service; determining whether the type of the target handheld device is an existing type in the head-mounted display device; obtaining, in response to the type of the target handheld device being not the existing type in the head-mounted display device, corresponding model resource data based on the type of the target handheld device; and generating, based on the model resource data, a handheld model corresponding to the target handheld device, and loading the handheld model.


