iLogic error is requiring restart of Inventor 2022 to clear

[llorden4]

I'm running into a new issue with programming in iLogic, having just swapped to Version 2022.  Not always, but quite often I'm finding that when test running some code I'm working on, if there's an error then the rule will simply not run again unless I restart Inventor.  Manually firing the rule again does absolutely nothing.

I am making changes to a created Model State after getting to a common point, so I do have a "Master" and a custom model state, and the custom state is where the error occurs.  I'm not sure if the new model states is causing the lockup or if there's some processes I should be wary of, or if this is just the new norm.

Anyone else also noticing this and have any tips to avoid they can share?

[bradeneuropeArthur]

could you upload the code?

[llorden4]

I've got a NDA to contend with, so I can't openly share my work else I would have.  I'm currently just curious if I'm alone in this headache.

Besides, the code is a novel at the moment and would be more work than anyone would be willing to sort through.

[Curtis_Waguespack]

---

@llorden4 wrote:

Anyone else also noticing this and have any tips to avoid they can share?

---

Hi @llorden4 

I think I saw some very similar "weirdness" when doing some testing with 2022/Model States and iLogic.

I think there is a bug in there somewhere, and my hunch is that it is related to Model States, but I was never certain that if it was truly due to Model States and not just 2022 in general. 

Unfortunately, I didn't take the time to investigate, so I don't have any recommendations, but I did want to let you know that you're not alone in seeing this.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[llorden4]

To provide some type of context to my issues...

I missed adding the ".geometry" to this line originally, which failed to generate the sketch dimension.  I was forced to restart Inventor after correcting the line to get iLogic to run again.

oArc = oSketch.SketchArcs.AddByCenterStartEndPoint(oLine(4).EndSketchPoint, oLine(3).EndSketchPoint, oLine(2).EndSketchPoint, True)
oTmp = oDC.AddRadius(oArc, oLine(4).EndSketchPoint.Geometry, False)

I had another syntax error when placing some sketch workpoints, it also required a restart of Inventor to get the code to run again.

I'm also noticing that if the user changes Model States, ilogic is firing and this may not always be desirable.  I'm thinking we might need to some control over this in the Event Trigger manager.

[llorden4]

I'm about ready to put a bow on this new utility and am now facing a serious hurdle with getting iLogic to run more than once.

This is similar to an LOD issue I discovered back when the enhanced iLogic was introduced, that too never really got addressed and this may still be the root cause.

I've attached a video to show how I'm utilizing the new model states feature and the results I'm getting.  I cannot openly share this code due to a NDA, but I can share with @johnsonshiue for tech support if needed.

[llorden4]

So I'm starting to get worried here that Autodesk is still appearing to be ignoring this issue since I've gotten no feedback at all from either post on this LOD vs iLogic issue.  Can you duplicate it, are you working on it?  I'm on my own again, what's the deal?

I've been prepping to rollout updates for 2022 usage at the end of the year and I'm about to put the brakes on any updates without something in the works to resolve this issue of rules only running once.

[llorden4]

Update:  My current work around is simply not to create any new model states and I don't have the issue of only one run.  I'm currently just creating a DXF export of the flat model state to send to CNC and then deleting that work so that there's only one model state to store.  I can get away with this since it's fairly quick to regenerate the flat, but this isn't a workflow I should have to do, I would think.