Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b4
Issue ID
934437
Regression
Yes
output_log.txt file is created in AppData/LocalLow/CompanyName/ProductName instead of the usual buildName_Data folder
The file appears in C:/users/UserName/AppData/LocalLow/CompanyName/ProductName instead. But the build was ran on Medium Integrity Level and Use Player Log was checked on in the Player Settings.
To reproduce:
1. Create a new project
2. Build the project for Windows standalone
3. Launch the build
4. Exit the build, open the buildName_Data folder and look for output_log.txt file
Expected: output_log.txt file is created in buildName_Data folder after the build was launched.
Reproduced in 2017.2.0b3, 2017.2.0b4, 2017.3.0a1
Did not reproduce in 2017.1.0p1 2017.2.0b2
Regression introduced in 2017.2.0b3
By design: user can specify a path using the -logfile commandline argument
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment