f.lux latest releases have enabled support for DisplayLink indirect displays (Windows 10)
You can download f.lux from https://justgetflux.com/
For the few wanted to do real monitor calibration, please contact firstname.lastname@example.org to discuss how to enable this on your particular configuration.
That's correct Gregor. F.lux implemented this on Windows 10.
Thank you Anon, but we cannot take any credit. What you have today is all thanks to the F.lux team.
@JI, there is a separate thread for Mac and it has different challenges. I have renamed this idea to specifiy Windows.
@Anonymous, the Dell D1000 is using the same hardware family (DL-3000/DL-5000) as the Dell D3100 and I have been using f.lux on Windows 10 successfully for weeks. Therefore there is no issue on that side. I have also tried it on the Dell D6000 using the latest DL-6950 chip and it works.
I suggest you check f.lux options.
F.lux has announced supporting DisplayLink indirect displays with their latest release. I have personally been using it since.
@mmm Dell D3100 with Windows 7 is targeted for release 8.3 currently scheduled for July. It's the right hardware, but wrong OS for 8.2 preview.
I'm looking at trying to get an *alpha* version of the 8.3 driver in May/June for those who feel like trying unfinished software. Today, it's not been tested enough to be acceptable even as an alpha. When I have news I will post.
Because of the issue with gamma tables in the Anniversary Update, we will not be able to enable this feature by default on that OS. Your feedback validates our testing with issue seeing the login screen as Windows may send black gamma tables instead of default which is not acceptable for people who didn't ask for that feature! You can use the current trick from the forums though.
Windows 10 Creators Update has the fix so we will enable support by default. Engineering is currently testing on Windows 7 - Windows 10 TH2 (build 10586). If testing goes well, then gamma table will be supported from DisplayLink driver v8.3 on devices whose Hardware ID starts with USB\VID_17e9&PID_43 which is the majority of devices in the field.
Devices whose Hardware ID starts with USB\VID_17e9&PID_6 are next in line but we have already identified restrictions on HDMI during feasibility study.
Devices whose Hardware ID starts with USB\VID_17e9&PID_FF will come later.
Devices whose Hardware ID starts with USB\VID_17e9&PID_0 and USB\VID_17e9&PID_40 cannot have new features added once they are in the field so will not get new features.
@Henrik, best channel is here. When ready I will communicate how to try for those who want and have the adequate hardware and OS. I'll probably open a new forum board for the colour correction feedback on Windows. Testing will tell me when it's ready.
Hello Piotr, our Mac team is starting evaluating if it possible. We have met issues with another part on Mac (DDC/CI) so this is not a straight forward port from Windows.
Hello Sven, very nice monitor, I use it for trade shows as it's light. This device will not be supported in the initial version version. We are still unsure about possibility. They are built differently and already have gamma curve tables which manufacturers like Asus would use to calibrate them in factory depending on panel used. We need to see if we can override the feature. Investigating is definitely planned.
@johan and all. The products which will first be supported have their hardware ID starting with USB\VID_17e9&PID_43. You can get the hardware ID from Device Manager in the device details (see how to find the HWID in http://support.displaylink.com/knowledgebase/articles/544834#otherdevices).
Once I have a development build, I will probably create a forum board.
It's not been "planned" for two years Rowen...
TL;DR: It's a big job and we don't do hack jobs so it takes time.
f.lux support is under analysis. This requires extensive firmware and some host software work.
There are 10s of millions of devices in the field with a bit more than one version of Windows, some with one display, some with two, some with three... Some with HDMI, VGA, DisplayPort, DVI, and a combination of everything.
Today, we do not modify the image in any way, we take the output of the graphics card. This is brand new feature that is requested, not just a tweak. This new feature MUST NOT, in any way, create issues when not in use (so in most cases). We need to setup brand new test rigs and test suite to defend it.
I have deleted injurious comments from Marek Ziel (Apsik).
@All. f.lux support is under analysis. We met with the f.lux developers to discuss an implementation which will keep working with new versions of f.lux.
We are trying to think about to support individual colour correction rather than just an identical gamma curve change applied to all displays. However, we don't yet if it is possible.
@Andrew. DDC/CI pass-through on DL-3000 and DL-5000 was released as part of 8.0 M0 so has been available already.
@Viking, you do not need f.lux to change brightness. You can use Screenbright, a free utility which is already supported across all recent docking stations with DisplayLink technology.
@Sergio, the comment about Windows 10 is not about applicability of the solution, but the reason for not having implemented it yet.
The flickering on Anniversary Update is a f.lux bug they are aware of and are working on. Please look for new versions of f.lux.
Felix, colour correction and contrast are different. From our 8.0 Beta 4, you are able to use applications like ScreenBright to change the contrast settings via the computer.
Colour correction is totally different, as f.lux states in their online contributions. The feature is currently on the roadmap for the devices which have the horsepower to handle it. Device with a USB Product ID starting with 0x0 will never be able to support it because, unlike brightness or contrast which are just a command to send, colour correction requires the device to compute.
The change is needed in the operating system kernel mode graphics driver. Microsoft is looking into scheduling this development. In the meantime, provided you have purchased a platform allowing you to, the workaround is to disable the low end GPU so Windows uses the only one left. Today, Windows will always use the POST graphics card.
Jan, this report says Windows 8.0 (that's the build 9200). This discussion is about Windows 10 Anniversary Update onwards. If you're really on Windows 10 and the graphics tool reports Windows 8.0, I wouldn't trust it understands how the Anniversary Update graphics subsystem fundamentally changed the deal and how it can measure things properly for something it doesn't understand. If you are really on Windows 8.0, I don't see us doing any new development for it as almost no-one uses that OS (~1% maybe). Could also be the OpenGL bug on the Intel graphics driver affecting your tests.
Feedback about the OS using the GPU from POST is not a DisplayLink opinion, this is a Microsoft graphics team affirmation. They wrote that part of the feature. I am inclined to believe both the author and general test feedback.
Hell Jan, how do you check what GPU is used? I am rather inclined to believe Microsoft graphics engineers who told me the kernel driver doesn't change on the fly and that they won't change until they receive feedback from Windows 10 users.
https://aka.ms/Cojpi9 is a Windows 10 Feedback Hub entry from someone about the graphics card selection for Windows 10 v1709.
This is an operating system feature. The graphics card used is the POST one. if your Dell 7559 gaming laptop uses the Intel GPU for POST, then Windows will also assign it to indirect displays like DisplayLink.
Unless you report this to Microsoft for them to change the selection, then I don't foresee any suitable resolution.
@Manatax, can you use our Customer Support Tool (http://support.displaylink.com/knowledgebase/articles/533818) and that will create a ticket. We would need to find a machine close to yours to see how the disabling works. We can then discuss this with Microsoft.
Also, please do complain through the Windows 10 Feedback Hub that you want to use your high end graphics card with indirect display because the iGPU is not powerful enough to do <whatyoudo>. We need to send enough feedback for this to get prioritised.
No Zachary, unfortunately there hasn't been enough feedback through the Windows Feedback Hub to make it a priority for them. At the moment this is scheduled for Redstone 4 but may well be postponed again if customers don't flag this is important.
Creating a universal Windows 10 driver is in progress. However, for phones, it will need your phone manufacturer to integrate the driver as the phone does not behave like a desktop Windows.
Weak interest for ARM 32-bit architecture is the main reason it wasn't in productisation!
The second reason is you can't put such a driver as an app in the store. A driver is not an app. It's the same with desktop. Apps will be in an App Store, drivers are on Windows Update... and there was no remote deployment possible to these devices. For the demo, Microsoft used specialised tools to add the driver to the phone.
Also depending on how the operating system evolves, it may become possible to do remote deployments.
If you have a mobile phone OEM who is willing to integrate, then it will happen. Our driver will be ready when they are...
What was shown at CES2017 was DisplayLink, nothing to do with Alt-Mode, it was real USB.
The Universal Windows Platform (UWP) driver production release is coming. However, we've been told you can't just install a driver on a Windows 10 Mobile phone with Windows Update like you can for big Windows.
Hello, that's correct. This won't work until we have access to the pixels. Our driver need to do a bit more than just be a USB device. Windows Phone also has additional restrictions compared to the full blown OS... but at a minimum, we need to get access to the pixels before we can think about packaging them through USB. That will require an OS change so please make sure to also flag your interest to Microsoft.