This page lists the common problems and limitations that might occur when using the QNX Player.
Due to an ABI breakage in the QNX 7.1 screen system headers, the Player might not be able to query all available display modes. For more information, refer to the QNX Article - Ref# J2941150.
When using the LightmapperA tool in Unity that bakes lightmaps according to the arrangement of lights and geometry in your scene. More info
See in Glossary in the Editor, the GI cacheThe cached intermediate files used when Unity precomputes lighting data. Unity keeps this cache to speed up computation. More info
See in Glossary gets corrupted if UWP is selected as the Target platform.
The -nographics commandline argument in the Player build of the Unity Editor is the root cause of this problem, because it generates sky ambient probe and reflection probeA rendering component that captures a spherical view of its surroundings in all directions, rather like a camera. The captured image is then stored as a Cubemap that can be used by objects with reflective materials. More info
See in Glossary that require loading a gfx device, otherwise these probes include uninitialized data.
To prevent this from happening, run the Player build without -nographics, or generate lighting in the Editor for each sceneA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary included in the build. That is, don’t add lights or generate lightmapsA pre-rendered texture that contains the effects of light sources on static objects in the scene. Lightmaps are overlaid on top of scene geometry to create the effect of lighting. More info
See in Glossary, and instead generate lighting that will automatically bake the sky probes. When -nographics is set, no probes will be rendered.