Please visit our Customer Support Center for contact options. For more information see our End of Support Policy.įor support in English, our Customer Support team is here to help you Monday - Friday, from 1 a.m. If that doesn’t help, booting the system without the dock connected, launching SketchUp, and then connecting the dock may also help.Tip: SketchUp's Support Team provides support for users with a current SketchUp subscription plan or those with a Classic License using a supported version of SketchUp. The first is to configure Windows to have the ‘Main’ display set to a display directly connected to your internal graphics adapter, whether that is an internal laptop display or another external display connected to one of the systems built-in video outputs (a quick guide to doing so should you need it is here -> ). Pending Microsoft fixing the issue within Windows itself, there are two possible workarounds. DisplayLink speaks to this issue here if you are curious -> … (under the section ‘OPENGL 1.1 REPORTED INSTEAD OF 4.X’) Or docking station is not a traditional graphics adapter in and of itself (it relies on the CPU and internal graphics adapter to work), and this results in the error message you received. In some instances, Windows mistakenly directs the tasks intended for your internal graphics adapter (which does support OpenGL) to the DisplayLink-based docking station.
In your specific case, the SketchUp application requires the use of graphics adapter that supports a standard known as OpenGL -> … With the Anniversary Update to Windows 10, Microsoft has now integrated support for the DisplayLink technology used in our docking station into Windows itself and in certain cases things may not work as expected.
Thanks for posting, and I would be happy to help with your docking station!īased on your description of the behavior, it sounds like you are running into a bug identified by both Microsoft and DisplayLink (the maker of the chip in our dock and author of the driver) with Windows 10 Anniversary edition.
0 kommentar(er)
