Proxy server example does not work for me

[UserMcUser]

Not sure what I've done wrong, but I can't get the example proxy server to actually work.

It starts, connects to the real server, and opens the proxy port and accepts incoming connections. Clients can connect to the proxy and can choose consoles. However once the client tries to join the simulation (does not matter if you join before or after the server starts the simulation) the proxy-ed client process freaks-out - it maxes out a single CPU core and starts eating up memory until it crashes. Meawhile, simpleProxy keeps running, echoing packet events to the console until the client dies.

Artemis is v2.1.5
node.js is v0.12.4
Tried Windows 7 32bit, OS X 10.6.8, and Ubuntu 14.4.2 LTS with the same basic results. Oddly with OSX, Artemis doesn't start allocating memory, just maxes out its CPU.

[IvanSanchez]

I never really tested out the proxy server - it's meant to be a very naïve example. I'll try to reproduce later and see if there's any easy fix.

The real goal is to make a proper single-ship proxy (in a separate repo, with persistent world model for reconnections, etc), so I'm not really worrying a lot about the simple proxy example.

[UserMcUser]

OK, thanks.

I'm trying to make a proxy that will intercept and re-write the playerShip packet to replace the mainScreen variable - that way you can have a main-screen view that stays fixed and doesn't change with the primary mainscreen.