Aaron Edmistone

My feedback

  1. 1,646 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    74 comments  ·  Oculus Quest » General  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Edmistone supported this idea  · 
  2. 1,103 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    61 comments  ·  Oculus Quest » General  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Edmistone supported this idea  · 
  3. 6,129 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    648 comments  ·  Oculus Quest » Core Software / Guardian  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Edmistone supported this idea  · 
  4. 2,542 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    211 comments  ·  Oculus Rift S and Rift » General  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Edmistone supported this idea  · 
  5. 67 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Oculus Rift S and Rift » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Aaron Edmistone commented  · 

    While I think Oculus could have been more careful about their choice of words saying things like "Your Quest is now a Rift too!". They stated this idea of remote rendering was just speculation at the time of release with the Quest, but had serious doubts of ever delivering something suitable for consumers.

    There was an insane amount of hurdles for them to go through:
    1. Sending the tracking data to the computer
    2. (likely) Interpolating that data to compensate for that latency
    3. Rendering the images using new systems to allow this kind of remote rendering
    4. Encoding that and sending it to the to the headset as fast as possible without too much compression
    5. Decoding and adjusting that (again?) compensating for that latency (Time warp)

    All of those *extra* steps on a last-last gen Snapdragon 835.
    Yes the SoC doesn't need to handle the rendering but currently there is an 80ms latency (this may be reduced as we get closer to November release) being compensated for with interpolation and time warp.

    The idea is not some ploy to phase out the Rift S. I know there are people saying that now your Quest >= Rift S, but this is simply not true.

    The Rift S will be the superior experience for PCVR. Much lower latency, much higher perceived visual fidelity, higher frame rate (currently), larger tracking volume, at the same price point.

    In summary, I think Oculus feels this product can exist along side the Quest with the new features.
    Leaving it up to the consumer to make the decision, of trading off higher quality PCVR experience for some mobile and wireless play options.

    As for the people feeling betrayed by this announcement, please remember that buyer remorse is a real thing and it is everywhere. Every time any company announces a new feature or better product, there is always people who feel cheated that they did not have some inside info about upcoming products and feel they would not have spent the money if they had known about these releases.

    I'm not saying that makes it okay; It does suck, but that is just how the release cycle goes with technology in general.

  6. 46 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Oculus Rift S and Rift » General  ·  Flag idea as inappropriate…  ·  Admin →
    Aaron Edmistone supported this idea  · 

Feedback and Knowledge Base