add setup game asset structurre
This commit is contained in:
parent
42b04f3699
commit
facc6467f8
@ -3,5 +3,82 @@ sidebar_position: 1
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Default Asset Structure
|
# Default Asset Structure
|
||||||
|
---
|
||||||
|
|
||||||
> To be added
|
## Overview
|
||||||
|
|
||||||
|
| | Core Asset | Game Asset |
|
||||||
|
| :--: | :---------- | :---------- |
|
||||||
|
|<img width="400"/> | - Contains all the necessary game modules.<br/>- Reviewing the [Add submodules](../setup-the-project/add-submodules) for details. | - Contains all the necessary game assets.<br/>- Reviewing the [Create Game Folder Structure](../setup-the-project/create-game-folder-structure) for details. |
|
||||||
|
|
||||||
|
## Asset Folder Structure
|
||||||
|
|
||||||
|
### Asset Loading Manager
|
||||||
|
|
||||||
|
#### Preloads Asset
|
||||||
|
|
||||||
|
Refers to the process of loading necessary game resources (such as images, audio, animations, prefabs, etc.) into memory before they are needed in the game.
|
||||||
|
|
||||||
|
❓ Why Preload Asset?
|
||||||
|
|
||||||
|
🔹Reduce runtime lag: Prevents the game from stuttering or freezing when assets are loaded on demand.<br/>
|
||||||
|
🔹Improve user experience: Ensures smooth transitions between scenes or when many resources are needed quickly.<br/>
|
||||||
|
🔹Better memory management: Allows you to control exactly when and what to load into memory.
|
||||||
|
|
||||||
|
#### Postloads Asset
|
||||||
|
|
||||||
|
Refers to the process of loading resources after the game or a scene has already started running. This is often used to optimize initial loading time and to progressively load non-critical assets in the background.
|
||||||
|
|
||||||
|
❓ Why Use Postloads Asset?
|
||||||
|
|
||||||
|
🔹Faster initial loading: Only essential assets are preloaded; the rest can be loaded later.<br/>
|
||||||
|
🔹Better performance on low-end devices: Distributes memory usage more efficiently.<br/>
|
||||||
|
🔹Allows dynamic content loading: You can load content only when it’s actually needed (e.g., when entering a specific area or level).
|
||||||
|
|
||||||
|
**Example:** Assets used for background.
|
||||||
|
|
||||||
|
🔹Preloads Asset contains static image with low capacity.<br/>
|
||||||
|
🔹Postloads Asset contains animation with higher capactity.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
### Asset Platform Manager
|
||||||
|
#### 💻 Desktop Asset
|
||||||
|
|
||||||
|
Refer to visual, audio, or data resources that are specifically designed to take advantage of the performance, resolution, and user interaction available on desktop computers and laptops.
|
||||||
|
|
||||||
|
🔹High-resolution textures and sprites<br/>
|
||||||
|
🔹Advanced visual effects (particles, lighting, shaders)<br/>
|
||||||
|
🔹High-quality audio files (uncompressed or lightly compressed)<br/>
|
||||||
|
🔹UI/UX elements optimized for mouse and keyboard<br/>
|
||||||
|
🔹Assets that support large resolutions (Full HD, 2K, 4K)<br/>
|
||||||
|
|
||||||
|
❓ Why use Desktop-Specific Assets?
|
||||||
|
|
||||||
|
🔹Performance optimization: Desktops can handle larger and more detailed assets due to stronger hardware.<br/>
|
||||||
|
🔹Enhanced experience: Larger screens and precise input devices allow for more complex and polished visuals.<br/>
|
||||||
|
🔹Scalability: Developers can utilize advanced shaders, visual effects, or input schemes not suitable for other platforms.
|
||||||
|
|
||||||
|
#### 📱Mobile Asset
|
||||||
|
|
||||||
|
Refers to images, audio, and other data that are specifically designed or adjusted to meet the hardware limitations, screen sizes, and memory constraints of smartphones and tablets.
|
||||||
|
|
||||||
|
🔹Smaller and optimized images (compressed textures).<br/>
|
||||||
|
🔹UI/UX tailored for touch input and smaller screens.<br/>
|
||||||
|
🔹Simplified effects with reduced use of heavy shaders.<br/>
|
||||||
|
🔹On-demand asset loading to minimize memory usage.
|
||||||
|
|
||||||
|
❓ Why Optimize Assets for Mobile?
|
||||||
|
🔹Hardware limitations: Mobile devices have less RAM and GPU power compared to desktops → assets must be lightweight.<br/>
|
||||||
|
🔹Storage size constraints: Mobile apps are often limited in total install size.<br/>
|
||||||
|
🔹Better performance & stability: Lighter assets improve game loading speed, reduce crashes, and enhance compatibility across different devices.
|
||||||
|
|
||||||
|
**Example:** Assets used for background.
|
||||||
|
|
||||||
|
- Assets used for desktop have larger size and capacity than mobile.
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|
### Asset Feature Manager
|
||||||
|
#### Main Game Asset
|
||||||
|
#### Feature Game Asset
|
BIN
docs/04-game-asset-structure/img/assets-loading-manager.png
Normal file
BIN
docs/04-game-asset-structure/img/assets-loading-manager.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 21 KiB |
BIN
docs/04-game-asset-structure/img/assets-platform-manager.png
Normal file
BIN
docs/04-game-asset-structure/img/assets-platform-manager.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 366 KiB |
BIN
docs/04-game-asset-structure/img/overview.png
Normal file
BIN
docs/04-game-asset-structure/img/overview.png
Normal file
Binary file not shown.
After Width: | Height: | Size: 20 KiB |
Loading…
x
Reference in New Issue
Block a user