No its not lol
Oh? So a poster verified by Bish saying that the numbers are incorrect is wrong? Please, tell me what they are then sir?
No its not lol
So how is your Ouya?
But the Esram only constitutes a paltry 32mb lol. I left it out on purpose, as I'm only talking about the 8GB of ram, the real crux of the memory allocation.
No its not lol
Surely the thread is done then if you have confirmation that the information is incorrect?
Let me restate once more since no one cares to dispute it, how are devs ok with this but some Gaffers not? What would you like devs to use the space they don't quite know what to do with yet? Ragdoll physics on nose hairs? Real time fart particle simulation? That last bit is about as ridiculous as this issue being made into something.
Bisoptl would have banned him if he couldn't verify it privately.
To be fair, devs are rarely unhappy about the specs of new systems before they launch. Then it's all glowing praise for new power and new possibilities. It's in the year before the new systems launch that they start lamenting the slow beasts they've been saddled with for the past X years and the limits they impose on what they'd like to make...and how they're excited about those new machines to come.
I am only concerned developers have 10 times the system memory but still the same disc space like last gen.
DF is in full meltdown mode. Sad to see it happening in real time.
Are you saying the PS4 DOESN'T have real time fart particle simulation?
FFS.
I'm going to stick to playing the Microwave game.
176GB / 30 fps = 5.86 GB per frame.
Can anyone describe how devrlopers could have utilized more ram if available? Specially this early in console cycle.
Doesn't matter. Those things help to alleviate the bandwidth issues from DDR3, not get rid of them altogether. It does not work how you think it does. Move Engines and Esram can help fill in some of the gaps, but the main bulk of the ram, the 8gb of ddr3 is always going to be limited by its bandwidth, and none of the other elements will change that. You will not be able to get more ram out of the ddr3 than my figures above state. That's based on the absolute max memory bandwidth figure for the ram.
Yes, we talked privately already. Take from that what you will.
What if there aren't fixed numbers yet? Maybe Sony doesn't want to commit to an specific ratio right now because it's not yet set in stone.
So what then is taking up all the memory? Obviously some is being partitioned for future use.
Lets just leave it at you have no figure how much impact the move engines and Esram will have for the entire pipeline, so unless you have an accurate number, its not fair to apply math and purposely leave out elements that in your opinion do not matter when in fact they do.
i noticed that after being confronted by bish yesterday, filopilo is still around...
choice quotes:
http://www.neogaf.com/forum/showpost.php?p=72993941&postcount=1466
http://www.neogaf.com/forum/showpost.php?p=73003591&postcount=1920
http://www.neogaf.com/forum/showpost.php?p=73006491&postcount=2061
hmm!
Yes, we talked privately already. Take from that what you will.
I think the mods get a kick out of watching this stuff sometimes.
I agree.I feel like this should be in the OP.
Yes, we talked privately already. Take from that what you will.
So as Bish has verified filopilo's authenticity, can we assume that DF are wrong on the numbers now?
Or we can just leave it at GDDR5>DDR3+eSRAM. Boom! We're done here.
I feel like this should be in the OP.
3 people in a box. Shown one at a time. The future is now.
So do Devs as several have already commented outside of this thread.
i noticed that after being confronted by bish yesterday, filopilo is still around...
choice quotes:
http://www.neogaf.com/forum/showpost.php?p=72993941&postcount=1466
http://www.neogaf.com/forum/showpost.php?p=73003591&postcount=1920
http://www.neogaf.com/forum/showpost.php?p=73006491&postcount=2061
hmm!
Yes. The other information about the "flex" memory has been verified by Sony.
So as Bish has verified filopilo's authenticity, can we assume that DF are wrong on the numbers now?
Interesting.
I'm curious, as I've been, to how reliable Digital Foundry's sources are. Certainly they have a great deal of trust in their sources running the article as fact, but those sources in which they trusted, be them separate from today's "new source," told them different yesterday. Who's to say the new one is right today?
Then there's some conflicting information from at least one inside source "from a dev at one of the biggest in the industry" yesterday, which, besides one different element, agreed with the initial story that 4.5 gigabytes are guaranteed, 1 gigabyte is developer reserve, the OS uses 1.5 gigabytes, and that another gigabyte is OS reserve.
And of course, then there's folks like Filopilo (1, 2, 3) claiming the initial story was "all wrong." Or Verendus also saying it was wrong.
Anyhow, I wonder why Sony won't come out with specific numbers, but will clarify the differences between types of memory systems. While I certainly don't see the story as negative, there are clearly a number of people that do. People who are acting like it's confirmed, regardless of if it's rumor. So if those numbers from the Digital Foundry are accurate, might as well come out and say it. And if not, might as well calm the storm a bit with the correct numbers.
Happy Saturday, everyone! =)
What if there aren't fixed numbers yet? Maybe Sony doesn't want to commit to an specific ratio right now because it's not yet set in stone.
Yea they are not going to confirm or deny the numbers because that could still change.
Let me restate once more since no one cares to dispute it, how are devs ok with this but some Gaffers not? What would you like devs to use the space they don't quite know what to do with yet? Ragdoll physics on nose hairs? Real time fart particle simulation? That last bit is about as ridiculous as this issue being made into something.
Lets just leave it at you have no figure how much impact the move engines and Esram will have for the entire pipeline, so unless you have an accurate number, its not fair to apply math and purposely leave out elements that in your opinion do not matter when in fact they do.
DF has gotten the specific numbers of things wrong before. Wouldn't be surprised if they did it again.
What if there aren't fixed numbers yet? Maybe Sony doesn't want to commit to an specific ratio right now because it's not yet set in stone.
Chances are flex memory is right, but the numbers are wrong.
So do Devs as several have already commented outside of this thread.