Search Issue Tracker
Won't Fix
Votes
0
Found in
3.5.0f5
Issue ID
451796
Regression
No
Remove gfxDevice dependency when building shaders
Remove gfxDevice dependency when building shaders
(Premium Support case 2050 filed by Ricardo)
To Reproduce:
1. Unzip project.
2. Build in command line without the "-nographics" parameter. Run the App.
3. Build in command line with the "-nographics" parameter. Run the App.
Expected:
1. Same results.
Actual:
1. Different results. When built using "-nographics" the gfxDevice is null. Therefore it will throw:
if( !m_Shader )
{
printf_console("Unsupported: %s\n", m_ShaderName.c_str());
}
After failing to parse the shader.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment