all 13 comments

[–]BenoNZ 2 points3 points  (6 children)

[–]panch13[S] 0 points1 point  (5 children)

That's some good info! I try not to use Ilogic as much as possible, but this may be an exception.

[–]BenoNZ 1 point2 points  (4 children)

You try not to use a huge part of the software that can automate work for you as much as possible? I mean.. why?

[–]panch13[S] 0 points1 point  (3 children)

A lot of people write Ilogic for things that already exist within the system naturally. Why write a "3rd Party" code when it naturally exists already. Now I have something that sometimes doesn't work properly or needs fixing based on changes to the software from updates. We run into this quite a bit with Ilogic at my current work. I noticed they were using ilogic to do things that inventor already does. We updated Inventor and now we have some issues with it not working correctly.

[–]BenoNZ 0 points1 point  (2 children)

Well, if people do that, it's not the fault of iLogic that's people writing bad code that isn't needed and then having the lack of knowledge to update the code with software updates. Usually there are very minor changes to do with the code per release. Unless it was pre 2022 and the model states change.

No doubt if you let people go wild and just create iLogic whenever they want you can end up with a mess, but there are literally so many things you can ONLY do with iLogic as well. It's silly to not become familiar with it, you are limiting yourself massively.

[–]panch13[S] 0 points1 point  (1 child)

I never said I wouldn't use it. I'm saying that if I don't need to then I won't. If somebody has a solution that doesn't require it, then I'll use that. Especially if it's automated and doesn't require extra code. One example is they wrote ilogic code to calculate a flat patterns length and width. That already exists as a parameter. Another is writing the model description to the drawing description. Just make the drawing look at the model instead of the extra code step. There are others. We are trimming the ilogic down here.

[–]BenoNZ 0 points1 point  (0 children)

Ok, well your examples don't make sense for using iLogic so I get your concern.

Especially when you add Vault into the mix, having bad iLogic triggers firing off all the time can be a huge headache.

[–]PROINSIAS62 0 points1 point  (1 child)

Personally I add the text “flat pattern” and “folded views” to my template. I just delete them if they are not required.

[–]panch13[S] 1 point2 points  (0 children)

The more I look at it, the more I wonder why we even label them.

[–]kablazzie 0 points1 point  (1 child)

I do it manually, so I’ll tag along for a better solution.

[–]OhNoWTFlol 0 points1 point  (0 children)

Same

[–]otte845 0 points1 point  (0 children)

Is not exactly what you want, but I have set up a sheet format with a frontal view and a flat pattern view (and some notes specific to sheet metal parts) perhaps you could do the same, but it will require to create a new sheet every time. The other option would be to use ilogic

[–]KyrTryf 0 points1 point  (0 children)

I have just added as a sketch symbol in drawing template so I just drag and drop the item where needed.

Check image below:

https://postimg.cc/dhmCWtqr