New Adrenalin 23.4.3, new Win11 Canary build 25352.1, aaaand still no compatibility!
The fuc*ing invisible text cursor on a white background is still there!
What happens if you set a custom color for the mouse pointer ?
What happens if you set a custom color for the mouse pointer ?
I can't reproduce the issue when a custom color is set. Then the cursor invert color is off.
Yeah, it could be some kind of workaround but the view of the text cursor is a little ugly and bold in this case.
The normal inverted view of the cursor on a white background is buggy. Then the cursor should be black but it's white. It happens just in the edit mode of Chrome text controls.
Actually, forgot to mention that it did set the frame rate target control to 60 FPS which was super weird and I thought things were messed up after I ran Time Spy and got a terrible score. If you update to this driver and have terrible performance check your frame rate target control to see if it is set it to 60 for some strange reason. I have mine set to 240 normally as that is the refresh rate of my monitor.
My timespy port royal scores have been garbage since few recent windows updates, if i do clean install no updates on latest drivers i get a much higher score not sure whats causing it.
I have just installed a new 7900XT and these drivers.. In the Radeon Software it says that the Smart Access Memory is not available but in GPU-Z and in the BIOS it says it's enabled.
I have just installed a new 7900XT and these drivers.. In the Radeon Software it says that the Smart Access Memory is not available but in GPU-Z and in the BIOS it says it's enabled.
Maybe you did a UEFI update and that disabled the SAM?
Looks like I was wrong that increasing minimum clocks in Wattman would be only placebo. I don't know if it was a change in one of the latest drivers, but I need to go higher than 500MHz now to avoid reported delayed frames in mpv. I've set 2300 minimum now to also cover high min clocks in games, still seems to save enough power with desktop usage. Also avoids configuring per-app minimum clocks in WM, as that is just annoyingly buggy by occasionally applying a per-app setting to global setting.
In my case, it happens with Chrome browser when I edit text. Some people say that they have the same problem with MS Word. It doesn't depend on a specific Win11 build. I have it on 22621.1635 and 25352.1.
Are these recent versions better than 22.11.2 for 6700 xt already?
They are much better on a 6800XT, so I would say that yes, they should be better for 6700 XT as well.
I haven't experienced any single crash or black screen with 23.3.x and above, and that's more than a month of use.
Also, all games that I play run well (generally older games, I'm not into these recent Sony console ports stuff)
In my case, it happens with Chrome browser when I edit text. Some people say that they have the same problem with MS Word. It doesn't depend on a specific Win11 build. I have it on 22621.1635 and 25352.1.
I've had this problem for a few driver versions, but I've forgotten about it for a while. It will appear once, when first capturing written text, and all I have to do is move the cursor to another word and then it is visible again. I have this on Opera GX.
However, I still have a problem with Radeon Image Sharpening and Source engine games in full screen. Just a black screen. I have reported this again.
AMD still hasn't fixed the AF control in the driver!
I decided to recheck the situation with forcing AF via drivers using the AVP benchmark tool:
AVP AFx2 = 594.5 fps / AVP AFx16 (Forced AFx2) = 596.2 fps (frame rates are almost the same as expected)
AVP AFx16 = 570.5 fps / AVP AFx16 (Forced AFx16) = 605.8 fps (frame rates are totally different even higher than AFx2)
It looks like forcing AFx16 via drivers doesn't work correctly (if ever works)!
Does anyone have some other explanation for this? I don't know how to make a screenshot of the specific frame so I can visually compare the quality with different options.
One more thing related to this benchmark. A few months ago, when I had 6800XT, this benchmark was affected by another option in the driver - the "Anti-Aliasing Method". Forcing "Adaptive Multisampling" instead of normal "Multisampling" was causing a noticeable drop in frames (almost in half). Now because of the new driver or because of the new 7900XT, it doesn't affect the results at all.
Does anyone have some other explanation for this? I don't know how to make a screenshot of the specific frame so I can visually compare the quality with different options. One more thing related to this benchmark. A few months ago, when I had 6800XT, this benchmark was affected by another option in the driver - the "Anti-Aliasing Method". Forcing "Adaptive Multisampling" instead of normal "Multisampling" was causing a noticeable drop in frames (almost in half). Now because of the new driver or because of the new 7900XT, it doesn't affect the results at all.