jasdr.blogg.se

My laptop runs the Intel Xe graphics and you can't use

On my Acer Nitro 5 AN515-56 running Win-11 (this also happens in Win-10 btw) as The flag will now be included every time you start COMSOL Multiphysics.If you are having the Intel Xe Graphics Driver orĪny other graphics from Intel and you get a loop problem like I've experienced Open the file C:\Program Files\COMSOL\COMSOL61\Multiphysics\bin\win64\comsol.ini in a text editorĪdd the line -Dcs.disablehwacceleration=on to the file and then save it.Ĭlose the text editor. Starting with COMSOL Multiphysics version 6.1, it is also possible to set a permanent flag in the comsol.ini file. If you have installed COMSOL Multiphysics in the default installation directory, the full text field should look like: "C:\Program Files\COMSOL\COMSOL56\Multiphysics\bin\win64\comsol.exe" -disablehwacceleration.On the Shortcut tab, add a space and then paste -disablehwacceleration to the Target field.Right-click the icon and select properties.You can accomplish this by editing the COMSOL Multiphysics 5.6 icon on your desktop in the following way: The approach described below would be the same, but with 5.6 and 56 replaced with 6.0 and 60 respectively.Īfter installing the update, you need to launch COMSOL Multiphysics with the option -disablehwacceleration. The fix is also included in COMSOL Multiphysics 6.0. If you have not yet updated your installation, you can initiate the update by going to File > Help, and select Check for product updates in COMSOL Multiphysics.There is a fix for this issue included in Update 1 for COMSOL Multiphysics 5.6.Workaround 3 - For COMSOL Multiphysics 5.6 and later. To start COMSOL Multiphysics with the cross-platform GUI, launch the file comsolxpl.exe from the bin\win64\ directory in your COMSOL Multiphysics installation directory. Run the cross-platform GUI for COMSOL Multiphysics instead of the default. Workaround 2 - For older versions of COMSOL Multiphysics The fix for this issue is included in that version of the Graphics Drivers.

Update your Intel Graphics driver to at least version 30.0.100.9805. There are three suggested workarounds for this issue.