Can not add custom resolution 2880x1920 (Surface Pro 8)

[dab51]

Hello. I had the best shot with using the beta release of your driver. However, i edited the XML file to change the last resolution to 2880x1920 but it did not work. I added it but it didnt add the resolution either. It stayed at the default.

How can I add this resolution?

[zjoasan]

First of all, did you deactivate and reactivate the driver in driver manager after editing the xml?

Could you provide the .xml in use, after editing.

[dab51]

I didnt only deactivate and reactivate, i reinstalled it multiple times with deactivating then uninstalling and ticking the box. Also deleted certificates after uninstalling and run the .bat again.

This is the last one i used.

<?xml version='1.0' encoding='utf-8'?> <vdd_settings> <monitors> <count>1</count> </monitors> <gpu> <friendlyname></friendlyname> </gpu> <resolutions> <resolution> <width>2880</width> <height>1920</height> <refresh_rate>30</refresh_rate> <refresh_rate>60</refresh_rate> <refresh_rate>90</refresh_rate> <refresh_rate>120</refresh_rate> <refresh_rate>144</refresh_rate> <refresh_rate>165</refresh_rate> </resolution> </resolutions> </vdd_settings>

However i also used the default where i changed the last resolution just like here, and i also added this resolution as an extra option but it didnt work.

[dab51]

Is there a specific directory where the XML gets copied after installation? Because originally when i first installed it, i did not change anything, it was default XML.

[dab51]

Okay so i can confirm that also when editing the XML to activate 2 virtual displays it doesnt really work. But i also have the Hyper V on atm. I tried shutting down all VMs as well as Hyper V then reinstalling, didnt help.

[zjoasan]

If count doesn't change monitor count, have actually updated the driver to the beta release?

The xml file should be in the same folder as the rest of the driver files. We are working on an installer prototype, but it's on the back burner, with other parts with higher priority.

[dab51]

The xml is in the same folder yes. Every time.

…

On Fri, 23 Aug 2024, 18:21 Joakim Sandström, ***@***.***> wrote: If count doesn't change monitor count, have actually updated the driver to the beta release? The xml file should be in the same folder as the rest of the driver files. We are working on an installer prototype, but it's on the back burner, with other parts with higher priority. — Reply to this email directly, view it on GitHub <#138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKW2LHIV6L2WTWLQPM4TLXTZS5OQDAVCNFSM6AAAAABM6OT7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBXGQYDONJRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[zjoasan]

To make sure you are on beta, try this command in a powershell prompt:

get-pnpdevice -class Display | Where-Object {$_.FriendlyName -like("Virtual*") -or $_.FriendlyName -like("IDD*")}

If it comesback with "Idd*" you are on standard release, If "Virtual Display Driver*" then it's beta, and there is something in the surface version that we have to look at.

[dab51]

OK Display Virtual Display with HDR ROOT\UNK...

This is not on Surface Pro 8 but on a PC with Windows 10 Pro. However the resolution is from Surface Pro 8.

I tried restarting after deleting the driver, didnt work.

[jiangyeyilinzhou]

Author, may I ask if you can help me? I also encountered the same problem. I tried to add a resolution of 2224 * 1668, but it didn't work. I have confirmed that it is the Bata version, and I have also tried adding a refresh rate of 170, but it does not work at any resolution. I have also tried starting from scratch multiple times.
The translation based on Baidu may have errors, but thank you for your help

To make sure you are on beta, try this command in a powershell prompt:

get-pnpdevice -class Display | Where-Object {$_.FriendlyName -like("Virtual*") -or $_.FriendlyName -like("IDD*")}

If it comesback with "Idd*" you are on standard release, If "Virtual Display Driver*" then it's beta, and there is something in the surface version that we have to look at.

[sofmeright]

I have this driver working on a SP9 with 2880x1920 at 120hz I set it to 144hz and let the screen saturate as it can. You really need to make sure that the options.txt is within the C:\IddSampleDriver\options.txt location and make sure the entry exists. I include my workstation and tested devices @ http://sh.uni2.cc/28JLJ . Good luck! SP8 should work, no problem!

In example:

C:\IddSampleDriver\options.txt

1
...
1080, 1920, 120
1080, 1920, 144

[jiangyeyilinzhou]

我让这个驱动程序在 2880x1920 分辨率、120hz 的 SP9 上运行，我将其设置为 144hz，让屏幕尽可能饱和。您确实需要确保

Okay, thank you, but I think I may eventually give up. The main reason is that I think AMD graphics cards have poor compatibility. If possible, I will prepare to replace the Nvidia graphics card. Thanks for your help. However, I followed the instructions you described, but it still doesn't work.
Although I won't be using it in the future, to provide reference for others, please specify 1920x1080. Do I need 1080 at the beginning of the document?
I am no longer concerned about this issue. Thank you for your reply

[dab51]

I tried the non-beta version after the beta, it doesnt work for me on my Windows 10 but the beta works.

…

On Fri, 6 Sept 2024, 01:21 sofmeright, ***@***.***> wrote: I have this driver working on a SP9 with 2880x1920 at 120hz I set it to 144hz and let the screen saturate as it can. You really need to make sure that the options.txt is within the C:\IddSampleDriver\options.txt location and make sure the entry exists In example: options.txt 1 ... 1080, 1920, 120 1080, 1920, 144 — Reply to this email directly, view it on GitHub <#138 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKW2LHOIX3IDYWQBHAQ6OXDZVDRO3AVCNFSM6AAAAABM6OT7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZSHA3DQNBTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bud3699]

If the non beta works and the beta does then that's because the beta is falling back to its default resolutions meaning it's not reading the config file. The paths for the config definitely need to be in the right spot or you can add a custom path in the registry

Hkey local machine\SOFTWARE\MikeTheTech\VirtualDisplayDriver

If the paths don’t exist then add them then create a dword called vddpath then place the new directory address in there

After that disable and re-enable the driver and it should read from that directory instead

[sofmeright]

我让这个驱动程序在 2880x1920 分辨率、120hz 的 SP9 上运行，我将其设置为 144hz，让屏幕尽可能饱和。您确实需要确保

Okay, thank you, but I think I may eventually give up. The main reason is that I think AMD graphics cards have poor compatibility. If possible, I will prepare to replace the Nvidia graphics card. Thanks for your help. However, I followed the instructions you described, but it still doesn't work. Although I won't be using it in the future, to provide reference for others, please specify 1920x1080. Do I need 1080 at the beginning of the document? I am no longer concerned about this issue. Thank you for your reply

I would be curious if this tool helped you! https://github.com/sofmeright/VirtualDisplayDriver_Wizard
As of the most recent release Sunshine Integration is implemented. If by any chance you are using Sunshine you can follow the instructions in the readme and all your resolutions for the Virtual Display Driver will be set dynamically here on out from what you set in the moonlight clients settings. If it doesn't work YEA maybe somethings wrong. But this will take user error out of the scenario otherwise! It is setup to work with either the txt or xml formats so it will convert the txt to xml format for you too if you follow the instructions!

[cloudrainstar]

I've had success with editing the xml after moving the files to the path C:\VirtualDisplayDriver

Seems to be the default path as specified here:

https://github.com/itsmikethetech/Virtual-Display-Driver/blob/master/Virtual%20Display%20Driver%20(HDR)/MttVDD/Driver.cpp#L93

Hopefully that helps someone

[bud3699]

The latest beta changed to that path, as did updated installation instructions in the read me