V3 Build 8 Uploaded

October 28, 2009 · Filed Under MeshCAM Development 

I just uploaded build 8 to the standard location.  It fixes a bug that Randy found and adds the option to drag and drop a 3D file onto an already-open 3D file.  This will give you the option of opening the new file or inserting it into the current file as a check surface.  This is good for times when you want to define your own supports in a CAD program of if you want to add a shut-off surface to an open area.  This capability has been available via scripting but it was never a first-class function so I don’t think anybody ever used it.  Hopefully this will be better.

 

I’m still eager to get any bug reports as you play with this build or build 7.

Comments

4 Responses to “V3 Build 8 Uploaded”

  1. Randy on October 28th, 2009 8:24 pm

    Yeesh, Robert, you’re really making me work harder to dig out ever more obscure bugs. :) Thank you!

    The drag’n'drop check surface function is sweet. If you have two different versions of an STL, you can also use it to superimpose them and see the differences (as long as the origin is the same for both files…) And it is way more convenient than digging out the script. Bravo!

    Your fix to the not-calculating-toolpaths-when-loading-settings problem works great also.

    So now that I’ve confirmed all that, when is 3r9 coming out? [ducking and running]

    Randy

  2. Robert on October 29th, 2009 9:43 am

    You can have another build when you find another bug- kind of like eating your dinner before you get desert.

    -Robert

  3. Randy on October 29th, 2009 12:00 pm

    Sounds more like eating a bug before I get dessert… :)

    Randy

  4. Randy on November 2nd, 2009 11:56 pm

    Robert, the worst thing I’ve found so far is in the one mixed-unit job I tried. Model (supplied by user Richard on the forum) was in mm so rawstock dialog was in mm. Good there. My tools are in inches, so Generate Toolpath dialog was all in inches, except for “Machine geometry +” number in mm. Good there too. Output gcode was in inches (reasonable, since that was my tool UOM). Only glitch was that [CUTVIEWERSTOCK] was output in mm. Reasonable in itself, but not matched to the gcode UOM. If that’s the worst bug I find I’ll skip dessert. :)

    Randy