I can confirm when rolling back to Sierra and using the installation made for the product it functions well. I also have seen this error before when using vmware fusion and it boiled down to a stupid switch being enabled to allow the older package to access some internal "new macOS" package.
I develop software as well and can sympathize with DisplayLink and I too am not upset with DisplayLink but rather upset with MacOS pushing out releases and not communicating with software drivers that should work as expected.
The best advise I can give you all is this reading that had similar issues:
I assume at some point the displaylink software will bear a cost and it will be to pay for drivers of older equipment and those who purchase new equipment will gain access to supported hardware "wink".
I can confirm when rolling back to Sierra and using the installation made for the product it functions well. I also have seen this error before when using vmware fusion and it boiled down to a stupid switch being enabled to allow the older package to access some internal "new macOS" package.
I develop software as well and can sympathize with DisplayLink and I too am not upset with DisplayLink but rather upset with MacOS pushing out releases and not communicating with software drivers that should work as expected.
The best advise I can give you all is this reading that had similar issues:
https://kb.vmware.com/s/article/79989
I assume at some point the displaylink software will bear a cost and it will be to pay for drivers of older equipment and those who purchase new equipment will gain access to supported hardware "wink".