Oxygine vs uScript + Unity3D

Most interesting is ability to build C++ Oxygine application for Web via Emscripten. So you write C++ code and it will compile it to HTML5/JS.

All of them available publicly at github.

• oxygine-movie for playing Theora movies with alpha channel
• oxygine-sound player for ogg sound/music with streaming
• oxygine-freetype library
• oxygine-billing for in-app-purchases on Android/iOS
• oxygine-spine for playing Spine animations
• oxygine-magicparticles for playing particles made with MagicParticles

If you are familiar with ActionScript3/Flash API, then you will find it easy to begin working in Oxygine. Oxygine is much like Flash in C++, as its Event Handling model is very close to that of ActionScript 3 and SceneGraph.

Oxygine is written in C++. It provides easy to use API, which is designed with "do more with less code" philosophy. It uses a managed scenegraph system that takes care of rendering and updates, and provides ability to extend with custom rendering and updates.

Oxygine is a free framework that works on OS X, Windows, Linux, iOS, Android, HTML5. It's licensed under MIT with source code available on GitHub.

It's very rare to experience bugs with Oxygine.

Using oxygine-movie extension for Oxygine you could play in your game any videos encoded with Theora codec.
You movie could have alpha channel and used as simple sprite instead of classic spreadsheet animations.

uScript's nodes are a visual representation of actual code blocks, and it takes advantage of C#'s reflection capabilities to automatically create nodes for any scripts it finds in your project, regardless of the source. This makes it inherently compatible with pretty much everything.

Custom nodes can also be created by hand, for cases where the automatically created ones contain more elements than they actually need.

Modeled after UDK's Kismet (the predecessor to UE4's Blueprint), uScript's scripts resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish.

Nodes are translated directly to C# files in your project. This is great for learning to code, and also for advanced users who can use uScript for fast prototyping and then further optimize the scripts if necessary.