Quote:
Originally Posted by player.elite
Hey, I started working seriously with Unity today and I have some questions about the project  |
Your already in my skype sir! and always free to ask.
Personally, I strongly criticize Unity 3D as platform for serious game developments. Known fact is - "browser game without downloads!" a biggest lie, caused by game resources chache on your PC. If your look to in this cause - what the difference between stand alone and browser app? Generally they are identical. If present Unity3D as game engine - that is poor variant (imho), i prefer Unreal Engine or self-maded engines.
Here the some reasons why:
1) Software Security. Unity can be decompiled, sources - leaked and etc. C# and supported by Unity Engine lang's - can be easy reversed. Engines written on C99, C++ - lack of this. In C/C++ cause max what you can return - asm code. C# - full source code.
2) Low level propietary libs. You cant change a render (and other) capabilities of Unity3D, becouse they libs are propietary.
I guess - using Unity3D, in serious project - is a biggest mistake. Try to Unreal, Irrlicht, Ogre for example. In both causes - game resources (2++ Gb for example. Models, Musics and etc) stored on players PC. Client app is better alot, becouse, that is a fact - Unity 3D have a memory leaks on some browsers, irrational resource usage, and mid-to-low stability. Client app - lack of this problems if they are coded in a "right way". Remember one important thing. Plugins - never provide a native support for working with OS, Drivers and etc. Stand-alone client - do that. And for example WebGL - do that too.
Here the little scheme how them works really:
Browser (in example Firefoxy), initiate Plugin Container, and Client APP.
1)Client app send requests for plugin container, him serialize them and send to plugin instance(initiated by container).
3)Establish communication uplink.
4)Asks game data. "Compiled" Unity 3D plugins and scripts in binary compiled by WinAPI (Unity3D plugin, initiator the call).
6) Code Returns to plugin container, and become to client. Client sends some callbacks to plugin.
8) Plugin initiate call in plugin container for graphics. Container calls WinAPI--->Native low level libraries for provide graphics.
10-11(b) - Data returns to the Client (if shortly lol
). Client send some callback to plugin container and browser.
Start play! lol.
Well for some small games - i am agreed, usefull. But if you wanna using Unity3D with their brainfck paradigm in large project... someone, call the medics please for that person.
Essence of this post - if you have a possibility for create a serious game - do that with client. Dont try re-place them by Unity or Flash or WebGL. Plugins are good for small and simple games such as DO. Good choice for indie developer. Nothing moar. If you want a serious game with a great quality and perfomance - client based game is your choice!
Kind Regards.
:')
