Bug Report Misplaced cursor and random pixels glitch in OBS (64bit)

AquamarineArts

New Member
Since I've installed OBS on my new laptop, I've had several glitches that I can't seem to fix in any way. The first one that I noticed is random pixels appearing at the bottom of the video, like this:
unknown.png


And the bug I noticed later on throughout the process was a misplaced cursor (cursor should be somewhere within the area of the blue circle, but wasn't there):
1533653302535.png


I'm running OBS on Windows 10 Home in this case, and I didn't have this issue back when I used it on Windows 7 Home Premium.
 

Banyarola

Active Member
I may be wrong but it seems your graphics card doesn't have the muscle for the demand being put on it...
 

AquamarineArts

New Member
The scale of the Display is 100% in Windows?
It's not. But I tried changing the scale to 100% and it didn't work out too well for me. I admit that I haven't tried to see if this changes anything on OBS, but it resized literally everything including the icons on my taskbar.
 

Banyarola

Active Member
Well, I'm sure someone here will help you..
Go to Help/Upload log file and post the link here...
 

Suslik V

Active Member
Cursor is hardware thing, so OBS Studio uses emulation to render it for Window Capture. If (x; y) coordinates doesn't match (different scale) - you can get this kind of errors.
 

AquamarineArts

New Member
Cursor is hardware thing, so OBS Studio uses emulation to render it for Window Capture. If (x; y) coordinates doesn't match (different scale) - you can get this kind of errors.
So basically all I can do is change the scale? That's just great. I tried this and I really didn't like what it did with my screen, so um...
 

Suslik V

Active Member
It looks like the application is recognized by system like "DPI unaware" and you are running Win10. Thus, you can try compatibility tab from the FireAlpaca.exe shortcut - make checked the Disable display scaling on high DPI settings option if any (application restart required).

It is hard to resolve this kind of issues in other way. Here is some info:
https://docs.microsoft.com/en-us/windows/desktop/hidpi/high-dpi-desktop-application-development-on-windows said:
... if a process is DPI unaware (and running on a high-DPI display) and queries the screen size, Windows will virtualize the answer given to the application such that it sees the screen size in 96 DPI units ...
Something similar happens in the OBS Studio. Studio captures picture before it scaled up by the display manager, but the metrics says that the window is already scaled up. DPI handling changes from build to build of the Windows, so it worsens the things. The simples way to resolve this on OBS side - is to implement custom (user defined) parameter for dpi unaware windows inside the 'Window Capture' source. Common row of Windows display dpi: 96, 120, 144, 168, 192, 216, 240, 264, 288, 312, 336, 360, 384 (from 100% to 400% in 25% steps). This could remove black bars when will be enabled and align cursor to the captured picture. Is this feature needed in OBS itself?
 
Top