NVIDIA GeForce Desktop Linecard 2014


OpenGL Tools: glRAW and glIsDeprecated



NVIDIA has released the GeForce desktop linecard for 2014. You can download the PDF file from this link.

The linecard shows also which AMD Radeon card can be replaced by a NVIDIA GeForce card.

Another big PDF is available for latest NVIDIA news: GeForce Update – Feb 2014.





16 thoughts on “NVIDIA GeForce Desktop Linecard 2014”

  1. Frank

    Why do they write DX11.2 for these cards when they still not support feature_level_11_0? I known what they said about it, but 64 UAV in a pipeline is definitely a gaming feature and all GeForce only support 8 UAV.

  2. John Smith

    My 660 still in the line, good. But Kepler doesn’t support DX11.2, maybe some features are software driver based. I still use Win7 so it doesn’t matter for me though.

  3. John Smith

    Frank
    what are you talking about? GeForce support DX11 games and is a great performer. Gaming feature is how many FPS your card can show, not some unknown “UAV”

  4. NV

    http://nvidia.custhelp.com/app/answers/detail/a_id/3196

    Fermi and Kepler GPUs do not support two of these features:

    UAVOnlyRenderingForcedSampleCount supports 16x raster coverage sampling
    TIR – aliased color-only rendering with up to 16x raster coverage sampling

    These two features are intended as path rendering acceleration aids for Direct2D, used optionally if the hardware supports feature level 11_1. We felt that for Fermi and Kepler, it was more important to maximize our investment in work that is more important to 3D graphics and therefore chose not to implement support for those two features.

    The third feature…

    UAVs in the vertex, geometry and tessellation shaders

    is supported by Fermi and Kepler GPUs however because this is only exposed through the hardware feature level 11_1, as a group of three features, we currently do not support it via the DX11.1 interfaces. We may expose support for the UAVs in the vertex, geometry and tessellation shaders feature on an app-specific basis in the future.

  5. NV

    Fermi, Kepler and Maxwell supports DX11.2 Tiled Resources, so it supports DX11.2, period.

  6. Frank

    My problem is that they don’t support larger number of UAVs for the pipeline. Only 8 UAV is available, when the feature_level_11_1 needs 64.
    This is the most important feature in D3D11.1 for me, because I can write more cs to the program.

  7. John Smith

    Frank
    I don’t understand what did you mean “still not support feature_level_11_0″

  8. przemo_li

    If partial support would mean full support…

    Well Mesa drivers have support for some OpenGL 4.3 extensions…

    Nobody claim OpenGL 4.3 compliance though.

    Problem with DX is that its not designed for extensions, and thus people do not have that paradigm in mind when talking about DX features.

    That way or this way, its not what full DX have to offer.

    So its bit better than DX11.1 at least.

    And could be better if only MS allowed extensions…

    (Back on topic. Where TF are OpenGL versions? :P)

  9. DrBalthar

    Interesting blah from nVidia here. So they don’t think path rendering in Direct2D is important but on the other hand they added their own proprietary extensions to OpenGL for path rendering. Hmmmm I love those schizophrenic nVidia people

  10. John Connor

    nV is not compatibile with DX 11.1 or 11.2 PERIOD
    STOP lying to customers.
    All is in the spec of those cards, nV canot lie so only DX11 basic in nV 6xx & 7xx

  11. John Smith

    DrBalthar

    hardware doesn’t support it and OpenGL doesn’t have Direct2D

    “These two features are intended as path rendering acceleration aids for Direct2D, used optionally if the hardware supports feature level 11_1. We felt that for Fermi and Kepler, it was more important to maximize our investment in work that is more important to 3D graphics and therefore chose not to implement support for those two features.”

  12. John Smith

    “Fermi and Kepler GPUs do not support two of these features:

    UAVOnlyRenderingForcedSampleCount supports 16x raster coverage sampling
    TIR – aliased color-only rendering with up to 16x raster coverage sampling

    These two features are intended as path rendering acceleration aids for Direct2D, used optionally if the hardware supports feature level 11_1. We felt that for Fermi and Kepler, it was more important to maximize our investment in work that is more important to 3D graphics and therefore chose not to implement support for those two features.”

Comments are closed.