help
help > RE: vglrun display error with standalone conn
Jul 13, 2018 12:07 PM | Alfonso Nieto-Castanon - Boston University
RE: vglrun display error with standalone conn
Hi Joseph,
That makes sense. Just a couple of suggestions in case these help: 1) I would suggest perhaps trying TurboVNC (instead of xquartz), even if just for debugging purposes in order to bypass any potential issues related to the X display on your client-side; and 2) using "vglrun matlab -nosoftwareopengl" instead of "vglrun matlab" when testing will force Matlab to avoid software OpenGL if at all possible
Good luck!
Alfonso
That makes sense. Just a couple of suggestions in case these help: 1) I would suggest perhaps trying TurboVNC (instead of xquartz), even if just for debugging purposes in order to bypass any potential issues related to the X display on your client-side; and 2) using "vglrun matlab -nosoftwareopengl" instead of "vglrun matlab" when testing will force Matlab to avoid software OpenGL if at all possible
Good luck!
Alfonso
Threaded View
Title | Author | Date |
---|---|---|
Joseph Orr | Jul 10, 2018 | |
Alfonso Nieto-Castanon | Jul 11, 2018 | |
Joseph Orr | Jul 11, 2018 | |
Alfonso Nieto-Castanon | Jul 12, 2018 | |
Joseph Orr | Jul 13, 2018 | |
Alfonso Nieto-Castanon | Jul 13, 2018 | |