Hello,
First post here. Really tried hard to find an answer but no luck, therefore looking for some help!
I am using a Mac Pro 5,1 (12-core) and recently added an evga gtx 980 and I am using a 27 inch LG UHD (3840X2160 native), connected via display port to my mac pro tower. I am running 10.11.6 with the most recent NVIDIA Web drivers 364.03.15f01.
Installing the nvidia web drivers is the only way to go, since the gtx 980 is not internally supported and the image with no drivers is not accelerated, sluggish and barely usable.
Upon nvidia web driver installation, everything became large, fonts icons etc. On the display panel there is selected the Resolution "Default for Display". First I thought that I was getting a UHD resolution with very high dpi's but was wrong. The monitor displays a 1080p image (checked via the system report panel). Shouldn't the "Default for display option" show a full UHD image? Now, the only way to go UHD is via the Scaled option, which should'n be the case. Is this a known issue?
Any ideas on how to resolve this issue would be highly appreciated!
First post here. Really tried hard to find an answer but no luck, therefore looking for some help!
I am using a Mac Pro 5,1 (12-core) and recently added an evga gtx 980 and I am using a 27 inch LG UHD (3840X2160 native), connected via display port to my mac pro tower. I am running 10.11.6 with the most recent NVIDIA Web drivers 364.03.15f01.
Installing the nvidia web drivers is the only way to go, since the gtx 980 is not internally supported and the image with no drivers is not accelerated, sluggish and barely usable.
Upon nvidia web driver installation, everything became large, fonts icons etc. On the display panel there is selected the Resolution "Default for Display". First I thought that I was getting a UHD resolution with very high dpi's but was wrong. The monitor displays a 1080p image (checked via the system report panel). Shouldn't the "Default for display option" show a full UHD image? Now, the only way to go UHD is via the Scaled option, which should'n be the case. Is this a known issue?
Any ideas on how to resolve this issue would be highly appreciated!