Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0a1
2018.3.2f1
Issue ID
1118833
Regression
Yes
Building an application generates WinPixEventRuntime.dll when "Development Build" is unchecked and "Architecture" is "x86_64"
How to reproduce:
1. Create a new Unity project
2. Navigate to File -> Build Settings... -> make sure "Development Build" is unchecked and "Architecture" is "x86_64"
3. Build an application
4. After the Building is complete, observe the Build location folder
Expected result: the WinPixEventRuntime.dll file is not found
Actual result: the WinPixEventRuntime.dll file is found even though the "Development Build" is unchecked
Reproducible with: 2018.3.3f2, 2019.1.0a14, 2019.2.0a2
Not reproducible with: 2017.4.19f1
Comments (2)
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Mafutta
Aug 28, 2021 23:55
still in 2020.x
Bip901
Aug 05, 2019 10:59
Are there any temporary workarounds for this issue? I'm working on a huge project so I have to freeze on version 2018.3.0f2 (64-bit).