- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I bought a new b570 card.
With my old NVIDIA rtx3050 card and monitor philips 222v8 i could enable in control panel that my monitor is g sync compatible, with display port.
The monitor supports adaptive v-sync.
With the b570 intel i cant enable the vrr support.
My monitor is 75hz and i connect with display port.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Philips lists only AMD graphics cards as compatible in the user manual for the 222V8 monitor (see section 4 "Adaptive Sync"). However, if an Nvidia card supports variable refresh rates via DisplayPort, this should also be possible with an Intel Arc B570.
Please run edid-test.exe:
https://www.monitortests.com/edid-test.zip
This will create a file named "edid-test.txt" in the same folder. Please attach this TXT file here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The data shows that the monitor supports both VESA AdaptiveSync and AMD FreeSync in the 48–75 Hz frequency range.
Can this be enabled in the Intel Graphics Software?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In this display menu and general section i see only scaling mode and scaling method.
The variable refresh rate section does not exist.
In the last section that says information it says that variable refresh rate does not supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your driver version 32.0.101.8247 is up to date. This DisplayPort to DisplayPort connection is usually foolproof. I don't understand this either.
We need advice from the Intel Graphics Team. Is there a driver/compatibility issue here?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monitor Hardware ID: Monitor\PHLC251
Can anyone please answer?
I have connected this with display port.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My device id for monitor is PHLC251
If i use cru and change the id to DELA179
The vrr works as intended.
You seem to don't correctly identify the Philips monitor or you have hardcoded the ids in the driver.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, that's very interesting.
Before:
After:
The device ID was originally read into the Windows registry by the Nvidia card. This could have led to an unintended incompatibility after the graphics card change. I've never seen anything like this before.
It would be interesting to see what happens if you run the "reset-all.exe" file from the CRU download package. This resets all ever created EDIDs in the Windows registry, and after restarting the computer, only the actually connected devices will be recognized. I'm almost certain the monitor would then work correctly again with its original device ID.
How did you uninstall the Nvidia driver? For a graphics card change, using Display Driver Uninstaller (DDU) is recommended.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I uninstalled the nvidia driver with ddu.
When i run the reset-all.exe ,at restart the vrr is not supported.
I also uninstalled the intel driver with ddu and reinstalled.
Now when i re-edit the id to DELA179 it works again.
It seems that is an easy fix to add support for Philips with PHLC251 id.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your feedback. That's really interesting.
The Intel Graphics Team should definitely take a closer look at this. Very strange.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I created a thread there in igcit for the workaround and this is the answer:
-https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/1294
Totally disappointed and i was a beta tester for big companies.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page