Recent Posts

Pages: 1 ... 7 8 [9] 10
81
Linux Display Driver - x86 BETA     349.16     April 14, 2015
Linux x64 (AMD64/EM64T) Display Driver  BETA     349.16     April 14, 2015
Linux 32-bit ARM Display Driver BETA     349.16     April 14, 2015
Solaris Display Driver – x64/x86 BETA     349.16     April 14, 2015
FreeBSD Display Driver – x86 BETA     349.16     April 14, 2015
FreeBSD Display Driver – x64 BETA     349.16     April 14, 2015

Quote
  • Added support for the following GPUs:
    • Quadro K1200
      Quadro M6000
      GeForce 920M
      GeForce 930A
      GeForce 930M
      GeForce 940M
      GeForce GTX 950M
      GeForce GTX 960M
      GeForce GTX TITAN X
  • Added support for G-SYNC monitors when used together with non-G-SYNC monitors.  When G-SYNC is enabled, non-G-SYNC monitors will display with tearing.
  • Fixed a bug that caused nvidia-settings to crash when assigning an attribute whose value is a display ID on a system with multiple X screens.
  • Updated the reporting of in-use video memory in the nvidia-settings control panel to use the same accounting methods used in other tools such as nvidia-smi. nvidia-settings was not taking some allocations into account, e.g. framebuffer memory for the efifb console on UEFI systems, causing discrepancies in the values reported by different tools.
  • Removed the "EnableACPIHotkeys" X configuration option. This option has been deprecated and disabled by default since driver version 346.35. On modern Linux systems, display change hotkey events are delivered to the desktop environment as key press events, and the desktop environment handles the display change by issuing requests through the X Resize and Rotate extension (RandR).
  • Added support for lossless H.264/AVC video streams to VDPAU.
  • Added support for VDPAU Feature Set F to the NVIDIA VDPAU driver. GPUs with VDPAU Feature Set F are capable of hardware-accelerated decoding of H.265/HEVC video streams.
  • Fixed a bug that prevented GPU fan speed changes from getting reflected in the text box on Thermal settings page.
  • Added nvidia-settings commandline support to query the current and targeted GPU fan speed.
  • Added a checkbox to nvidia-settings to enable a visual indicator that shows when G-SYNC is being used.  This is helpful for displays that don't indicate themselves whether they are operating in G-SYNC mode or normal mode. This setting can also be enabled by running the command line
    nvidia-settings -a ShowGSYNCVisualIndicator=1
  • Added support for the X.Org X server's "-background none" option. When enabled, the NVIDIA driver will try to copy the framebuffer console's contents out of /dev/fb0.  If that cannot be done, then the screen is cleared to black.
  • Added support for YUV 4:2:0 compression to enable HDMI 2.0 4K@60Hz modes when either the display or GPU is incapable of driving these modes in RGB 4:4:4.  See NoEdidHDMI2Check in the README for details.
  • Fixed a bug that could cause multi-threaded applications to crash when multiple threads used the EGL driver at the same time.
  • Fixed a bug that caused Sync to VBlank to not work correctly with XVideo applications in certain configurations.
  • Fixed a bug that prevented the X driver from correctly interpreting some X configuration options when a display device name was given with a GPU UUID qualifier.
  • Fixed Pixel Buffer Object operations when row length is less than width. GL_[UN]PACK_ROW_LENGTH can be set to a value lower than the width of the operation being carried out. The OpenGL specification allows for this (the source or destination lines will be overlapping). Previously, our implementation of Pixel Buffer Objects did not support this case and would throw an error.
  • Fixed a bug that caused corruption when switching display modes in some applications that use transform feedback.
  • Fixed a bug that caused texture corruption on framebuffer depth attachments cleared using glClearTexImage().
  • Fixed a bug that artificially limited the maximum pixel clock on displays in some SLI Mosaic configurations.
  • Fixed a kernel memory leak that occurred when looping hardware-accelerated video decoding with VDPAU on Maxwell-based GPUs.
  • Fixed a bug that could cause nvidia-settings to crash on exit on 32-bit Linux systems.
82
English forum / Re: Fixes for MadShaders 0.4.0
« Last post by JeGX on April 14, 2015, 09:52:57 AM »
Thanks for your contribution!

I will update the Windows version of MadShaders asap with your batch file.

The am_i_dreaming_gl2.xml demo is not listed in the main interface and I even forget it. Anyway, I fixed it.
83
GpuTest / Re: Gputest 0.7.0 does not recognize SLI
« Last post by JeGX on April 14, 2015, 09:47:13 AM »
I will release a major update of GpuTest shortly, and I'll check the SLI support at this moment.
84
Quote
Grand Theft Auto V GeForce Game Ready Driver Released

The new GeForce Game Ready 350.12 WHQL Grand Theft Auto V drivers are now available to download from GeForce Experience and GeForce.com. With Game Ready optimizations for the highly anticipated PC release of Grand Theft Auto V, new SLI profiles, and new 3D Vision profiles, our latest drivers are a recommended update for all GeForce GTX users.

For all Windows versions released
PhysX has been recompiled against CUDA 6.5, otherwise no new engine folders named with magic numbers
Supports OpenCL 1.2

85
English forum / Fixes for MadShaders 0.4.0
« Last post by Drest on April 13, 2015, 09:17:20 AM »
First, I saw the comment in the Windows batch file saying it needed updating. Here's my suggestion:
Code: [Select]
@echo off
rem All command line parameters: http://www.geeks3d.com/forums/index.php/topic,3066.0.html
set params=/fullscreen /width=1920 /height=1080 /benchmark_duration_ms=120000 /benchmark_log_score /no_menubar
for /r demos %%f in (*.xml) do GLSLHacker.exe %params% /demofile="demos/%%~nxf"

Adjust the params line to suit your needs. I discovered the duration is only half what it's set to. Why?

I also fixed the LUA errors in am_i_dreaming_gl2.xml
...but there doesn't seem to be an option to attach a file here.

So I uploaded it here:
https://gist.github.com/anonymous/b198d433f382046fe15c

This is my first post here, so go easy on me :-[
86
GpuTest / Gputest 0.7.0 does not recognize SLI
« Last post by jasjuang on April 13, 2015, 02:07:38 AM »
Hi,

I ran all the stress tests in Gputest 0.7.0 downloaded from here http://www.geeks3d.com/20140304/gputest-0-7-0-opengl-benchmark-win-linux-osx-new-fp64-opengl-4-test-and-online-gpu-database/, and whether I enable or disable SLI the fps is always the same.

But what's funny is I tested with a stand alone furmark from http://www.geeks3d.com/20101209/tips-how-to-enable-sli-and-crossfire-support-for-opengl-applications/. I did see a performance boost with SLI enabled. So does that means there is something wrong with Gputest 0.7.0 that prevents it from recognizing SLI?

Thanks
87
Quote
Ashes of the Singularity Can Handle Upto 20000 Units At Once, DX12 Allows Thousands of Light Sources

Stardock Studios’ upcoming real time strategy game Ashes of the Singularity was the star of this year’s GDC. It’s one of the first games that will support DirectX 12 and it goes without saying that it looks gorgeous...

One of the biggest changes was the inclusion of an Asynchronous Scheduler that makes sure all GPU commands are being processed parallelly.
“The big thing here is that Nitrous has what you call an Asynchronous Scheduler. In a normal engine, like pretty much every engine that’s been released, commands that are going to be sent to your graphics card are serialized. You send them to the scheduler, it serializes them up, and they go one at a time. What we’ve managed to do with Nitrous is that it’s done in parallel. So it’s Asynchronous, every single core on your CPU can talk to your graphics card at the same time.”
...
So is this happening due to Microsoft’s upcoming API, DirectX 12? “DX12, Mantle and Vulkan make it really practical, so even under DirectX11 we’re doing a lot of crazy stuff with all the cores but the problem with DirectX 11 is that even with our scheduler, DirectX11 still serializes up a lot of our commands so we lose a lot of benefits. Not all of it but you know, a substantial amount, so we have to turn down a lot of our cool effects. But we’re still able to do thousands of units on-screen at once, we just can’t show them at quite the same glory. On DirectX 12 though they get out of our way entirely and we can have complete control of the GPU.”
88
3D-Tech News Around The Web / AMD FirePro Unified Driver 15.3 WHQL
« Last post by Stefan on April 11, 2015, 07:11:30 AM »
AMD FirePro™ Unified Driver 15.3
Quote

New Features

Display Features

Eyefinity™ Pro
Eyefinity Pro provides users with the ability to expand display configurations beyond the output
capabilities of a single graphics card. Use up to four graphics cards to drive up to 24 displays as a
single desktop. A beta of this feature is now available through a special driver build option.
Eyefinity™ with 10-Bit Color Depth
Desktop configured in Eyefinity mode will now be able to drive projectors and displays that
utilize 10-bit color depth.

AMD Freesync™ Support for Single GPU Product Configurations
AMD Freesync technology support is now available for single GPU configurations. For more
information on how Freesync works, FAQ's and what products are currently supported, please
visit the Freesync Technology Page

EDID Management With MST
EDID management provides the ability to emulate displays using the display’s EDID values.
These values are retained by the driver so in the event a display is physically disconnected, the
driver “remembers” the last display attached. This feature was originally designed for display
walls with multiple displays attached to the graphics card. By enabling EDID management,
display configurations are not reset (by the OS) if one or more displays is/are physically
unplugged. By adding MST support, EDID management capability is extended to displays and
monitors connected to MST hubs

Code: [Select]
;----------1503311212-14.502.1019-150317a-182167C-Retail_End_User
DriverVer=03/17/2015, 14.502.1019.0000
AMD6608.1 = "AMD FirePro W2100 (FireGL V)"
AMD6649.1 = "AMD FirePro W5100 (FireGL V)"
AMD6704.1 = "AMD FirePro V7900 (FireGL V)"
AMD6707.1 = "AMD FirePro V5900 (FireGL V)"
AMD6749.1 = "AMD FirePro V4900 (FireGL V)"
AMD674A.1 = "AMD FirePro V3900 (ATI FireGL)"
AMD6780.1 = "AMD FirePro W9000 (FireGL V)"
AMD678A.1 = "AMD FirePro W8000 (FireGL V)"
AMD678A.2 = "AMD FirePro S9000 (FireGL V)"
AMD678A.3 = "Radeon Sky 700"
AMD678A.4 = "Radeon Sky 900"
AMD678A.5 = "AMD FirePro S9050 (FireGL V)"
AMD678A.6 = "FirePro S10000 Passive"
AMD678A.7 = "AMD FirePro S10000 (FireGL V)"
AMD678A.8 = "FirePro S10000 Passive (FireGL V)"
AMD67A0.1 = "AMD FirePro S9150 (FireGL V)"
AMD67A0.2 = "AMD FirePro W9100 (FireGL V)"
AMD67A1.1 = "AMD FirePro S9100 (FireGL V)"
AMD67A1.2 = "AMD FirePro W8100 (FireGL V)"
AMD6808.1 = "AMD FirePro S7000 (FireGL V)"
AMD6808.2 = "Radeon Sky 500"
AMD6808.3 = "AMD FirePro W7000 (FireGL V)"
AMD6809.1 = "AMD FirePro R5000 (FireGL V)"
AMD6809.2 = "AMD FirePro W5000 (FireGL V)"
AMD6821.1 = "FirePro S4000X MxM"
AMD6828.1 = "AMD FirePro W600"
AMD682C.1 = "AMD FirePro W4100 (FireGL V)"
AMD6888.1 = "ATI FirePro V8800 (FireGL V)"
AMD6889.1 = "ATI FirePro V7800P (FireGL V)"
AMD6889.2 = "ATI FirePro V7800 (FireGL V)"
AMD688A.1 = "ATI FirePro V9800P (FireGL V)"
AMD688A.2 = "ATI FirePro V9800 (FireGL V)"
AMD688C.1 = "AMD FireStream 9370"
AMD688D.1 = "AMD FireStream 9350"
AMD68A9.1 = "ATI FirePro V5800 (FireGL V)"
AMD68C8.1 = "ATI FirePro V4800 (FireGL V)"
AMD68C9.1 = "ATI FirePro V3800 (FireGL V)"
AMD68F1.1 = "AMD FirePro 2460"
AMD68F2.1 = "AMD FirePro 2270"
AMD692B.1 = "AMD FirePro W7100 (FireGL V)"
AMD9906.1 = "AMD FirePro A300 Series (FireGL V) Graphics Adapter"
89
New-  Intel® HD Graphics Driver posted for Ivybridge and Baytrail version 15.33.35.4176

The 15.33.35.4176 has been posted to Intel Download Center at the following direct links to the drivers:

32 bit - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=24825
64 bit - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=24826

 Note: It is recommended to upgrade the below list of applications to avoid any unexpected issues.
  • 3DMark11*: Upgrade to 1.0.3 or later
  • Batman Arkham City*: Upgrade to the latest patch
  • Mafia 2*: Upgrade to the latest patch
  • Company of Heroes*: Upgrade to 2.101 and update Opposing Fronts to 2.500 or Tales of Valor to 2.601
  • HomeFront*: Upgrade to 1.0.5 or later
  • Unigine Heaven*: Upgrade to 2.5 or later
  • Battlefield 3*: Upgrade to latest patch
90
CUDA Application Support:
In order to run Mac OS X Applications that leverage the CUDA architecture of certain NVIDIA graphics cards, users will need to download and install the 7.0.36 driver for Mac located here.

New in Release 346.01.02f01:
  • Graphics driver updated for Mac OS X Yosemite 10.10.3 (14D131)
  • Contains performance improvements and bug fixes for a wide range of applications.
  • Includes NVIDIA Driver Manager preference pane.
Release Notes Archive:
This driver update is for Mac Pro 5,1 (2010), Mac Pro 4,1 (2009) and Mac Pro 3,1 (2008) users only.
Pages: 1 ... 7 8 [9] 10