Note sure what the original setting for 2drend was. If you want faster performance when sitting at the actual-box with openGL (or using NX-client), you may need to manually edit the comsol.prefs file back to the original '=ogl' setting. So it is comsol itself that changes comsol.prefs file I believe. In my case I was using 'ssh -Y' to login and run comsol4 installed on a linux box from a remote X-server (including X11 or Xquartz on Mac osX, or various windows X11-software). That is why it runs on the 2nd (and subsequent) launches. 'Īs Ping mentions, apparently the reason it works remotely the 2nd time you launch consol is that when open-gl error causes launch to fail, it (silently?) modifies comsol.prefs not to use open-gl next time, but instead to use 'sw' (software rendering). Without doing anything, I lauched comsol for the second time and it worked.

The first time I got some error related to OpenGL. I had same experience as Ping at abpveURL: '.tried launching comsol remotely through putty and xming from a windows machine. When I ran again at the actual-box, not remotely, it did not change the lines back to their original 'ogl' settings, so you may need to do that manually per below. The comsol software seems to be able to change automatically these 2 lines to 'swt' and 'sw' respectively: (B.) In the ~/.comsol/v40/comsol.prefs file, rendering parameters can be either 'ogl' or 'sw'.

As noted at (A.) If you remotely launch comsol again after getting openGL errors, it runs fine on 2nd and all following launches.

Open nx vs nomachine vs vnc server