Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Application scaling #17

Open
Karmoq opened this issue Oct 6, 2017 · 2 comments
Open

Windows Application scaling #17

Karmoq opened this issue Oct 6, 2017 · 2 comments
Assignees

Comments

@Karmoq
Copy link

Karmoq commented Oct 6, 2017

Hey hecomi,
first of all, thank you for making such a powerful tool.

My issue is that I have a 4k screen and I am using the scaling in the display settings to scale up texts, apps etc. The problem now is if I use uDD that I get a grey texture instead. It has probably to do with the resolution because it says in the Unity editor that the monitor has only a resolution of 2560x1440 instead of the 3840x2160 when I use a scaling of 150% in the display settings of windows.

Many thanks again for this package and for making it open source

@hecomi
Copy link
Owner

hecomi commented Oct 19, 2017

Sorry for my late reply....
Thank you for using this asset and I'm very glad to hear that.

I also use two 4K screens and both are scaled to 150% (same as you). I've faced the same problem when I use uDD for the first time because Windows returns the wrong display size. When I use it for the second time, however, this bug doesn't occur. But If I change the name of the .exe or move it to the other directory, it occurs again. Is this the same case as yours? Or does this always occur in your environment?

@lux
Copy link

lux commented Sep 14, 2018

I believe I ran into the same thing my first run as well. The plugin showed grey and my desktop's display settings changed causing Unity's UI to go tiny. Here's my output log in case that helps:

uDesktopDuplication.log

Edit: It's worked perfectly on every subsequent launch. Not sure if this is related too, but another of our developers saw a repeated "d3d11: attempt to lock null buffer" message on first launch and everything froze.

@hecomi hecomi self-assigned this Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants