Game 30% done on HTML5. Maybe it was a bad idea. Should I change to Unity3d? [on hold]
- by Dokkat
I'm creating a 3d game on HTML5. It's 30% complete and the hard part is already coded. The server is on node.js.Now I'm realizing that maybe it was not a wise choice. This is because I realized:
Three.js still has many bugs. I don't see the same thing on every machine. Each browser, OS, can give different results. I'm afraid my clients will have a great stress installing my game properly.
I have tons of sprites and models on my game. I wonder if my clients will have to load all them again everytime they want to play?
I wonder if a Node.js server will be fast enough to handle it, and I'm afraid it won't be scalable.
What would you advise me? Should I continue and finish the game on HTML5 or is it better to remake it on something else, like Unity3d for the client and (what?) for the server?
