AMD has pushed back the release of a beta driver meant to bring frame pacing to Eyefinity multi-monitor configs and 4K displays—and to a bunch of other configurations, as well. The driver was originally scheduled for a fall release, but AMD now tells us to expect it next month.
Currently, only the Radeon R7 260X, R9 290, and R9 290X support frame pacing on multiple displays and at 4K resolutions via their XDMA transfer hardware, which other Radeons lack. The new driver will add frame pacing support for 4K and Eyefinity display configs on older Radeons. AMD says it will also expand frame pacing to "all [Graphics Core Next] and earlier products that didn't have it until now."
The current release time frame for the driver is "January." AMD doesn't expect additional delays, but it warns that, "as always," its schedule could change.
AMD's first frame-pacing driver came out this summer. Much like Nvidia's frame metering, frame pacing technology synchronizes frame delivery between multiple GPUs in order to minimize microstuttering and dropped frames. The result is noticeably smoother gameplay and a greater perceived benefit from the addition of an extra GPU. Without frame pacing, a dual-card CrossFire config often doesn't feel much quicker than a single-GPU setup.
|1. Ryszard - $603||2. Hdfisise - $600||3. Andrew Lauritzen - $502|
|4. Redocbew - $350||5. the - $306||6. SomeOtherGeek - $300|
|7. chasp_0 - $251||8. Ryu Connor - $250||9. mbutrovich - $250|
|10. YetAnotherGeek2 - $200|
|In the lab: FLIR's One thermal camera||25|
|Black Friday deals: Dell's U3415 curved monitor for $650 and more||20|
|Abu Dhabi government fund may be shopping GlobalFoundries||42|
|Asus goes for the gold with its 20th Anniversary GTX 980 Ti||6|
|MSI's Eco motherboards let owners fine-tune power consumption||6|
|Gigabyte's Z170X-Gaming G1 motherboard reviewed||14|
|Star Wars Battlefront video review||38|
|Club 3D active adapters convert DisplayPort 1.2 to HDMI 2.0||22|
|Phanteks' Power Splitter lets two systems run on one PSU||45|
|This is the answer to SSK's question on the Firefox news post.||+33|