Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
0
Members

Can't make a working build on Windows 10, MS Surface 3

A topic by gmg created Mar 19, 2016 Views: 595 Replies: 1
Viewing posts 1 to 2
(1 edit)

I have been able to build and run Superpowers Game on my Mac without any problems, but I can't seem to get it working on my MS Surface 3 running Windows 10. I have the latest node installed, the npm build script executes correctly. There are some warnings about graceful-fs and lodash that concern me.

However, when I launch it, firstly the server hub does not seem to be working properly. I get JavaScript errors creating new projects, and the project does not display in the list until I refresh. The errors -

  • SCRIPT5022: SyntaxError - index.js (2348,13)
  • SCRIPT5007: Unable to get property 'classList' of undefined or null reference - index.js (2260,9)

Then, when I try to edit a project, the tool bars display in red and it does not connect to the server, so I am unable to create assets. There is another JS error -

  • SCRIPT5022: SyntaxError - index.js (4767,9), seems related to tabstrip

Running in IE11 results in different errors. I haven't tried any other browsers yet, as I have read that they don't work so well on the Surface.

The errors seem to be related to the html elements and the tabstrip, both of which I know have been under development recently. I'm just wondering if the code on GitHub currently runs out of the box. I haven't tried to run a build on my Mac for a while, so all I know is the it worked fine on there a few weeks ago, following the instructions in the docs. The 0.19 build works fine, but I want to work with more up-to-date code, and I want to work on some of the plugin code.

Any ideas?

Weird, Superpowers dev work well on my Surface pro3 with Windows10.

Work on google chrome only for Superpowers (Firefox and IE have a lot of problems).

I think the problem comes from NodeJS version. Recently a complete rebuild of packages is required. So with SP 19 try with the LTS version of Node or Try the dev version with NodeV6.