Don, this is something we're looking into.

^ funny!

Peter- In the trimming function, makes sure you're set to "break": and "to point" in depressed: Then you can sketch the point with your mouse and break it where you want. Doug

Thad- Our programmers have confirmed that this is a bug. I'm going to log it now. Thanks for confiming it with me! Doug

Thad- If I do this and keep the start point on the first entity chained, it works. But if I round the corner onto the next entity, I get what you're getting. Can you confirm or deny this? Doug

Yes Jim. the holder definition is new in the HS toolpaths. Of course, the intent is to have this definition in all toolpaths in upcoming releases. There's so much new functionality in the HS toolpaths it's tought to know where to start. Just play with them; you'll figure it out! And if you haven't looked at the videos for HS yet, definately do. They do a very good job explaining and demonstrating the functionality and benefits of these new toolpaths.

I can't seem to reproduce this. I can turn on and off my wirepaths, and when they're on, they remain on. Both in backplot and otherwise. If you'd like to e-mail your file to me, I can test it on my system. Doug

John- His problem is trying to use multiple origins in the same plane. Try creating 2 random circles all in the Top plane. When toolpathing the 1st one, use it's center as a new origin (through the Planes dislog). Now do the second arc and set the origin to the center of it. You'll notice that it will corrupt the previous operation, because you're actually moving the origin for it too. I think this is the problem. The workaround is to create multiple named views; 1 for each origin. It's more work than before and I've already logged it.

Thanks for the file Justin. I believe that the problem is that in X, we've done away with numbered and corresponding system views. Let me explain: In V9, when you created a new origin, Mastercam would create a new system view, although most people didn't know this because it happened behind the scenes. So if you had 5 origins all in the Top view, there would actually be 5 different system views for each. This is why if you changed one, the others would not be affected. In X, we did away with system views and numbered views for a lot of reasons, most to do with simplification. What this means is that all origins created in 1 plane will be linked. The solution is to do what Brilu said: create a new named view (multiple copies of TOP for instance)for each origin that you want. You only need to do this for multiple ops with different origins that share the same plane. I can see where this would be a pain and create extra work, so we're going to look at this and see if we can do something to make it work more like V9 while at the same time not reintroducing system and numbered views.

I can't seem to repeat this issue. I can have different tool planes and origins for different operations, and one does not affect another. If I change my t-plane and/or work origin for one of my operations, it only affects that one. I am running a production candidate or MR1, so maybe this was a bug that's now fixed. Accu if you'd like to e-mail the file to me, I'll take a look at it.

Are you changing the t-plane or just the work origin or both? I just want to make sure I'm understanding the issue.

Or hold down the 'shift' button and you select the endpoint from which you want to be relative. Just a shortcut to the selection that davidb just pointed out (relative).

DavidB does it the way that I like to do it. In fact, all attributes in X (Level, color, line style, line thickness) can be changed by first pre-selecting the geometry and then right-clicking on the appropriate attribute that you want to change (in the bottom prompt area). I think it's the quickest and easiest way to change attributes.

I'm not sure that's a windows-capable function. You can add multiple nested fly-outs; one within another. We've figured out that you could just about include every Mastercam function in the RMB by doing this.

Murlin- You mean this, or are you talking about someting different?

Murlin- This is a known problem and has already been fixed in the Beta version of MR1. So it's not just you

Murlin- At first I thought you may be double-clicking one of the selection points, because this would end the selection. But I'm seeing the same thing here. I'll click a few times and then it won't take anymore points. If I keep trying, it'll eventually add more points, but I have to click several times to do this. Is this what you are experiencing? Doug

Hi Mark- all of your custom toolbars, right mouse menu, toolbar locations and toolbar states can be moved. just go to settings, customize and look for the location of your .MTB file in the lower left corner of the dialog. It's located in c:mcamxconfigmastercam.mtb. Just copy this file into the cofig folder of the new install. Your machine and control defs are located in C:mcamxcnc_machines. Just find the ones you want and move them to the same place on the new PC.

quote: I would think that the 'update mastercam" button would look to see what updates had already been applied like windows update does and some other software packages. Yes, this is correct. But Peter's point was that, from a tech support standpoint having, say, 10 small updates per year would be a nightmare. Resellers would have to have all 10 versions running to be able to trouble shoot potential customer's problems. quote: What percentage of people who use the forum have internet access? 100%? On this forum, yes. But the unfortunate fact is that not all of our users have internet access, at least not from the machines that are running Mastercam. This forum only represents a small (but very important ) cross section of our user base. On a global scale, having this many small releases would be a big logistical problem for us.

quote: I guess I am being selfish. Nah, you're not being selfish Jeremy. If it were my problem, I'm sure I'd feel the same way . I'm not exacly sure of the reason we don't have weekly or bi-weekly updates as they become available. But my guess would be that it would be difficult to QC these at such a high frequency. I'll look into this question and see if I can get a good answer.

Hi Jeremy- It's not our policy to try to force a customer into purchaing a maintenance contract by withholding bug fixes. That being said, maintenance is the best way to make sure you are receiving the most up to date software you can. SPs are and will continue to be free to all current Mastercam users. The problem is that SPs won't always address every issue of every user that we have. And if something doesn't make it into a SP, but does a make it into a MR, then the customer not on maintenance will miss these fixes until they update to the next major release. There is not a lot of time in between the SP1 that's now available and the MR1 that's coming out, so the chances of an SP2 in between are slim. It's just a scheduling thing. We're already running daily versions of MR1 internally and many bugs have already been addressed for the MR1 release, as well as some really high-end high-speed toolpaths that we're releasing. Still, it's ultimately the customer's choice.

Yes, it will be called Design LT, and will be available with the release of MR1. Pricing is still up in the air, but it should be close to the current price of Draft V9.

Dan- Hold the shift key down when you select the point that you need to be relative to. This will bring up the relative ribbon bar.

Juat a reach here, but since installing X, have you maxed your graphics card acceleration? X wants full acceleration to run, but in many cases V9 does not, and will act sluggish if running with full acceleration.

John- can you get this to happen consistently when adding points? I just tried it, but it works OK here. Sometimes I do get this message, but I haven't in a while, and when I did, I found it very difficult to duplicate. If you can duplicate this consistently, please let us know. thanks! Doug