Bug/Feature request: Scaling mode doesn't change

[woon0]

I use a 21:9 Ultrawide. I want to be able to switch between [16:9 stretched to 21:9] and [16:9 on 21:9 with black bars] for use in different games (stretched on CS, black bars on Fortnite). I do this in NVIDIA Control Panel by switching "Scaling mode" between "Fullscreen" and "No scaling"/"Aspect Ratio". This scaling setting however does not save in DisplayMagician, if I have "Fullscreeen" selected in NVIDIA Control Panel and try switching to a profile where "Aspect Ratio" was picked, the resolution is still stretched as if I had "Fullscreen" selected (which the now applied profile shouldn't). If DisplayMagician had this feature, it would save me the effort of having to switch in (the surprisingly slow) NVIDIA Control Panel every time.

I would like the scaling setting to be stored in the profile file.

I have considered and tried other software, but they have their own negative quirks, and soDisplayMagician is the best software I've found.

I know it is possible to save this setting in a profile file, Helios Display Management is able to (however I can't stand the seemingly unchangable 30 second time countdown every time a profile should switch).

[terrymacdonald]

Hi @woon0, It's likely that I just haven't written the code that stores that information. I have to write a function that interacts with the NVIDIA driver and that takes a bit of time to do. Also, adding this feature to DM will mean that everyone's existing DisplayProfile will need to be updated to a newer format, as that information currently doesn't seem to be included in the information I grab from the NVIDIA driver. The upshot of this is that it will most likely be a while before I'll be able to add that functionality to DM. I'll have to have a think as to whether I am going to add this to the next release of DisplayMagician (v2.6.0) as it will force people to have to recreate their Display Profile's again from scratch. ANyway thanks for the feature request. It's good to have feedback like this so I can add it into my future dev roadmap. Thanks Terry

[woon0]

I understand. I mainly reported this to bring it to your attention, and to hope that it fit into a future addition.

I can continue to look for a replacement, or just use Helios despite the 30s wait.

Thank you.

[terrymacdonald]

@woon0 I had a closer look at your issue, and this feature should already be supported in v2.5.0 of DisplayMagician. Though with that said I've just realised that there is a bug in v2.5.0 where it doesnt always apply the NvAPI_SetDisplayConfig configuration every time due to a bug in my library (due to the way that C# handles interfacing with the C++ NVIDIA NvAPI DLL).

Basically you'll be a bit stuck for the next little while as I'm going to need to slightly rewrite NVIDIALibrary to use classes rather than structs for how it interacts with the NVIDIA driver, so I might need to look at how Soroush Falahati handles it in his NvAPIWrapper.net codebase. Le sigh.

I've also just realised this is a critical bug that will stop me releasing the upcoming DM v2.6.0. I hadn't realised that SetDisplayConfig was involved in handling the NVIDIA scaling, and to avoid this error I've simply disabled that code in v.2.6.0. This isn't going to work, as many people use the NVIDIA specific controls, and that is going to cause some issues.

Damn.

Looks like I've got a lot of code writing in my future, and looks like I will have to delay the release of DM v2.6.0 for another month or two :(.

Thanks
Terry

[terrymacdonald]

Hi All,

Time for an update.

The fix is in the code and works (also we now support 3rd apps and games added to Steam library too!) but my current hold up is actually in the packaging of the application into a windows installer. I've been testing different ways to do this as the move from .net framework 4.8.1 to .net core 8.0.0 has been a massive change. It has resulted in a completely different set of binaries and dlls and other files being created, as well as a different build process too. This is all taking some time to figure out.

I've gone from a WIXv3 based installer to a windows default installer to an NSIS installer then back to a WIXv4 installer all within the last month. It's necessitated me building a brand new way of handling the desktop background context menu, and even down to which libraries are used within the application. It's been a ton of work.

I'm now down to the last few bugs to iron out, and to finish the new packaging process. I think I should have something ready for everyone to test within the next month (assuming there aren't anymore show stoppers.

My goal is to then send out messages through this issues list to get you all to test some DM v2.6.0 test builds, and then once the major bugs are ironed out I will push out the DM v2.6.0 beta to those users who opted in the beta builds. And then I'll finally push the DM v2.6.0 update to the main user group.

Lastly, I've decided to hold back the NVIDIALibrary update for now until DM v2.7.0 as it requires a LOT more work testing and troubleshooting many errors. The Steam beta client changing file structures has forced my hand here a little bit, so a better NVIDIALibrary will just have to wait for now.

Thanks
Terry