Changes to iLogic 2017 R2?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Has iLogic been changed?
I have just spent many hours (always on a rush job when I don't have the time) trying to get iLogic to generate duplicate/instance components.
While not a function I have used greatly, in the past I previously found that by using "Place iLogic Component" in an assembly all the elements within that assembly would be duplicated/instanced to create a new assembly, this then locked the driven changes within the new whatever it was.
For example if I drove the size of a box through iLogic the first instance of say the side would be Side-01 the next Side-02 etc.
This wasn't without issues previously as IIRC it would make instances of all parts whether they have been driven to a different size or not.
Now, for some reason, it seems to only generate instances of the parts if they have a matching file name precursor "Hydrant Case Side" Hydrant Case Rail" etc. "HC Rail" will drive the change in size in part "HC Rail" but not generate an instance of the rail - very frustrating.
I'm not saying this is a bad thing, and could be very useful - Who wants Handle-01, Handle-02 etc when they are all identical and haven't changed.
What is a major pain is I didn't know and now have a devils own job in unpicking and reassembling my assembly to rename all the parts I want to drive to change and create instances and swap them in.
My head may yet explode before I get it done.
Has anyone else come across this or (more likely) am I just doing something wrong?