FOUND IT!!!! "Blank original geometry"

also note that if I make the problem level/model not visible and turn on another level, I can open the toolpaths as usual and then turn the level on and it is there. but then it disappears again when I try to open the toolpath again. I'm finding it increasingly difficult to program something I can't see.

I thought the same thing so I checked for an updated driver and there was so I did that to no avail. So I went to two other computers in the shop and pulled up the file and they did the same thing. something must be corrupt. I tried deleting the operations that seem to cause this issue but deleting them causes it to vanish also. boooooo

Hello Has anyone been having this issue where you have a model visible, levels manager shows it's visible and that there is an entity quantity, then you do a certain function like open a toolpaths properties and it vanishes. Level manager says it's still there but it is not displayed in the graphics pane. I turn on another level and that stuff shown up but that level is gone from view. I verified that the "only display associative geometry" toggle is NOT on. It does it over and over and over. If I save, then when I reopen it it will still be missing. On this mcam file, if I turn on a different level with the same model and open the same toolpaths properties I don't have the issue. Level 2 is my issue. A co-worker yesterday said he was importing a vise model, like he's done a hundred time before, and his part vanished just like mine. He imported a different vise model and all was well. Any thoughts on this? I hope it's something I'm doing but everything that I am doing is standard practice.

That is my default approach I was just wanting to learn how. Having to go 4" deep to get to this hex is my issue. The holders I have on hand don't give me adequate clearance. If I can produce this on the first op then my second op can be 3 axis and the setup becomes much more simple. There is a unilateral profile of .002 on this hex so if a bore bar is possible then centerline of the hex ought to be spot on. This machine moves around a bit so anything helps.

Hey y'all Today I am trying to figure out a wa y to generate this hex using a bore bar on an Integrex i300. So far I used basic contour and rotary axis set to C and turned off cutter comp. When I run it in the air it works as expected and should perform. The problem is going to be the rubbing on the back side in the tight corners. The corners are .05". I'm fine with relieving the back side more but does anyone know of a way to gradually lead the tool into the corners ( requiring the Y to come off center ) and also exiting the corners? Or is this a dream i'm having? Thanks for any input! The real part has an extra 2.5" on the CB side FYI Mcam 2023 HEX-TEST.mcam

Yo, Has anyone else been seeing this in 2023? It's random but I will be creating toolpaths, like I do everyday, and all of a sudden my highspeed paths go dirty. Not all of them but some. Just today I had a new one pop up. I created new wireframe on different construction planes and it wiped out basic contour paths. What I created had no association to the contour paths. Totally different tool/construction planes, 2D Z-depths. Everything different that I can think of. Up till now in 2023 it's only been highspeed paths. Usually I get dirty ops when I edit common parameters and modify the "Misc Values" before posting. I do this so the auto regen doesn't take off and wipe out all the stock models, plus it's much faster. Yes I do realize I can set all that as I create them but I don't. 2022 I never had the issue, not once. What am I doing different between versions or what rule changed? There are many things that are frustrating in 2023, like every release, and I'm one that likes change, for the most part. I hope it's just a simple thing I accidentally clicked. Any insight would be valued.

gee wizzzzzzzzzzzzzzzzzzzzuhhhhh! looked everywhere except there. Thank you.

Yo, Is anyone else having this issue with backplot? When I launch backplot and select "simple verify" it will show the shaded area the tool covers only it shows it as the completed render. Before I single block or hit "Play". In the past It would show the shaded areas progressively. Other computers in the shop work correctly so I must have screwed something up. Thoughts?

So Postability made this post for us. Not sure my employer wants me sharing this post they paid for so I can't post it....sorry. I know that would help a lot. Also it's encrypted. Top-Top-Top is what I am talking about. I do understand that I could leave the AC moves in. I just seem to have issues more often than not when I leave them in so just eliminating them completely would be great! It also just makes the file that much cleaner. This 5th doesn't have a clamp/unclamp rather it's just a brake. Servos hold everything. So I did remove the clamp/unclamp codes so those aren't in there anymore. I will play with the axis combos and see what I can get. You know I haven't actually reached out to our reseller regarding this. Not sure if this falls under maintenance.

Yo, Is there a simple way to take an existing 5x post and convert it to 3 axis? I love the format of the 5axis post we have but I don't want it to output A/C moves and don't want to hand edit the moves out, either after posting. Thoughts?

Hello, So I am running an Integrex and am making a custom grooving tool and want to cut the pink surfaces with a flat bottom em ( a true flat bottom ). Making the toolpath was easy and backplot and simulation show correct only the posted code is different. I know simulation doesn't read code. The first initial B rotation is B-15. and this is correct. All passes after are reversed so the C rotates 180° and starts the cut at the top. When it does this I overtravel when the head gets to the bottom. When it is B-15. and works bottom up, all is well. When i run the first pass on the machine it cuts perfectly. Is there a way I can prevent/force the post to keep all the passes the same? Looking at the picture with the pink surfaces shows that the toolpath is clean and no weird jerky moves. I am using multiaxis Curve using 3D Curves for the Curve Type and lines for the tool axis control. I did try using Misc Integer 4 which is the start solution + or -. When I changed this that is when I got it to post B-15. on the first pass only. So it worked but not on every pass. I also do get a rotary/tilt axis unwind message. It makes one pass just fine, why can't it do the others that are the same cut? What are your thoughts? Thanks for any assistance.

I believe they did it so the toolpath you have selected stands out. Earlier releases was just a little checkmark inside the folder. This new change does help isolate what you are selected on. Like anything, I will get used to it. It was set up in the past that when there were inactive machine groups with toolpaths in them, that they would be grey. Start working inside that machine group and they come back to color.

I don't understand why the wording needs to change on some things such as, when you right click in the operations manager in 2021 and I believe all releases before, you have the "select" function. In 2022 you still have it only they now named it "Operation Selection". Operation Selection is more clear on it's function at a glance than "select" is alone but I'm right clicking in the operations manager. What else would I be selecting in there other than operation related things ? Also the greyed out folders drives me nuts. I understand why they did it though. If they could make the stock model always be it's own color and not grey that would help it stand out when you have stock models buried in a lot of toolpaths. Folders were yellow and stock models were grey. They stood out nicely. Can we please change this ( not to yellow or a different shade of grey either) ? P.S. please tell me there is setting for this somewhere. hahahah Thank you!

gee wiz, Where do I start when learning about custom drill cycles? I can see a huge benefit here. Nice work!

just like the AutoRegen.dll add-in. Nice!

Sure enough you are correct. Though I won't be of any help here I did find something new? What is this Generate Toolpath toggle?

Yes, Power Keys is turned on. But hey I didn't know that was a selectable thing. Nice to know. Thanks!

Yo, For a long time now I have seen this bug that didn't used to be there. It's not a huge deal but I use hot keys and the built in shortcuts a lot. In this example I am using the "Line Endpoints" like I do 400 times a day. As many know once you are in the line endpoints window you can switch between freeform, vertical, horizontal by hitting the corresponding letters F,V,H. Well with 2021 when I ( not sure if it's just me ) launch the line endpoints and hit " V " I get vertical as expected but when I then hit "F" still in the same session of line endpoints, it won't switch over to freeform. I have to hit V again and then F but then I can't draw because it won't let me click anywhere. It gets confused somewhere. I have to close the window and launch again and hit F first if I want freeform. With that said I can use my mouse and click on the Freeform Vertical and horizontal buttons and it works fine. Just the shortcuts are glitchy. Can you try this on your setup and see if you get the same thing? Also if this has been covered then sorry for the redundancy. Thanks for tuning in

I s this a multiaxis path? On my Integrex ( not that it's machine specific but it's also mill turn ) when this is selected it will do the same thing on approach moves. But note that it will use this for all linking within the path. If not this then I'm not sure.

OK I got it! Stinkin thing! I have narrowed it down to one thing. What are the chances? If "display end points" is on when you launch backplot then it immediately crashes mastercam once you hit run or single block. I had a coworker verify on another computer and it was the same thing. So by default that button will be turned off. Now if you launch backplot with it turned off and then toggle display endpoints once its loaded, it will work for that backplot session only. WOW!!!!! Don't worry it's only a days worth of work. Now where was I yesterday at noon when all this started? hahaha I am curious if this is repeatable for others with lathe / multiaxis seats ? Those are the two seats that I have seen the issue on.

Yes. I deleted everything that had to do with Mastercam

Ok so I uninstalled mastercam and at the same time I uninstalled all previous versions and deleted everything mastercam related as if it was never on this tower. Might not have been necessary but now I have a clean slate....... didn't fix it though. GRRRRRRRRR!!!!!!!!! But hey, now I only have the one version which i've wanted to do for a long time. I also just checked the video driver update just to see and wouldn't you know that just today they released one. Installed that and still no go. Also tried turning off hardware Acceleration just to see and that didn't do anything. All this said I have now contacted mastercam support. Lets see what they can think of. FYI I have an Nvidia Quadro M2000 card which has worked for 3 years now with very few issues. Thanks for continuing to think on this "Thee Byte".

I shall try that and see what happens. Thanks! Just recently I had a second guy setup his own user account on the computer and it seem to be right around that time that issues started happening including this. Not sure if that is related.

Hey, Recently, in the last week, I have been having an issue with backplot. You know, the thing we use 1000 times a day? When I go to backplot a turning operation, it will either crash mastercam or when I hit run ( play ) it won't display any movement and I can't manipulate the graphics view. If I go to roll the graphics view it won't update till I close backplot. If I create a mill path like contour and backplot that then all is good. It seems to only be turning operations. Randomly it will work for one use on the same problem toolpath. I attached the stripped mcam file for reference. This is on an Integrex i300 FYI. I did have the same issue with a Swarf path last week but it never crashed mastercam it just wouldn't show any positions. Verify still works like it should though. Things I have tried : Restarting Mcam Restarting Computer checked for updates used the mastercam default config rolled back to previous video card driver ( tried backplot but no dice ) ( put the current updated driver back ) repair file function deleting toolpath then creating a new one. Tried using multiple turning tools thinking it was a corrupted tool....if that's even a thing. using different stock defs using different stock planes using no stock whatsoever toggle stock update on/off I am at a loss here. Is this an issue anyone else is having or that mastercam already knows about? Or is this just an isolated incident. Any thoughts would be greatly appreciated. Thanks all! test.mcam