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:
The attached vbs file will create duplicates of all 0.076 diameter arcs, with a new diameter of 0.075
Following is the code, if you wanna copy / paste:
Dim objMyArc '#Obj : Arc parameters
Dim objMyNewArc '#Obj : Arc parameters
Dim blnEntity '#Bln : DB search
blnEntity = StartDBSearch(mc_alive, mc_arctype)
Do While blnEntity
Set objMyArc = New McAr
Set objMyNewArc = New McAr
If GetArcData(GetEntityEptr, objMyArc) Then
If (objMyArc.R = 0.038) Then
With objMyNewArc
.X = objMyArc.X
.Y = objMyArc.Y
.Z = objMyArc.Z
.R = .0375
.SA = objMyArc.SA
.SW = objMyArc.SW
.View = objMyArc.View
CreateArc objMyNewArc,mcCONSTRUCTION_COLOR_CURRENT, mcCONSTRUCTION_LEVEL_CURRENT
End With
End If
End If
blnEntity = NextDBSearch
Loop
vbscript can't edit the existing entity (well perhaps if you jumped through enough hoops).
It would relatively easy to create duplicate entities, with the revised diameter, if that would help.
Thank you, I can confirm that.
Would be even nicer to be able to revert to the original selection order
after playing with the sort options & deciding I didn't like the results.
No, we work over the network, gigabit, but there's always gonna be latency issues.
Not sure how the server is configured, raid 5 with lower end HDD's I'd bet.
File open time was just a quick & easy measurement. I'll play with toolpaths as time
permits, they keep wanting actual work out of me though. Hopefully I can document
enough savings so we can get current & not be wading through mud, as it seems with X5.
As you said earlier about luxury... I may just be flogging myself here.
Pro version is required? Error message follows:
4/11/2013 11:12:31 AM - Microsoft VSIX Installer
4/11/2013 11:12:31 AM - -------------------------------------------
4/11/2013 11:12:31 AM - Initializing Install...
4/11/2013 11:12:31 AM - Extension Details...
4/11/2013 11:12:31 AM - Identifier : CSharpNETHook..921ec445-8fb7-4d73-92c3-c32f1d3f60ec
4/11/2013 11:12:31 AM - Name : CSharpNETHook
4/11/2013 11:12:31 AM - Author : [email protected]
4/11/2013 11:12:31 AM - Version : 1.0
4/11/2013 11:12:31 AM - Description : A project for creating a C# class library (.dll) NETHook hosted in Mastercam.
4/11/2013 11:12:31 AM - Locale : en-US
4/11/2013 11:12:31 AM - MoreInfoURL :
4/11/2013 11:12:31 AM - InstalledByMSI : False
4/11/2013 11:12:31 AM - SupportedFrameworkVersionRange : 4.0
4/11/2013 11:12:31 AM -
4/11/2013 11:12:31 AM - Supported Products :
4/11/2013 11:12:31 AM - Microsoft.VisualStudio.Pro
4/11/2013 11:12:31 AM - Version : 11.0
4/11/2013 11:12:31 AM -
4/11/2013 11:12:31 AM - References :
4/11/2013 11:12:31 AM -
4/11/2013 11:12:31 AM - Searching for applicable products...
4/11/2013 11:12:31 AM - Found installed product - Microsoft Visual C# Express 2010
4/11/2013 11:12:31 AM - Found installed product - Microsoft Visual Studio Express 2012 for Windows Desktop
4/11/2013 11:12:31 AM - Found installed product - Global Location
4/11/2013 11:12:31 AM - VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
at VSIXInstaller.App.InitializeInstall()
at System.Threading.Tasks.Task.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
Been playing with a 1.4GB file in X5 & X7 for the last hour.
X5 takes 6 minutes to open it, X7 is at half that (3 minutes).
Both versions take ~30 seconds to shade. In X5 I can't
manipulate (rotate, etc.) the shaded model, in X7 it's
just a bit sluggish but I can manipulate it with no issues.
Haven't compared any toolpathing yet, hopefully I'll
see similar improvements.
I'm sure any further comments I have will be specific to
X7, so I'll move over to the X7 thread at this point.
After a little investigation, it turns out that we're actually current on maintenance.
Somebody just felt it wasn't important to distribute the hasp code files.
Migrating the previous configuration files now.
It'll be interesting to see how X7 handles these (large) files.
Unfortunately it'll be a LONG while before we ever implement a newer version.
Maybe all the bugs will be worked out by then. ;-)
You'll get no argument from me.
For various internal reasons we're stuck at X5. Mostly because we're an old (+100 years) stodgy company,
a lot of people here don't like change. If I wasn't here prodding them they'd probably still be running V9.
I downloaded X7 to play with, turns out our maintenance expired last August. Oh well.
~300MB files are pretty typical for us, nothing but the usual Mcam issues.
Generally over 1GB & things start to get interesting.
The cavity insert I recently finished ended up at 1.4GB for rough / semi
and 1.2GB for finishing, I think the core was 2.1GB. Takes 10 minutes
or so just to open the files. IIRC there were +60K surfaces in the cavity.
Once open things are sluggish, but workable.
I had to break my paths up into quadrants, otherwise I'd end up with
"memory" errors while generating. Every few paths I'd restart Mcam,
otherwise I'd end up with 0 byte NCI files.
I never physically ran out of RAM, just seems to be general Mcam "quirkiness".
UG handles the parts MUCH better, unfortunately we don't use manufacturing.
Running X5, FWIW.
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.