Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

RobP

Verified Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

564 profile views

RobP's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Sorry, but I'm really lost at where you're trying to send me to find this GFX Acceleration option that can be turned off. I've tried all the other suggestions. This is a problem on 2 machines sitting next to each other. Both Nvidia cards, one a 660 and one a 980, both Intel I5 CPUs. This setup has run solid for over 2 years, and didn't go down in flames until around the time 2018 was installed which also coincided with Windows 10 Fall Release Update. Since then, it will load, but I am locked out of the Workspace. I can see a cursor and click on icons, but I just can't do anything or manipulate anything in the workspace. The most frustrating thing is everything was working fine, and then one day just doesn't. I'm personally blaming the Windows update, but that would mean others should be in the same boat, and so there should be a troubleshooting path that can fix this, but so far I haven't been able to find it.
  2. I was wondering if anyone had this issue and found a decent work around or fix. Windows 10 64-bit fresh install, and fresh install of X7. I can do nothing in the work area. I cannot rotate the view, change view, or draw anything. Once I disable Hardware Acceleration in screen settings, it works, but once I load a file it becomes very slow. I have the latest drivers etc. Just wondering if someone has been through this, or could offer me insight as to where to look to try and fix this. I do have 2018 and it works fine. The backstory on my problem is that everything was working fine until one day it just stopped, possibly after a Win10 update. Possibly after having someone come in to install MCAM2018.
  3. Thanks for the reply. I did that and everything moves much quicker now. My next question would be, should I be concerned at all with the statements show in the .err? Like, Post variable 'ltol$' was re-initialized from 0.0005 to 0.002
  4. I've done a side by side install (X2->X3), and after using import directory and getting everything looking okay, I went to post a trial program, and it took forever. As I've found in some of the other posts on the forum, by returning to the default.control file it speeds back up. Is there a particular way to import an X2 .control file to be used with X3, or am I just missing some obvious setting. I'm getting the same errors some other folks have posted (when I log them to an .err file.) code: 04 Oct 2008 08:44:23 PM - <0> - Report created. 04 Oct 2008 08:44:23 PM - <2> - Initialize posting log file 04 Oct 2008 08:44:23 PM - <2> - Using MP run version 11.00 and post components version 10.00 04 Oct 2008 08:44:23 PM - <2> - Initiate opening the post processor file(s). 04 Oct 2008 08:44:23 PM - <2> - Post processor file name: C:MCAMX3MILLPOSTSHAASVM3.PST 04 Oct 2008 08:44:23 PM - <2> - The post processor file has been successfully opened. 04 Oct 2008 08:44:23 PM - <2> - Post version information (input): 04 Oct 2008 08:44:23 PM - <2> - UPDATEPOST Version 11. was used to modify this file. 04 Oct 2008 08:44:23 PM - <2> - The file was modified by this product on 26 Oct 06 09:26:17 04 Oct 2008 08:44:23 PM - <2> - The post was written to run with Mastercam Version 11. 04 Oct 2008 08:44:23 PM - <2> - The post product type is Mill. 04 Oct 2008 08:44:23 PM - <2> - Initialization of pre-defined post variables, strings, postblocks was successful. 04 Oct 2008 08:44:23 PM - <2> - Search for defined post variables, strings, postblocks was successful. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'ltol$' was re-initialized from 0.0005 to 0.002 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'maxrad$' was re-initialized from 999.9999 to 999. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'helix_tol$' was re-initialized from 0.0005 to 0.0001 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'met_helix_tol$' was re-initialized from 0.005 to 0.001 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'atol$' was re-initialized from 0.5 to 0.01 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'error_msg$' was re-initialized from 0. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'err_file$' was re-initialized from 0. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'dec_seq_right$' was re-initialized from 3. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'dec_seq_left$' was re-initialized from 3. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'sub_seq_typ$' was re-initialized from 0. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'bldnxtool$' was re-initialized from 0. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrk$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrkxz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'nobrkyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrk$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrkxz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lnobrkyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutput$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutputxz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'arcoutputyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'larcoutput$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'larctypexz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'larcoutputyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcs$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcsxz$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'breakarcsyz$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcs$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcsxz$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lbreakarcsyz$' was re-initialized from 0. to 2. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'do_full_arc$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'do_full_arcxz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'do_full_arcyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'ldo_full_arc$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'ldo_full_arcxz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'ldo_full_arcyz$' was re-initialized from 1. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'arccheck$' was re-initialized from 111. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'larccheck$' was re-initialized from 111. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'rotfeed4$' was re-initialized from 2. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'rotfeed5$' was re-initialized from 3. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lrotfeed4$' was re-initialized from 2. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'lrotfeed5$' was re-initialized from 0. to 1. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'sub_level$' was re-initialized from 0. to 0. 04 Oct 2008 08:44:42 PM - <2> - CONTROL DEFINITION - - Post variable 'peckacel$' was re-initialized from 1. to 0.6 04 Oct 2008 08:44:42 PM - <2> - Successful completion of posting process! Much thanks in advance.
  5. Can you change the search radius of the auto cursor? Or even cursor size for that matter?
  6. But Autocursor would require me to run the cursor along the circumference of the circle and watching for the 4 points of the circle. 2 quads, 1 midpoint and 1 endpoint.
  7. And one other questions regarding selection. I see that after a move we still have the moved entities turning purple since they are now considered a 'result'. I'm wondering if there is anyway to select this result the way we could in all previous versions of MC. Before it was just a simple tap of the 'R' key. I'm not sure where it is now, I'm hoping I don't have to dig through drop downs.
  8. I've just moved into MCX MR1 for Wire and I'm a little frustrated to say the least, about not being able to use my left hand (at the keyboard) to move through menu's or switch between say, point, endpoint, center, etc. Being told I can basically cut off my left hand because I'll never need it in Mastercam, ever again (at the keyboard atleast) is sort of dumb. Anyhow, my question is, if I am using Analyze Position, and I need to check a series of endpoints, is there anyway to make the function be stuck to 'endpoints'. Before I could simply tap "E" on the keyboard and click through all my circles/lines, but now it seems the only way to do this is to continuously go back up to the corresponding button and clicking on it first before going back to the next arc. I guess I'm wondering if there's an option to make it modal (is that the correct term?) You already have a function like this when creating circles where the value box turns red (although I think it should default to this mode personally.) Not sure if anyone else had asked but, can we atleast have this simple function back, associating the first letter of the word with it's selection, so E=Endpoint, C=Center, etc.

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...