Unity has their own and if I'm not mistaken Vision has their own.

But the support is of a nature that seriously limits you. The manner you do things is always in scripts, so it completely negates the OO features of C# and you don't get to use the actually useful parts of it like the GUI API so it's completely meaningless.

Lots of teenagers and people making cell phone games use it, sure. It would also be fine for a corridor shooter or other simple game.[/quote]
First of all, there's nothing wrong with an engine being good for 'cell phone games' or targeting a particular niche.

That said, you seem to be ignoring the facts completely. Just to cite a couple examples, Unity was used by EA for some of their games, and it was also used for FusionFall. Like any engine, Unity has its own niche and its own limitations, but to say that it's only good for simple games shows that you don't know much about it.

Your interface method between the engine and the coding language forces you into a scripting paradigm (interface is all created by a scripting call), so it makes no difference what language you use you are forced to do everything in a simple manner.[/quote]
Sorry, that doesn't make any sense. You can write whatever code you want, and it can be as simple or complex as you want. If you want, you can interact with the engine minimally (e.g. by manipulating object transforms only), and do everything else yourself (more or less) in your own code.

From my own experience working with Unity, I can tell you with certainty that you are not forced to do everything in a 'simple manner'. (I really can't imagine where you got that impression.)

In Unity you can't even reuse code between projects[/quote]
Absolutely, completely, 100% false. What gave you that idea?

let alone make a real OOP project (unless you have the very expensive full source version).[/quote]
I'm not sure what you mean by a 'real OOP project', or why you couldn't make one using Unity.

So given that last little tidbit and the comments you made that unity does nothing to limit OOP which of us is unfamiliar with the engine?[/quote]
Based on your comments, I can say with almost complete certainty that I'm more familiar with it (and understand it better) than you.

Unity not only limits OOP but it pretty much eliminates any kind of basic organization you could get from using straight up C as well.[/quote]
I'm not sure what you mean by that.

And you know the little API that C# is a part of, the .NET frameworks? You can't use that either, not that it would be too helpful due to the other constraints, but really it's the only thing truly good about C# in the first place.[/quote]
What are you talking about? Of course you can use .NET. Not every module is available, but you can absolutely use .NET. (Where are you getting this information exactly?)

Like I said, I don't want to be argumentative, but people do read these threads, so I think it's important to counter misinformation when it comes up. Maybe I'm just not understanding your points, but everything you've said so far seems to indicate that you know very little about Unity or how it works.

And sure you can share code...via cut and paste or copying a whole file into another project.[/quote]
How is that not sharing code? If you write a class for project A, and then re-use it in project B, isn't that sharing code?

Just as an example, what about heavily templated libraries in C++? Generally, you re-use that code by referencing the same file from multiple projects. How is that any different?

In any case, although I haven't done it myself, I believe you can use your own assemblies in Unity (although maybe not in the browser version). If that is in fact the case, then it completely negates your point (whatever it is).

And back to .net, you can't use all the GUI code in the API you have to rely on the simple tools provided or make your own based on them, which drastically limits your ability to separate your code from the engine.[/quote]
Ok, earlier you said you couldn't use .NET. So are you now at least acknowledging that you can use .NET?

And what GUI API are you talking about? Are you talking about something from .NET, like Windows.Forms or something? What is it that you can't use exactly?

Unity has a built-in GUI system, but I probably wouldn't use it for production code. There are some good third-party solutions though, and you can roll your own just like you would with any other engine. I really don't understand what you're getting at about the GUI stuff though. If you mean something from .NET, then what game engine allows you to use GUI-related features of .NET in a scripting environment? Can you clarify?

And that's it in a nutshell, everything is tightly mashed in to an ubertool you have little control over.[/quote]
This is the closest you've come to a valid point :) When you use a development tool like Unity, you do trade some control for ease of use, and that's something you have to weigh when deciding what tool to use. However, based on everything you've said, I think the 'giving up of control' that you're talking about is very different from the reality of it.

Complicated gameplay and GUI? no.[/quote]
Again, you're 100% incorrect. Unity imposes absolutely no limitations on the complexity of the gameplay or the UI. Why do you think it does?

but it's a different story to make cell phone games and make something like a flight simulator or old school RPG. For unity that is virtually if not entirely impossible.[/quote]
Where are you getting these ideas? There's absolutely nothing about Unity that would make it impossible to make an RPG or a flight simulator. Why do you think these things can't be done?

I apologize for being contrary; it's easy to fall into this trap on occasion when participating in forums such as this one :) But, it is a little frustrating when people post misinformation persistently. A lot of people read these forums, and some may not have the background or context to separate the good information from the misinformation. So, I do think it's important to counter misinformation where possible.

To be honest, it really sounds to me like you don't understand how Unity works. Like I said earlier, it's not for everyone (no tool is), but if you don't have a good grasp of it yourself, I'd at least refrain from discouraging others from using it.