I updated to beta 3 hoping for a fix (some reason i dont get updates on this thread to me email)
I still get the yellow screen only with mouse cursor.

Then roll back your OS to the last STABLE version. We all run Betas knowing there could be issues. this is one of them. Dont get feisty with DisplayLink because your running beta software they got the same time you did, and things arent working properly. If this is a major issue, use the Stable release where Displaylink works properly. These are designed for DEVELOPER machines, you know like the ones at Displaylinks office.

Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Attached is the output from the information tool you requested as well.

Thank you we're looking at the logs, we'll have a new series of experiments to run.

Cheers,
Carlo

This worked for me as well. Second screen up and running. There is definitely lag and some rendering issues (white boxes over menu items, etc.) but it's mostly useful.

[QUOTE=toastido;85374]Sooooo this morning, I felt a little feisty, so I tried a thing.

┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:25]
└─[$] <> launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist
┌─[twisted@clarity] - [~] - [Mon Feb 26, 11:26]
└─[$] <>

As soon as I unloaded the useragent, the monitor sprang to life and began functioning. It's laggy, but it's working.

Hi,
Can you please specify what exactly to enter in the commond line? Is it only the 2nd two lines each beginning with the $ sign and if so, it appears there are more brackets in your summary than I'm used to working with in Terminal.
Thanks very much.

[QUOTE=dizash;85386]Oh, sure. I'm using ZSH with some customizations, so that's why my command line looks like that. the actual command is:
launchctl unload /Library/LaunchAgents/com.displaylink.useragent.plist

[QUOTE=toastido;85387]Thanks Toastido - especially for the quick reply. Much appreciated!!!!

UPDATE: Immediately after utilizing the command, my DL Connected Monitor also SPRANG TO LIFE:

THANKS AGAIN TOASTIDO - this is huge for me!!!

[QUOTE=dizash;85388]NP. This will at least work until DisplayLink gets a real fix in place. It's more of a bandaid since it's a little laggy and whatnot, but at least it's a workaround for the time being.

This workaround doesn't work for me. Maybe it's hardware specific? I'm using an older Kensington SD3500v I believe. I can confirm the model if display link need it.