Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.
mattdlr89
2597 Views, 35 Replies

Output Folder in NC Program - Not saving

Just been cleaning up one of my programs. Went through to change the Output folder of where it posts. However when I go back into it it does not remember that I have changed it. Just reverts to what was there previously. Never had a problem before today's update. 

 

This happens when I click both "Ok" and "Post" although when I click post it posts to the folder I have enter it just doesn't remember that for next time. 

 

mattdlr89_0-1614700123712.png

 

 

 

mattdlr89
in reply to: mattdlr89

Quick update...


This was happening in one file with all 4 of my NC programs. I then created a new NC Program and the four that were not remembering the NC Program seem to have updated now. Perhaps it was saving the write path but loading the incorrect one when looking at the NC Program window?

Axelzzon
in reply to: mattdlr89

Yeah, same for me!

I was posting my different operations to different folders directly to the machine (or so I thougt...)

The last operation overwrote the first one because of the output folder was not saved.

Crashed machine, crached tool and crached fixture.....

Have not summarazed the damage yet because was pretty pissed off yesterday and went home to cool off.

 

How is it possible that a bug this significant is pushed to the customers?

I really think this should be found in beta testing or even better unit testing the code!

 

Well, enough ranting for now and time to check on the machine.

 

 

christianXP3EW
in reply to: Axelzzon

I have the same problem. I post directly to the machine but luckily I caught it before a crash. This needs to be fixed ASAP as its a productivity killer and a crash hazard.

mattdlr89
in reply to: christianXP3EW

@seth.madore @jeff.pek 

 

Experiencing this again today. 

 

Has this issue been logged/replicated by the dev team, I can share a screencast if dev team are unaware of what is happening?

jeff.pek
in reply to: mattdlr89

Hi - We are still doing some work to improve this area. Sorry we didn't get all those improvements into the recent update. We've got another update coming in the next couple of weeks, and may be able to make it incrementally better.

 

Jeff

mattdlr89
in reply to: jeff.pek

Thanks for the response @jeff.pek 

 

Just worth noting that the latest update has caused this issue it was never a problem for me last week. 

Axelzzon
in reply to: jeff.pek

Just as @mattdlr89  said, this bug was introduced in the latest update.

It´s a bug that caused damage for around 3000$ for us, not including production loss or mental damage.

This should be a higher priority than "in the next couple of weeks".

jeff.pek
in reply to: mattdlr89

Could someone please take a screencast of what you're doing and seeing, and also let me know whether you've got the "Post Process with NC Program" preview feature enabled?

 

I just tried a couple of post operations, and it remembered the output folder fine. 

 

Thanks,

  Jeff

jeff.pek
in reply to: mattdlr89

Or is it that you're expecting the output folder to be saved *per operation*, and instead it's remembering it globally?

  Jeff

mattdlr89
in reply to: jeff.pek

Hi @jeff.pek 

 

I do not have that preview feature turned on and my expectations are based on what was happening before the last update. 

 

I've got a screencast no microphone so couldn't talk over it but I will summarise. If I go to the NC Program and select a new folder I can post it there but then when I next go back to that NC Program the folder has not remembered the location. I show this a few times in the NC Program.

 

I then go and make a new NC program and if I set the output folder when the NC Window is present for the FIRST time then it will change all my output folders to whatever I select then.

 

https://autode.sk/38d4ltE

 

jeff.pek
in reply to: mattdlr89

Thanks for that. I see the problems now -- and unfortunately it's not just the output folder. I'm emphasizing the priority of getting this fixed up with the responsible team. It seems to be just the edit workflow that goes bad; if you just post with the existing NC Programs, it seems to use the right values. I realize that's little consolation.

 

Jeff

zach.allaun
in reply to: jeff.pek

This kind of fundamental workflow breakage is extremely frustrating and seems to be very commonplace. I greatly appreciate the speed at which improvements are made to Fusion, but I would happily wait for 3-month release cycles instead of monthly release cycles if it meant these sorts of things would be caught.

mattdlr89
in reply to: zach.allaun

Agreed @zach.allaun 

 

I like to see the pace of new features etc being added to Fusion but it's a little unnerving to see some of the bugs that make it into releases. We're not talking about extreme edge use cases here. This is basic functionality - text boxes and settings essentially. While I understand things are a lot more complicated under the hood - it's also hard to excuse these sneaking into the release. Hoping for a quick fix and as always appreciate the forums as a place to report these and get responses from AD.

Anonymous
in reply to: mattdlr89

Please fix this asap, it's becoming very very annoying and expensive.

DanOMFG
in reply to: mattdlr89

I almost scrapped a five-figure part on Friday because of this.  I checked throughout the weekend and this bug is still present.

mattdlr89
in reply to: DanOMFG

This has caught me out a lot and continuing to do so today. Luckily it hasn't caused damage/scrapped parts just inconvenience. 

 

I hope a hotfix is coming this week...??

zach.allaun
in reply to: mattdlr89

I hope a hotfix is coming today. This is a ludicrous and dangerous bug to still be present 4+ days later. @jeff.pek Any clarity on when this will be addressed?

jeff.pek
in reply to: mattdlr89

We are actively working on a fix.

  Jeff

ltomuta
in reply to: mattdlr89

Ugh!!!