This page lists known limitations, compatibility notes and common issues related to MediaPixel Games assets.
The goal is to document potential problems clearly so users can understand what to expect, how to work around common issues, and where to find updated information.
MediaPixel Games assets are created and tested gradually.
Some early assets, free samples or experimental files may have fewer formats, simpler documentation or limited compatibility notes compared to complete packs.
Known issues may be updated over time as assets are improved, repackaged or tested in more software.
Different file formats may not preserve the exact same information.
For example:
If an asset looks different depending on the imported format, check the material setup, scale, normals and texture paths.
Materials may look different depending on the software, renderer or game engine.
This can happen because each tool handles materials, lighting and shaders differently.
Common material differences may include:
When needed, materials should be adjusted inside the target software or engine.
Some software may not automatically reconnect texture files after import.
If textures appear missing:
Not all assets include texture files.
Some stylized assets may use simple material colors.
Scale can vary depending on the import settings of each software or engine.
If an asset appears too small or too large, check:
For modular packs, always test how pieces fit together before building a large scene.
Pivot placement may vary depending on the asset type.
For simple props, the pivot is usually placed for practical scene placement.
For modular pieces, the pivot may be placed to support snapping, alignment or repeated construction.
If the pivot does not match your workflow, it can usually be adjusted inside your 3D software or game engine.
GLB previews are intended for quick inspection and web display.
They may not represent the final appearance inside a full production environment.
Possible differences include:
The web preview is useful for checking the model quickly, but it should not replace testing inside your target software or engine.
Large GLB files, high-resolution previews or complex assets may load slowly on some devices.
Performance can depend on:
If a preview is slow, try using a desktop browser or downloading the asset directly.
If a ZIP file does not extract correctly:
If the issue persists, contact MediaPixel Games with the asset name and download page.
For packs distributed through external stores, download and account issues are handled by the store platform.
The MediaPixel Games website and wiki may provide documentation, but external store systems manage:
If the issue is related to a store purchase or download, check the store support page first.
Some assets may be released as experiments, prototypes or early samples.
Experimental assets may have:
These assets are still intended to be useful, but they may not be as polished as final pack releases.
When reporting an issue, please include as much useful information as possible.
Useful details include:
This makes it easier to identify and fix the issue.
Known issues will be listed here as they are discovered.
This section will be updated when specific asset, pack or download issues are confirmed.
Known issues are part of a living documentation process.
As MediaPixel Games grows, this page will help track compatibility notes, common problems and fixes across assets, packs and workflows.