Matlab freeze without crashing each time Mechanics Explorer opens

4 views (last 30 days)
Hello,
Each time the Simscape Multibody Mechanics Explorer opens, every Matlab window freeze, while no error or crash detail are provided in the main console. Most of the time it occurs right after Simulink displaying "Initializing" but sometime it is right after 100% of the simulation.
The only solution I have right now is to kill Matlab process and open it again.
The problem occurs even for simple exemple projects such as "sm_bumper_car".
Every suggestion would be appreciated.
EDIT : opening a "solid bloc" has a similar effect, for the "floor" solid of the "sm_potters_wheel" for exemple.
EDIT 2 : I went through this page but nothing helped
  3 Comments
Charper
Charper on 3 Feb 2022
@Ben Rancici Did you ever find a permanent solution? I'm having the same issue but found a good workaround
MATLAB has to be on the primary monitor so the Mechanics Explorer launches there. If I put MATLAB on the second monitor I get a freeze when the Mechanics Explorer launches, exactly as you described.
Mehmet Can Türk
Mehmet Can Türk on 25 May 2022
Edited: Mehmet Can Türk on 5 Jun 2022
This frozen grey screen problem is not specific to Mechanics Explorer, it may appear in different windows of Matlab. Mine was on the mechanics explorer window and my solution was to uninstall Java completely and reinstall it after restarting the computer. I'm guessing most of these grey screens are caused by this problem. Hope this helps you fix the problem.
Edit: The problem occurred again. Then I followed the suggestion in @Ben Rancici's post below and put the two windows of MATLAB into one monitor and it appears to be solved for now.

Sign in to comment.

Answers (1)

Ben Rancici
Ben Rancici on 8 Jul 2020
After further investigation, Matworks Support suggested that I quit using a second display since the company does not fully qualify its products on multi-monitor systems (!). I have also been advised to stop opening the Mechanics Explorer Window...
At last, the issue disappeared once I uninstall a previous Matlab distribution (2019a). I suspect that the need to reactivate the licence to use 2020a again was the solution. Is it possible that the licensing mechanisms of Simscape Multibody are slightly different from Matlab/Simulink ones?
I also uninstall Nahimic and MSI True Color from my laptop the day the issue was resolve.

Categories

Find more on Simscape Multibody in Help Center and File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!