This original thread was sidetracked with recording software. I just had the same problem today with 2023. Dimensions wouldn't set down when clicking mouse button and when I wanted to move a dimension from a previously saved file, it would pick it up and move it but not able to set down. Couldn't change dimension size, decimal places or make any other changes either. The only solution was to reboot the computer. Just exiting Mastercam wouldn't fix it. Memory corruption of some sort is my guess... maybe with .NET Hope this helps someone else.

JParis--- no problem for me doing a reboot if needed. We tried it and it works. I have a pretty fast connection. Mcam & Solidworks pans & rotates at a nice smooth speed and a lot faster that I thought it would. I've got Spectrum with 100 gb connection, tested at 70 gb.

Brutal indeed !

The license is networked. No dongle.

Hi all, First time I'm working from home due to having a bad cold with lot's of coughing. IT dept set me up with a laptop and Remote Desktop thru a VPN. Mastercam doesn't pan or rotate with the simple mouse I have at home. I'm thinking it's because Mastercam is not "seeing" the mouse at home and only the one plugged in to my office desktop. But strangely, the Pan/Rotate works the way I customized it in Mastercam with the laptop touch pad and buttons. Is there a way to get this working that I don't know about besides using the Dynamic Rotation in the right click menu or the arrow keys?

Now on the same topic of slowness, I found that Mastercam gets incredible slow opening a window after many windows opening and closing. The more windows opening and closing the slower it gets no matter how many hours I've been programming. If I opened and closed 10 windows in 8 hours, the windows open quickly , if I opened and closed windows a thousand times in 2 hours, the window openings get slower and slower. The 5 axis windows are the worse and take the longest. Looks like there is inefficient use of memory handling during those window routines. I've got a Precision 3431 with 16G ram. None of the other software I use causes a slowdown and the only other app running all the time is Outlook mail. I don't recall this problem with Mastercam 2019.

What we do when we bring in part from Solidworks that we need as surfaces is we save it as an .IGES file, LOAD or MERGE it into Mastercam, then move it out of position in one direction at least as long or wide as the part, go to HOME, UNBLANK, then select all those hidden wireframes, click End Selection then delete those wireframes. Don't delete the surfaces that were blanked, those are needed for the actual surfaces of the part. We found the Solidworks .IGES export settings in the pic to work the best for us. It also makes a good clean file for Calypso software on the CMM. I'm not sure if these extra hidden wireframes will be in the NX files. You'll just need to give it a try.

The dust isn't the only issue. I think the CE & LE phenolics are made with and release when cut.... "Includes, but is not limited to, phenol-formaldehyde, phenol-furfural and resorcinol-formaldehyde." source... https://www.epa.gov/stationary-sources-air-pollution/manufacture-aminophenolic-resins-national-emission-standards My nose burns when the a lot of parts are being cut on the saw. Inhaling too much of it makes my nostrils burn. Ventilation is required. When parts get to CNC milling & turning, not a problem because we use synthetic coolants. Don't use oil based on phenolics or it with get absorbed into the material by the fibers. Not good for insulating materials. CE & LE also come in the color black, by added graphite. Makes it more abrasive.

Never mind, I found the fix here... https://www.emastercam.com/forums/topic/99841-2020-killed-my-thumbnails/

No previews working on any of my Mastercams after MCX-9 but I only get previews on MCX-9 files. Does anyone know of a fix for this? I am currently using 2019 & 2020.

True, I've been clicking on an area for years then they add it in another easier spot but I still end up going to the less efficient area to click. I figure they're always changing things anyway so why not give it a shot.

I have an idea / suggestion and wondered if this would work for others. Maybe if enough users like it, it would be implemented in the next release. #1 - Since the correct plane must be selected before clicking the Depth button in Linking Parameters, why not move Planes before Linking Parameters... #2 - Move the Breakthrough into Linking Parameters under the Depth. I don't see a need to have it separate and above the Linking Parameters when logically it's added to the depth when posted and represented graphically on screen. Even the Drill toolpath has Tip Comp under Linking Parameters, which is pretty logical so why not for Contour and all tool paths where there is a Breakthrough field... #3 - Depth cuts can also be just before Linking Parameters since it's about depths and the number of contours. This will also put Lead In/Out after Cut Parameters which is where Compensation Type is. More room can be made if needed by making graphical representations smaller. There seems to be a lot of wasted real estate on some of those windows. Any thoughts / other ideas?

Prodoggg, nope, already checked. Once the M65 is given all the feed rates work as intended for G01, G02 & G03. Only time we use Feed per rev is for rigid tapping. Thanks for chiming in.

I just got an email from our reseller and his OLF SimpleSansCJK OC font is a stick font. Three new installations here and ours are all as shown in this pic. He sent me his font of the same name and now it works correctly. Not sure how this font got corrupted during the install on 3 different computers. I hope this helps others having the same problem.

I've used letters for engraving but we also put a lot of dimensions for setup reasons for the guys on the shop floor. Now, Stick font is no longer available for dimensions. Stick font is simple & much easier to read.

Sorry, my bad, I didn't read rchipper's entire post.

Yeah I agree!!! Where's the Drafting stick font with leader ??? Bring it back please. It takes up less screen, paper space an ram, and is much easier for the guys on the shop floor to read. Also font OLF SimpleSansCJK OC is defective on the 1,2,4 & 7.

Cool thanks. Here are pics of those parameters. Are these one-shot M-codes, on a line by themselves ? And also, would these M-codes be described elsewhere and do something else I'm not aware of because I don't recognize these codes. except M6.

I am having a similar issue. I use #701 as an update counter for serial number engraving on a part. When I cycle start the tool at the beginning, it engraves only 2 blocks after plunging into the part then the #701 updates waaaay before going to the macro subprogram to do the serial number engraving, the +1 increment for the next part then M99. This was freaking me out until I realized the Matsuura 520 31i has about a 1000 block look ahead buffer. It remembers the original #701=2 an engraves the "2" but before the control ever gets to the subprogram #701 shows 3 on the offset page. I thought it was going to skip 2 and do a 3. Took about an hour to finally understand it. I thought the macro was written wrong and then thought the control was messed up. There is an M or G code I saw once upon a time in another macro on the machine. I'll have to look thru all of the macros to find it. I hope it is commented as such or I'll never find it. I'll try the M20 first though. If anyone needs this tip, I also remember seeing a parameter (forgot the number) to allow single block execution for macros, block by block (give or take), just like normal positioning moves. I turned this on for the Robodrills a few years ago.

Oh, I get it. Thanks. I read it too fast. Thanks for the tip guys.

Yep, been doing that, but when I'm on a roll and can't watch every plane creation, I end up with thousands. I already had to delete around 3000. That takes a while and becomes a crying moment.

Does 2021 do this? I haven't installed it yet.

Using 2020. I haven't found anyone else having this problem on this forum and I really don't understand it. A pic is worth a thousand words so take a look at it. I've had about a thousand planes created automatically named DfSave-1-2-2-2-2 etc, etc, etc. Looks like an array issue in the Mcam code. Anyone else have this problem?

Dell Precision 3431, (Intel Core i7-8700 CPU @ 3.2GHz) 16G RAM Quadro P1000 500G SSD (NVMe BC501 SK hy) Pretty slow but glad we don't do big number cruncher tool paths like this benchmark. All our work is non-metallic and use larger radial & axial cuts.

I just found out there are 2 places for this value in Windows 10 64 bit. The other is here... Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows Found the info here... https://stackoverflow.com/questions/38612364/how-to-increase-the-maximum-amount-of-gdi-object-for-windows-10