Printable View
Quote:
Originally Posted by SpikeyKit
My new policy too.
This issue has given me an idea for an event. Collect 3 tubes of lube to get a temporary 20% pain reduction from the reaming you are about to receive. That would be the faction boost. The individual would be collect 3 exam gloves for a doctor with small hands
You could call it the "Proctologist" mission plan
Tadaaah, perhaps there could be some sort of fast track to move people with problems on iOS to android if they have one available.
Now that was funny lol.Quote:
Originally Posted by CC1
Post of the day. :cool:Quote:
Originally Posted by CC1
Here is a new one. Didn't do the update. Been running well.
Commiserating with my faction members who have been locked out and unable to play. You guys here as well.
But today I could not login to the game on my iPad 2. iOS 8.0.1. Same hang ups at launch with force closes. All other apps and games worked just fine. I did a hard reset of my device and got it to log in. But now it force closes once in the game every now and then.
Running 4.4 data set
I have the exact same issue....since the update that had a nov 10th date I am unable to load the game. I have an iPhone same iOS with no issues loading mw v4.4. This is complete bs.Quote:
Originally Posted by Somebody
Tadaah, I don't say any of the following to be overly critical, synical or flaming but I think it's time for a new approach to addressing this issue with the community. I personally have not updated to any of the new versions yet I still feel the same frustrations of those who have. Members of my faction have been impacted, teams we faced in WD were impacted, so even if the update doesn't impact all of us individually we feel the same burden as those who have because we are a part of the community. The relationships that have developed over the lifecycle of the game have become a foundational element of this game and we want to feel that matters. In my opinion it is a reason many continue to play through some of the challenges that have occurred outside of this update. As of this posting there are 52 pages of comments. I think you have done well to keep us informed but a large problem with the information you have provided is the commitment to it being addressed. That the issues have persisted into a second week is creating a lack of confidence that any future releases will be successful. It is hopefully clear from the passionate replies to this thread that the members of this community care about the game and a signicant frustration for players like myself is the lack of any clear path towards a resolution that would leave us to feel comfortable with completing the next download. As I said you have done well to provide us with information but at the same time your posts are lacking the level of detail that I think most need to feel our concerns are being addressed. For example, your most recent post that with each update more players were able to access the game comes off as more of an opinion than fact as you provided no detail to substantiate your claim. The appearance of a post like that in my opinion is that you are considering a players ability to open the game and connect to the server but if 15 seconds later they crash out is that really an improved experience? Perhaps it's time for you to provide us with more detail behind these statements, something substantial enough for us to gain a better understanding of what is actually occurring and why it's so complex when it comes to a resolution. If you can do that than perhaps the trolling and flaming will subside and we can begin to believe that Gree cares about its community. Until and unless we get to the point where the players have confidence in the stability of the game we will view each new release as a risk to be avoided because at the heart of all of this is the desire for access and without access we feel removed from the community we care so much about.
Well said mate
As each update has gone out, the number of crashes has gone done. There's a tool that tracks that for us. Additionally, the number of players logging in is normal in comparison to the past. We are not permitted to give you exact numbers.
Well I also cannot get into the game since downloading the latest update. I keep trying to keep my ticket open, but Gree keeps closing it. Ticket #2036932). I know many that are in the same position, and they don't post in the forum.Quote:
Originally Posted by Tadaaah
The overwhelming majority of players have not downloaded beyond 4.4. I don't think it is safe to do it yet.
I too have been unable to play my account since the update. Missed panama epic boss and final ltq/fltq. Wd was a bust and now first Hong Kong ltq/fltq is nearly over and I am a day behind for the ltb. It's a game so not the end of the world, but Edbl79 is right on point as was speed ump earlier by calling out Gree to dig deep in the compensation treasure chest.
Tadaaah, with all due respect breaking down the update/crash analysis is frankly worthless to those that remain unable to play. Like me I bet most want solutions not restatements of the obvious,
.
Below are the diagnostics from my iPad.....suggests MW is consuming all the resources and can't load best I can tell. Give me back v4.4 please. Works on my iPhone with same iOS version.
{"os_version":"iPhone OS 7.1.2 (11D257)","version":"104","bug_type":"198"}
Incident Identifier: 9CEF0D31-AC1F-4F19-A976-A949C10FFC08
CrashReporter Key: 932eb90bf95b6a0e6618062228a4e83d94c9c5bd
Hardware Model: iPad2,1
OS Version: iPhone OS 7.1.2 (11D257)
Kernel Version: Darwin Kernel Version 14.0.0: Thu May 15 23:10:44 PDT 2014; root:xnu-2423.10.71~1/RELEASE_ARM_S5L8940X
Date: 2014-11-12 20:20:03 -0500
Time since snapshot: 288 ms
Free pages: 1031
Active pages: 4083
Inactive pages: 1921
Speculative pages: 205
Throttled pages: 105495
Purgeable pages: 0
Wired pages: 15968
File-backed pages: 5579
Anonymous pages: 630
Compressions: 0
Decompressions: 0
Compressor Size: 0
Uncompressed Pages in Compressor: 0
Largest process: Modern War by GR
Processes
Name <UUID> rpages recent_max fds [reason] (state)
MobileMail <262d66a062ac3cfcb8b3ac74edfcfb79> 1154 1154 100 [vm-pageshortage] (resume) (continuous)
tccd <f9cb39991094301eb98c82da1b51e737> 158 158 100 [vm-pageshortage] (daemon)
kbd <ccadac0744e83dd38aa209fd4b9ff320> 603 603 100 [vm-pageshortage] (daemon)
pasteboardd <2d0b29493a76331995a52f38728520b5> 119 119 100 [vm-pageshortage] (daemon)
Modern War by GR <4142f0178ba7356eb84783e62bc2bb5c> 88079 88079 100 [vm-pageshortage] (audio) (frontmost) (resume)
identityservices <3c0f882c3e3436d69174270762c0ff8c> 400 400 100 (daemon)
wifid <09a3baec3d3b3ca78be3ce47592cf7b2> 336 336 25 (daemon)
syslogd <7836ef0f18d432578cc4422e9900c992> 138 138 50 (daemon)
locationd <ae5a5acf14ce3950be40d5c244e0635e> 941 941 100 (daemon)
powerd <0b46cf6679f33dd8a6132ed1a82f5a9f> 109 109 50 (daemon)
imagent <d2c21d8050e531c68fcc81435c2dde3a> 284 284 100 (daemon)
mediaserverd <3527ad93ade239719cce8ac2dea07000> 875 875 50 (daemon)
iaptransportd <b7e3fee1773230969b80495ea813c0c2> 213 213 50 (daemon)
mDNSResponder <7375b959d31f330c80c0e4b42a0c5ef5> 171 171 50 (daemon)
apsd <06cb3ee8aa4934c48ac6ecd740da765f> 410 410 100 (daemon)
dataaccessd <aea4708132163828a8d5c7e877a345a8> 1236 1236 100 (daemon)
itunesstored <0acf434a094c310985ac0837bb8d7143> 527 527 100 (daemon)
SpringBoard <5299e27756133806b7bc6e48e90c9f89> 3593 3593 50
backboardd <050ad910dd043cac880d683ab31f39ba> 5426 5426 50 (daemon)
lockdownd <be85f353ab0b31d5ba2f3a9f3f1d46bb> 279 279 100 (daemon)
fairplayd.A1 <10ddcf5632103103bf816ab1a4068642> 126 126 50 (daemon)
configd <41a2f89698143633a77e93fc4ba68446> 419 419 100 (daemon)
fseventsd <62fd8e0b42ae37019fa0755fde2e5175> 162 162 100 (daemon)
aggregated <9206f40c1fb23657ae98a2f1842c0560> 370 370 50 (daemon)
BTServer <24ccfa1663c73a59910d21254cb6d654> 313 313 100 (daemon)
UserEventAgent <26651787173137d4ae5fabf0160cf298> 459 459 50 (daemon)
distnoted <2cb1cd27a19a3a57b772164bd2dcc878> 114 114 100 (daemon)
networkd <3dc27aea200c3c7194198c739886367b> 409 409 100 (daemon)
ubd <634f175a401a33198f89a8ec1246e430> 881 881 100 (daemon)
filecoordination <91d3801f9f2238a99eff5c6ee6be3ef7> 130 130 100 (daemon)
MobileGestaltHel <839ac6c44c743b41b31cc5deac517fc2> 128 128 100 (daemon)
DuetLST <d201150060c93ec4aae001ebf1e8648e> 46 46 100 (daemon)
CommCenterClassi <9bafadb90fd93ddba1e6b03e82515d7f> 198 198 100 (daemon)
notifyd <05ac2e245e0b35b78ca8685a12336c0a> 172 172 100 (daemon)
Tadaaah, while I appreciate your quick reply I don't think it addressed what I said. While you may only see less than 3% impacted by crashes the number is much higher. There are 5 players from my 60 member faction that downloaded the update that triggered this issue. Two of the 5 quickly reported their experience to the faction so that we could avoid their fate. Of the remaining 55 members 36 are iOS and because of the warning we received we did not fall victim to the issue. Our auto-post bot continues to warn faction members not to download any new game version until further notice. I suspect the same experience is true for many other factions. It is for these reasons that I think the less than 3% you have stated is innacurate and flawed. My ability to access the game should not disqualify me from that statistic. I am not and will not be downloading any future updates of the game until a percentage of players much greater than 3% is reporting a successful experience. A much greater percentage than what you have stated is feeling the impact and until real talk can occur to show us that we do not need to fear the game there will unrest in the community.
Well, when another update is released, we'll let everyone know. Those that can't get in download and when they report, it can build more confidence in the update.