Interface not usable on Hybric PC (Surface pro like)

[mokamars]

Godot version:
Godot_v3.0-rc2_win64

OS/device including version:

• Dell PC Hybrid (Surface Pro like)
• Windows 10

Issue description:
Impossible to work with Godot :
On the project selection window, all the button interface are difficult to click
On the project window, all menus does not appear

I think this is because of the Hybrid capability of the PC, All the interface is by default zoomed by 150%, but if I try 100% zoom, it is not working

[mokamars]

I add a screenshot of the main window : Menu does not appear

I can help to test if necessary

[mhilbrunner]

@mokamars Why did you close this?

[mokamars]

@mhilbrunner : Just because I'm a looser :) I din't want to close it and didn't realize it in fact. I reopen it right now !

[eon-s]

GPU? sounds like the intel driver issue.

[mokamars]

Graphic card : Intel HD grpahics 620
Processors : i-5 7300 CPU @ 2,6GHz (4 cores)
Is that the kind of information you want ?

[mokamars]

And i have a similar issue when using the 2.1 version of godot. But it seems a little bit better. For example, if I want to click on a button on the project selection window I need to put my mouse pointer maybe 5 pixels below a button. In 3 RC2, I need to put my mouse poitner 10 pixels below

[bojidar-bg]

Looks potentially related/duplicate of #9275.

[eon-s]

Also looks like this #8902

Check if you can up/downgrade the drivers.

[mokamars]

I can't change the drivers.
I thinks it's probably more something like #9275 effectively.

Godot is the only application that has this problem.

I'm looking at parameters to see if I can do something with the windows configuration options.

[mokamars]

I can't change the drivers.
I thinks it's probably more something like #9275 effectively.

Godot is the only application that has this problem.

I'm looking at parameters to see if I can do something with the windows configuration options.

PS : I tried to use ProcessExplorer to diagnose godot but the process is invisible.
PS2 : I need to apply the creator update this evening, ite ssems there is some improvements about DPI awareness, maybe it'll change something.

[shonlove]

I'm having this same problem - with both the downloaded .exe and one I compile myself.

It seems like all my trackpad/keyboard input are all delayed by one event - I move the mouse over a button and it doesn't highlight until I move the mouse pointer OUT of the button. Typing is delayed by one keystroke - I type a character and it doesn't appear until I type the NEXT character, etc.

Weirdest thing is that if I run either .exe with the --verbose command-line option, everything works splendidly! So very strange.

I'm testing this on a new Microsoft Surface Pro i5 w/ Intel HD graphics 620 on Windows 10 Pro. The behavior doesn't change when I flag the .exe for HiDPI mode, either.

I don't think this is a driver issue since everything works amazingly well when I include "--verbose" on the .exe command-line. Either way, AFAIK I have the latest Intel graphics drivers installed.

[ghost]

Solution to this problem on Surface Pro 4's at the end of this comment.

Right clicking Godot_v3.0.6-stable_win64.exe and creating a shortcut and modifying the shortcut to include --versbose fixes it on a Surface Pro 4.

Setting "Disable Fullscreen Optimizations" under compatibility doesn't help.

In comparison with @shonlove above I have a 520, not a 620.

My wife also has a Surface Pro 4 and Godot works properly WITHOUT using --verbose, but her drivers are older:

I've downgraded my driver using the enabled downgrade option:

### I can CONFIRM this fixes the issue on Surface Pro 4's, the problem was caused by User (aka me) downloading newer Intel graphics drivers from Intel's website directly instead of just using Surface Pro's older but reliable built in driver.

If I may make a suggestion as to what the problem is, it might boil down to a "mixup" between what constitutes a pointer/mouse update event. My Surface Pro 4 currently has 5 input devices:

1.Touchscreen
2.Pen Input
3.Keyboard Input
4.Keyboard Touch Pad
5.USB Wireless Mouse

The reason --verbose works must be that it's triggering a UI update either regardless of input or just more often enough where it's no longer a problem. I was having worse issues with Ogre3D, which I've ceased using after finding out about Godot and how much easier it is to use.

Additionally the built in graphics drivers might have better support for filtering through different input devices. (Is that a thing Graphics Drivers even do?) Might just provide better "refresh" update commands, I'm talking way out my league here so take it with a grain of salt.

My natural inclination when I noticed this issue immediately was to go the the editor options and find some kind of "refresh continuously" option that would warn about performance but would fix the symptoms.

[reduz]

This is an intel bug, nothing can be done about it from our side. As far as I tested, latest driver fixes it, so will be closing this.