It's a bug that's been logged and corrected for the 1st Service Pack. See... http://www.emastercam.com/cgi-bin/ultimate...ic;f=9;t=001115 ... for a workaround

There are a couple of places where the interaction gets confused by where you are and where you're trying to go. In other words, it's a bug. Please document and send to qc@mastercam exactly what you were doing at the time. Not just where you were trying to go, but where you were at the time.

Recap: Layouts on the individual solids can be done pretty quickly. In X, we modified Solids Layout to actually perform hidden line removal on multiple-solid parts. It looks great when it works, but I need to pass this one over to Parasolid.

The arrow length is now user-controllable. Did it get set to 0 or something tiny (see the Analyze/Dynamic dialog)

Go ahead and email me the file ([email protected]). I'll take a look at it

Gcode - Got it. Thanks for the details.

Complicated model? How long have you waited? Multiple solid layouts do tend to take longer, since we now do hidden line removal on the complete part, not just on the individual solids.

First we've heard of that. Could you give us a play-by-play of what you're seeing?

Alt-O toggles display of it, or you can just drag the vertical divider between it and the graphics window to make it narrower or wider.

If you're in the File/Open dialog and you click on the little light blue button in the upper right (the button looks like it has 2 blue checkmarks), what is checked? If it says "Use Last Directory" it shouldn't be changing on you. If it says "Use Default Directory", it'll use what's set in Setting/Config/Files in the "Data Paths" box.

Actually, now that I look at it a little further, it's actually an .MTB file - which is our way of storing all your toolbar information. Since there looks like there's a newly created toolbar ('analize'), my guess is that in Settings/Customize, when using the 'SaveAs' button to save the toolbar setup, .CONFIG was used instead of .MTB. The 2 filetypes DO exist in the same sub-folder ("CONFIG"), so I guess it wouldn't be a reach to think that RIZZO.CONFIG was selected instead of the default .MTB file type.

Yeah, sorry

That's a section of our Function Table file (Mastercam.FT). Don't know how it got there, maybe a cutting-and-pasting induced error???? Your best bet is to delete it and the next time you run, a .CONFIG file will be saved with default values.

But you don't really need the 2nd 'enter'! Just go to another function. I like being able to pick the line, pick the point (or enter the distance) and then just go elsewhere.

That's simply telling you that there are lines in the file that are shorter than our Mastercam tolerance (see Config/Tolerances). I've seen this quite often before, but there's only a slight chance that it's related to what might be missing geometry. Has this been happening with several files? Are they coming from someone who has been sending you good files in the past? This is a reach, but have you perhaps changed your Mastercam Tolerance? Feel free to e-mail me a file ([email protected]) and I can take a look at it sometime this week.

Chipps... ---------------------- There are so many differences even the help is not F1 like windows software. The undo with solids and geometry has many quirks and is not windows just to name a couple. The graphic card problems that are there and the necessary settings to get it to work affects Solidworks too so it wont handle standard windows graphics either. ---------------------- 1) It's easy for you to change F1 to be 'Help'. It's hard for us to re-train tens of thousands of users who are use to it being 'zoom'. 2) The only known "quirk" is that anything you do involving a solid is not undo-able. But is modifiable in th Solids Manager. It has nothing to do with being "windows". 3) In V9 you most likely had to turn down your hardware acceleration to run Mastercam. If so, turn it back up to run X. I've got X and SolidWorks (& Inventor & SolidEdge & and a handful of CAD viewers) and I run fully accelerated all the time. Again, this had nothing to do with being "windows", but with our OpenGL implementation. In general, I don't know where you're getting your information about whether a software product is what you call "windows".

Yes.

Works for me, so I don't think the problems' with the site itself. Have you gotten on there in the past?

When reading in parts from other CAD systems, their views for the 6 sides of a cube may not match ours. The Z vectors will be the same (our maybe opposite!) but the X and Y directions may be different

Great! You'll find that both STEP and Pro/E are greatly improved in X.

X offers virtually unlimited levels. So do many other CAD systems - AutoCAD for example. We've survived more than a year of Beta test and a month of use in the field without any issues coming up. All - please let us know (by emailing [email protected]) if you come across anything.

Now I see... You can import the NCI files to make operations in the OpMgr, then you can post them. To do this right click in the OpMgr and choose "Import..." (note that you have to choose a "Machine Type" first - the right click menu is not active when the OpMgr is empty)

To find ANY C-hook: You can use 1) Alt-C or 2) you can go to Settings/RunUserApplication or 3) you can go to Settings/Customize, and in the "Toolbars" tab, change the "Category" to "Mastercam C-Hooks". Then wave your cursor over the icons until you find the one you want and drag that icon up into your toolbar area in Mastercam.

It's there... You can use 1) Alt-C or 2) you can go to Settings/RunUserApplication or 3) you can go to Settings/Customize, and in the "Toolbars" tab, change the "Category" to "Mastercam C-Hooks". Then wave your cursor over the icons until you find the CoonsSurf one (6th from the left in the 1st row) and drag that icon up into your toolbar area in Mastercam.

Did you copy the .DLL I sent you into the 'Apps' subfolder and then run the STEP importer as usual (File/Convert/STEP/Read)?