View representations not up to date

[mat_hijs]

I've encountered this a couple of times now. I have a master assembly which I copy and then configure using ilogic, changing lengths, angles, turning on/off visibility of components,... After I've configured my assembly, the view representation sometimes doesn't seem to be up to date, meaning a (custom content center) part is visually there while the visibility of that part is turned off. If I change the view representation to default and then back to my desired view representation, everything is ok. I've also had this happen with work planes.

Is this something I'm to blame for or is this a bug?

It doesn't seem to be caused by a specific assembly or part. I'm using Inventor 2021.2.2

[mcgyvr]

Well.. that all depends on what exactly your ilogic is doing and what its not that an "out of the box" workflow would be doing I suppose...

Can you give steps to duplicate this issue consistently?

If so there is a small possibility that sharing your dataset with Autodesk would help nail down the reason for the issue and allow them to either correct a bug if it is one or point out code issues where you aren't handling things properly..

[mat_hijs]

I can't explain exactly what and how it does here because that would be way too complicated, but I'll try to simplify it to the core. In my master assembly there's one standard part, which is a profile, and a bunch of content center parts. I made a form in which I enter some values, first to define features in the profile, then to resize content center parts and make them visible or invisible. So I basically use ilogic to send parameters from the assembly to the part and to control the content center parts.

I attached a pack and go of my master assembly, but I couldn't include the content center library because the file is too big.

[mcgyvr]

---

@mcgyvr wrote:

Can you give steps to duplicate this issue consistently?

First.. Can you duplicate the issue consistently?

[johnsonshiue · Accepted solution]

Hi Mathijs,

This is a bug. I suspect the bug here is probably somehow the cache graphics (Express mode) becomes out of sync with the actual component visibility (Design View). The issue here is that there isn't an easy way to reproduce the behavior. When it happens, the corruption already occurred. If you find a way to reproduce it, please let us know asap.

In the meantime, I suggest you turn off Express mode (go to Tools -> App Options -> Assembly -> uncheck "Enable Express mode"). The assembly looks small to me. I don't think you would benefit much by turning on Express mode.

Many thanks!

[mat_hijs]

This assembly is indeed small, but this assembly is copied hundreds of times with different configurations and placed within my main assembly. This main assembly at the moment has 10 000-ish occurrences so I wouldn't consider that small, even though I know there's people with much larger assemblies. However, I'm still not using Express mode, I always want to load the full model.

[dutt.thakar]

@mat_hijs 

I have not seen your zipped file or code, but I have encountered a similar thing earlier in Inventor 2019

Let me try to explain something with an example if it helps you.

Example: If you have a sub-assembly named SA:01, your iLogic is turning on and off the components inside it and once it is done, you are not seeing the correct view representation in your main assembly, in that case, you need to do two things. One in the subassembly(SA:01) the view representation should not be locked (i.e. you need to create a view rep, that is always active , name it "iLogic")

After that use the below code in the main assembly.

Component.InventorComponent("SA:01").SetDesignViewRepresentation("iLogic",Associative:=True)

This will make it associative and you will see the up-to-date state of your sub-assembly. Please note that this line should be triggered in the end.

See if this helps you.

[mat_hijs]

I've already made a view representation for my subassembly. I also place my subassemblies with this view representation and make sure that it's associative. But the problem is not within the main assembly, it's within the subassembly itself. I open my subassembly, I configure it using my ilogic forms and then I sometimes notice this bug. Within the main assembly the chance that I'd see this is pretty small. In the end it doesn't even really matter that much to me what it looks like in the main assembly. The main assembly is basically just to know which configuration is at which position in the building. The view representation is most important in my drawings for production of these things. That's what I'm concerned about, what if this happens and my drawing view would be wrong?

[johnsonshiue · Accepted solution]

Hi Mathijs,

10K-component assembly isn't small but it is not that large either. We have customers building 50~100 times bigger than that. I still think you may want to turn off Express mode for the time being. As long as you have enough RAM (32GB+), Inventor should be able to handle 10K assembly without the need to store cache graphics.

Please don't get me wrong. It is a bug. But, I don't think the bug can be easily fixed due to its randomness. It is better to find a reliable workflow for now.

Many thanks!

[mat_hijs]

Once again, I'm not using Express mode. And as stated in my previous post, I realize people work on much larger assemblies than a mere 10 000 occurrences. I just stated that to make it clear that it's not just this assembly that I'm working on, but a whole lot of different configurations of it and more. My workstation has 16 GB of RAM, but once my main assembly is opened it works perfectly fine without being slow or anything. I'll keep an eye out for this bug, if I stumble across it again, I'll try to make another copy of my master and follow the exact same steps with the exact same configuration to see if that somehow has anything to do with it. I'll mark this post as solved for now and update if I find something.

[johnsonshiue]

Hi! I thought you were using Express mode. It is because the iam file you attached contains cache graphics segment. It means it was saved in Express mode. Possibly somebody else saved the file on a different machine with Express mode enabled.

Many thanks!