Post processor properties reset after update

[Anonymous]

The title is pretty descriptive: my post processor properties get reset after every update I receive of Fusion 360. This might also be related my entire post processor library gets somewhat moved after every update and I'm asked to reset it to the default folder.

I'm on Windows 10 and my post processor is othermill.cps, but I don't believe this is specific to my post processor of choice.

Any advice?

[jeff.pek]

We've seen intermittent reports of similar issues, but so far nothing that's reproducible. There is certainly no intention to clear any user settings during an update, and if this is something that happens with any consistency, we'd love to track it down. Perhaps sharing your diagnostic logs around the time of the update might shed some light on what happened?

Jeff

[Anonymous]

Sure! Where can I find those logs on Windows 10? I know I've just fixed
this for the n-th time...

[jeff.pek]

You can get the logs from the Diagnostic Logs command in the help menu.

  Jeff

[Anonymous]

This issue occurred to me after each and every update, so on my computer, this is easily reproducible: what it needs is an update.

Every time I restart after an update the bold setting in the screenshot gets reset to its default value:

Obviously, in September this occurred twice.

As I'm a software developer myself feel free to ask for any technical details which might help to nail down this issue.

[Anonymous]

I hate to revive such an old post, but I am still having the exact issue described here. Since I finally got some time to look it up, this is the first time I realized it isn't being done on purpose.

All of the post processing defaults have to be reset after any update, even if the update has nothing to do with the manufacturing workspace, and it has been doing it since I started using Fusion as my go to for generating tool paths about a year ago. (over two different computers, Windows 10 & 😎

The biggest issue here is if I don't happen to remember that it updated when I'm trying to get my machine running, one of the defaults on the post processor crashes the machine, which causes me to have to stop and readjust everything before continuing production (I had changed the defaults in the post file once, which held for a while, but was over written in an update several months ago...). There are other issues with it, but this is the one that will stop me from having a good day.

Is there anything I can do to keep this from happening?

[seth.madore]

It sounds to me like you may be using the built in "generic" posts. While these posts are (mostly) quite solid, I continuously encourage users to "make them their own". By doing that, they essentially become insulated from any future update that would reset all your choices. You can read up more on that HERE and HERE

[M&GToolWorks]

I just had my first experience with this... 

After the last update Fusion decided to add a G90 G53 X0 Y0 at the end of my post. No idea why. Cannot find anything that changed as far as options, and I have my own post, saved on my computer. 

Scared the crap out of me because as my luck would have it, I had a long tool in the spindle and the 4th on the table. There is a reason my post does not home X. 

[seth.madore]

Machine configuration?

[M&GToolWorks]

Could be? Looking at the machine configuration page, I do not see what or why that would be added to my program?

I stopped doing machine configurations because they kept disappearing after updates. 

[Anonymous]

Seth,

Thanks for the reply, you gave me quite a bit of insight as to why this is happening. I even found the post I edited, that I thought was overwritten in a previous versions folder. So, if I use the personal post library instead of whatever webdeploy folder, it should pretty much not change, right?

[seth.madore]

That is correct. Now, if you are also using Machine Configurations, that does add another level of frustration to the mix...

[agilbert.uav]

I encountered the same issue this morning.
I am using a heavily modified version of the FANUC/Turning Post to be compatible with my old Nakamura lathe.

The issue is that after every update, the reference folder is moved.
For example, there was an update yesterday and it copied/installed everything into the folder "*USER*/appdata/local/autodesk/webdeploy/production/8fc78e02ada35f7bfe8c61944f4c29231b2e06ab"

Today's update did not use the same folder, and all the Post (and I assume most of the software) nor resides in "*USER*/appdata/local/autodesk/webdeploy/production/f0e2e428a92efb9c5ee46c0f9dc446a06adaa1d2"

Both folder use a hefty 1.2GB of disk space. I am assuming that this is to keep the last version of Fusion in case the user wants to revert to a previous version if the update breaks something.

However I can't see why the Post are updated every single time.

As a work-around I have copied every "stock" Post into a local folder and pointed Fusion there instead.
I can't see why the update should change every Post, even if they are "stock" setups. Almost all software I have ever used create a local setup folder where the "defaults" are updated if need and a different local folder for the user setup. I assume there is already a folder like this somewhere linked to fusion, so why not move the Post files there so it does not get overwritten every update?

[jeff.pek]

Hi -

What you're doing is exactly what we recommend -- if you happen to modify the posts that are delivered with Fusion, don't do that directly in the Fusion install location -- make a copy instead in your local user area instead.

Jeff