Unity 5.4.2f1 blank screen.

Questions & Answers
1

LICENSE SYSTEM [20161014 20:53:27] No start/stop license dates set

LICENSE SYSTEM [20161014 20:53:27] Next license update check is after 2015-09-26T02:53:23

Built from ‘5.4/release’ branch; Version is ‘5.4.2f1 (94e3a60ee258) revision 9757606’; Using compiler version ‘160040219’
OS: ‘Windows 7 Service Pack 1 (6.1.7601) 64bit’ Language: ‘en’ Physical Memory: 6039 MB
BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 0, IsPro: 0
Initialize mono
Mono path[0] = ‘D:/Unity/Editor/Data/Managed’
Mono path[1] = ‘D:/Unity/Editor/Data/Mono/lib/mono/2.0’
Mono path[2] = ‘D:/Unity/Editor/Data/UnityScript’
Mono config path = ‘D:/Unity/Editor/Data/Mono/etc’
Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y,address=0.0.0.0:56064
ListPackages failed, output: {
“name”: “unity-editor”,
“version”: “5.3.0”
}
npm ERR! code 1

InstallEditorPackages failed, output: npm ERR! addLocal Could not install C:\Users\Nags\AppData\Roaming\Unity\Packages\2>null
npm ERR! Windows_NT 6.1.7601
npm ERR! argv “D:\Unity\Editor\Data\Tools
odejs
ode.exe” “D:\Unity\Editor\Data\Tools
odejs
ode_modules
pm\bin
pm-cli.js” “install” “unity-editor-home.0.1.35.tgz” “unityeditor-cloud-hub.0.0.13.tgz” “unityeditor-collab-history-0.0.27.tgz” “unityeditor-collab-toolbar.0.0.46.tgz” “–cache=./.npm” “–json” “2>null”
npm ERR! node v0.12.7
npm ERR! npm v3.3.3
npm ERR! path C:\Users\Nags\AppData\Roaming\Unity\Packages\2>null
npm ERR! code ENOENT
npm ERR! errno -4058

npm ERR! enoent ENOENT, open ‘C:\Users\Nags\AppData\Roaming\Unity\Packages\2>null’
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Nags\AppData\Roaming\Unity\Packages
pm-debug.log

installJavascriptPackages failed

(Filename: C:/buildslave/unity/build/Runtime/Utilities/Argv.cpp Line: 171)

Error loading file:///C%3A%2FUsers%2FNags%2FAppData%2FRoaming%2FUnity%2FPackages%2Fnode_modules%2Funity-editor-home%2Fdist/index.html#/project/recent

(Filename: C:/buildslave/unity/build/Editor/Platform/Interface/NativeWebViewWindow.cpp Line: 50)

Can someone please help. I have followed the copying of tar balls from Unity installation to AppData solution as well but it gives a blank screen always. Please help.

2

I fixed it by editing, in your case, D:\\Unity\\Editor\\Data\\Tools\ odejs\ ode_modules\ pm\\bin\ pm-cli.js by removing the 2>null argument.

Add the following before log.verbose('cli', process.argv)

  var twoNull = process.argv.indexOf('2>null')
  if (twoNull > -1) {
    log.info('twoNullFix', '2>null was found. Removing')
    process.argv.splice(twoNull, 1)
  }

After that, start Unity and you will be able to see the window.

4

I wasn’t sure if by copying tar balls you meant extracting files from the .tgz files and putting them into app data. This worked very well for me:

Find packages unityeditor-cloud-hub-0.0.1.tgz and unity-editor-home-0.0.7.tgz in C:\Program Files\Unity\Editor\Data\Resources\Packages.
Create folders node_modules\unityeditor-cloud-hub and node_modules\unity-editor-home in C:\Users%user_name%\AppData\Roaming\Unity\Packages.
Extract dist folder and package.json from unityeditor-cloud-hub-0.0.1.tgz and put into unityeditor-cloud-hub, dist folder and package.json from unity-editor-home-0.0.7.tgz and put into unity-editor-home.

I found this method in this answer: http://answers.unity3d.com/questions/1110300/unity-530f4-32bit-blank-screen.html?page=1&pageSize=5&sort=votes

5

Thanks to @Perro it worked just perfect for me!

Before I had to solve another issue to install Unity to a folder which path doesn’t contain any spaces, because the error in log was saying something like ‘cannot find a file at D:\Program’ (I pointed the installation into D:\Program Files\Unity). Obviously there is an bug somewhere in the installation script. :wink:
Checking the log file helps to understand a possible problem: c:\Users\AppData\Local\Unity\Editor\Editor.log

6

I just add one more Detailed explanaition of the fix above:

In the file D:\Unity\Editor\Data\Tools
odejs
ode_modules
pm\bin
pm-cli.js

Add:

   var twoNull = process.argv.indexOf('2>null')
   if (twoNull > -1) {
     log.info('twoNullFix', '2>null was found. Removing')
     process.argv.splice(twoNull, 1)
   }

After the lines

  if (path.basename(process.argv[1]).slice(-1) === 'g') {
    process.argv.splice(1, 1, 'npm', '-g')
  }

Ultimative the file looks like this:

#!/usr/bin/env node
;(function () { // wrapper in case we're in module_context mode

  // windows: running "npm blah" in this folder will invoke WSH, not node.
  /*global WScript*/
  if (typeof WScript !== 'undefined') {
    WScript.echo(
      'npm does not work when run

’ +
'with the Windows Scripting Host

’ +
"‘cd’ to a different directory,
" +
"or type ‘npm.cmd ’,
" +
“or type ‘node npm ’.”
)
WScript.quit(1)
return
}

  process.title = 'npm'

  var log = require('npmlog')
  log.pause() // will be unpaused when config is loaded.

  log.info('it worked if it ends with', 'ok')

  var path = require('path')
  var npm = require('../lib/npm.js')
  var npmconf = require('../lib/config/core.js')
  var errorHandler = require('../lib/utils/error-handler.js')

  var configDefs = npmconf.defs
  var shorthands = configDefs.shorthands
  var types = configDefs.types
  var nopt = require('nopt')

  // if npm is called as "npmg" or "npm_g", then
  // run in global mode.
  if (path.basename(process.argv[1]).slice(-1) === 'g') {
    process.argv.splice(1, 1, 'npm', '-g')
  }


   var twoNull = process.argv.indexOf('2>null')
   if (twoNull > -1) {
     log.info('twoNullFix', '2>null was found. Removing')
     process.argv.splice(twoNull, 1)
   }
  log.verbose('cli', process.argv)
  var conf = nopt(types, shorthands)
  npm.argv = conf.argv.remain
  if (npm.deref(npm.argv[0])) npm.command = npm.argv.shift()
  else conf.usage = true

  if (conf.version) {
    console.log(npm.version)
    return
  }

  if (conf.versions) {
    npm.command = 'version'
    conf.usage = false
    npm.argv = []
  }

  log.info('using', 'npm@%s', npm.version)
  log.info('using', 'node@%s', process.version)

  process.on('uncaughtException', errorHandler)

  if (conf.usage && npm.command !== 'help') {
    npm.argv.unshift(npm.command)
    npm.command = 'help'
  }

  // now actually fire up npm and run the command.
  // this is how to use npm programmatically:
  conf._exit = true
  npm.load(conf, function (er) {
    if (er) return errorHandler(er)
    npm.commands[npm.command](npm.argv, errorHandler)
  })

})()
3

Hi Perro,

I tried this edit and still getting same error. Can you post the entire contents of the “updated” js file? Maybe I missed something.

thanks,

v.

7

how do i save it after editing the npm-cli.js ??