Generated Frames do Not Always Update

[el_jefe_de_steak]

I have noticed recently that frames made with the frame generator do not always automatically change with the master sketch if only small changes are made (2-3" inches or less). This results in significant frustration when making small incremental changes to generated frames.

An easy workaround is to make a big change to the master sketch, then change it back to what you want it. 

[johnsonshiue]

Hi! The behavior sounds like a bug. Could you share an example here? I would like to understand the behavior better.

Many thanks!

[el_jefe_de_steak]

Here is a good example video. In the second part of the video, note that the stair step array was constrained to the frame itself, and it actually moved to where it knew the frame should be.

The issue is bigger than I thought - these two examples are completely broken, and the frames do not update at all. When I first drew them, flexing the model produced appropriate results but now it doesn't work at all.

[el_jefe_de_steak]

And the latest workaround to fix this is to:

1. insert random part into assembly
2. constrain it in one direction to [anything]
3. save assembly and close
4. open assembly
5. make desired changes to sketch
6. move random part (that was inserted earlier) with mouse 
7. tada!!

This problem seems to get more complex as the day goes on...

[cadman777 · Accepted solution]

Hi jm,

Have you tried Manage>Update>Rebuild All?
That's what I do when that happens.

It happens a lot when I make handrail.

Another thing I do is grap (click and hold w/mouse) one part and pull it in any direction.

That seems to activate Inventor to force a full/deep update like using Rebuild All.

Cheers

[johnsonshiue]

Hi! I think you might be seeing two different issues. The first one is about the frame members losing associativity to the skeletal sketch. The second one is probably related to assembly constraint compute when there are pre-existing failed constraints. I will need to see the files in order to tell where the problems are. The video does not help much unfortunately.

Many thanks!

[el_jefe_de_steak]

Thanks! This seems to work. You saved me a ton of time!

[el_jefe_de_steak]

You may be correct. However, I just noticed this morning that even my "solution" doesn't always work. However, I don't think there were any conflicting constraints, as the times it did work was when I intentionally skipped some necessary constraints.

I think the problem is that there are some instances where changing the master frame sketch does not force an update. The solution given by @cadman777 seems to take care of this. 

---

[johnsonshiue]

Hi! The fact that Rebuild All is needed to bring the assembly up-to-date is already a bug. In theory, when a part or an assembly has update pending status, one click on Update button should bring everything within the document up-to-date. Sometimes, it is not the case. If you want, you can share the files with me directly (johnson.shiue@autodesk.com), so I can take a look and see if there is anything wrong.

Many thanks!

[el_jefe_de_steak]

Ok, here are the assembly files.

The "Factory Stair" is a completed project, but the "L Stair" is just the raw frame, with no end treatments applied yet.

[cadman777]

My pleasure!

[cadman777]

 Hi Johnson,

"The fact that Rebuild All is needed to bring the assembly up-to-date is already a bug."

I'm using 2010 Suite, and it's been like this through out all the service releases.

If jm's dataset is done on a newer version, then apparently this 'bug' has been around 'since forever', eh?

Cheers

[johnsonshiue]

Hi Jeff,

Many thanks for sharing the files! I took a quick look. I think I have seen this behavior before. This has something to do with compute sequence. The assembly has components forming a compute loop. PartA -> PartB -> PartC -> PartA. I will need to take a closer look to see how to break the loop or find the correct update sequence.

Hi Chris,

Yes, indeed, this particular behavior is not new. We never claim that Inventor is bug-free or perfect. There is always room for improvement. If you find a perfect product, please let me know.

Many thanks!

[cadman777]

Hi Johnson,

Thanx for your retort!

But let's not compare apples to rocks to divert attention from the issue at hand.

Cheers!

[johnsonshiue]

Hi Jeff and Chris,

I am able to simplify the case to bare minimum and still reproduce the behavior. Something is wrong indeed but I cannot explain it. I have sent it to the project team and they will take a further look.

Many thanks!

[cadman777]

Hi Johnson,

Thanx for getting back to us.

That's what we appreciate about you ... your ability to isolate causes and deliver solutions!

Cheers

[johnsonshiue]

Hi Chris,

I appreciate your kind words! This is less about me than about the team. 99% of the work I do involves the team. I cannot do anything just by myself. I just happen to be on the forum replying to threads.

Thanks again!

[Pavel_Holecek]

Hello Chris,

this is known issue and we already have it in our tracking system. 

here is ticket number: INVGEN-13804

Regards

[cadman777]

Thanx Pavel.

Where do I go to 'track' it?

Thanx

[johnsonshiue]

Hi Chris,

The defect system is used by Autodesk internally. I do not believe it can be accessed outside of Autodesk domain. But, you can pretty much ask any Autodesk employee about any given defect ID. They can look up the status for you.

For this particular one, the fix is available in the internal future release branch. Pavel has requested it to port it to 2019 but we are not sure when it will happen precisely.

Many thanks!