GeForce 6800 May Deliver Lower Performance


Recommended Posts

Software Developer Says NVIDIA GeForce 6800 Specifications May Alter

NVIDIA GeForce 6800 Graphics Processors May Deliver Lower Performance

A software developer who is behind the famous RivaTuner utility for graphics cards? tweaking said specifications of graphics cards powered by NVIDIA GeForce 6800 graphics processing units may be slightly changed by makers of actual add-in cards which results in lower geometry performance and also affect actual speed delivered by the product.

Leadtek. The table plainly states that the GeForce 6800 delivers lower geometry performance ? 406 million vertexes against 600 and 525 million of more powerful chips ? compared to the GeForce 6800 Ultra and GeForce 6800 GT models. The difference in geometry performance submitted by Leadtek is higher than the difference in clock-speeds between various models.

X-Bit Labs

Guru3D

Just a heads up if someone is consideri:whistle:n-ultra 6800. :whistle:

Rather interesting, good that they can turn of faulty components, but bad if they arent actually faulty...

Guess we'll have to wait for the official Nvidia response on this one, more than likely its was a way to use defective chips as working ones, it would certainly affect the yeilds they are getting...

(why waste good waffer hey)

If you can do it and have the things running go for your life, just as long as the results or similar cards are consistant. I mean pixel pipelines are one thing, but buggy vertex shaders could pose a problem (with bugged up or disabled pipelines) and people could end up with a vertex shader bottleneck if too many are disabled and they are running a really intensive program (future programs of course, as most out there right now wouldnt cause a vertex shader bottleneck on the nv40). But i guess that depends on whether the number of disabled parts brings it into line with the expected specs for that model, if it drops below then id be a little worried.

The geo procs could probably wont cause much more mischief, but we shall see....

edit, ill add this cos original post hasnt got it :

Clarification from X-bit Labs

Reference GeForce 6800 graphics card provided by NVIDIA Corp. and used by X-bit labs? laboratory in Tallinn, Estonia, scored identical fps in Xbitmark vertex shader test against NVIDIA?s reference GeForce 6800 Ultra graphics card working at the same clock-speeds, indicating equal per MHz geometry performance of the 6800 model against the ?Ultra? model.

Such results are unlikely to represent certain changes in vertex processors array and indicate lower number of such units within the chip. In case the majority GeForce 6800 come with 6 geometry engines, X-bit labs can reaffirm that the GeForce 6800 benchmark results available in our articles are correct and reflect speed of the majority actual graphics cards available on the market. Performance figures delivered by our articles should not be extrapolated on the GeForce 6800 flavours with 5 or less vertex pipelines.

It is unclear whether additional vertex processors can be enabled by reflashing a more advanced BIOS. Some pre-production BIOS versions caused inadequate results and behaviour on some GeForce 6800-based graphics cards.

Edited by EnIgMa-PenGuIn

Interesting...I wonder what nvidia's comment will be...and what the manufacturers are going to say too :s

I always knew Alexey Nikolaychuk was a sharp guy ( I've been using RivaTunner for a good long while) and once again, my hats off to him.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!