new post process total garbage

new post process total garbage

leo358JY
Contributor Contributor
514 Views
6 Replies
Message 1 of 7

new post process total garbage

leo358JY
Contributor
Contributor

a few updates ago they changed the (already perfect) post process after the first update when i post processed a setup would just pick a random name, and random folder to go into and then i have to go find it, and then put it in the right spot and then rename it, now its better but still total garbage (when compared to the old system). now in the new update, when i post process my gcode file it makes me manually type out the name and file type (which i didn't used to have to do because it would just pick the name in the setup, and the file type from the export type) then i have to  pick  a folder and i just hate how its now so annoying to do (as i have to make alot of files and also redo a ton too), it used to be so easy you just click post process and then select the folder where you want it and your done and now its just a huge pain to do each time.

0 Likes
515 Views
6 Replies
Replies (6)
Message 2 of 7

Anonymous
Not applicable

Dont you just hate it when you get use to something that works great and somebody decides to screw with it?

Message 3 of 7

engineguy
Mentor
Mentor

@leo358JY 

 

Hmmm, as there doesn`t seem to be any issues here and I am not able to replicate your issue I am inclined to think that there is something amiss at your end, can you upload a Fusion .f3d file that has the problem and maybe then someone will be able to pinpoint what/where the problem lies better.

 

I can start a new job from scratch, make the model, go to manufacture, create a setup with a name in Comment, set the WCS, create some operations, toolpath them and then go to Post, when the dialog opens depending on which machine I want to code for then I select the PP for that machine, that automatically sets the Folder that holds all code programs for that machine and the name that I put in the Setup appears in the Comment box and appears in the G code that is generated.

 

All I can think is that you don`t have your Post Processor saved in your "Local Post Library", if it is in the "Installed Post Library" or Cloud Posts", then yes, I have seen issues when updates have set PPs back to a "Default" in the past but I thought that issue had been fixed, possible it has reared it`s ugly head again, I wouldn`t have noticed as I never work online and/or save anything outside my Local Libraries and Offline Cache so it is a possibility !!

 

Stay Safe

Regards

Rob

0 Likes
Message 4 of 7

Laurens-3DTechDraw
Mentor
Mentor

While it shouldn't matter. Can you inform us if you are running on Windows or on MAC?

Laurens Wijnschenk
3DTechDraw

AutoDesk CAM user & Post editor.
René for Legend.


0 Likes
Message 5 of 7

engineguy
Mentor
Mentor

@Laurens-3DTechDraw 

 

I suspect the OP is a Mac user, there does appear to be issues for Mac users,even as you rightly say it should not matter.

I uploaded a demonstration Screencast to another Thread and it turned out the user there was on a Mac.

The solution put forward by Seth Madore was to move to using the NC Program system which apparently workd OK for the postsers.

@leo358JY 

@NMAutomation 

The current method on a Win PC seems to be OK, here is the  Screencast again 🙂

 

Stay Safe
Regards
Rob
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
0 Likes
Message 6 of 7

leo358JY
Contributor
Contributor

i am on mac i forgot to mension that also when i post process it used to default where my last save wasnow it doesnt thats not a huge problem it was just a really nice feature when post processesing multible setups at once and i want them in the same folder, anyway i uploaded a video of me showing in a brand new file everything i was talking about its also happening on all the other macs here (we do have a windows machine to test it but then we have to installl fusion and all that)

0 Likes
Message 7 of 7

seth.madore
Community Manager
Community Manager

Yes, this is a known (and logged) bug that seems to have crept into the last update. I did find that using NC Programs mostly eliminated the issue, I suggest giving that a whirl.


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes