31–40 of 74 posts
Does anyone know if they updated their default GUI elements (they were pretty rudimental in v3), so you don't need to use custom GUI elements?
They are planning the GUI update for the later 4.x releases. At-least that's what i could guess from the forums.
disclaimer: I spent the last three years making Unity. You can share code between projects by having seperate visualstudio projects that create a managed library. just put the managed library into your assetsfolder. it live reloads as smoothly as when you edit just one script. While I'll be the first to admit that we have some things that you can consider basic that don't work as well as they could yet, the perspecti…
Earlier quoted context omitted.
How about never? The Ouya is a pig-in-a-poke at best. There's nothing compelling about it that you couldn't do with an ARM evaluation board (in fact, it's more limited), the average console gamer opinion regarding it is 'meh' and it will be obsolete the moment it arrives as what you can buy for $100~ in the ARM SoC space is getting crazier every minute. The Mali-400 on http://www.hardkernel.com/renewal_2011/products/…
There is rather a big difference between a board and a consumer product. Most people are not keen on building their own system from scratch - and so far there isn't another 99$ game console out which is pretty much what OUYA seems to be about. Not to mention a console specific software stack. The fact that there is really hardware already around for that price makes me rather optimistic that OUYA isn't just the dream…
Earlier quoted context omitted.
Version control on Unity isn't as bad as you describe. Go to Edit > Project Settings > Editor, then set Version Control to Metafiles. If you have a Pro license, also set Asset Serialization Mode to Force Text. The downside is that this litters your project with .meta files, but that lets you work with external version control pretty easily. Edit: You should also exclude the Library folder from your VCS, because with…
You're responding to an argument I didn't make. Version control works fine. The problem is that there is no method to build libraries and share them between multiple projects, since all the code needs to be under the Assets folder of each project. There is no support for classpaths. If you update the code in one project, you have to copy the file to the other. Or have some equivalent method of doing so outside of Uni…
Ever since unbuntu ruined their desktop with the same brand name, I flinch a little everytime I hear the word
-the ability to launch a command line will be gone, because the command line could allow accidental damage to your system
-it will not be possible to minimize or maximize windows (if you can still call what they have turned it into "windows"), those buttons will instead have been replaced by a shopping basket, and a helper assistant button, respectively
-because top left is not exotic enough, the window close button will now be in the bottom left
-launching more than one window of the same application will not work because this is confusing
-the menu of a program will be on the right side of the screen. You'll have to hover the mouse there first, then wait for a list of helpful suggestions to slide into view, scroll through it with an awesome fluent scrolling animation, and then finally at the end will be the menu options.
-the file system is abstracted away. Directories are confusing, so the concept of directories is hidden. Instead it presents the files as if they're in one large "basket". Extensions won't be shown because those, too, are not understood very well by most users.
-the scrollwheel, middle and right mouse button, and keyboard shortcuts, are ignored, to unify the desktop better with touch interfaces of mobile devices
Earlier quoted context omitted.
There is rather a big difference between a board and a consumer product. Most people are not keen on building their own system from scratch - and so far there isn't another 99$ game console out which is pretty much what OUYA seems to be about. Not to mention a console specific software stack. The fact that there is really hardware already around for that price makes me rather optimistic that OUYA isn't just the dream…
You don't seem to understand that Android already is first. This is a $100 Android box with an 'app store of its very own!' and not much beyond that. We've already got Android and it's not difficult to make a similar enclosure. We've already got better hardware! The cost of porting from Ouya to other Android consoles in general is almost assuredly trivial to possibly zero depending how lazy they are about their softw…
I am an ex Web developer who got into game programming with Unity over the last 3 years. Its been amazing, i have learned a ton by using C# and actually needing to apply Math knowledge to a real world project. Unity is awesome but also has some issues, but as i havent really worked with the other big engines, i guess these have similar issues. * Version control is a pain. We used Git (with Github) all the time but un…
Earlier quoted context omitted.
Can you just checkout a subrepo into your assets?
Yes, this is the only way the handle it. Git subrepos make this a hassle though, in our experience. It's the one thing that SVN would do much better.
I would be curious to see how Ouya will fit in there, yes Android is supported, but at what point will Ouya be supported or not by Unity 4?
As I understand it, the only departure from standard Android UIs is that there's a sort of in-game menu, and games may need to be modified to support that.