Ubuntu 16.10 support

Sparxy · 01-10-2017, 08:22 AM

The displaylink issue with chrome can be worked around by disabling hardware acceleration or disabling vsync in chrome.
From what I can tell OpenGL appears to VSync to 1Hz (1 frame per second) on DisplayLink devices.
Disabling hardware acceleration can be done through the settings. To just disable VSync you can edit the shortcut and add
env vblank_mode=0
at the start of exec, i.e. Exec=env vblank_mode=0 /usr/bin/google-chrome-stable

01-10-2017, 08:22 AM	#2
Sparxy Junior Member Join Date: Jun 2016 Posts: 12	The displaylink issue with chrome can be worked around by disabling hardware acceleration or disabling vsync in chrome. From what I can tell OpenGL appears to VSync to 1Hz (1 frame per second) on DisplayLink devices. Disabling hardware acceleration can be done through the settings. To just disable VSync you can edit the shortcut and add env vblank_mode=0 at the start of exec, i.e. Exec=env vblank_mode=0 /usr/bin/google-chrome-stable Last edited by Sparxy; 01-10-2017 at 08:40 AM.