Hi everyone,
I just heard over at Androidforums.com, that Unity doesn’t run on these devices without a freeze. Madfinger was forced to pull Samurai 2 for these devices and that seemed to have happened to Battleheart before.
Please talk about such problems, when you encounter them. As a Unity license holder I check in here daily and it is kind of scary to hear from raging consumers, that your game engine has a bug for at least the last 4 weeks on the hottest devices on the market and nobody who encountered it said something, instead everyone quietly drops support for the best devices from one of the biggest manufacturers.
It took a while, before we figured out the Galaxy S 30 MB Limit etc., but it is not ok that I heard about this problem by chance on a official forum and not here where it belongs. Here is the thread, where a bunch of angry consumers are crucifying Madfinger for pulling the game: http://androidforums.com/android-games/364036-samurai-ii-vengeance-pulled-e3d-sensation.html
2 weeks on the hottest device that is not existant outside of Vodafone, keep that mind in mind. Until later next month, Vodafona has western globally locked it down from any other distribution path due to an exclusive contract with HTC.
Also the GPU is new and the drivers totally untested due to that so nobody can be crucified for the Android driver syndrom aside of HTC which did again not put their stuff through realistic testing on the market place top 100 as on each OS update for the other devices too and fixing the issues, they care that the device works, not that it works compliant to android standards
Its unfavorable, no question, but get used to it, its Android.
There is a reason why EA has device checks in their games locking out new devices for an eternity, I’m still waiting to play Sims 3 on my Galaxy S2 for example
I don’t have a problem with the device not being supported yet, since Unity and Qualcomm are partners I’m sure it will get fixed soon, I just wish that people would talk more about these matters here.
Everybody is really active in discussions when there are problems with 3rd party ad integration or other monetization problems, but when a problem arises with a device, it takes too long until it is common knowledge that there is a compatibility problem. If everybody just ticks off the compatibility to the device on the publishing site when a support request comes in, it will just hurt Unity.
I rarely hear about support requests here, but I’m sure Mika mobile, Madfinger and Galapagos had at least a dozen people contacting them, who wanted to know why their bought games don’t work. All I’m asking is that people talk more about these problems, because if one Unity game has problems on a device, probably all games will run into similar problems on this hardware sooner or later.
Being that the EVO 3d just came out I don’t think a lot of people can talk to much about it. I am still waiting for the EVO 3d my self and was told it wouldent be out till the begining of July.
Unsure if they have that many support requests. Keep the automatic refund time period in mind, if people find it to not work, its just refunded with a few clicks.
Also a few dozen is nothing, thats insifignicant enough to ignore business wise as a few dozen on a few ten thousand to a 6 figure user number is not significant in any way.
Its also not to expect that either of the two devices will gain any reasonable install base or become a leader like the desire, the 4-6 devices / year route HTC has been going is preventing that by definition already (without considering that most that could be interesting are locked in with their HTC desire from last year till 2012). And as mentioned, till next week or even some weeks later its vodafone lock in if you want to get the Sensation at all
and if you consider it, you talk about it with UT directly or on the beta lists, not here where it has no meaning other than bragging which is the most worthless form of timewaste if you have an issue to solve or the situation to handle
I’m already blocking a lot of devices on the market, what’s 2 more?
Seriously though, there’s not much I can do besides block new hardware when I find out it isn’t compatible. I didn’t think to run here and start posting about it, but I guess the community at large ought to know. I know the guys at Unity are aware of the issue, I’m sure they’ll address it if and when they can, so you needn’t lose any sleep over it.
K just got done talking to the Sprint store and I pick mine up tomarrow. They also told me there was a spider man 3d app that comes with it, but they have been having problems with that app. So it would be safe to say that there is gona be some upgrades to the EVO 3d.
Hopefully that statement is true. Whether or not HTC is incompetent is irrelevant since other developers have game engines running flawlessly on the MSM8x60/Adreno 220 while games based off of the Unity engine are not. I’m sure there are improvements that can be made on both ends of the spectrum here.
I can’t speak on behalf of the Unity developers by any means, but I know for a fact this issue is on their radar. Whether it turns out to be a simple fix or a catastrophic, unfixable problem is anyone’s guess, but they have a pretty good track record. I don’t think there’s cause for alarm, nor can I really blame them for not being 100% future proof when the android platform is a constantly moving target.
most of those engines also run worse to much worse than Unity though or have only 1 title to support not beyond a thousand potentially of any genre. its easier to fix an engine for exactly one case than for any case.
it also allows very fast fixing within days as fixes to unity require much more indepth testing to not break the other XXXX games.
So if your need and desire is to be always up to date, you will have to write your own and pay your own set of engine architects and engineers to fullfill that target …
But if you are fine with waiting until UT has found the issue, tested the fix and then deploying it, I think its a great place cause UT is pretty surely going to fix it if its fixable and not on behalf of broken drivers only where HTC has to fix it (I doubt you will see a “break unity” to comply to something thats broken out of the box - Galaxy S on Android 2.1 had a broken os too that was up to samsung to fix, happened in 2.2 and thats what unity requires to run on galaxy s), so primarily a matter of time less of if
I like the engine can’t wait to see if this gets fixed. I really think its good for developers and users as a whole, only problem is if something goes wrong the actual developer of an app using Unity can’t really do anything. Loving the EVO 3D so powerful but I like a lot of the Unity Engine games so hope there’s a fix soon. Guess I’ll be playing all my 3D gameloft games till then.
I appreciate the responses, and I hope I’m not sounding hostile in anyway. I do appreciate what developers do and what Unity has allowed developers to accomplish on multiple platforms. It does get somewhat frustrating though when everyone points their finger at someone else when it’s possibly a problem on their end as well (non of your previous posts showed any indication that UT was actually looking into the problem, but that everything was in the hands of HTC).
Yeah I’ve test a ton tested of games all with the Unity Engine freeze at some point. Those without it run flawlessly. The Unity Engine needs a fix for EVO 3D Sensation, but then we have to wait on updates. I’m scared some wont anytime soon unless its easy considering half don’t seem to be worrying about reviews.
So many Unity apps getting bad reviews from EVO 3D/Sensation owners complaining about freeze its not even funny. Most don’t know its the engine not the developer. Never knew so many games used Unity almost every ios game.
The op is suggesting we commumicate when we know a device doesn’t work with Unity. I don’t understand why someone would disagree with that idea or shoot it down by saying that’s just how Android is.
Here’s a thought: how about a thread for Android devices that do not work with Unity? We have a thread for devices that work, and that helped developers buy a device that will work with Unity, but it seems a list of devices that won’t work will help avoid bad reviews on the market.
How does one exclude the Evo 3d? In market.android.com, I was able to manually exclude the Sensation (it’s listed as HTC Sensation Z710e), but don’t see a corresponding entry for the evo 3d.
