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

Snip and Sketch incompatibility #25

Open
Scarlaid opened this issue Mar 15, 2022 · 9 comments
Open

Snip and Sketch incompatibility #25

Scarlaid opened this issue Mar 15, 2022 · 9 comments
Labels
fixed by window flag patch FSE symptoms Fullscreen Exclusive mode (forced by drivers/etc) is likely to be causing this issue

Comments

@Scarlaid
Copy link

I'm currently using the lastest Borderless Fullscreen a.k.a v1.1.1
Whenever I wanna take a screenshot using Snip & Sketch (hotkey is Windows + Shift + R), normally it would show the toolbar on middle top with a "plus" mouse cursor, instead it kinda overlapped
For tabbing in and out, the screen flashed for a split second

Here's the video: https://streamable.com/xlzrb4
(to recognize the flashing screen, look at my mouse which flashed for a split second)

If these ain't bugs then I'm sorry for bothering 👀

@comp500
Copy link
Owner

comp500 commented Mar 15, 2022

Could you try the test build in #19?

@Scarlaid
Copy link
Author

Could you try the test build in #19?

I tried the test build, the one problem I encountered is somehow my monitor refresh rate downgraded to 60hz, originally was 75hz

I don't know if this the mod fault since my screen meant to be 60hz but I overclocked it to 75hz

@comp500
Copy link
Owner

comp500 commented Mar 15, 2022

Try setting your refresh rate to 75Hz in the Windows settings: https://support.microsoft.com/en-us/windows/change-your-display-refresh-rate-in-windows-c8ea729e-0678-015c-c415-f806f04aae5a
as the test build isn't forced into exclusive fullscreen anymore (assuming it's working) it will use the refresh rate you have configured for your Windows desktop. If changing that still doesn't work, let me know what hardware and driver versions you're using.

@Scarlaid
Copy link
Author

Did exactly what the support link said and it does not put me in 75hz while having Minecraft in Borderless Fullscreen
The display settings said 59hz (which is 60hz becuz windows is weird) after I go both fullscreen and windowed afterward
But when I get in the display adapter properties it's still 75hz

I decided to use my phone to record exact issue I'm facing, here's the video: https://streamable.com/1kcrvm

Here are the specs

  • Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, 3101 Mhz, 4 Core(s), 4 Logical Processor(s)
  • KINGSTON (KVR16N11S8/4) 8GB (2x4GB) DDR3 1600MHz
  • NVIDIA GeForce GTX 750ti OC 2GB DDR5 (Elpida)
  • Driver version 511.79 (ShadowPlay is enabled)
  • Windows 10 Enterprise LTSC build 1809

@comp500
Copy link
Owner

comp500 commented Mar 15, 2022

Hmm, it looks like the game is requesting a 60Hz refresh rate display mode... could you check in the video settings what the "Fullscreen Resolution" slider says? If you're using Sodium, you'll need to press Shift+P to see the vanilla menu with this slider.

For Borderless Fullscreen to work properly, it should be set to "Fullscreen Resolution: Current". If that still doesn't work, check if there are other options in that slider mentioning 75Hz (i.e. "1366x768@75 (24 bit)") and try them.

@Scarlaid
Copy link
Author

Scarlaid commented Mar 16, 2022

The "Fullscreen Resolution" it's always in "Current" state because I don't really bother changing it, as said "High performance impact". I did check around the slider for my resolution "1366x768@75 (24bit)" but the best it could support is "1366x768@60 (24bit)".

Here's another video to detail the issue: https://streamable.com/jwamvu

My guess for this is somehow Minecraft is now forced to use the meant to be supported refresh rate that the monitor offers, not the refresh rate that I overclocked it, though, going back to the v1.1.1 of Borderless Fullscreen, the overclocked refresh rate "1366x768@75 24bit" runs fine 🤔

I did try to disable NVIDIA ShadowPlay afterward but it did nothing

@comp500
Copy link
Owner

comp500 commented Mar 16, 2022

Does "1366x768@75 (24bit)" show up in the menu with 1.1.1 installed? Also try without any mods installed... I'm not sure why it doesn't show up. It might also be worthwhile checking the NVIDIA Control Panel "Change resolution" section; that should show you all the display modes you have available to applications. It could be a bug in the GLFW/Minecraft window handling code, or Windows might not be listing the display mode for some reason...

@Scarlaid
Copy link
Author

Scarlaid commented Mar 16, 2022

Only Sodium, Sodium Extra for the resolution settings, SodiumOption run with Borderless Mining
Neither give me the supported "1366x768@75 (24bit)"
But, the current version does not overwrite the resolution normally, but if I drag down the resolution bar in Vanilla settings (Shift+P), now both the settings will be in "Current" state, it will eventually overwrites the current resolution im having. Going back to the "Borderless Fullscreen" state (in 1.1.1 you did provide in the mod the option to put this as in the slide bar) just works fine
Unlike Dev release, it just overwites instantly

Dev release: https://streamable.com/4lc52q
Current release: https://streamable.com/ukp082

For the NVIDIA "Change resolution", I said above is I overclocked the monitor to run 75hz
Picture below is the available supported resolutions
image

@comp500
Copy link
Owner

comp500 commented Mar 16, 2022

I'm going to split this issue as there are 2 different problems being tracked here :P

@comp500 comp500 changed the title I seriously don't know how to call this "bug" Snip and Sketch incompatibility Mar 16, 2022
@comp500 comp500 added the FSE symptoms Fullscreen Exclusive mode (forced by drivers/etc) is likely to be causing this issue label Dec 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed by window flag patch FSE symptoms Fullscreen Exclusive mode (forced by drivers/etc) is likely to be causing this issue
Projects
None yet
Development

No branches or pull requests

2 participants