SysID crashes due to imgui assertion failure

SysID had been working fine on my Windows 10 laptop but isn’t any more. Now when I start sysid I get an assertion error Expression: blocking_modal != 0 at D:\a\thirdparty-imgui\thirdparty-imgui\imgui\imgui.cpp Line:6298. Maybe it’s a red herring but I don’t have a d: drive mounted on my laptop.

I think this problem was caused by a sysid crash I had for another reason (my characterization program was sending poorly formatted telemetry data to sysid). Every since that crash, sysid won’t start because of the imgui error. I assume imgui is in some strange state relative to window management as a result of the original sysid crash.

I’ve re-booted and re-installed sysid but the imgui problem persists.

Any ideas?

1 Like

You can work around this issue by removing C:\Users\username\AppData\Roaming\sysid*.json. The 2022.3.1 release also has a number of sysid fixes, so upgrading may fix the issue too.

Nice. That worked. Thanks for the quick response!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.