Search Issue Tracker
Fixed in 5.3.5
Votes
0
Found in
5.3.1p1
Issue ID
760234
Regression
No
Cache Server uses old version of Node.js (0.6.6)
Steps to reproduce:
1. Download the cache server from our site (http://unity3d.com/unity/collaboration/)
2. Extract the downloaded package
3. Navigate to one of the 'builds' folder
4. Notice that it uses a very old version of node.js (0.6.6 to be exact)
Workaround: Download newer version of node.js (currently newest is 4.2.4) from their official page (https://nodejs.org/en/download/) and replace it with the one used by cache server (also, the obsolete method "path.existsSync" should be replace with "fs.existsSync" in the scripts)
There is also a 64-bit version, which we should use to prevent out of memory problems.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment