Illegal characters in path when importing STEP model while having "New" event trigger active

[ReneRepina]

Hello!

We encounter an error "Illegal characters in path" when importing STEP and having "New" event trigger active (it can be blank iLogic rule).

Before trying to simulate, open new Inventor, because you will have to click a lot of times on OK when error occurs or it can even crash I think.

We are using Inventor 2020.4.3.

How to simulate:

1. Before importing the STEP, create a blank iLogic rule and place it under "New" event trigger (All documents).
2. Import the STEP (in link below - could not attach it in attachment because file is too big).
3. When dialog for import pops-up, just click OK.
4. Wait for the STEP to import and you will encounter the error "Illegal characters in path".

Temporary link to the STEP file:

https://cloud.ledinek.com/index.php/s/tJLBsPaH7xZgGiS

Best regards,

Rene Repina

[WHolzwarth]

Don't worry much about iLogic issues, Rene.

I've imported the STEP into a blank IAM and got only lots of tiny faces, even for tube-shaped parts or T-shaped steel beams. Many of them came in as surface only, too, and each and every part seems to have it's own file.

The initial file seems to be an IFC. Perhaps importing this one gets better results. I would need testing.

[ReneRepina]

@WHolzwarth 

Well iLogic is causing this problem. If you remove event trigger from "New", it works fine. Regardless of this, error lies somewhere deeper in the code, which Autodesk programmers should check.

[johnsonshiue]

Hi Rene,

I am sorry to reply to you late. I tried accessing the file but it is no longer available. Could you share it again?

Many thanks!

[ReneRepina]

Hello Johnson!

Welcome back!

Ofcourse, I will send you on the email.

[johnsonshiue · Accepted solution]

Hi Folks,

I got some information to share regarding this issue. Though we still have trouble reproducing the behavior on our system, it seems that it is related to a known defect, INVGEN-49644 (iLogic global event triggers fail on internal AnyCAD documents). This defect has been fixed on 2021.3 update but the fix has not been ported to 2020. Porting the fix requires escalation from Support. If you want the fix ported to 2020, please contact Autodesk Support and reference the above defect ID.

Many thanks!