 |
|||
Almost a month ago I said we’re preparing reports of Unity Web Player hardware statistics.
Well, here they are: unity3d.com/webplayer/hwstats
Operating system versions, desktop resolutions, graphics driver versions, shader models, memory sizes and some more. All broken down by quarter so some sort of “trends” can be seen (sure, changes can be caused by general hardware change or simply different people groups playing different games).
Enjoy!
Pretty much everyone knows Valve’s hardware survey - it’s a very valuable resource that shows what hardware the typical “hardcore PC gamer” has (that is, gamers that play Valve’s games).
However, the “casual gamer”, which is what Unity games are mostly targeted at, probably has slightly different hardware. “Slightly” being a very relative term of course.
Lo and behold - we have a glimpse into that data.
Read the rest of this entry »
People have been asking: why built-in shadows don’t work on Unity’s terrain? (here, here, …) Yes, right now (Unity 2.0.2) they don’t. Why - because we didn’t have time to make them work yet. Both terrain and built-in shadows are new features in Unity 2.0, and those two don’t happen to just work together.
Here’s a glimpse into what is needed to get it working. Read the rest of this entry »
A request I’ve gotten from quite a few new users is to have some indicator axes in the Scene View showing you what is up and what is down. There is a reason why they are not there, and it ties into the core of my Job here at UT: GUI design. I’ve wanted to comment a bit on this.
We’ve got a feature we want to do — it’s something we call “intermediate mode render calls”. The idea is that some script could say:
Draw( position, rotation, mesh, material );
And that would make the mesh appear with the given material at the given position on the screen, and it would just work with pixel lights, shadows, projectors and whatnot.
