Loading ...
Sorry, an error occurred while loading the content.

Re: [mach1mach2cnc] Re: Lazy Cam Pro version

Expand Messages
  • art
    Paul: Version 2.05 is online, let me know what those messages read. It shoudl say how many chains were created in the process.. Thanks, Art www.artofcnc.ca
    Message 1 of 20 , Jun 1, 2007
    • 0 Attachment
      Paul:

      Version 2.05 is online, let me know what those messages read. It shoudl say how many chains were created in the process..

      Thanks,
      Art
      www.artofcnc.ca

      Videos And Support Forums http://www.machsupport.com
      Users Map: http://www.frappr.com/machsupport
      ----- Original Message -----
      From: Paul W. Chamberlain
      To: mach1mach2cnc@yahoogroups.com
      Sent: Friday, June 01, 2007 2:52 PM
      Subject: [mach1mach2cnc] Re: Lazy Cam Pro version


      Hi Art,

      I've posted the screenshot here:

      http://www.artsoftcontrols.com/forum/index.php?topic=3253.new

      Thanks, Paul, Central OR

      *****

      --- In mach1mach2cnc@yahoogroups.com, art <fenerty@...> wrote:
      >
      > Paul:
      > Actually, I did add some messages on that one. What does the
      report tab say when you do an offset in current version?
      >
      > Thanks,
      > Art
      > www.artofcnc.ca
      >
      > Videos And Support Forums http://www.machsupport.com
      > Users Map: http://www.frappr.com/machsupport
      > ----- Original Message -----
      > From: Paul W. Chamberlain
      > To: mach1mach2cnc@yahoogroups.com
      > Sent: Friday, June 01, 2007 1:38 PM
      > Subject: [mach1mach2cnc] Re: Lazy Cam Pro version
      >
      >
      > Hi Art,
      >
      > While you're code thrashing LCam, I thought I would offer a
      reminder
      > for my Offsets issue. You mentioned something about embedding a
      trace
      > function to see what's going on. Again, Offsets don't work on my
      Dell
      > 2350 (onboard Intel Graphics), but does work on my IBM T23
      > ThinkPad... both with WinXP Pro SP2.
      >
      > I have installed the latest driver for the Intel Graphics, and
      > installed the latest .net 2.0 on the Dell.
      >
      > My Dell is still using the original Mach3 directory since early
      > development versions. The IBM ThinkPad has a fresh install of
      both
      > Mach3 and LCam.
      >
      > Before investing in a graphics card, I would like to know for
      sure
      > that would fix the issue. I haven't had any other graphics
      related
      > issues for any other apps I use on the Dell.
      >
      > Thanks, Paul, Central OR
      >
      > *****
      >
      > --- In mach1mach2cnc@yahoogroups.com, art <fenerty@> wrote:
      > >
      > > Hi J:
      > >
      > > The islands issue is my fault. I coded each chain to know if
      > another chain is inside it. Then , while pocketing, I
      > > check for any inside chains, and flag them as island chains. I
      do
      > see though, that the way your trying to use it makes much
      > > better sense. I will add a checkbox for "Use Islands" instead
      on
      > the pocketing control. I hate to set it so only inside chains
      > > on the layer invoved will island, I suspect it woudl confude
      more
      > people than just having a "Use Islands" selection. Your thoughts?
      > >
      > > As to the stepover, your right. Its related to an original
      brain
      > fart of mine where the tool was radius, not diameter. We fixed
      that,
      > BUT neglected
      > > to fix the secondary symptom that the stepover now needs to be
      > multipled by two now that the tool is divided by two. Ill fix
      that
      > today as well.
      > > LCam is a bit torn up for the next upgrade, which involves alot
      of
      > new code for drawing and chain rotation and such, so I cant
      promise
      > youll see
      > > it till next week, but Ill make sure those two issues are
      solved
      > for sure..
      > >
      > >
      > > Thanks,
      > > Art
      > > www.artofcnc.ca
      > >
      > > Videos And Support Forums http://www.machsupport.com
      > > Users Map: http://www.frappr.com/machsupport
      > > ----- Original Message -----
      > > From: motimon99
      > > To: mach1mach2cnc@yahoogroups.com
      > > Sent: Friday, June 01, 2007 12:32 AM
      > > Subject: [mach1mach2cnc] Re: Lazy Cam Pro version
      > >
      > >
      > > Hi Brian,
      > >
      > > Sorry for the delay.
      > >
      > > Here's the latest. I took extra time to get back to you because
      I
      > > wanted to get this right and to be sure-about what I spoke of
      and
      > > was seeing, than to possibly waste time chasing items that may
      be
      > > found as no longer relevant or erroneous.
      > >
      > > The diameter-radius offsetting for Pocketing and Offset tabs
      both
      > > seem to work (and very-Glad to find this).
      > >
      > > However, I see two unexpected performance items remaining (in
      > > addition to the incidental "Set All Layers" item earlier
      > mentioned
      > > and which you had requested more information-on); one of these
      > two
      > > remainders is new to the "recent-discussions."
      > >
      > > At the moment, unexpectedly, my LazyCam 2.02 install seems to
      be:
      > >
      > > 1) treating ALL layers as "interrelated," and treating all
      > chains,
      > > including those located within other layers which fall within
      the
      > > shape of a pocketed chain yet not residing in the layer of the
      > > pocketed chain, as "Islands" to the one being pocketed,
      > regardless
      > > (it seems) of how I load or what I do to clean, not-clean,
      choose-
      > > tool or not, etc...
      > > Such occurrence largely impedes the ability to accomplish the
      > > desired cutting of multiple (nested) pockets (of sequentially
      > > increasing depth) from a single DXF file having multiple
      chains.
      > >
      > > The cnc work idea at hand is to clear all the material from
      > > an outermost profile-chain at some-depth, then pocket an inner
      > > profile-chain at a deeper depth (with the first pocket
      operation
      > > being wholly unaffected by the presence of the inner profile-
      > chain
      > > located in a different layer, and thus usefully-cutting right
      > over
      > > the inner profile-chain as if it weren't even there --- like a
      > > lawnmower literally cutting everything inside the outer profile
      > > chain at the depth of the first-pocket). ...Such performance
      > enables
      > > portions of the second and future pocket to be cut during the
      > > cutting of the first pocket, and thus avoiding a "tall-island"
      > > effect which otherwise would need to be machined away on its
      own
      > in
      > > order to cut the second pocket deeper than the first
      pocket. ...I
      > > hope I explained this clearly-enough...
      > >
      > > My understanding is that if the chain to be pocketed is in
      > > its own layer (with no other chains in that-layer), then the
      > > performance that one should-see is the chain being pocketed
      > without
      > > influence from other chains in the other layers; my install
      > doesn't
      > > seem to have this performance, and seems to be treating all
      other-
      > > layers and their chains as islands even after I have moved the
      > inner
      > > chain out of the layer that has the outer chain. The video
      noted
      > > below shows this occurring for the example "spanner" DXF-file.
      I
      > > also did assign dedicated layers to each of several nested
      chains
      > in
      > > a different, very-simple, dedicated test file, before the CAD's
      > DXF
      > > export for LazyCam import, yet it didn't seem to make a
      > difference
      > > for this behavior.
      > >
      > > This occurrence could be a misunderstanding on my part
      > > regarding LazyCam expected-performance, or perhaps an install
      > > related or windows-component update-related anomaly, or related
      > > somehow to DXF import (or DXF export from CAD)?
      > >
      > > 2) (something NEW to recent discussions) [At the moment,
      > > unexpectedly, my LazyCam 2.02 install seems to be:] treating
      the
      > > pocketing "Step" Percent-stepover as HALF of the percentage
      value
      > > that was input. When I put in 100% "Step"-stepover on a 1/2-
      inch
      > > tool I get a pocketing-toolpath stepover of half that amount or
      > 1/4-
      > > inch..! ...It seems to halve also the Step-input values which
      are
      > > less than a 100% as well. And likewise, to get a full-diameter
      > > stepover, I have to put in 200% for the stepover value. ...Any
      > > insights there would be great...as I may be missing some basic
      > > concept or action here.
      > >
      > > 3) not implementing the "Set All Layers" button-push, though
      the
      > > Project tab of the Information Window responds that "it did
      copy
      > the
      > > height data to all the layers." The initial part of the video
      > noted-
      > > below explains and shows-this; this occurrence is not much of a
      > > bother to me presently. If it may prove-helpful, I did notice,
      > > though, that layers that are created from other layers do adopt
      > > settings-values of the parent layer.
      > >
      > > As may be needed, "A Camtasia video*" in media player format,
      > broken
      > > into 3-pieces for uploading to avoid the 5-MB file size limit,
      > and
      > > totaling 9 minutes and showing the above three items in basic-
      > > regards, is in the MotiMon99 folder in the "Files" section, so
      > one
      > > can see and analyze events exactly as they occurred.
      > >
      > > Note; due to the need to split the file, the first two of these
      > > videos stops abruptly, so if it looks like a video "froze"
      during
      > > playback it just means that it has reached the end of that-
      part,
      > and
      > > the next video will pick up right at the location where the
      other
      > > left off. Too, the ending of the last video seems a bit choppy
      > due
      > > to the editing needs relating to the discovery of offsets as
      okay
      > > and the stepover as having a possible unexpected performance.
      > >
      > > As such...
      > >
      > > ...Any insights or comments on the above-noted unexpected
      > > performances are much appreciated...
      > >
      > > Many Thanks!
      > >
      > > Regards,
      > >
      > > J
      > >
      > > PS- I'll keep an eye out for anything further you might need
      and
      > do
      > > whatever I can to respond quickly.
      > >
      > > * As I think Art once said in one of his videos, Camtasia can
      > make
      > > it sound like one has a cold, and the result is similar here -
      > > doesn't sound like me at all really. Too, there are a few
      > > more "uh's" in the video-beginning than I might like, but they
      > get
      > > much-fewer as the video progresses... !
      > >
      > > Lastly, once the above activity is completed the videos will
      > > probably be deleted to save space, reduce clutter, et al...
      > >
      > > --- In mach1mach2cnc@yahoogroups.com, "motimon99" <motimon99@>
      > > wrote:
      > > >
      > > > Sounds good Brian..!
      > > >
      > > > I'll look forward to figuring this one out; I really think it
      > has
      > > > to do with my setup somehow (an odd interaction of installs,
      or
      > a
      > > > windows update?) since I -thought- it should have been doing
      the
      > > > radii as you said;
      > > >
      > > > I'll post whatever I find out about layers once I have a
      better
      > > > handle on it, m'self.
      > > >
      > > > Thanks for the clarification on the Red X's.
      > > > You and Art seem to be doing a great job on all (including-
      > > graphics)!.
      > > >
      > > > Thanks for the reply and help
      > > >
      > > > Have a great holiday-weekend! (NRN)
      > > >
      > > > J
      > > >
      > > >
      > > >
      > > > --- In mach1mach2cnc@yahoogroups.com, Brian Barker <brianb@>
      > wrote:
      > > > >
      > > > > Hello J,
      > > > > It should be offsetting the half the Dia of the tool... I
      > just
      > > > checked
      > > > > the code in Lcam :( ... I will have to run a test file to
      > check
      > > it,
      > > > I
      > > > > hope to have time on Tuesday (have to spend some time with
      > the
      > > wife
      > > > and
      > > > > baby this weekend).
      > > > >
      > > > > The Red x's are normal and only there because Art and I
      both
      > > have
      > > > not
      > > > > made new Icons :) We are what you call "Graphically
      > > challenged"...
      > > > >
      > > > > Cool, if you can find where your layer problem is we will
      get
      > it
      > > > fixed
      > > > > as soon as we can :)
      > > > >
      > > > > Thank you for the help!
      > > > > Brian
      > > > >
      > > > >
      > > > > motimon99 wrote:
      > > > > >
      > > > > > Brian,
      > > > > > Heres a screen shot of my LazyCam ver2.02 screen with Red
      > X's
      > > and
      > > > > > maybe its similar to Wes's (Wes is doing Lathe work so
      > maybe
      > > that
      > > > > > is/was you perhaps really-wanted). The Screenshot is
      > > called "Red
      > > > Xs
      > > > > > and Dia Offset" in the photos folder called MotiMon99.
      Link:
      > > > > >
      > > http://ph.groups.yahoo.com/group/mach1mach2cnc/photos/view/b7c0?
      > > > b=1
      > > > > >
      > >
      <http://ph.groups.yahoo.com/group/mach1mach2cnc/photos/view/b7c0?
      > > > b=1>
      > > > > >
      > > > > > Are the Red X's normal in Mill Mode at this point...
      (using
      > > Mach3
      > > > > > ver 2.0.065 and LazyCam 2.02)? Or have I got a setting or
      > an
      > > > update
      > > > > > wrong etc? Would these Red X's indicate that the software
      > is
      > > or
      > > > may
      > > > > > be operating in any improper or inaccurate manner, etc.?
      > > (Based on
      > > > > > my current experiences it would seem I'm seeing some
      truly
      > odd
      > > > > > behaviors -and I'm just getting back to it after
      > downloading
      > > and
      > > > > > installing it awhile back weeks ago.)
      > > > > >
      > > > > > In the thread that Wes-started, I commented to Wes (and
      > Andy)
      > > > that I
      > > > > > was seeing issues with layer-copy, so your comment for
      info
      > on
      > > > layer-
      > > > > > copy issues may have applied more to me than to him.
      > > > > > ...As soon as I have a chance to get the exact conditions
      > and
      > > > > > particulars about layer copy problems in an
      understandable
      > > order
      > > > for-
      > > > > > myself, such that it will be useful to you, I'll post
      them
      > > with
      > > > any
      > > > > > needed screenshots. (An unexpected activity came up this
      > > morning
      > > > > > that needed my attention or this would be done by now.)
      > > > > >
      > > > > > Too, if there are certain things I need to do (like
      clean,
      > or
      > > > > > not zoom with a chain selected, etc), that would be good
      to
      > > know
      > > > > > since its possible some of those actions weren't
      completed
      > > before
      > > > I
      > > > > > completed a pocket, an offset, and then-tried a layer-
      copy
      > > which
      > > > > > didn't seem to be working somehow. (Adjusting the layer-
      > > settings
      > > > > > First, and the pressing the Apply to all button, and then
      > > doing a
      > > > > > Pocket and an Offset didn't seem to change the results.)
      > Again,
      > > > > > could be, too, that I'm not understanding how the
      software
      > is
      > > > > > supposed to be working for this feature.
      > > > > >
      > > > > >
      > > > > > Sorry for the delay in getting back on this but things
      got
      > > busy
      > > > this
      > > > > > morning; thanks for checking in and asking questions like
      > you
      > > did;
      > > > > > like Tony the Tiger of Kellogg's cereal says, you guys
      are
      > G-
      > > RRR-
      > > > E-A-
      > > > > > T..!!!
      > > > > >
      > > > > > Anything else that's needed, just say so...!
      > > > > >
      > > > > > Thanks much!
      > > > > >
      > > > > > J
      > > > > >
      > > > > > BTW:
      > > > > > HUGE-CUDOS! on the Tool Selection feature!!
      > > > > > I like it A LOT!! It's going to save me and others a TON
      of
      > > > > > time...!
      > > > > > Exactly what I would have wanted, as soon as I had a
      moment
      > to
      > > > write
      > > > > > to request for it...!
      > > > > > Just-Great it is!
      > > > > >
      > > > > > --- In mach1mach2cnc@yahoogroups.com
      > > > > > <mailto:mach1mach2cnc%40yahoogroups.com>, Brian Barker
      > > <brianb@>
      > > > > > wrote:
      > > > > > >
      > > > > > > Hello Wes,
      > > > > > > Not sure... could you send me a screen shot of what you
      > are
      > > > seeing?
      > > > > > > Thanks
      > > > > > > Brian
      > > > > > >
      > > > > > >
      > > > > > > wildman9802 wrote:
      > > > > > > >
      > > > > > > > Brian as i look at my Pro version of lazycam
      > > > > > > > I notice that there are Red x's on my turn, text,
      > offsets,
      > > > Foam
      > > > > > 2D and
      > > > > > > > Foam 3D buttons, this usally means that these buttons
      > are
      > > not
      > > > > > availble.
      > > > > > > > However the buttons are availble so what gives?
      > > > > > > >
      > > > > > > > Wes
      > > > > > > >
      > > > > > > >
      > > > > > >
      > > > > >
      > > > > >
      > > > >
      > > >
      > >
      > >
      > >
      > >
      > >
      > >
      > > [Non-text portions of this message have been removed]
      > >
      >
      >
      >
      >
      >
      >
      > [Non-text portions of this message have been removed]
      >






      [Non-text portions of this message have been removed]
    • Paul W. Chamberlain
      Hi Art, Results posted here: http://www.artsoftcontrols.com/forum/index.php?action=post;board=14.0 Thanks, Paul, Central OR ... shoudl say how many chains were
      Message 2 of 20 , Jun 1, 2007
      • 0 Attachment
        Hi Art,

        Results posted here:

        http://www.artsoftcontrols.com/forum/index.php?action=post;board=14.0

        Thanks, Paul, Central OR

        *****

        --- In mach1mach2cnc@yahoogroups.com, art <fenerty@...> wrote:
        >
        > Paul:
        >
        > Version 2.05 is online, let me know what those messages read. It
        shoudl say how many chains were created in the process..
        >
        > Thanks,
        > Art
        > www.artofcnc.ca
        >
        > Videos And Support Forums http://www.machsupport.com
        > Users Map: http://www.frappr.com/machsupport
        > ----- Original Message -----
        > From: Paul W. Chamberlain
        > To: mach1mach2cnc@yahoogroups.com
        > Sent: Friday, June 01, 2007 2:52 PM
        > Subject: [mach1mach2cnc] Re: Lazy Cam Pro version
        >
        >
        > Hi Art,
        >
        > I've posted the screenshot here:
        >
        > http://www.artsoftcontrols.com/forum/index.php?topic=3253.new
        >
        > Thanks, Paul, Central OR
        >
        > *****
        >
        > --- In mach1mach2cnc@yahoogroups.com, art <fenerty@> wrote:
        > >
        > > Paul:
        > > Actually, I did add some messages on that one. What does the
        > report tab say when you do an offset in current version?
        > >
        > > Thanks,
        > > Art
        > > www.artofcnc.ca
        > >
        > > Videos And Support Forums http://www.machsupport.com
        > > Users Map: http://www.frappr.com/machsupport
        > > ----- Original Message -----
        > > From: Paul W. Chamberlain
        > > To: mach1mach2cnc@yahoogroups.com
        > > Sent: Friday, June 01, 2007 1:38 PM
        > > Subject: [mach1mach2cnc] Re: Lazy Cam Pro version
        > >
        > >
        > > Hi Art,
        > >
        > > While you're code thrashing LCam, I thought I would offer a
        > reminder
        > > for my Offsets issue. You mentioned something about embedding a
        > trace
        > > function to see what's going on. Again, Offsets don't work on
        my
        > Dell
        > > 2350 (onboard Intel Graphics), but does work on my IBM T23
        > > ThinkPad... both with WinXP Pro SP2.
        > >
        > > I have installed the latest driver for the Intel Graphics, and
        > > installed the latest .net 2.0 on the Dell.
        > >
        > > My Dell is still using the original Mach3 directory since early
        > > development versions. The IBM ThinkPad has a fresh install of
        > both
        > > Mach3 and LCam.
        > >
        > > Before investing in a graphics card, I would like to know for
        > sure
        > > that would fix the issue. I haven't had any other graphics
        > related
        > > issues for any other apps I use on the Dell.
        > >
        > > Thanks, Paul, Central OR
        > >
        > > *****
        > >
        > > --- In mach1mach2cnc@yahoogroups.com, art <fenerty@> wrote:
        > > >
        > > > Hi J:
        > > >
        > > > The islands issue is my fault. I coded each chain to know if
        > > another chain is inside it. Then , while pocketing, I
        > > > check for any inside chains, and flag them as island chains.
        I
        > do
        > > see though, that the way your trying to use it makes much
        > > > better sense. I will add a checkbox for "Use Islands" instead
        > on
        > > the pocketing control. I hate to set it so only inside chains
        > > > on the layer invoved will island, I suspect it woudl confude
        > more
        > > people than just having a "Use Islands" selection. Your
        thoughts?
        > > >
        > > > As to the stepover, your right. Its related to an original
        > brain
        > > fart of mine where the tool was radius, not diameter. We fixed
        > that,
        > > BUT neglected
        > > > to fix the secondary symptom that the stepover now needs to
        be
        > > multipled by two now that the tool is divided by two. Ill fix
        > that
        > > today as well.
        > > > LCam is a bit torn up for the next upgrade, which involves
        alot
        > of
        > > new code for drawing and chain rotation and such, so I cant
        > promise
        > > youll see
        > > > it till next week, but Ill make sure those two issues are
        > solved
        > > for sure..
        > > >
        > > >
        > > > Thanks,
        > > > Art
        > > > www.artofcnc.ca
        > > >
        > > > Videos And Support Forums http://www.machsupport.com
        > > > Users Map: http://www.frappr.com/machsupport
        > > > ----- Original Message -----
        > > > From: motimon99
        > > > To: mach1mach2cnc@yahoogroups.com
        > > > Sent: Friday, June 01, 2007 12:32 AM
        > > > Subject: [mach1mach2cnc] Re: Lazy Cam Pro version
        > > >
        > > >
        > > > Hi Brian,
        > > >
        > > > Sorry for the delay.
        > > >
        > > > Here's the latest. I took extra time to get back to you
        because
        > I
        > > > wanted to get this right and to be sure-about what I spoke of
        > and
        > > > was seeing, than to possibly waste time chasing items that
        may
        > be
        > > > found as no longer relevant or erroneous.
        > > >
        > > > The diameter-radius offsetting for Pocketing and Offset tabs
        > both
        > > > seem to work (and very-Glad to find this).
        > > >
        > > > However, I see two unexpected performance items remaining (in
        > > > addition to the incidental "Set All Layers" item earlier
        > > mentioned
        > > > and which you had requested more information-on); one of
        these
        > > two
        > > > remainders is new to the "recent-discussions."
        > > >
        > > > At the moment, unexpectedly, my LazyCam 2.02 install seems to
        > be:
        > > >
        > > > 1) treating ALL layers as "interrelated," and treating all
        > > chains,
        > > > including those located within other layers which fall within
        > the
        > > > shape of a pocketed chain yet not residing in the layer of
        the
        > > > pocketed chain, as "Islands" to the one being pocketed,
        > > regardless
        > > > (it seems) of how I load or what I do to clean, not-clean,
        > choose-
        > > > tool or not, etc...
        > > > Such occurrence largely impedes the ability to accomplish the
        > > > desired cutting of multiple (nested) pockets (of sequentially
        > > > increasing depth) from a single DXF file having multiple
        > chains.
        > > >
        > > > The cnc work idea at hand is to clear all the material from
        > > > an outermost profile-chain at some-depth, then pocket an
        inner
        > > > profile-chain at a deeper depth (with the first pocket
        > operation
        > > > being wholly unaffected by the presence of the inner profile-
        > > chain
        > > > located in a different layer, and thus usefully-cutting right
        > > over
        > > > the inner profile-chain as if it weren't even there --- like
        a
        > > > lawnmower literally cutting everything inside the outer
        profile
        > > > chain at the depth of the first-pocket). ...Such performance
        > > enables
        > > > portions of the second and future pocket to be cut during the
        > > > cutting of the first pocket, and thus avoiding a "tall-
        island"
        > > > effect which otherwise would need to be machined away on its
        > own
        > > in
        > > > order to cut the second pocket deeper than the first
        > pocket. ...I
        > > > hope I explained this clearly-enough...
        > > >
        > > > My understanding is that if the chain to be pocketed is in
        > > > its own layer (with no other chains in that-layer), then the
        > > > performance that one should-see is the chain being pocketed
        > > without
        > > > influence from other chains in the other layers; my install
        > > doesn't
        > > > seem to have this performance, and seems to be treating all
        > other-
        > > > layers and their chains as islands even after I have moved
        the
        > > inner
        > > > chain out of the layer that has the outer chain. The video
        > noted
        > > > below shows this occurring for the example "spanner" DXF-
        file.
        > I
        > > > also did assign dedicated layers to each of several nested
        > chains
        > > in
        > > > a different, very-simple, dedicated test file, before the
        CAD's
        > > DXF
        > > > export for LazyCam import, yet it didn't seem to make a
        > > difference
        > > > for this behavior.
        > > >
        > > > This occurrence could be a misunderstanding on my part
        > > > regarding LazyCam expected-performance, or perhaps an install
        > > > related or windows-component update-related anomaly, or
        related
        > > > somehow to DXF import (or DXF export from CAD)?
        > > >
        > > > 2) (something NEW to recent discussions) [At the moment,
        > > > unexpectedly, my LazyCam 2.02 install seems to be:] treating
        > the
        > > > pocketing "Step" Percent-stepover as HALF of the percentage
        > value
        > > > that was input. When I put in 100% "Step"-stepover on a 1/2-
        > inch
        > > > tool I get a pocketing-toolpath stepover of half that amount
        or
        > > 1/4-
        > > > inch..! ...It seems to halve also the Step-input values which
        > are
        > > > less than a 100% as well. And likewise, to get a full-
        diameter
        > > > stepover, I have to put in 200% for the stepover
        value. ...Any
        > > > insights there would be great...as I may be missing some
        basic
        > > > concept or action here.
        > > >
        > > > 3) not implementing the "Set All Layers" button-push, though
        > the
        > > > Project tab of the Information Window responds that "it did
        > copy
        > > the
        > > > height data to all the layers." The initial part of the video
        > > noted-
        > > > below explains and shows-this; this occurrence is not much of
        a
        > > > bother to me presently. If it may prove-helpful, I did
        notice,
        > > > though, that layers that are created from other layers do
        adopt
        > > > settings-values of the parent layer.
        > > >
        > > > As may be needed, "A Camtasia video*" in media player format,
        > > broken
        > > > into 3-pieces for uploading to avoid the 5-MB file size
        limit,
        > > and
        > > > totaling 9 minutes and showing the above three items in basic-
        > > > regards, is in the MotiMon99 folder in the "Files" section,
        so
        > > one
        > > > can see and analyze events exactly as they occurred.
        > > >
        > > > Note; due to the need to split the file, the first two of
        these
        > > > videos stops abruptly, so if it looks like a video "froze"
        > during
        > > > playback it just means that it has reached the end of that-
        > part,
        > > and
        > > > the next video will pick up right at the location where the
        > other
        > > > left off. Too, the ending of the last video seems a bit
        choppy
        > > due
        > > > to the editing needs relating to the discovery of offsets as
        > okay
        > > > and the stepover as having a possible unexpected performance.
        > > >
        > > > As such...
        > > >
        > > > ...Any insights or comments on the above-noted unexpected
        > > > performances are much appreciated...
        > > >
        > > > Many Thanks!
        > > >
        > > > Regards,
        > > >
        > > > J
        > > >
        > > > PS- I'll keep an eye out for anything further you might need
        > and
        > > do
        > > > whatever I can to respond quickly.
        > > >
        > > > * As I think Art once said in one of his videos, Camtasia can
        > > make
        > > > it sound like one has a cold, and the result is similar here -
        > > > doesn't sound like me at all really. Too, there are a few
        > > > more "uh's" in the video-beginning than I might like, but
        they
        > > get
        > > > much-fewer as the video progresses... !
        > > >
        > > > Lastly, once the above activity is completed the videos will
        > > > probably be deleted to save space, reduce clutter, et al...
        > > >
        > > > --- In mach1mach2cnc@yahoogroups.com, "motimon99"
        <motimon99@>
        > > > wrote:
        > > > >
        > > > > Sounds good Brian..!
        > > > >
        > > > > I'll look forward to figuring this one out; I really think
        it
        > > has
        > > > > to do with my setup somehow (an odd interaction of
        installs,
        > or
        > > a
        > > > > windows update?) since I -thought- it should have been
        doing
        > the
        > > > > radii as you said;
        > > > >
        > > > > I'll post whatever I find out about layers once I have a
        > better
        > > > > handle on it, m'self.
        > > > >
        > > > > Thanks for the clarification on the Red X's.
        > > > > You and Art seem to be doing a great job on all (including-
        > > > graphics)!.
        > > > >
        > > > > Thanks for the reply and help
        > > > >
        > > > > Have a great holiday-weekend! (NRN)
        > > > >
        > > > > J
        > > > >
        > > > >
        > > > >
        > > > > --- In mach1mach2cnc@yahoogroups.com, Brian Barker
        <brianb@>
        > > wrote:
        > > > > >
        > > > > > Hello J,
        > > > > > It should be offsetting the half the Dia of the tool... I
        > > just
        > > > > checked
        > > > > > the code in Lcam :( ... I will have to run a test file to
        > > check
        > > > it,
        > > > > I
        > > > > > hope to have time on Tuesday (have to spend some time
        with
        > > the
        > > > wife
        > > > > and
        > > > > > baby this weekend).
        > > > > >
        > > > > > The Red x's are normal and only there because Art and I
        > both
        > > > have
        > > > > not
        > > > > > made new Icons :) We are what you call "Graphically
        > > > challenged"...
        > > > > >
        > > > > > Cool, if you can find where your layer problem is we will
        > get
        > > it
        > > > > fixed
        > > > > > as soon as we can :)
        > > > > >
        > > > > > Thank you for the help!
        > > > > > Brian
        > > > > >
        > > > > >
        > > > > > motimon99 wrote:
        > > > > > >
        > > > > > > Brian,
        > > > > > > Heres a screen shot of my LazyCam ver2.02 screen with
        Red
        > > X's
        > > > and
        > > > > > > maybe its similar to Wes's (Wes is doing Lathe work so
        > > maybe
        > > > that
        > > > > > > is/was you perhaps really-wanted). The Screenshot is
        > > > called "Red
        > > > > Xs
        > > > > > > and Dia Offset" in the photos folder called MotiMon99.
        > Link:
        > > > > > >
        > > >
        http://ph.groups.yahoo.com/group/mach1mach2cnc/photos/view/b7c0?
        > > > > b=1
        > > > > > >
        > > >
        > <http://ph.groups.yahoo.com/group/mach1mach2cnc/photos/view/b7c0?
        > > > > b=1>
        > > > > > >
        > > > > > > Are the Red X's normal in Mill Mode at this point...
        > (using
        > > > Mach3
        > > > > > > ver 2.0.065 and LazyCam 2.02)? Or have I got a setting
        or
        > > an
        > > > > update
        > > > > > > wrong etc? Would these Red X's indicate that the
        software
        > > is
        > > > or
        > > > > may
        > > > > > > be operating in any improper or inaccurate manner,
        etc.?
        > > > (Based on
        > > > > > > my current experiences it would seem I'm seeing some
        > truly
        > > odd
        > > > > > > behaviors -and I'm just getting back to it after
        > > downloading
        > > > and
        > > > > > > installing it awhile back weeks ago.)
        > > > > > >
        > > > > > > In the thread that Wes-started, I commented to Wes (and
        > > Andy)
        > > > > that I
        > > > > > > was seeing issues with layer-copy, so your comment for
        > info
        > > on
        > > > > layer-
        > > > > > > copy issues may have applied more to me than to him.
        > > > > > > ...As soon as I have a chance to get the exact
        conditions
        > > and
        > > > > > > particulars about layer copy problems in an
        > understandable
        > > > order
        > > > > for-
        > > > > > > myself, such that it will be useful to you, I'll post
        > them
        > > > with
        > > > > any
        > > > > > > needed screenshots. (An unexpected activity came up
        this
        > > > morning
        > > > > > > that needed my attention or this would be done by now.)
        > > > > > >
        > > > > > > Too, if there are certain things I need to do (like
        > clean,
        > > or
        > > > > > > not zoom with a chain selected, etc), that would be
        good
        > to
        > > > know
        > > > > > > since its possible some of those actions weren't
        > completed
        > > > before
        > > > > I
        > > > > > > completed a pocket, an offset, and then-tried a layer-
        > copy
        > > > which
        > > > > > > didn't seem to be working somehow. (Adjusting the layer-
        > > > settings
        > > > > > > First, and the pressing the Apply to all button, and
        then
        > > > doing a
        > > > > > > Pocket and an Offset didn't seem to change the
        results.)
        > > Again,
        > > > > > > could be, too, that I'm not understanding how the
        > software
        > > is
        > > > > > > supposed to be working for this feature.
        > > > > > >
        > > > > > >
        > > > > > > Sorry for the delay in getting back on this but things
        > got
        > > > busy
        > > > > this
        > > > > > > morning; thanks for checking in and asking questions
        like
        > > you
        > > > did;
        > > > > > > like Tony the Tiger of Kellogg's cereal says, you guys
        > are
        > > G-
        > > > RRR-
        > > > > E-A-
        > > > > > > T..!!!
        > > > > > >
        > > > > > > Anything else that's needed, just say so...!
        > > > > > >
        > > > > > > Thanks much!
        > > > > > >
        > > > > > > J
        > > > > > >
        > > > > > > BTW:
        > > > > > > HUGE-CUDOS! on the Tool Selection feature!!
        > > > > > > I like it A LOT!! It's going to save me and others a
        TON
        > of
        > > > > > > time...!
        > > > > > > Exactly what I would have wanted, as soon as I had a
        > moment
        > > to
        > > > > write
        > > > > > > to request for it...!
        > > > > > > Just-Great it is!
        > > > > > >
        > > > > > > --- In mach1mach2cnc@yahoogroups.com
        > > > > > > <mailto:mach1mach2cnc%40yahoogroups.com>, Brian Barker
        > > > <brianb@>
        > > > > > > wrote:
        > > > > > > >
        > > > > > > > Hello Wes,
        > > > > > > > Not sure... could you send me a screen shot of what
        you
        > > are
        > > > > seeing?
        > > > > > > > Thanks
        > > > > > > > Brian
        > > > > > > >
        > > > > > > >
        > > > > > > > wildman9802 wrote:
        > > > > > > > >
        > > > > > > > > Brian as i look at my Pro version of lazycam
        > > > > > > > > I notice that there are Red x's on my turn, text,
        > > offsets,
        > > > > Foam
        > > > > > > 2D and
        > > > > > > > > Foam 3D buttons, this usally means that these
        buttons
        > > are
        > > > not
        > > > > > > availble.
        > > > > > > > > However the buttons are availble so what gives?
        > > > > > > > >
        > > > > > > > > Wes
        > > > > > > > >
        > > > > > > > >
        > > > > > > >
        > > > > > >
        > > > > > >
        > > > > >
        > > > >
        > > >
        > > >
        > > >
        > > >
        > > >
        > > >
        > > > [Non-text portions of this message have been removed]
        > > >
        > >
        > >
        > >
        > >
        > >
        > >
        > > [Non-text portions of this message have been removed]
        > >
        >
        >
        >
        >
        >
        >
        > [Non-text portions of this message have been removed]
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.