Incorrect windows scaling - mouse offset from view - menu bar invisible #51521

Closed
opened 2017-05-16 14:32:13 +02:00 by John Brown · 104 comments
Member

System Information
Windows 10 (1703)
Intel 7th gen HD graphics
Intel and Lenovo display drivers behave the same.
Lenovo ThinkPad Yoga 370 Intel Core i5 7th gen.

Blender Version
Broken:
2.68a 64 bit,
2.75a 32 and 64 bit,
2.77a 64 bit,
2.78c 64 bit,
2.78 f3d9f0c 64 bit both standard and the experimental vc14 compilers,
2.80 branch f637145 64 bit.

Worked: (I cannot find a version of Blender from the last few years that works with the latest Intel drivers!)
It works if I revert to an older version of the Intel HD drivers for 7th gen as suggested by @someDragon.
Intel drivers version 15.45.16.4627 previous release 23 March 2017, works.
Added to the Intel developer support forum:
https:*software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/735289#

Short description of error
Window layout does not fit the screen. The title bar appears to overlay the top menu bar. The positions are all offset like the graphics on display are a different size to the internal calculations. The mouse pointer needs to be a few millimetres under the screen button to be able to click on it!
The image attached best describes the issue. Note that there is no menu bar visible and the side bar is partly outside the window edge.
Blender-278and277NoMenuBar2017-05.png

Exact steps for others to reproduce the error
I suspect it is a specific hardware combination that causes the issue. 1920x1080. I've tried both the Lenovo and the Intel versions of the display drivers.
By default I have the Windows 10 display scaling set to the recommended 150% however I have tried changing the scaling to 100% and the behaviour of Blender is unchanged!

**System Information** Windows 10 (1703) Intel 7th gen HD graphics Intel and Lenovo display drivers behave the same. Lenovo ThinkPad Yoga 370 Intel Core i5 7th gen. **Blender Version** Broken: 2.68a 64 bit, 2.75a 32 and 64 bit, 2.77a 64 bit, 2.78c 64 bit, 2.78 f3d9f0c 64 bit both standard and the experimental vc14 compilers, 2.80 branch f637145 64 bit. Worked: (I cannot find a version of Blender from the last few years that works with the latest Intel drivers!) It works if I revert to an older version of the Intel HD drivers for 7th gen as suggested by @someDragon. Intel drivers version 15.45.16.4627 previous release 23 March 2017, works. Added to the Intel developer support forum: [https:*software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/735289# ](https:*software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/735289#) **Short description of error** Window layout does not fit the screen. The title bar appears to overlay the top menu bar. The positions are all offset like the graphics on display are a different size to the internal calculations. The mouse pointer needs to be a few millimetres under the screen button to be able to click on it! The image attached best describes the issue. Note that there is no menu bar visible and the side bar is partly outside the window edge. ![Blender-278and277NoMenuBar2017-05.png](https://archive.blender.org/developer/F600005/Blender-278and277NoMenuBar2017-05.png) **Exact steps for others to reproduce the error** I suspect it is a specific hardware combination that causes the issue. 1920x1080. I've tried both the Lenovo and the Intel versions of the display drivers. By default I have the Windows 10 display scaling set to the recommended 150% however I have tried changing the scaling to 100% and the behaviour of Blender is unchanged!

#53534 was marked as duplicate of this issue

#53534 was marked as duplicate of this issue

#53255 was marked as duplicate of this issue

#53255 was marked as duplicate of this issue

#53199 was marked as duplicate of this issue

#53199 was marked as duplicate of this issue

#53184 was marked as duplicate of this issue

#53184 was marked as duplicate of this issue

#52967 was marked as duplicate of this issue

#52967 was marked as duplicate of this issue

#52956 was marked as duplicate of this issue

#52956 was marked as duplicate of this issue

#52879 was marked as duplicate of this issue

#52879 was marked as duplicate of this issue

#52874 was marked as duplicate of this issue

#52874 was marked as duplicate of this issue

#52830 was marked as duplicate of this issue

#52830 was marked as duplicate of this issue

#52810 was marked as duplicate of this issue

#52810 was marked as duplicate of this issue

#52770 was marked as duplicate of this issue

#52770 was marked as duplicate of this issue

#52799 was marked as duplicate of this issue

#52799 was marked as duplicate of this issue

#52783 was marked as duplicate of this issue

#52783 was marked as duplicate of this issue

#52773 was marked as duplicate of this issue

#52773 was marked as duplicate of this issue

#52789 was marked as duplicate of this issue

#52789 was marked as duplicate of this issue

#52673 was marked as duplicate of this issue

#52673 was marked as duplicate of this issue

#52600 was marked as duplicate of this issue

#52600 was marked as duplicate of this issue

#52228 was marked as duplicate of this issue

#52228 was marked as duplicate of this issue

#52033 was marked as duplicate of this issue

#52033 was marked as duplicate of this issue

#51959 was marked as duplicate of this issue

#51959 was marked as duplicate of this issue

#51952 was marked as duplicate of this issue

#51952 was marked as duplicate of this issue

#51872 was marked as duplicate of this issue

#51872 was marked as duplicate of this issue

#51786 was marked as duplicate of this issue

#51786 was marked as duplicate of this issue

#51784 was marked as duplicate of this issue

#51784 was marked as duplicate of this issue

#51670 was marked as duplicate of this issue

#51670 was marked as duplicate of this issue
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @jcbdigger

Added subscriber: @jcbdigger
Author
Member

I've experimented with command line options.
The -W to make it full screen borderless works.
I don't like this setup but at least Blender is usable.

I've now gone back as far as 2.68a and have the same behaviour. I am confident it is an an incompatibility with the operating system but I am unable to find a way to circumvent it.

I have tried all of the Windows compatibility options.

On another machine running Wndows 10 (1607) I have it working.

I've experimented with command line options. The -W to make it full screen borderless works. I don't like this setup but at least Blender is usable. I've now gone back as far as 2.68a and have the same behaviour. I am confident it is an an incompatibility with the operating system but I am unable to find a way to circumvent it. I have tried all of the Windows compatibility options. On another machine running Wndows 10 (1607) I have it working.
Author
Member

If I use DPI scaling or the Double option, I can see the missing elements but the mouse position is still offset vertically so it is difficult to use.

Even with the -W option, where the primary view works correctly, the User Preferences dialogue boxes have the issue with the mouse pointer being offset from the icon or text they are clicking on!

If I use DPI scaling or the Double option, I can see the missing elements but the mouse position is still offset vertically so it is difficult to use. Even with the -W option, where the primary view works correctly, the User Preferences dialogue boxes have the issue with the mouse pointer being offset from the icon or text they are clicking on!
Author
Member

My other machine has finally got round to updating to Windows 10 (1703).
Blender still works and scales as expected. So at least it's not an underlying Windows 10 (1703) issue.

The machine that is displaying properly is 4th gen Intel HD graphics.
The one that is not displaying correctly is 7th gen Intel HD graphics.

My other machine has finally got round to updating to Windows 10 (1703). Blender still works and scales as expected. So at least it's not an underlying Windows 10 (1703) issue. The machine that is displaying properly is 4th gen Intel HD graphics. The one that is not displaying correctly is 7th gen Intel HD graphics.
Author
Member

Is there any debugging I can run or logs I can check to try to identify what the rogue machine is doing with it's display scaling?

Is there any debugging I can run or logs I can check to try to identify what the rogue machine is doing with it's display scaling?

Added subscriber: @brecht

Added subscriber: @brecht

Please try the latest build from here, there have been some DPI improvements for 2.79 that might help.
https://builder.blender.org/download/
https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.79/UI#Automatic_DPI

Please try the latest build from here, there have been some DPI improvements for 2.79 that might help. https://builder.blender.org/download/ https://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.79/UI#Automatic_DPI
Author
Member

@brecht thanks for the suggestions.
None of them were any different, they all had the same problem with the window being partially under the title bar and the mouse pointer being offset!
I've now tried:
2.78 f3d9f0c both standard and the experimental vc14 compilers
2.80 branch f637145

@brecht thanks for the suggestions. None of them were any different, they all had the same problem with the window being partially under the title bar and the mouse pointer being offset! I've now tried: 2.78 f3d9f0c both standard and the experimental vc14 compilers 2.80 branch f637145

Added subscriber: @NicNic

Added subscriber: @NicNic

Good afternoon.
I have exactly the same problem on my new laptop.
Also tried different builds, very old and new ones from graphicall.org.

I attached the system-info.txt file.

system-info.txt

I also removed the manufacturer graphical display drivers and let Windows 10 install them again automatically. No change.
Then I let the Intell installer install the latest drivers. Still no difference.

Just tried the https://builder.blender.org/download/ version. Same problem.
See sys-info.txt

system-info.txt

Good afternoon. I have exactly the same problem on my new laptop. Also tried different builds, very old and new ones from graphicall.org. I attached the system-info.txt file. [system-info.txt](https://archive.blender.org/developer/F607335/system-info.txt) I also removed the manufacturer graphical display drivers and let Windows 10 install them again automatically. No change. Then I let the Intell installer install the latest drivers. Still no difference. Just tried the https://builder.blender.org/download/ version. Same problem. See sys-info.txt [system-info.txt](https://archive.blender.org/developer/F607345/system-info.txt)
Author
Member

@NicNic good call on the system-info.txt file. I've attached the same from my system.
system-info.txt

The bit that stands out to me is that the graphics are from the 7th gen processors:
renderer: 'Intel(R) HD Graphics 620' (and your's is 630)
vendor: 'Intel'
version: '4.4.0 - Build 21.20.16.4664'

What is the exact make and model of the computer you are using?
I would guess, it has a 7th gen Intel processor in it.

The Intel(R) HD Graphics 630 and 620's are built in to the latest generation of the Core i7 and i5 processors. More and more people will get those when they buy new computers.

@NicNic good call on the system-info.txt file. I've attached the same from my system. [system-info.txt](https://archive.blender.org/developer/F607944/system-info.txt) The bit that stands out to me is that the graphics are from the 7th gen processors: renderer: 'Intel(R) HD Graphics 620' (and your's is 630) vendor: 'Intel' version: '4.4.0 - Build 21.20.16.4664' What is the exact make and model of the computer you are using? I would guess, it has a 7th gen Intel processor in it. The Intel(R) HD Graphics 630 and 620's are built in to the latest generation of the Core i7 and i5 processors. More and more people will get those when they buy new computers.

Added subscriber: @John-44

Added subscriber: @John-44

@jcbdigger, You are right about the processor (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz / Intel(R) HD Graphics 630). This info is also in the system-info.txt, near the end.

@jcbdigger, You are right about the processor (Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz / Intel(R) HD Graphics 630). This info is also in the system-info.txt, near the end.

Added subscriber: @someDragon

Added subscriber: @someDragon

I'm having the same issue with an (also 7th gen) Intel Pentium g4560 desktop CPU (Intel HD Graphics 610). Also on Windows 10. For me, using these older drivers seems to fix it for now.

I'm having the same issue with an (also 7th gen) Intel Pentium g4560 desktop CPU (Intel HD Graphics 610). Also on Windows 10. For me, using [these older drivers ](https://downloadcenter.intel.com/download/26604/Graphics-Intel-Graphics-Driver-Beta-15-45-?product=80939) seems to fix it for now.
Author
Member

@someDragon Thank you. I've deliberately tried the previous release drivers rather than the Beta drivers and they also work.

Intel HD Drivers for 7th gen:
Working
15.45.16.4627 previous release 23 March 2017
Beta 15.45.4614 dated 23 Feb 2017

Not Working
15.45.18.4664 latest release (at time of writing) 3 May 2017

I will attempt to report this to Intel.

@someDragon Thank you. I've deliberately tried the previous release drivers rather than the Beta drivers and they also work. Intel HD Drivers for 7th gen: Working 15.45.16.4627 previous release 23 March 2017 Beta 15.45.4614 dated 23 Feb 2017 Not Working 15.45.18.4664 latest release (at time of writing) 3 May 2017 I will attempt to report this to Intel.
Author
Member
Added to the Intel developer support forum: [https:*software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/735289# ](https:*software.intel.com/en-us/forums/graphics-driver-bug-reporting/topic/735289#)

15.45.16.4627 is also working here!
Thanks all for now!

Hope Intel will fix it in the future.

15.45.16.4627 is also working here! Thanks all for now! Hope Intel will fix it in the future.
Member

Added subscriber: @tyason-4

Added subscriber: @tyason-4
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Aaron Carlisle self-assigned this 2017-05-30 20:16:03 +02:00
Member

Because this is a driver version there is nothing we can do. Closing.

Because this is a driver version there is nothing we can do. Closing.
Member

Added subscriber: @Ivan_Klimov

Added subscriber: @Ivan_Klimov
Member

Added subscribers: @UDIFY, @mont29

Added subscribers: @UDIFY, @mont29
Member

Added subscriber: @Yassine_Boutaouas09818

Added subscriber: @Yassine_Boutaouas09818
Member

Added subscriber: @MidnightEdge

Added subscriber: @MidnightEdge

Added subscriber: @jaimi

Added subscriber: @jaimi

Added subscriber: @stas-4

Added subscriber: @stas-4

Added subscriber: @d4r1u5

Added subscriber: @d4r1u5

Hello
As a temporary fix you can force blender to run on your GPU (if you have one). This resolves the issue

(DELL XPS 9560 with 4K display)

Hello As a temporary fix you can force blender to run on your GPU (if you have one). This resolves the issue (DELL XPS 9560 with 4K display)

Added subscribers: @awsaunier0115, @fablefox

Added subscribers: @awsaunier0115, @fablefox

Added subscriber: @kitengland

Added subscriber: @kitengland

I had the same problem on a new Dell Precision laptop. I downloaded Blender 2.77 windows 64 and everything is working correctly.

I had the same problem on a new Dell Precision laptop. I downloaded Blender 2.77 windows 64 and everything is working correctly.

Update: I was wrong. 2.77 is not operating correctly

Update: I was wrong. 2.77 is not operating correctly

Added subscriber: @defton

Added subscriber: @defton

Added subscriber: @MattPenner

Added subscriber: @MattPenner

Fixed!

Had the same problem on a Win10 x64 Lenovo X1 Yoga with Intel HD Graphics 520. The 5/17/2017 21.20.16.4678 drivers seemed to break the UI.

However, I just updated to the 8/13/2017 22.20.16.4771 drivers and the issue is fixed. Edges of the UI are no longer cut off and the mouse alignment is corrected.

Fixed! Had the same problem on a Win10 x64 Lenovo X1 Yoga with Intel HD Graphics 520. The 5/17/2017 21.20.16.4678 drivers seemed to break the UI. However, I just updated to the 8/13/2017 22.20.16.4771 drivers and the issue is fixed. Edges of the UI are no longer cut off and the mouse alignment is corrected.

Added subscriber: @voxelv

Added subscriber: @voxelv

I'm also having this issue on Win10 x64 Lenovo X1 Yoga (2nd gen) with Intel HD Graphics 620. In the entire time I've had my laptop (since June 2017) I have had this issue.

I can't seem to find the correct driver version that MattPenner mentioned on Intel's site. Can someone share a link?

I'm also having this issue on Win10 x64 Lenovo X1 Yoga (2nd gen) with Intel HD Graphics 620. In the entire time I've had my laptop (since June 2017) I have had this issue. I can't seem to find the correct driver version that MattPenner mentioned on Intel's site. Can someone share a link?

I guess the Intel HD 620 Graphics has a different number (of course haha).

It wasn't as straightforward to install on the Lenovo ThinkPad X1 Yoga (2nd Gen) though. It kept saying something to the order of "This driver is not approved for your computer by its manufacturer" and wouldn't install.

EDIT: (I forgot the link): https://downloadcenter.intel.com/download/27058/Graphics-Intel-Graphics-Driver-for-Windows-15-46-?product=96551

In case others come here looking for a solution on the 2nd Gen, here's the steps I took:

  1. Open Device Manager
  2. Right Click Display Adapters -> Intel HD Graphics
  3. Properties -> Driver tab -> Update Driver button
  4. Use the "List of drivers on my computer" option
  5. Set to Microsoft Basic Driver. Note, your graphics may now be quite wonky because they aren't using the GPU...
  6. Install the new driver from Intel.
  7. Reboot.
  8. Done!
I guess the Intel HD 620 Graphics has a different number (of course haha). It wasn't as straightforward to install on the Lenovo ThinkPad X1 Yoga (2nd Gen) though. It kept saying something to the order of "This driver is not approved for your computer by its manufacturer" and wouldn't install. EDIT: (I forgot the link): https://downloadcenter.intel.com/download/27058/Graphics-Intel-Graphics-Driver-for-Windows-15-46-?product=96551 In case others come here looking for a solution on the 2nd Gen, here's the steps I took: 1. Open Device Manager 2. Right Click Display Adapters -> Intel HD Graphics 3. Properties -> Driver tab -> Update Driver button 4. Use the "List of drivers on my computer" option 5. Set to Microsoft Basic Driver. Note, your graphics may now be quite wonky because they aren't using the GPU... 6. Install the new driver from Intel. 7. Reboot. 8. Done!
Author
Member

@voxelv it is quite common for laptop vendors' drivers to warn that chipset manufacturer drivers are not approved.
The slightly tidier way, to achieve the same as you have described, is to completely uninstall the laptop vendors' drivers and then install a clean set of drivers from the chipset manufacturer. Intel in this case.

Regards

@voxelv it is quite common for laptop vendors' drivers to warn that chipset manufacturer drivers are not approved. The slightly tidier way, to achieve the same as you have described, is to completely uninstall the laptop vendors' drivers and then install a clean set of drivers from the chipset manufacturer. Intel in this case. Regards

I have religiously stayed with the Lenovo System Update Utility just because I've ran into issues in the past (namely with Windows 8 and Miracast drivers) where reference drivers were incompatible compared to the vendor drivers.

However, in this case Lenovo was happy to tell me my system was up to date, and even wanted to suggest a different graphics driver when it noticed I had the reference driver loaded. So, I'm ignoring the System Update Utility for my graphics for the time being.

My update actually was a much easier process than described above. Not sure why. I went to the Device Manager, Display Adapters, right-clicked on my Intel(R) HD Graphics 520 device and selected Update Driver Software. Not sure where Windows looks compared to Lenovo but it loaded the Intel driver and all was fixed. Strangely as I mentioned above I have driver version 22.20.16.4771, yet the Intel website states 15.46.05.4771 is the latest.

I have religiously stayed with the Lenovo System Update Utility just because I've ran into issues in the past (namely with Windows 8 and Miracast drivers) where reference drivers were incompatible compared to the vendor drivers. However, in this case Lenovo was happy to tell me my system was up to date, and even wanted to suggest a different graphics driver when it noticed I had the reference driver loaded. So, I'm ignoring the System Update Utility for my graphics for the time being. My update actually was a much easier process than described above. Not sure why. I went to the Device Manager, Display Adapters, right-clicked on my Intel(R) HD Graphics 520 device and selected Update Driver Software. Not sure where Windows looks compared to Lenovo but it loaded the Intel driver and all was fixed. Strangely as I mentioned above I have driver version 22.20.16.4771, yet the Intel website states 15.46.05.4771 is the latest.
Author
Member

@voxelv and @MattPenner I take back what I said. My Lenovo was a pain to update. The new drivers kept claiming they did not support the operating system I was using.
Uninstalling the previous drivers kept reverting within a few seconds to an older version of the Intel drivers!

Thank you @voxelv your method worked.

Regards

@voxelv and @MattPenner I take back what I said. My Lenovo was a pain to update. The new drivers kept claiming they did not support the operating system I was using. Uninstalling the previous drivers kept reverting within a few seconds to an older version of the Intel drivers! Thank you @voxelv your method worked. Regards
Author
Member

Sadly the new drivers no longer work in conjunction with a DisplayLink adaptor.
Previously, as long as I had the lid to the laptop open, I could use Blender on one of my external screens connected to a USB 3 DisplayLink dock.

Now Blender will only render on the laptop screen!

Disappointing.

Sadly the new drivers no longer work in conjunction with a DisplayLink adaptor. Previously, as long as I had the lid to the laptop open, I could use Blender on one of my external screens connected to a USB 3 DisplayLink dock. Now Blender will only render on the laptop screen! Disappointing.

I can confirm that rendering still works while using the ThinkPad OneLink+ dock, even with the laptop (X1 Yoga) closed. I've got two monitors both on DisplayPort and was able to render without an issue. I'm not sure how current the USB 3.0 dock drivers are. When my company used that with several older Lenovo X1 Carbons we had a few issues. For the most part they worked but I had to reboot weekly for the screens to show up and we had a couple that just died unexpectedly.

I can confirm that rendering still works while using the ThinkPad OneLink+ dock, even with the laptop (X1 Yoga) closed. I've got two monitors both on DisplayPort and was able to render without an issue. I'm not sure how current the USB 3.0 dock drivers are. When my company used that with several older Lenovo X1 Carbons we had a few issues. For the most part they worked but I had to reboot weekly for the screens to show up and we had a couple that just died unexpectedly.
Author
Member

@MattPenner the OneLink+ connector is unique to Lenovo's as far as I know. Whereas DisplayLink is a chipset embedded inside nearly all USB 3 docks. It's advantage is that it works with nearly any laptop, the disadvantage is that it needs display drivers on the PC and these are not as powerful as the Intel HD chipset.
The DisplayLink based docks are OK for most corporate business uses but not optimised for graphic intensive applications.
At home I can just use a direct connect cable but at work that's not so convenient!

@MattPenner the OneLink+ connector is unique to Lenovo's as far as I know. Whereas DisplayLink is a chipset embedded inside nearly all USB 3 docks. It's advantage is that it works with nearly any laptop, the disadvantage is that it needs display drivers on the PC and these are not as powerful as the Intel HD chipset. The DisplayLink based docks are OK for most corporate business uses but not optimised for graphic intensive applications. At home I can just use a direct connect cable but at work that's not so convenient!

Added subscriber: @bitluni

Added subscriber: @bitluni

Added subscriber: @AustinAmakyeAnsah

Added subscriber: @AustinAmakyeAnsah
Added subscribers: @TheRooneyBros, @VukGardasevic, @JoshuaLeung, @LazyDodo

Added subscriber: @FordRenault

Added subscriber: @FordRenault
Member

Added subscriber: @jacksonreed196

Added subscriber: @jacksonreed196

Added subscriber: @blender_maddin

Added subscriber: @blender_maddin

Added subscriber: @suburbiagames

Added subscriber: @suburbiagames
Member

Added subscriber: @RossiAir

Added subscriber: @RossiAir

Removed subscriber: @suburbiagames

Removed subscriber: @suburbiagames

New drivers has resolved my issue, using Intel HD Graphics 520.

New drivers has resolved my issue, using Intel HD Graphics 520.

Added subscribers: @BoomProductions, @sebastian_k

Added subscribers: @BoomProductions, @sebastian_k

Added subscriber: @Leonardo_Oliveira75

Added subscriber: @Leonardo_Oliveira75
Member

@VukGardasevic With the number of these reports we're getting, perhaps it'd be a good idea to add a note to the release logs page (maybe under the compatability stuff) telling people with Intel cards to update their drivers if they get this problem?

@VukGardasevic With the number of these reports we're getting, perhaps it'd be a good idea to add a note to the release logs page (maybe under the compatability stuff) telling people with Intel cards to update their drivers if they get this problem?

@JoshuaLeung I agree that is generally a good idea, however drivers/OS updates can break up all the versions of Blender and can happen months after the release.
I think that could be a topic for the next / some developer meeting in the future - where to place a web page with the known driver issues / affected hardware and how to make it known to the users.

@JoshuaLeung I agree that is generally a good idea, however drivers/OS updates can break up all the versions of Blender and can happen months after the release. I think that could be a topic for the next / some developer meeting in the future - where to place a web page with the known driver issues / affected hardware and how to make it known to the users.

Added subscriber: @tarek-2

Added subscriber: @tarek-2

Thanks @voxelv, this helped me fix it for now

Thanks @voxelv, this helped me fix it for now

Added subscriber: @AnaRadosavcev

Added subscriber: @AnaRadosavcev

Added subscriber: @SMX

Added subscriber: @SMX
Member

Added subscriber: @mchamish

Added subscriber: @mchamish

Added subscriber: @AjFrostX

Added subscriber: @AjFrostX

Added subscriber: @AceOfTricks

Added subscriber: @AceOfTricks

I have this issue also but my graphics card says everything is up to date.
It's an Intel(R) HD Graphics 520 on Windows 10 Pro.

I have this issue also but my graphics card says everything is up to date. It's an Intel(R) HD Graphics 520 on Windows 10 Pro.

Can you try following the instructions from voxelv, it involves reinstalling the driver. I don't know if that helps since it says updated already for you, but go ahead and install it from Intel's website and reinstall it in the device manager

Can you try following the instructions from voxelv, it involves reinstalling the driver. I don't know if that helps since it says updated already for you, but go ahead and install it from Intel's website and reinstall it in the device manager

Added subscriber: @anushan.m001

Added subscriber: @anushan.m001

I am experiencing the same problems but I can't seem to fix them

I am experiencing the same problems but I can't seem to fix them

Can anyone help please?

Can anyone help please?

Added subscriber: @Komomo

Added subscriber: @Komomo

I have tried reinstalling the driver and checked it's up to date, but I still have the same issue.

I have tried reinstalling the driver and checked it's up to date, but I still have the same issue.

Added subscriber: @Taurusko

Added subscriber: @Taurusko

I can replicate the same behavior.
Machine: Lenovo T 470, i7-7600U, Intel HD 620 integrated GPU, running on Dell P2414H through Lenovo dock
Tested with portable versions of 2.79b, 2.74, 2.65, 2.63 (random older versions), the same problem occurs all the time.
Tested with 100% and 125% scaling and various resolutions with no difference.

The interface looks "broken" (no top menu, preferences menu does not have tabs) and the mouse cursor is scaled off (near the bottom of the screen it tracks OK, but the higher I move the cursor, the bigger the offset is, up to 1-2cm off).

Can not update the driver due to not having admin privileges (at work).

I can replicate the same behavior. Machine: Lenovo T 470, i7-7600U, Intel HD 620 integrated GPU, running on Dell P2414H through Lenovo dock Tested with portable versions of 2.79b, 2.74, 2.65, 2.63 (random older versions), the same problem occurs all the time. Tested with 100% and 125% scaling and various resolutions with no difference. The interface looks "broken" (no top menu, preferences menu does not have tabs) and the mouse cursor is scaled off (near the bottom of the screen it tracks OK, but the higher I move the cursor, the bigger the offset is, up to 1-2cm off). Can not update the driver due to not having admin privileges (at work).

Added subscriber: @qubodup

Added subscriber: @qubodup

The issue is apparently caused by Intel´s drivers.
Does Blender have a policy regarding including detection, fixes and/or warnings for issues caused by 3rd party software?

SOLUTION:

  • Update the graphics driver.

For example installing: win64_25.20.100.6326.exe and restarting solves the issue on the computer I´m using right now, which has a Intel Iris Plus Graphics 640.*Requires Administrator rights.//

WORKAROUND:

  • In Blender, press ALT+F11 (on some laptops: ALT+FN+F11)

This maximises the screen, removing the window title bar - which seems to be related to the displacement of the mouse position inside Blender.

Does not require administrator rights.

Video guide of both in case you need it: https:*youtu.be/_rhJs2Brc-8

The issue is apparently caused by Intel´s drivers. Does Blender have a policy regarding including detection, fixes and/or warnings for issues caused by 3rd party software? **SOLUTION:** - **Update the graphics driver.** For example installing: [win64_25.20.100.6326.exe ](https:*downloadcenter.intel.com/download/28240/Intel-Graphics-Driver-for-Windows-10?product=98911) and restarting solves the issue on the computer I´m using right now, which has a Intel Iris Plus Graphics 640.*Requires Administrator rights.// **WORKAROUND:** - **In Blender, press ALT+F11** (on some laptops: ALT+FN+F11) This maximises the screen, removing the window title bar - which seems to be related to the displacement of the mouse position inside Blender. *Does not require administrator rights.* **Video guide of both in case you need it: [https:*youtu.be/_rhJs2Brc-8 ](https:*youtu.be/_rhJs2Brc-8)**
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
21 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#51521
No description provided.