Search Issue Tracker
Fixed
Votes
0
Found in
2019.1.2f1
Issue ID
1237920
Regression
No
[Perforce] Environment variables are not preserved when project is launched through Unity Hub
How to reproduce:
1. Open Unity Hub
2. Add the attached project to the list
3. Open the added project
4. In the top toolbar, click Tools->Try perforce
5. Inspect the Console Window
Expected result: A message appeared with information about the Perforce version
Actual result: Error "Cannot find the specified file" is thrown
Reproducible with: Unity Hub 2.3.1
Notes:
1. Not reproducible on Windows
2. Can be worked around by launching project trough the Terminal (<PathToUnity>/Contents/MacOS/Unity -projectPath <PathToProject>)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment