I am evaluating the Unity 3D Engine. There are multiple questions below(I am aware). Asking all these questions separately would cause much duplication in the various explanations. I seek rather a complete answer that addresses the concerns listed. Can anyone elaborate on these questions and return a write-up that covers all of the concerns listed along with a complete explanation on how all of the different parts are used whether inclusive or exclusive of each other.
Some of my early concerns:
- can VB.NET be used instead of C# (or BOTH?) in anything coded via the (object) tag?
- can and is javascript (be) used via the (object) tag or is it used as standardly done on the clientside with a call in the (head) of the page? or possibly the question is: how are the javascript scripts in Unity hooked/delivered into the overall scheme of the web page, the .unity file, the .js files, and any other associated files?
- is the (object) tag smart enough to use the modules(passed) from the cache rather than downloading them each time the page is brought up?
- can the Unity Scripts access HTML objects on the page(text boxes, etc) outside of the Unity predefined screen object?
- can the Unity plug-in be delivered to the clientside from my own servers or must it be downloaded from the Unity Web Site?
- is the plugin the unity.player?
- what files are downloaded for the app(game) to run on the web page and what do these files contain(language, compiled, interpreted, speed, file names, etc...)?