For the love of God, tell me you didn't tested Battlefield 4, please.
So that's why they released on Android first. Free QA.
On the flipside, this means that Final Fantasy 6 for Android is, technically speaking, the first ever version of the game whereGeneral Leo doesn't die.
Yeah, if we were seeing legitimate high quality, non-exploitive works there I think people would just be miffed they don't port those to handhelds too. As is it just feels like they're digging themselves into a deeper and deeper hole as far as quality is concerned and are absolutely self destructive. Have to hope this burns them on the ass so they shape up, peacefully or violently.Man, and this is what worries me about SE's approach on mobile; They want to go full steam ahead but with absolutely none of the effort. This is absolutely ridiculous.
As someone who works as a QA Tester for EA, I know what it's like to find an issue and have the devs say "Fuck it, that's not worth fixing", but an issue like this is ridiculous. A game ending hard lock like that is an A class bug that is a mandatory, top priority fix. We'd immediately be cross checking on other devices to see if it occurs on those too. With a team of at least 5 or 6 people on different devices playing the game for 40 hours a week, I highly doubt they wouldn't have found this issue. I also highly doubt that that "espier" typo wouldn't be spotted. I'm having doubts that this went through QA at all.
No, I'm on The Sims 4. I also tested the Future expansion pack for The Sims 3 as well as a few stuff packs. I also worked on a few Madden games and a UFC game a few years ago. Madden is really bad with the devs refusing to fix bugs we find. Doesn't help that half of us (myself included) couldn't care less about football. The Sims is pretty great though.
As someone who works as a QA Tester for EA, I know what it's like to find an issue and have the devs say "Fuck it, that's not worth fixing", but an issue like this is ridiculous. A game ending hard lock like that is an A class bug that is a mandatory, top priority fix. We'd immediately be cross checking on other devices to see if it occurs on those too. With a team of at least 5 or 6 people on different devices playing the game for 40 hours a week, I highly doubt they wouldn't have found this issue. I also highly doubt that that "espier" typo wouldn't be spotted. I'm having doubts that this went through QA at all.
Good point. It does seem like this is something QA would have caught right away. Particularly the "espier" typo, doesn't it appear at the very beginning of the game? It beggars belief that not a single tester would have reported it, so it's almost more logical to assume there was no QA at all, though that's really pathetic.
I wonder, did anybody not pick up on the horribly horrible pathing issues Sims 3 suffers from? I can never stay in a town too long without turning into a horribly laggy mess.
Good point. It does seem like this is something QA would have caught right away. Particularly the "espier" typo, doesn't it appear at the very beginning of the game? It beggars belief that not a single tester would have reported it, so it's almost more logical to assume there was no QA at all, though that's really pathetic.
When I was a QA Lead at Activision I sometimes had some stupid testers on my teams who couldn't spell correctly to save their lives. So while I have no doubt that this possibly wasn't tested at all, I would also believe the testers were just too stupid to realize what was there.
So they forgot to link the events properly in the RPGMaker program.
Yeah let's do Square Enix's job.
First I was like "yup" and then I was likeSo they forgot to link the events properly in the RPGMaker program.
I would be curious what the android SDK console logs have to say about this crash... If I reach that point in the game I'll have a look see and figure out what happens
Yeah let's do Square Enix's job.
Even then, I would think you would have to have at least a few who do. I've spent entire weeks doing text sweeps of games and weeding out every error I could find. It's easy to do and it has a high bug number yield, so I'd always hop right on that during ad-hoc time. You seriously didn't have a single guy like that? I mean, it only takes one grammar nazi on a team to do a text sweep.
**************************
The following bugs have been confirmed and fixes are forthcoming:
- The game no longer crashes during the cutscene showing the fight between Kefka and General Leo.
- The icon for Sabin's Blitz ability now displays correctly.
- A misspelling of the term "Esper" has been corrected.
**************************
They're working on a fix right now.
Source: http://kotaku.com/major-glitch-makes-final-fantasy-vi-unbeatable-on-andro-1505100344
"The icon for Sabin's Blitz ability now displays correctly" makes it sound like they don't even know what they're talking about.
Chrono Trigger Play Store* Android Compatibility *
"CHRONO TRIIGER" may not perform as intended on the latest version of Android. We ask for your patience and understanding as we work to address this issue in the coming days.
FFVI deserves so much better than this port.
They also acknowledged that Chrono Trigger on Android has a problem and promised to fix it.
Chrono Trigger Play Store
But they still haven't fixed it.
[...] enjoy playing "CHRONO TRIIGER"
Would be perfect if not for the gutted audio quality.It already received a better port
Would be perfect if not for the gutted audio quality.
"The icon for Sabin's Blitz ability now displays correctly" makes it sound like they don't even know what they're talking about.
The following bugs have been addressed:
- The game no longer crashes during the cutscene showing the fight between Kefka and General Leo.
- The icon for Sabin's Blitz ability now displays correctly.
- A misspelling of the term "Esper" has been corrected.
- Various other minor bugs.
FF6 has been updated today, with a patch that fixes this issue.
While Chrono Trigger has been unplayable for god knows how long.
Probably not, All the Bravest simply wouldn't boot up on my Nexus 7 when I grabbed it for free while it clearly booted for most people on iOS.What's been happening there? And is it true for the iOS port as well?
Probably not, All the Bravest simply wouldn't boot up on my Nexus 7 when I grabbed it for free while it clearly booted for most people on iOS.