No, but with DxDiag report it was compiled 30 november
Also that's why it is 22.11.3, and not 22.12.1. Idk why i hadn't noticed it before. So stupid on my side)
Because you only was able to download it at 01.12... And trick is, it seems that 22.11.X means X version of November driver at 2022 year.
So that 30.11 date was mostly set just to make this driver as small update of 22.11 driver
But seems like there should be good stuff to wait from 22.12 driver from rumour? Not even saying that they wouldn't want to mess up RX 7000 series launch
Different time zones do exist. Yes.
Where is AMD based? Yup...
Actually good reasoning. But it only appeard at evening of 1.12 for me. Not accounts for even 13 hours of time zone difference
But still if we take in account, like 6 hours delay for any reason, then it makes sense.
Not directly it seems.
Like it is likely won't be named as Omega, but it will be major update as they hadn't ditched that strategy looking on that thread.
Please, add DX 11 optimizations for non rdna 2 users. It's sad to be left behind for so long.
Are you sure you wanna get pack of issues with them as well?
Black screens, screen flickering, and some applications not liking these optimisation still exist. And there are plenty of them.
Are you sure you wanna get pack of issues with them as well?
Black screens, screen flickering, and some applications not liking these optimisation still exist. And there are plenty of them.
For you and a few others. you're acting like EVERYONE has these issues.
Chrome UI still stuttering, hanging mouse pointer.
Twitch Player still crashing when maximizing video, at least entire chrome isn't freezing anymore, better than nothing 😀
MPO disable, it is again.
Not directly it seems.
Like it is likely won't be named as Omega, but it will be major update as they hadn't ditched that strategy looking on that thread.
Isn't it mostly a major update if you compare from last year's end of year driver? Like if you've kept up with releases there's not much new?
Not directly it seems.
Like it is likely won't be named as Omega, but it will be major update as they hadn't ditched that strategy looking on that thread.
Yeah it won't be named as Omega. Can confirm I talk to this guy who created Omega Drivers.
It seems like Microsoft and game devs are in a competition with AMD/Nvidia driver software engineers. Microsoft and game devs break something with updates and driver engineers try to fix their stupid coding.
Just some random advice for people that are reporting these bugs to AMD: don't act like you know what's causing the bug because most likely you have no clue and it doesn't help if you send bug reports with "fix mpo" or "chrome is stuttering" etc.
Just describe the steps to reproduce the bug, your hw config and if possible a screenshot or video that shows the problem. It's very important that they can duplicate the bug on their end, if they can't...the bug report doesn't help.
It seems like Microsoft and game devs are in a competition with AMD/Nvidia driver software engineers. Microsoft and game devs break something with updates and driver engineers try to fix their stupid coding.
Just some random advice for people that are reporting these bugs to AMD: don't act like you know what's causing the bug because most likely you have no clue and it doesn't help if you send bug reports with "fix mpo" or "chrome is stuttering" etc.
Just describe the steps to reproduce the bug, your hw config and if possible a screenshot or video that shows the problem. It's very important that they can duplicate the bug on their end, if they can't...the bug report doesn't help.
Simple have MPO enabled
Have flip model optimisations on
Have many apps running like firefox or anything else you would
Starts whatsapp video call
Move the window like crazy
Watch seeing a blackscreen occur either within 2 minutes or 1 to 3 hours.
22.7.1 can reproduce it under 2 minuts with MPO enabled, its not that hard.
Also are there any steps at all when a game is litterally just freezing the entire system?
It seems to only happen after couple of days as if its shader cache related then out of random it starts happening every 2 hours. consistently until you go back to old driver where shader cache resets and after it builds up again it starts all over again.
At this point I'd be running Linux and seeing if games still crashed there. If they crash on Linux, then it's hardware-related.
Not necessarily. Linux's drivers are pretty drastically different, where it might utilize your hardware differently enough that whatever was causing the crash might not be triggered. Though if your CPU is the problem then it might actually highlight your problem faster than Windows, since Linux drivers tend to use more CPU instructions and more cores.
Linux also tends to recover better from hardware-caused stability issues, so what might cause Windows to fail might just be a small glitch in Linux.
Doesn't hurt to try, but all I'm saying is if it doesn't crash, that isn't necessarily proving anything. I'd recommend you try memtest86+ and have it use all of your CPU cores. That's always been a great tool for me to test OC stability since you don't risk corrupting anything. Even if you didn't overclock your RAM, it can still become unstable just from pushing your CPU too hard.
No, but with DxDiag report it was compiled 30 november Also that's why it is 22.11.3, and not 22.12.1. Idk why i hadn't noticed it before. So stupid on my side)