OK - thanks for letting me know.

Try emailing me at [email protected] (let me know in the email who you talked to and what email addresses they gave you) and I'll see if I can get you connected to them. Connecticut got hit pretty hard last week by Isaias, and power in the office and in remote employees homes was out for a couple days (and is STILL out in some places) which might have impacted our response.

" Hasps are no longer supported" Completely untrue. We are moving toward a world where most or all MC users will have software licenses, including using license 'borrowing' to allow users to work away from the license server without having to use a dongle.

Thanks JP. Pete

Until we come out with a fix for this (and no promises on "when", sorry) there are a couple workarounds : 1) have the engineer go to System Options in SW and go to the 'Import' page and turn off '3D Interconnect' BEFORE importing models. If that is turned off when the CAD file is imported into SW and then saved from there, then we should be able to bring it in without doing any of the above steps. 2) or ... add a feature of some kind to the imported body in SW. The problem exists only when saving an imported model (imported via 3D Interconnect) with no additional features on it. 3) or ... (This one requires Admin privileges on your computer) get a copy of the SW2020 SP2 SWDocumentMgr.DLL from the "C:\Program Files\Common Files\SOLIDWORKS Shared" folder on a computer with SW2020 SP2 or SP3 on it - and copy this to your computer. There's a Mastercam.com KnowledgeBase article here that explains how to register the SWDocumentMgr.DLL. When it describes where to find that .DLL, point towards wherever you copied it locally from the other computer. Pete

We (very) recently were made aware of an issue involving a combination of using SolidWorks 2020 SP2 or SP3 and importing CAD models into it ... and then saving the result as a SW file and not having that SW file come into MC. Might this be the case with this issue?

Send it in to [email protected] (if you can) and we can take a look

I think you'll have to get in touch with support ([email protected]). They should be able to figure out what on your computer is causing this.

Has it worked for you in the past but now that you've updated its failing? Or has it never worked? Never mind, based on another Topic it sounds like you've gotten it to work before. So what's changed?

Make sure the SolidWorks CAM addin is not loaded. To ensure this, open SW, go to "Tools/Addins" and uncheck both checkboxes next to SolidWorks CAM. Then shut down and start SW again.

#4 - There's a conflict between MCforSW's Backplot and SolidWorks' Enhanced Performace graphics setting. (It's at the bottom of the System Options / Performance page). Uncheck that (I'm not sure what you're losing by doing that) and Backplot should co-operate.

"...Makes some for us happy they finally went in this direction and now others want it like it was..." I have to laugh since we just came to the same conclusion in the last couple minutes when I talked to the developer! There is no way to override the new behavior, but we'll consider it ... Reko - thanks for posting.

"...not being able to de-select solid faces in legacy surface contour...." What happens when you try? It looks OK from this end. I can select and de-select faces ... I can select a body and de-select some of the faces .... Can you send a part and the all-important "steps to reproduce"?

I can go into any MultiAxis toolpath and select 4 surfaces over and over without this problem. So without any more detail, there's not much we can help you with. if its something you can repeat - and, importantly, if you really want to help us make the software better - send the steps (and a file if necessary) to the QC team.

I would recommend going to forum.mastercam.com and logging this there so that the Tool team can look at it. Or better yet, email the support team.

"...Yeah, there is data being stored in the database that shouldn't be there, if you run a database search and do not check the alive bit you can access geometry from parts in mcx files that you opened hours before. Those definetly should not be there..." Entities that still exist but are not 'alive' are still in the database for the purposes of 'undelete'. There is not a separate place where they can be held (maybe someday...) They will be gone after you save and re-open the file, or if you run RAMSaver (oops... File/RepairFile) .

I checked with those in the know here and received word that there was a conflict in MC2020 between PowerSurface and the Moldplus addons. Do you have those installed? If so, what I've been told is that there is an update from Moldplus for MC2020 that clears this up. It should no longer be an issue in the MC2021 Betas.

"... I know we can save it as a dxf and import it into Coral Draw but it is a real pain as it will import all hidden levels as well..." You can use "Save Some" instead of "Save As" when outputting the DXF from Mastercam ... that will only put what you want in the DXF f ile.

The success of that functionality depends on several factors regarding the surface model. Are there any open edges where a surface does not share an edge with a neighboring surface? Does the Analyze "Test Surfaces" show any problems? Are there very thin surfaces in the model that might be so thin that its neighbors think that they share an edge?

Using a TrueType font will probably give you lines, arcs, and/or splines.

Leon82, Did you end up pursuing this any further? I'd like to investigate whether there's a STEP import issue we're not aware of. If you can't send a file, I understand, Pete

I've been asked by the Marketing folks here at CNC to post the following link to a mastercam.com forum post they just put up : Free Mastercam University Courses "...As we all adjust to the changes caused by the COVID-19 outbreak, many of us are finding ourselves working from home or spending more time on our computers and devices. We would like to offer you a way to sharpen your Mastercam skills while we are all dealing with the disruption..."

We're doing more in the last couple versions of MC to bring in the AP242 data, so that 'note' might actually be a '3D Annotation' entity that is actually lots of polylines and not a text string (depending on how its represented in the STEP file). If you want I could take a look at it and maybe provide some help as to what it is and why its there.

Thanks for the feedback ... I don't think we had heard that the stock transfer was being problematic in an assembly. I'm going to log that here and have the team spend some time debugging it. Thanks again.