Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.5.1f3
Issue ID
616179
Regression
Yes
Symbols (PDB) no longer being shipped for non-Development Windows
Under previous versions of Unity the Windows Standalone player came with a .PDB file containing debug symbols for all variations of the player (i.e. both 32bit and 64bit, and both Development and Release builds).
In 4.5.1 the file structure in PlaybackEngines has changed and now both win32_nondevelopment and win64_nondevelopment players no longer include symbols.
Comments (1)
Add comment
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
RPGCoder
Oct 21, 2015 01:07
I have Unity 5.1.4f1 installed and there are no PDBs for the non-development versions. Which version of Unity 5 was this fixed in?