Search Issue Tracker
By Design
Votes
0
Found in
4.5.0b5
Issue ID
601194
Regression
Yes
Master configuration will show Development Build if project was exported with Development Build checked
Master configuration will show Development Build if project was exported with Development Build checked
Steps to reproduce:
1. Open any project or attached one
2. Check Development Build and build to folder
3. Open exported Visual Studio solution, select Master configuration
4. Deploy it to device. Development Build watermark will be shown, but Profiler will be disabled.
Why is this by design?
This is intended behaviour.
When Development Build is selected, ENABLE_PROFILER is defined and can be used in user scripts, resulting in different binary (with some profiler related code, not intended for final release).
Documentation also mentions this: development watermark is shown if either scripts were compiled with 'Development Build' or non-master configuration is used or both.
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