Try mixing attachments that keep its damage and other stats but bring the range up because that's it's weak side.
That's actually a really good tip and I'm going to agree with it. The range on the compakt is honestly quite terrible. It is accurate when firing from the hip and it's not that bad when you aim down sights either, but the range doesn't reach as far as you'd hope.
"Starting May 1, new apps and app updates submitted to the App Store must be built for iOS devices with Retina display and iPhone apps must also support the 4-inch display on iPhone 5. Learn about preparing your apps by reviewing the iOS Human Interface Guidelines." Gameloft will have to optimise their games better because it looks like retina for ipad is staying.
That just means the text and 2D has to be retina quality. There's no way some games on the AppStore will run at full retina on some devices, such as IB2 on the iPad 3.
"lazy devs"? Most developers put so much effort and love into their games, not to mention the incredibly low price point. Your characterization is such bullshit on so many levels I don't know where to even begin.
Can't believe this can will run well on my new ipad (3), but Nova 3 runs fine now on my new ipad, so maybe this game can too. Can't believe they will make this a requirement for 3d games, or is it?
Call it whatever you wish. A developer turning on retina graphics by accident (admitted by gameloft) so it runs like crap on an iPad 4 is laziness. Its not like the retina iPad wasn't around during development. They optimized Modern Combat 3, NOVA 3, etc months ago. Another example is Super Stickman Golf 2. Its a blown up fuzzy version of the standard iPad res. In that case the developer claimed they wanted the file size at 30MB so people on 3G could download. A very sad excuse considering everyone with these devices has access to wifi at some point in their day. So they will be forced to update that game too. Apple has recognized things like this and they are taking action. Create a quality graphical experience on these devices or we wont approve your updates.
The iPad 4 wasn't. The game launched Decemebr 5th, 2012. The iPad 4 launched on November 2nd, 2012. A month is not enough time to optimise for the substantially different hardware between iPad 3 and iPad 4. As to whether they had enough time with developer units is open to debate. Now you can continue to rage on it all you want, denigrate the developer by calling them lazy and whatever else you want but until you understand the code behind the problem and the optimisation issue involved, which only directly relates to the newest iOS device, you might show some consideration for the developer by understanding that the problem is not a simple switch. With reluctance I can confirm that a fix is in the works, that there is a particular issue involved and that the dev is working very hard to sort this problem out. They are disappointed that this issue has come up. The people in Montreal care very much about this game and want it to be the best possible experience. The people who play it being happy with it is of priority importance to them. If your opinion is that they are lazy, you have zero understanding of the people behind it and how great they are at their job. If you're so unhappy, just delete it and move on. There are many more of us out there that understand the issue and the complexities and are happy to support the dev team behind it and patiently wait for a fix that will be optimised to the best of their substantial ability. The fix will come. Not soon enough for some of you obviously, but it is on the way.
I fully appreciate that there is a lengthy process involved in retina optimization. However that does not negate the fact that the game WAS running perfectly fine with lower res graphics. Your comments seem to ignore that they didn't intend to include the retina graphics in this update. It WAS a mistake and not suppose to happen, Gameloft already admitted this. Read the release notes. NOWHERE does it mention retina graphics which is a huge item to include on release notes. Someone, somewhere screwed up. Thats all I'm pointing out. Yes people make mistakes, of course. It would just be nice for them to give some sort of update. They were at least kind enough to tell us the retina graphics were a mistake in this update. Release notes: http://modern-combat.net/new.php?post=20130227140624
I'm perfectly aware they didn't intend to include retina in the update. They were big enough to admit that themselves as we are all well aware of. What I'm attempting to point out is that a fix is in the works. That's its not a simple scenario. Yes it was a mistake, it was not an intentional mistake, full retina was not meant to be turned on for the iPad 4 at this stage without further testing and optimising. The fact it is in it is not down to a simple on/off light switch type of code. Its a code and hardware interaction that is having the unexpected result of full retina being on. The retina code was in there already for other devices, the changes that were made for the update (which was lot more than simply adding the new guns) and other factors caused it to activate on devices it wasn't meant to. It was not foreseen. It happens. Its not a result of laziness, its simply one of those unpredictable results. And they have been very open about it. The rewriting of that said code is a substantially larger job than simply turning it off. It requires new code, rewriting and then optimising all over again. Easier said than done. The delay is down to many issues but an important factor that is being thoroughly double checked is the writing and optimisation of any proposed fix. And then it requires submission and approval from Apple. Hence the delay in a fix is down to more than just simply fixing it now, turning of a switch and sending it out. We can either accept that, acknowledge they know of the issue as they have admitted as much and are right now working to fix it and get it out there but also ensuring its working right and that the issue does not reoccur. Or just keep criticising them, push them to release something and take the risk that the fix doesn't fix and needs another fix. I know what I'd prefer. In relation to looking for more info or comments from them, they have acknowledged the problem and are fixing. When its ready, they'll let us know. What else do we need to know? An estimate wold be pointless and may not even be accurate. When they are sure its fixed, we'll be let know through the update, simple as.
