Probably did not make myself clear. another/further explanation. we start with v9 file with it turned off, we then take the file into X use nesting on the file. Take each separate sheet created and save it out using X. Once everything is done we then take each sheet in under X and save as a v9 file. So we can toolpath etc. (not ready to try x for toolpathing yet). This is when the WCS comes on, does not do it all the time but enough to be a pain. WCS causes us problems with other things in 9. We would love to get away from always trying to remember to check if wcs is on or off in 9 after we have had the file in X. Thanks GC

We use ver 9 and X together. It seems to work best in our shop for what we do. We are having a problem when we take a file from ver 9 to X. We have WCS turned off in the file on 9 but then when we open it up with X it magically turns on. When we save the file back out as ver 9 wcs stays on. What are we missing? thanks g.c.

We thought we would see more % used with the sheet size and part to part distance set. Instead we see less. That was what brought this question. On thanks for thhe replies!!!

Does anyone know how X figures percent used on a sheet when it nests? I did same parts twice, once with sheet margin of .25 and part distance of .4. X returned a value of 88% used. Then I did it again with sheet margin 0 and part distance 0. X returned a value of 90% used. Please don't tell me to ask my reseller cause this is what I THOUGHT these forums were for. To ask questions and not get told go back to who sold it to you. thanks g.c.

We Are debating if we should spend the money on priorities option and what if any other additional functionality comes with it. This is the question for the group after reading the field definition for priority. What will happen if we take a group of parts (small and large) and set them at priority one, and set the priority for all other parts (small and large) at a two? I think it will nest all the parts with priority one first and then the one's with a two. Others think it will not matter since we are mixing part sizes it will basically just ignore the priority. Also what other functionality do you get when you purchase advance nesting? Does Mastercam have a try it before you buy program for existing customers? Free 30 day trial? thanks g.c.

thank you I did not have true solid turned on. Thanks G.C. Overlooked it in my compare!!!!

I'm stumped, I haev compared settings between my v9 and the two others in the office that have no problem. What problem you ask, While in verify of a toolpath I try to zoom in and look closer at the sheet I receive a message saying Changing the Graphics view is not allowed at this time. any thoughts, thanks gc.

I realize this may be a beginner question but here goes anyway!! I noticed in X nesting that it assigns part names to parts , part #1, part #2 , etc... Is it possible (besides changing names each time) to have the part be named. I can't find it but then again sometimes I can't see the forest for the trees. G.C.

I like how X shoes percentage of sheet used but does it show me how many parts are on the sheet somewhere? I know how many parts I started nesting with but curious if I know how many it puts on a sheet. this is in X and MR-X. thanks g.c.

We have a number of parts toolpathed in V9 and would like to take advantage of toolpath nesting in X-MR1. I have been trying to get this working but have a problem with X maintaining the toolpath groups from 9. I especially have a problem when I try to nest multiple parts. X wants to ignore the grouping and try to put everything together. PRoblem is I need to do the operations in a certain order or else my material will go nuts!!! thanks g.c.

I just had it happen about 10 minutes ago in X-MR1. All I did was move a couple lines and points in a file and tried to save it. Didn't catch what it said at the bottom of the screen before I got the gray your screwed box. When I went back into it it was zero bytes. LUckily had a backup copy. (about 30 now) I am becoming very wary of x and it's female like mind!!!! thanks gc

I realize it would drive the cost up but don't forget once it is designed & done it is done. I did software developement for 20 years and just got started doing this 6 months ago. From my experience so far and what I know about programming the feature I am asking for cost next to nothing to develop but is marked as an add-on. Just a little silly. It reminds me of the upcharge for automatic transmission in your car. We are going to be getting another key with the added functionality. Does anyone know if it is worth getting the advanced nesting, what the cost maybe (our reseller is out) and where the price break starts for # of seats. thanks g.c.

I realize it would drive the cost up but don't forget once it is designed & done it is done. I did software developement for 20 years and just got started doing this 6 months ago. From my experience so far and what I know about programming the feature I am asking for cost next to nothing to develop but is marked as an add-on. Just a little silly. It reminds me of the upcharge for automatic transmission in your car. We are going to be getting another key with the added functionality. Does anyone know if it is worth getting the advanced nesting, what the cost maybe (our reseller is out) and where the price break starts for # of seats. thanks g.c.

I talked about ths earlier, and received a reply that there is a priority button in X but ours is grayed out. Was wondering if anyone knew if the option is available with advanced nesting? And now foir the rant, how many others think that when you buy a software package you should get ALL the bells and whistles, and not just a little ding and a little toot. I know it may cost a little more (hey the price doesn't need to go up that much), but you've already developed it so you might as get your money back a little at a time, have happier customers, and maybe just maybe get more business!!! thanks for any info g.c.

The catch is it does not do it all the time. It will do it one time then when I come back into mastercam and try to nest using the same nesting.nstx file it will work. So it is not 100% reproducible. i will send in the info as soon as I can anyways.... thanks g.c.

also after further review - I realized I only receive the above error when i am trying to add part labels. Not always but sometimes.

I have occasionally received a runtime error message from Visual C++ . The message reads: this application has requested the Runtime to terminate it in an unusual way. Pleas contact application's support. I have received this during nesting, when it has finished writing the .nstx file and is getting ready to display the sheets. (which I really like) Any thoughts or ideas on this problem thanks g.c.

OK, I knew I could find something to rant about, I finally have my points coming through nesting BUT it only takes v9 5 minutes to nest 155 parts. It takes X 10-15 minutes to nest the SAME 155 parts. Also when you are coming into the nesting routine in X it takes FOREVER to bring it up if you are trying to read the old session. So go try 155 parts and see what happens. Am I missing something in setup or what? At least tell me what I need to sacrifice to the Mastercam God!! Thanks G.C.

my bad I never noticed the priority BUT I can't seem to access it. thanks gc

OK, I found something to wish for. We use mastercam to build custom cabinets, we are very particular which sheets we use for the door and drawer fronts. When I am nesting in X (yea the points are here) it would be nice to have the option to set a priority for a part meaning if priority is set then this part will be put on the first sheet regardless, I don't care if the nsting routine leaves a big whole, I can fill it in later, I just want to able to pick a bunch of doors and drawer fronts along with other parts to fill a sheet and then go on. That is my dream!!! Thanks G.C.

I was so HAPPY when I loaded MR1 version of mastercam, nested and found points!!!! I almost kissed my boss!!! thank you all for listening to my rants!!! Give me time I will find something else to pick on eventually!!! thanks g.c.

The problem is the bit raps so this creates an issue. I would be OK if X would just bring in the points when you nest but for some reason they took it out in X even though it was in 9. I guess someone's infinite wisdom decided no one needed it. Jusr remember: No matter where you go there you are" thnks g.c.

Ok. it is that time of the month again!!!! Just wondering if I am the only one not getting points to nest? It would be really nice because I am getting told of wearing coke bottle magnifing glasses just so I can find all the arcs on my parts to put my tools to when I toolpath!!!! Yes, I know I could just grab them all and go on but here we drill different points to different depths, and since we are drilling plastic we have to peck with an operation that we can't seem to get it to work without doing 3 separate operations tied togeher as one. We thought going to X would be good since we could have different levels for each drill depth. Problem is you have to create an operation for each level at each depth otherwise when you turn off all the levels but one and import the operation it doesn't go to the correct level. I know I am ranting and I am done !!!! One good thing just 2 weeks till the Winter Star party in The Keys!!!! AND I can forget about all this!!! Thanks G.C. PS At the WSP I will be the one up all night serving coffee!!!

For my monthly whine!!!! I know (Jimmy I think) has requested this to be put back in but I don't understand why it was ever taken out. Why in v9 you can nest points on parts when you did geometry nesting BUT when you try to nest a part with only points in X you lose the points. So now you have to create a part using arcs for where you want to drill holes at instead of just using a point. Using a point sure makes it easier than hoping you are at the center of the arc when you are toolpathing. I know auto cursor should insure this but... Anyway hopefully someone from the "source" can answer. thanks g.c.

thanks