Posting Setup with Named View orientation also create a PNG file!

[HughesTooling]

Just found you get a PNG file if you post a setup using a named view for orientation, how can I stop the PNG being created?

[HughesTooling]

@seth.madore Just bumping this as it's gone unanswered. This seems like it should be an option for all setups, might be useful to people not just when using a named view? But does need to be something you can turn on\off either in the setup or preferences.

Thanks Mark

[seth.madore]

Thru which method are you creating Setup Sheets:

1) From NC Program

2) From the "Actions" menu

3) From the Right Click > Setup Sheet menu

4) From an Excel based post processor and setup sheet

Golly, too many ways of doing something, and all but two are different in their format and output

[programming2C78B]

I get these too from simply pressing CTRL+P on my setup and posting out some code. It only happens if I make a new named view (ie 4th axis setups, or lathe programs).

I coincidently started using Greenshot as soon as I started lathe CAM, so for the longest time thought it was because of that, but it IS from fusion. 

[seth.madore]

So you get this from just posting out g-code as well? Where are the PNG files ending up for you; same directory as your posted code?

[a.laasW8M6T]

I just tried this too, create a named view for a setup, then post the code and it posts an image in the same directory.

I've never used named views so have never seen it.

@programming2C78B , definitely handy for 4 axis setups

[seth.madore]

Thanks guys, I've shared this thread with the relevant dev team, hope to have answers for you..

[seth.madore]

After some quick investigation from a couple of developers, this does appear to be a bug and not intentional. There was an existing bug report for this issue, but it was an edge case that wasn't widely encountered. We've attached this thread to that ticket; CAM-41705.

There's no workaround to avoid this, outside of pausing the use of Named Views..

[seth.madore]

Just an update; we've fixed this internally, so it's just a matter of slipping it into a build and getting it out to our users. No date on when that would take place, but at least it's closer to the finish line that it was a couple weeks ago 🙂