![]() But you have to realize, in the past, many Users will post questions not aware of the capabilities of their Hardware or software and ask why it doesn't work. I am sure pokester‌ wasn't purposely trying to insult your intelligence intentionally. If you really want to officially contact AMD Support, you can open a ticket from here: Online Service Request | AMD At times, One or both AMD Moderators may get involved with a certain thread to help the Users. But this is a User to User Forum where Users try to help other Users help fix their issues. This forum is moderated by AMD Employees. Considering that I can't even get concrete understanding that my setup IS FreeSync compatible I'm probably doomed to juggling drivers to suit my needs. It's why I was hoping this could get the attention of those who actually work on the drivers and can explain some of what I'm seeing. I realize this issue is a massive pain to troubleshoot, with obscure hardware and use cases, and most people probably don't even know what to look for with FreeSync. If I can not talk to AMD employees here where can I go for proper support/discussion? I bought the card and the display expressly for FreeSync, low latency, and 120hz in a living room environment with emphasis on emulation + support for modern games. I'm willing to acknowledge that maybe these apps do some things outside of spec or what the drivers expect games to do, but regardless this is something that can be fixed with a rollback (but causes issues in some newer it was unhelpful because it was false and you insulted my intelligence by assuming I would start a thread with hardware that doesn't support the feature. Beyond 18.3.3 a long pause before rendering/alt tabbing is fixed, but FreeSync breaks in some instances while still working in most others, suggesting that something key has changed with how these newer drivers work. Beyond that point tearing and judder is exhibited in all three examples. What I know: smooth scrolling with no tearing will occur in Retroarch OpenGL exclusive mode in 50hz games, VICE rendering to DX surface, and Dosbox OpenGL exclusive mode at low framerates, all with no vsync and merely capped by the emulation speed in 18.3.3 and earlier. Guys, the display supports FreeSync, at the very least this is established and we can move on from that simple fact. ![]() Any insight on why FreeSync functionality has changed in the last year or so? I realize this is hard and fiddly thing to test for, but this is expensive tech, something you market, and a huge incentive for me to stick with your products in the future. I would continue to use 18.3.3 but it has bugs in some newer games so it's not magic bullet. I also notice that your own FreeSync windmill demo has completely broken FreeSync AND Vsync after 17.11.3 as stated in Freesync broken since 17.11.4 yet 17.11.3-18.3.3 will properly FreeSync in every other instance I could throw at it, including Nvidia's Pendulum demo. There will be a bit of a pause or black screen for ~3 seconds before rendering starts, like it's rendering a different way than in newer drivers where it's a lot quicker to start (but occasionally with broken FreeSync as stated). Of note, I notice the way any hardware accelerated game initializes in these older drivers is different. These issues are completely cleared up 17.11.3 through 18.3.3. My display is a NU8000 55" Samsung TV, for reference, updated to the latest firmware. A 60hz game seems to be fine in Retroarch. It will exhibit judder and even occasional tearing in these instances. Two reliable ways to recreate the issue: Retroarch with any PAL/50hz game with the only sync method being "sync to game's exact refresh rate", VICE (C64 emulator) which is primarily PAL. I've seen this referenced in other threads such as Ongoing freesync issues 18.3.4 , but there is indeed something broken or different about FreeSync in key instances starting with this driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |