If you don't game, there is no need to be on the game driver branch.
There is every chance that a bug in a gaming driver ends up in a studio driver as well, especially if it is something more under the radar. Often the fix for something is to simply roll back to the previous driver. (Though I did not care for the upscaling, it needs work and runs the GPU surprisingly hard.)Īlso note that this dforce bug didn't effect older versions of Daz Studio. There are times when the wait is much longer. However the studio drivers only got this feature a few days ago with the recent studio driver. The gaming drivers had this since February. For example, Nvidia has a new video upscaling option for streaming in some browsers, which also reduce noise in compression. Because of the more frequent releases, a gaming driver might actually get a new feature before a studio driver is released. I do not believe dforce is something that Nvidia would test for, but the specific bug that caused dforce to fail was fixed in a gaming driver. Sometimes the drivers break things, but that can happen with anything. Studio drivers are updated on a roughly quarterly schedule, while the game drivers might get an update each month or even more. Then another big game came out and sure enough a game driver came along with it. Like the recent game Harry Potter game, that was a huge game release, so Nvidia put out a new driver that optimized for it. Game drivers update far more frequently because they are released around new game launches.
The ONLY promise made with Studio drivers is that they are verified for the specific applications.ĭforce was not truly broken by a game driver. Studio drivers are really no different than game drivers in nature.
0 kommentar(er)
