Geddeeee
New member
I don't see a problem either... The game sucks. Played it for 2 minutes then 'Uninstall'.
The RAM problem doesn't matter, it's a yawn fest!!!!
The RAM problem doesn't matter, it's a yawn fest!!!!
It is fair to assume that AAA mobile developers, some of which are XBL-branded, who likely got early access to the Windows Phone SDK, were unable to optimise their games for a standardised platform after over half a year. Right.it is fair to assume that it's a matter of development costs
So TuneIn can manage on 512 (maybe even 256?) for WP7 but can't for WP8? And that somehow means "don't blame Microsoft"?Don't blame MS that a streaming app(tunein) requires 1gb devices. There are a lot of other streaming apps that do not need this. Clearly it can be done on 512 devices. Heck it runs on wp7 devices with less ram.
Actually, that's Microsoft's fault because they didn't support persistent WiFi until Portico. That means not all WP8, and zero WP7 devices.Don't blame MS that whatsup use an ugly hack (background audio streaming to support fast resume) blame whatsapp.
If you bothered to read what I said, you wouldn't have had to write this.If MS would mandate 1gb ram(high end at the time wp8 was conceived on paper) you won't get cheap phones and oems need cheap devices.
It is fair to assume that AAA mobile developers, some of which are XBL-branded, who likely got early access to the Windows Phone SDK, were unable to optimise their games for a standardised platform after over half a year. Right.
So TuneIn can manage on 512 (maybe even 256?) for WP7 but can't for WP8? And that somehow means "don't blame Microsoft"?
Actually, that's Microsoft's fault because they didn't support persistent WiFi until Portico. That means not all WP8, and zero WP7 devices.
If you bothered to read what I said, you wouldn't have had to write this.
Sorry, but your excuses have little merit.
you sound butthurt lol blaming MS and sh1t...go play Temple Run 2 on a cheap 512Mb Android and tell me how smooth, lag-free it is...i know because i owned one before my Lumia and it got me mad many times when the game was unresponsive!
1. Butthurt? I think butthurt describes the Microsoft defenders here who can't take any criticism. LOLing isn't going to get this platform anywhere.
2. Temple Run 2 will run decently on an Android with a MSM8227 and 512MB RAM. TR2 isn't even on WP, TR won't run on 512MB WPs, and TR lags on WP flagships.
3. The 720 has 512MB of RAM and is priced in the same ballpark as the Nexus 4.
Personally, I couldn't either. I think TR is about the stupidest game I've ever seen. The problem is others don't agree with us. I would say that the 520 & 620 are really the devices that can bring Windows Phone to the masses, but even though I see them to be crazily good value, others could be turned off by all these incompatibilities. It's like you're getting half a Windows Phone instead of a full one.i couldn't care less about that stupid game lol
GG2 is 2D, so they don't quite compare. I like 2D graphics a lot too, but 3D is more hardware intensive and you can't ignore that. Hope you're liking the 620, was so close to pulling the trigger then the 520 got announced.Gravity Guy 2 runs perfectly on my Lumia 620 and it has better graphics than TR so this is really a developer thing...
I don't know the specifics myself, but I do know Microsoft imposes some kind of RAM limit on apps depending on how much RAM the devices have. That limit is a pretty hard one in the case of 256MB WP7 devices, which is why there were problems with some Angry Birds games. I don't think people are doing a tonne of multitasking while running a game, they should allow games to use more RAM and free up more RAM by unloading frozen apps. Either that, or do whatever Apple is doing, because there aren't many incompatibilities on iOS devices and they remain smooth.srsly tho...what you think MS could do about this matter?
2011 device running what I believe is the same processor in Mango handsets (Lumia 800, for example), which is a rather bad reference point. Remember that WP7 devices aren't even getting these titles. Not saying Android doesn't lag, but you must also realise that ordinary people will put up with lag, as long as they can at least get what they want.edit: i had a Sony Ericsson Xperia Mini running ICS
Personally, I couldn't either. I think TR is about the stupidest game I've ever seen. The problem is others don't agree with us. I would say that the 520 & 620 are really the devices that can bring Windows Phone to the masses, but even though I see them to be crazily good value, others could be turned off by all these incompatibilities. It's like you're getting half a Windows Phone instead of a full one.
GG2 is 2D, so they don't quite compare. I like 2D graphics a lot too, but 3D is more hardware intensive and you can't ignore that. Hope you're liking the 620, was so close to pulling the trigger then the 520 got announced.
I don't know the specifics myself, but I do know Microsoft imposes some kind of RAM limit on apps depending on how much RAM the devices have. That limit is a pretty hard one in the case of 256MB WP7 devices, which is why there were problems with some Angry Birds games. I don't think people are doing a tonne of multitasking while running a game, they should allow games to use more RAM and free up more RAM by unloading frozen apps. Either that, or do whatever Apple is doing, because there aren't many incompatibilities on iOS devices and they remain smooth.
2011 device running what I believe is the same processor in Mango handsets (Lumia 800, for example), which is a rather bad reference point. Remember that WP7 devices aren't even getting these titles. Not saying Android doesn't lag, but you must also realise that ordinary people will put up with lag, as long as they can at least get what they want.
Personally, I couldn't either. I think TR is about the stupidest game I've ever seen. The problem is others don't agree with us. I would say that the 520 & 620 are really the devices that can bring Windows Phone to the masses, but even though I see them to be crazily good value, others could be turned off by all these incompatibilities. It's like you're getting half a Windows Phone instead of a full one.
GG2 is 2D, so they don't quite compare. I like 2D graphics a lot too, but 3D is more hardware intensive and you can't ignore that. Hope you're liking the 620, was so close to pulling the trigger then the 520 got announced.
I don't know the specifics myself, but I do know Microsoft imposes some kind of RAM limit on apps depending on how much RAM the devices have. That limit is a pretty hard one in the case of 256MB WP7 devices, which is why there were problems with some Angry Birds games. I don't think people are doing a tonne of multitasking while running a game, they should allow games to use more RAM and free up more RAM by unloading frozen apps. Either that, or do whatever Apple is doing, because there aren't many incompatibilities on iOS devices and they remain smooth.
2011 device running what I believe is the same processor in Mango handsets (Lumia 800, for example), which is a rather bad reference point. Remember that WP7 devices aren't even getting these titles. Not saying Android doesn't lag, but you must also realise that ordinary people will put up with lag, as long as they can at least get what they want.
The fanboyism is killing me.Still want to blame Microsoft all the way eh? Go read SDK of Windows phone 8 and see if they can create 512MB or just 1GB apps?
About 3D games? If only TR has the graphic as good as Asphalt 7 and I'll admit that TR deserves 1GB of RAM. Rather than that? Well, then Imangi devs are just too lazy to optimize it. End of story.
So why didn't I blame Microsoft? Cause I know the simple truth that I can't complain OS maker for other developer's apps. Isn't it simple enough?
P.S: don't ask why 3D in TR requires too much, or I'll ask you why games with better 3D IMO like "dredd vs zombies" or "mirror's edge" can run smoothly on 512MB devices. Even Asphalt 5 (which is at least 3 times better graphic than this crappy TR) can run on 620.
- So I take it you've "read" the SDK and deduced that the 512MB restrictions are perfectly fine? If not, why vehemently defend Microsoft?
- TR isn't the only game requiring 1GB of RAM. There are apps requiring it. How many times must this be said until it gets into your head?
- Asphalt 7 doesn't "deserve" 1GB of RAM. The 920 has to display over 2.5? the pixels that a WVGA, 512MB device has to. There shouldn't be a problem.
- Yes, multiple developers (some even XBL) are just too lazy to optimise. Developers who could optimise for a bajillion configurations on Android can't support WP8's two. Considering how important these titles are for the platform's viability, I can fault Microsoft on two things:
a) a potentially crappy porting experience
b) a pathetic job of getting these titles working well on their platform- Do you not understand that the tools, restrictions and environment provided for development can impact the development itself?
Android on the other hand needs very high-end specs and large amounts of RAM because the OS has no present RAM usage limit on apps, which basically explains why many android users complain about their low-tier, mid-tier, even high-end smartphones being laggy, unresponsive, and any other affiliated problems.
How is apple able to manage to run apps SMOOTHLY on 256 mb ram devices ? That's what wondering me.
There has to be some sort of magic lol
There is no magic there. The iOS is the oldest os there. It also uses mostly the same code languages and tools as the MacOSX (excluding strictly mobile stuff of course). So they did have access to a trained pool of developers at the beginning. And taking in to account it's popularity and age you will find a lot more proficient programmers there than on other ecosystem. And when you come to optimizations and quirks you do need the experience and the skill. Android really become a focus for development in recent years and you could find some horror story about development on android and how facebook needed to hack the guts of the Dalvik java machine to make the native facebook apps for all android devices. WP8 is completely new and while you use mostly the same tools as wp7(except games where you now have DirectX and not XNA anymore) when it comes to optimizations and os internals it's different. Also this time around you don't have the pool of trained wp8 programmers yet. To get those you need to look to windows 8 developers who are scares too. The windows developers are working for line of business apps who are paid pretty good to not need look for a career in mobile development on a 5 month platform.
The fanboyism is killing me.
- So I take it you've "read" the SDK and deduced that the 512MB restrictions are perfectly fine? If not, why vehemently defend Microsoft?
- TR isn't the only game requiring 1GB of RAM. There are apps requiring it. How many times must this be said until it gets into your head?
- Asphalt 7 doesn't "deserve" 1GB of RAM. The 920 has to display over 2.5? the pixels that a WVGA, 512MB device has to. There shouldn't be a problem.
- Yes, multiple developers (some even XBL) are just too lazy to optimise. Developers who could optimise for a bajillion configurations on Android can't support WP8's two. Considering how important these titles are for the platform's viability, I can fault Microsoft on two things:
a) a potentially crappy porting experience
b) a pathetic job of getting these titles working well on their platform- Do you not understand that the tools, restrictions and environment provided for development can impact the development itself?
- Mirror's Edge and Asphalt 5 look like garbage, lying doesn't prove a point.
why iOS apps run on 256mb ram? First, different platform. Then, would you think Apple will allow apps which surpass their devices' power on their store? While their devices have identical hardware?