If none of the above fixes the issue, please gather the following information and send it to What is your rendering strategy (rendering locally, remotely, GLX rendering, etc.)?Ģ) Please send the crash output to Tecplot Support, along with the context of the crash and any of the solutions attempted above.ģ) Please send Tecplot Support the output from running the getsysinfo script, located in the Tecplot 360 bin directory: For example: ~] glxgearsĥ520 frames in 5.0 seconds = 1103.988 FPSĦ) If you are running 2020 R1 or later, and receive an error message that 360 will not launch because of some issue with shared libraries, then one possible solution is to add the “-use-sys” flag: For example:ģ) Does the error contain font errors (undefined symbol: FT_Done_MM_Var)? If so, see this article.Ĥ) Are you rendering locally or remotely? Does Tecplot crash on remote GLX rendering? See this article for more information.ĥ) Does glxgears run on your machine? glxgears requires the glx-utils package. Are the native OpenGL drivers (from Nvidia for example) installed?Ģ) Does Tecplot still crash when running with the mesa flag? 1 This is not a complete solution, but it helps Tecplot Support diagnose the problem.

We always recommend that customers install the native graphics drivers on the machine that will be displaying Tecplot.

This Mesa is different from Tecplot’s Mesa drivers and many customers have problems with them as they are very buggy. Default Linux drivers are backed by Mesa. Please check these questions:ġ) Double-check that your graphics card driver is up-to-date. We’ve written up some instructions for responding to Linux crashes. See the Troubleshooting chapter of the User’s Manual for more information (also at the bottom of this article).

Note: The 2020 R1 release of Tecplot 360 introduced a change in the way Tecplot is rendered in mesa. I get a crash running Tecplot 360 on my Linux operating system.

Tecplot license