| Aielyn said: You're missing the point. The use of the terms "megatons" and "meltdowns" wasn't an issue due to English - you used the terms correctly in that regard. The problem is the CHOICE to use those terms. You could have said "major titles" instead of "megatons". You could have said "big surprises". Instead, you said "megatons" and "meltdowns". If you had inside information, you wouldn't be making predictions. And none of your predictions are so far outside of the realm of likely events as to be proof of anything, while the fact that you expect only half of them being true being proof of something is an issue since if you had inside information, it would be 100% correct, not 50% correct. If you can't provide solid proof that your information source is trustworthy, then providing vague and insubstantial claims isn't going to convince people. Solid proof can come in plenty of forms without exposing the person's identity. Kind of like how, in Groundhog Day, Bill Murray's character proves that he's not lying by mentioning things he knew were about to happen. None of them were major things, but it showed foreknowledge. But vague comments like "there'll be an old Sony franchise return from hiatus", which won't be confirmed for another 3-4 months at best, do not constitute solid proof. And if your source was third-party, and their information was first-hand information, how could they possibly know what Sony's first-party lineup looks like, the system price (which almost certainly hasn't been set in stone yet), or about other third-party titles that weren't from that person's studio (if that person's studio was the one that is making that "meltdown" game, then it would risk their identity)?
And let's not forget the other issue - the claim that Nintendo is actively and visibly (to them) screwing over the third parties by telling them that they can't use a certain section of RAM because it's for Nintendo only. It's the only specific claim you made, and it doesn't make any sense. Even if Nintendo were locking off some of the RAM, there's no way they'd be telling third parties that it's for Nintendo titles only, after spending so much time and effort in wooing them. Meanwhile, I find it highly unlikely that, in intending to send a third party a small code fragment explaining how to use the graphics chip in a certain way, Nintendo screwed up and sent a GB-sized file instead of one measuring in the kB range. That takes a special kind of incompetence that doesn't occur in a company as secretive as Nintendo. |
Y u write so much? =(
I used those terms because I was excited about what we will see! I never thought about how those choices could hurt my credibility :P And while not a single one is too far fetched, but together they add up to a pretty unlikely scenario. And since I only have my source to go by I can't say that 100% of these will come true, and I have since learned that some of these titles might be shown at tgs and not e3 as I first thought.
I'm really not all that good at giving hints and nods... When that Wii U exclusive title is announced I will say something; I think there should be enough hints in here to add up. And I don't know any dates or anything. I wish I could spell it out SOMEWHERE, but my source has said no. How do you suggest that I hint these things?
I don't know how he knows all of this, but I figure that they're working pretty closely with SOny and needs to co-ordinate the releases or something.
what happened was early on a very large publisher got their mitts on source code to a 1st party title accidentally (was meant to be sent a code segment on disk for assistance with a gpu addressing issue, but ended up with whole game source), and in the source for that, it became obvious that 3rd party sdks lacked vital and very helpful api's for graphics rendering, and the 'nintendo space' banned from use for 3rd party devs was being used without reservation - so basically 3rd party devs other than the one that found this got wind, and we've all basically said 'fix this shit or we go elsewhere', nintendo then issued an sdk update that added SOME of the api's for gpu processing but the memory restriction still in place - just with the commented code saying nintendo space changed to 'system reserved' - essentially nintendo got caught with its pants down blatently gimping 3rd party titles, then scrambled to fix it by letting some of the 1st part sdk features through a few months early, but all that did was piss devs off more, because it still shows that nintendo aren't playing fair and fucking 3rd party devs over.
I'm on Twitter @DanneSandin!
Furthermore, I think VGChartz should add a "Like"-button.
