Error when importing STEP file

cooperhood.zip (145.6 KB)

I face error when importing this STEP file in PrePoMax version 2.3.5-dev.

The newest stable version is 2.4.0. The newest dev version is 2.4.4. Please try in the latter if you can. For me, it works even in 2.4.0.

I forked the code (this week, so very recent state of code), and I have same issue (exception error: mesher is busy).
If I import ‘Axisymmetric.STEP’ file from models folder, it fails as well.
If I import model such as ‘L_bracket.step’, it works.

Do you have McAfee anti-virus by any chance ?

I do ! Is there something to set up ?

That would explain the issue. I have the same problem. The only workaround we’ve found so far is to add PrePoMax .exe files (particularly the Netgen/Gmsh mesher ones) to exceptions in McAfee’s live scanning feature: Problems importing .step and .stp files - #11 by robertorosa

This is strange since both step files go through the same pipeline.

Thank you.
I added an input rule in Windows Defender, for NetGen exe file (and other exe files from netgen folder as well), as suggested, but still same problem.

I meant adding exceptions in McAfee settings (Excluded files in Real-Time Scanning settings), but it doesn’t always work for me immediately either. It seems to depend on a build or time when it was generated.

I have imported and meshed nicely in v2.4.4.

Because you probably don’t have McAfee, the issue seems related to it. The geometry has some flaws, but is importable.

Yes, I´m in a corporative workstation with ESET Endpoint Security software as anti virus.

ESET should work normally, I had it before and never encountered such issues. They started when I switched to Windows 11 (not a problem by itself) with McAfee. I really dislike this anti-virus so I guess I’ll replace it as soon as possible and things should go back to normal (disabling its scanning features doesn’t help).

1 Like

I followed your advice (excluding files directly in McAfee) and after restarting it works fine now.

Many thanks for your help.
NB: I don’t like McAfee neither !

I will close this topic as the issue is resolved.