I'm not sure if this is a bug or intended.
But it seems in multiplayer browser's cant talk to nodewebkit. It will come up with 2 peers connected on both screens, but they seem unable to sync to each other or send messages.
I have tried hosting on Chrome and Firefox, with a nodewebkit as a peer, to no avail. And the other way round.
I have tried hosting and peering on the same computer, over multiple computers on the same network, and on a virtual private server.
Attach a Capx
Multiplayer example real time game.
Description of Capx
____ Concise description of what this CapX does ____
Steps to Reproduce Bug
____ What happens? ____
Unable to sync objects or send messages
____ What do you expect to happen? ____
I expected nodewebkit would work normally.
Operating System and Service Pack
____ Your operating system and service pack ____
I tried on Windows 8, Windows 8.1, and Windows server 2008 R2
Construct 2 Version ID
____ Exact version ID of Construct 2 you're using ____
(This happened in 166 as well)
Develop games in your browser. Powerful, performant & highly capable.
Closing as will be fixed by subsequent node-webkit update. Node-webkit is currently still using Chromium v32, which is presumably incompatible with the latest Chrome v34. The next node-webkit update should fix this.