Search Issue Tracker
Fixed in 2019.1.X
Duplicate in 2018.4.X
Votes
0
Found in
5.6.1f1
Issue ID
922692
Regression
No
Conditional compilation problem with RuntimeInitializeOnLoadMethod
Repro steps:
1. Open "DELETE.zip" project
2. Clear the Console and enter Play mode
3. Exit Play mode and check the Console output (Test A, B, and C should be output)
4. "File" -> "Build Settings..." -> "Build" -> Build the project for Windows Standalone
5. Open the built project
6. Go to the directory where you built the project -> "...._Data" -> "output_log"
7. At the very bottom notice that only Test B and C are output
Expected result: Test A, B, and C should be output to the Windows Standalone output log
Actual result: Test A isn't outputted to the output log
Fixed in: 2019.1.0a6
Reproduced with: 2017.2.0a4. 2017.1.0b10, 5.6.2f1, 5.5.4p1, 5.4.5p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment