"although my temp folder looks OK, there are files that date back to August in there." In that case I would be willing to bet it has to do with the error message you received just prior. I'll do a little Googling on that message and see if I can find some info online about what causes it and how to reproduce it.s Now onto you zip2go issue. That is definitely not something I've seen or heard of before. Our zip to go relies heavily on the SOLIDWORKS pack and Go. Try running the Pack and Go and see if that grabs the correct files. Also are the files it is grabbing just from another currently open document? "GUI buttons wouldn't work" This can happen for a number of reasons. After a SOLIDWORKS crash, when you 1st install a new version of the add-in, when switching back and forth between different versions of the add-in. In all cases the way to reset it would be to delete that reg key you mention above. The KB artical on this can be found here:

One issue that I have seen in the past was when the temp folder was being cleaned out in the middle of the day without the user even knowing. What was happening was the user would be working in MCfSW which is saving to and reading from their "C:\Users\your logon\AppData\Local\Temp" folder. Problem being their IT department had set up a utility to delete everything from this location everyday at noon. So if the user was in the middle of working on a file when it went to read back in the temp folder data there was nothing there, causing the user to losing everything they had been working on. So I would start there. Browse to your "C:\Users\your logon\AppData\Local\Temp" folder . Typically there are hundred if not thousands of files and folders in this location. If there is not, then it's being cleaned out. Which is OK, we just want to make sure it's being done after hours or when all applications are closed. We also noticed that one of our dealers just submitted a ticket on what sounds a lot like what you are describing here. So I'm guessing it may be your dealer? Anyways they mention the following: "The customer was editing a solidworks sketch that toolpaths were driven off of. Began receiving a new notification that the component he was working on was locked and that he should unlock it to create any referenced geometry." If this was you is that error message from SOLIDWORKS something you can reproduce? I can't say that I have ever seen that one before so you may have run into something that just isn't been taken into account. If you can reproduce the error and issue could you please send a sample assembly along with the steps used to [email protected] attn Ryan and we'll jump right on it. Thanks

OK thanks Mark. I added the note to the existing defect (D-33787).

Not yet but can you confirm you are using sketch geometry. We just want to make sure that is the same issue and not some other unknown issue. If it is I'll a note to the existing defect to help push it up the latter.

Hi Mark, This sounds like it may be related to a known issue that we are looking into that's specific to using sketch geometry vs solids. If that's not the case can you send us a copy of the file to [email protected] and we'll take a closer look. Thanks

I'm aware this has been logged but again, if you email us at [email protected] we can offer you a possible solution in the meantime.

Send us an email at [email protected] and we may be able to help you with this.

Hi Avshalom, I'm sorry but I don't understand the 1st question: "1. How to create tool-path using geometry we add to a face we work on, instead of the contour of the face? The image at the beggining of this topic describe it." The way nesting works in MCfSW is: You do not move your parts flat onto a plane prior to toolpathing or within nesting. This would break any SW mates used to position the parts within an assembly. This is also one of the reasons there is no "disassemble" function nor any plans to add one. Instead the intent is you toolpath the parts in what ever orientation they were designed in using a custom WCS. Then in nesting the toolpaths are automatically nested flat onto your sheet. Moving multiple copies of solid bodies into various nested orientations just isn't feasible within the SW application. SW only offers the ability to move solids using their move copy function, not sketches and nesting supports all geometry types. So with that in mind MCfSW is intentionally built around the SW work flow intent (assemblies, configurations, model space etc.)

"2. When routing in 2D where there is an undercut, how do I limit the area to cut so the tool path wouldn't cut out material that "shades" the undercut?" In this example when selecting the geometry for the toolpath, select the entire solid body. When you do this in MCfSW with in a 2D toolpath it will automatically generate a silhouette boundary around your part and project it down onto your toolplane.

Hi Avshalom, In SOLIDWORKS we wouldn't use a solid disassemble since that would break our mates. Instead what you do is toolpath each part in it's assembly orientation using a custom WCS. Then just select those toolpaths within nesting and it will automatically re-orientate you toolpath flat on your defined sheet and nest them based on your settings.

Actually no. This is a Mastercam "user" forum hosted by one of our resellars In-House Solutions. It's intended to give Mastercam users a place to bounce ideas, questions and issues off of each other. The forum is not moderated by CNC Software although some of us will pop on from time to time. To run an issue by CNC Software directly you would need to either send it in to one of the email addresses above or post it up on the Mastercam.com forum board.

Dear Lord, We are aware of this issue and are already looking into it. D-19263. Also please feel free to contact us anytime with any questions, issues or requests you may have or are running into. For technical or "how to" related questions email us at [email protected] To report a defect or to submit a request email us at [email protected]

Try re-registering the swdocumentmgr.dll using the following steps Close Mastercam Select "Start" In the search line type CMD but do not click enter Instead right click on CMD.exe and select "Run as administrator" This will open a command prompt that says Administrator on the title bar Next type the following string, don't forget the " " around the path: C:\Windows\syswow64\regsvr32.exe "C:\program Files\mcamx9\common\sworksdata\swdocumentmgr.dll" press enter and verify you get a succeeded message Now try importing a file into Mastercam

Hi Tom, Once you select your 1st edge that will wake up the Propagate options. Propagate along Tool Plane will get you your out side chain with far fewer selections. Or better yet enable the solid body selection and select the solid. This will project a silhouette boundary up onto the current tool plane. Just click on the chains tab and delete all but the outer chain and you are done.

Hi Bob, I ran some tests here and I was able to reproduce the chain reversal in newly spawned configurations from a design table in MCfSW X8. However in X9 I was not. In that version my chaining settings were retained in the spawned configurations. If you haven't already give X9 a try when you have a chance to see if it addresses you example as well. Note: In X9 we also added a new option called "Regenerate all Configurations". So now when you spawn multiple configurations from a table you can regenerate all Mastercam tool paths in all configurations with just one click. This option is under the "Tool Path Utilities drop down.