run vivado 2017.2 on linux with hidpi monitor and a tiling wm, also pass thru any arguments given, and set the current working dir to /tmp/vivado2017, hence it doesn't create various files in the current working dir. this is by far the most sane configuration i can come up with.

vivado

#!/bin/bash
VIVADO_PATH=/opt/Xilinx/Vivado/2017.2
VIVADO_TMP_DIR=`mktemp -d /tmp/vivado2017.2.XXXX`


export J2D_D3D=false
export _JAVA_OPTIONS="-Dsun.java2d.dpiaware=true -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true -Dsun.java2d.xrender=true"
export SWT_GTK3=0
wmname LG3
source $VIVADO_PATH/settings64.sh

# change to a temp dir, vivado will create logfiles and journal files here
cd $VIVADO_TMP_DIR

$VIVADO_PATH/bin/vivado "$@"

Does this actually scale the interface for you? When I run it the runtime apparently doesn't pick up the "dpiaware" part and the interface doesn't scale correctly. Did you make any other changes to get it to work?

sorry for the late reply. I did not manage to scale the userinterface of vivado (for the hardware part) correctly, but it is usable on my thinkpad t460p. But if you start Vivado SDK out of Vivado, the SDK is resized and rendered properly and as far as I can tell.