Recent content by astrograd

  1. A

    Xbox One (Durango) Technical hardware investigation

    One of my pet peeves is ppl trolling others by lying (repeatedly I might add) about what I've said. The utterly vast majority of what I've said since January has played out verbatim, much to your chagrin. Take your butthurt elsewhere Ketto and stop trying to color what Solarus said as some...
  2. A

    Digital Foundry Article Technical Discussion Archive [2013]

    PS4 only has 2 (1 for OS, 1 for games). It's not using 2 for games (and thus not 1 for game world; 1 for HUD).
  3. A

    Digital Foundry Article Technical Discussion Archive [2013]

    An unbiased analysis of the tech would conclude that (ignoring a variety of others factors). That's not the same thing as an analysis of how the game looks visually. Tech graphics and visuals aren't synonymous. The utility of high end tech graphics is ONLY to provide the end user with as nice...
  4. A

    Digital Foundry Article Technical Discussion Archive [2013]

    Nobody so much as suspected RYSE was anything but 1080p prior to us being told otherwise. That's all the argument ya need. Ppl played it literally 2 ft from nice HDTV screens by the hundreds, including DF, and nobody was the wiser. Posting comparisons from other games with totally different...
  5. A

    Xbox One Launch Titles

    So most likely made up FUD like the majority of his "leaks" then... :???:
  6. A

    Understanding XB1's internal memory bandwidth *spawn

    What would a PS4 GPU do with 1TB/s bandwidth? There were other reasons Cerny et al didn't go with embedded RAM, but it wasn't due to wanting the best performance possible in terms of distant hardware potential. It was due to them wanting simplicity. He never suggested that decision was due to...
  7. A

    *spin-off* Importance of Backward Compatibility Discussion

    Additionally, MS plans on moving into cloud streaming as is, so BC can be serviced that way anyhow like Sony is planning.
  8. A

    Understanding XB1's internal memory bandwidth *spawn

    Dear lord...you cannot be serious with this post. :roll:
  9. A

    Understanding XB1's internal memory bandwidth *spawn

    The validity of dev docs are now debatable? But you interpretation of silence is what...more valid than the dev docs now? I'm interpreting info directly from dev docs as support for my position that MS is NOT ruling out the eSRAM's latency as a boon for performance in some facet. Evidently...
  10. A

    Understanding XB1's internal memory bandwidth *spawn

    Applying this logic to the PS4 leads us to abandon absolutely all known info about these machines without prejudice. Congrats, you've taken us back to the stone age of 2012.
  11. A

    Understanding XB1's internal memory bandwidth *spawn

    Maybe? Hard to glean anything about what kind of latency is being referenced there but that could well be it for Goossen's quote. They did mention it was lower (VGLeaks says down to 60ms for Kinect, HotChips suggests 20ms but unsure what that figure is actually referencing).
  12. A

    Understanding XB1's internal memory bandwidth *spawn

    DF claims the latest article was the full transcript.
  13. A

    Understanding XB1's internal memory bandwidth *spawn

    So....you are willing to ignore the dev docs and Goossen's explicit note about Kinect utilizing the low latency, two reliable facts presented to you, in favor of your own interpretation of what someone else could have said in a given opportunity? You and Shifty are both on the wrong side of...
  14. A

    Understanding XB1's internal memory bandwidth *spawn

    The part about GPU hiding latencies is DF's commentary, not Goossen's.
  15. A

    Understanding XB1's internal memory bandwidth *spawn

    They were "originally" considering something with 4GB of DDR4 RAM, as per Yukon. I'm not saying that's something they really dug into in a serious fashion, but it was under some sort of consideration prior to 8GB of DDR3. If the agenda at that point was tons of cheap RAM, 4GB of DDR4 isn't...
Back
Top