Force Redraw - Path Pattern Caching

[graham.schmuland]

I'll cut to the question first:

Is there a way to manually force a project redraw (or feature redraw/cache clear)?

I am running into this minor issue where a Path Pattern isn't redrawing after the feature it is repeating has been edited and/or the Path Pattern feature itself has been edited. 

The example I have is a repeating sphere feature along a circular path. Originally the sphere was a 4mm Join, which I often change to a 2mm Cut. 

What happens is that the PathPattern still has its cache and is drawing the 4mm Join spheres but also draws the new cuts. but only underneath the cached pattern. (which I would attribute to the feature drawing the new version and then adding the cache after)

Once I edit a different feature and force a project redraw it corrects itself but adding new features doesn't have it update.

I'm assuming it is the cache of the PathPattern (which would be a reasonable implementation for performance) causing the issue, with possibly the implementation of the Sphere (creating a temporary sketch?) that is not calling for the cache to be updated once changes have been made (assuming it does update normally with other features, which I haven't tested)

[jeff_strater]

can you share the design here that is showing this problem?  I don't believe that it happens in all pattern on path instances, so perhaps there is something unique to this model that is triggering this bad behavior.

[graham.schmuland]

I would generally prefer not to at this point. Both for IP protection and, well, its an "adult" product.

I'll see if I can make a stripped-down version of the file with just the affected elements.
What's the preferred file type for sharing this?

[jeff_strater]

The easiest way is to export a "Fusion Archive" file.  Choose Export from the File menu:

The default should be a Fusion Archive file, but if not, select that type:

This will export the design as either an F3D (if all the components are local to the design), or an F3Z file (if it includes external references).  Post that here, or if that is still not something you are comfortable with, we can work out a way to send it directly to me.  Thanks!

[graham.schmuland]

I'm starting to wonder if this is even going to be that feasible to debug...
In classic debugging fashion, I am now struggling to recreate it intentionally.
I am fairly confident that it is some sort of caching "issue" caused by some part of my workflow through the model.

Because of this, even if I were to get a file that has the bug, I am assuming the file I would send you would just be the parametric instructions to recreate the model, and not any of the cached features. Which I imagine sending you a file with the issue would just naturally fix itself.
If that assumption is wrong, I will have to keep working till I get another bugged PathPattern and export that as I have now "fixed" all my previous bugged models via one of the methods below.

Things that fix it:
- Editing a previous feature
- Duplicating a bugged Design/model into a new Design via right click->Copy in the data panel removes the issue in the new Design
- Closing and reopening the model

I should also note that it is a part of the physical model and not just a visual bug as exporting the mesh exports the combined features of both the updated and cached PathPattern.

Is there any sort of log that I might be able to export? If there is a sort of process log, I could export a clean one and a bugged one to compare and breakdown which process(es) might be being skipped?
I don't know, just spitballing here from my softdev knowledge of how I imagine things might have been implemented.