Use `sudo pmset -a disablesleep 1` then mirror the built in Retina display to one of the two displays you want to use. you are going to close the lid anyway so just make one monitor mirror the laptop screen.
let me know if this helped.

Hi there, quite disappointed, so this means developers or testers of this product have never tested it on mac with the lid closed.. just for your attention if I may, almost everybody uses mac in lid closed mode with 2 monitors (which is the reason for buying this pricey addon)

just bought today, and have to turn back..

The latest update from the admin I see is on Jan 8, can we have latest update please. I just stopped ordering this, however earlier resources are complaining not being able to use clamshell using this dock

Hi. I am not an overly technical person, but I do want my two large screens working whilst my MacBook Pro is in clamshell mode. Alban, can you provide a timely update on this development enhancement please?

Hopefully this comes out soon. This is a huge deal for me also. thanks

Here the response from DisplayLink:

Hello,

Clamshell mode is not yet supported on Intel based Macs, it should be working on M1 with charging plugged in.

As for the future we are right now testing it on Monterey BETA and it is working over there.

Kind regards,
Jakub

I sent a message to the company in order to have some feedback, the issue has been "started" since January 8th and we don't have any feedback from then..

I support the request for a working clamshell.
I see the latest admin response is from Jan 8 stating development process is on its way. I would hire a different third party

+1000 for Michael Johnson, idem, thanks Vikas it's working but as Michael said, not the best solution.
So where is the fix??? Frankly it shouldn't be so difficult to code it. I can help if you need help.

As Vikas and Jared said, v1.4 with `sudo pmset -a disablesleep 1` seems to be working for me on Big Sur v11.5.2, but it keeps the built-in display active which is bad for many reasons including cursor disappearing and apps getting stuck on that display...

How is this bug not fixed yet??? I spent >$300 on a DisplayLink dock that hasn't worked properly with MacOS for more than a year...

Thanks Vikas, I just gave that a try. It "works" on 1.4 for me in that the screen stops flickering. However it keeps the screen "live" so apps often open on it and the cursor can get lost on it. So less than ideal and defeats the purpose of having the laptop closed.

I will give it a shot on 5.25 tomorrow when I have more time.

sudo pmset -a disablesleep 1. Works on v1.4 big sur

Hello, I too am having this issue on my MacBook Air 2017 / Catalina.

Hi,
I have the same issue here with the current version and the beta one. (1.5.0)
Do you have any information on a fix soon?
Thanks

If it helps with development - Switching to your legacy version Release: 5.2.5 from 13 Aug 2020, seems to work for Big Sur as well. Buggy - because the screen flickers and blacks out a bit sometimes, but other than that - works as expected in Clamshell mode on MacBook Pro 13 inch intel (no Touch Bar) plugged to 2 external monitors - Lenova and acer 27inch via alogic docking station
https://www.alogic.co/product-solutions/browse-by-category/laptop-docking-stations/usb-docking-stations/alogic-universal-twin-hd-pro-docking-station-with-85w-power-delivery-and-usb-c-usb-a-compatibility-dual-display-1080pat60hz.html

Tried the 1.5.0 Beta Version released today.

The problem still happening...

Running a Macbok Pro late 2016 with Big Sur latest update.

I had to go back all the way to

DisplayLink USB Graphics Software for macOS
Catalina 10.15, Mojave 10.14
Release: 5.2.5 13 Aug 2020

Now clamshell works, but the new problem: the screen of the MacBook won't restart after opening the lid. Everytime after using the clamshell modus I have to a hard restart.

Displaymanager gives me two options: no clamshell or crashing MacBook every time I uses the device for the reason I bought it.

I am also keen on a fix for this issue.

Guys, I know things aren't as simple as we'd like them to be, however, it's been 17 months since the problem was detected (yes a problem, not a feature improvement), and it's already been 7 months of development. I believe that many other users, believing that the problem is already addressed, did not comment on the post, and others certainly returned the hardware (according to some reports here in this thread). Can someone please give us some news about the progress in solving this problem, which has been affecting me for months as well?!

I've found a simple solution: returning my docking station :D and switching back to my old one without DisplayLink