V4 Build 12
I just uploaded V4 build 12 to: http://www.grzsoftware.com/v2dl.php . I made a number of little changes to the UI and one big functional change, the new “Set Machine Region” command. You can now define one of more regions to contain the toolpath without having to pull the trick of shrinking the stock to fool MeshCAM. I think this will be a huge benefit and that it will see lots of use. You can also load a DXF file but please note that only DXF V12 is well-supported. Later versions can be hit-or-miss.
Let me know how it works for you.
Link is broken. You forgot the .com
The link from the previous versio nworks, though.
The STL get’s lost and blends with the new base when you go to add tabs. So you can’t tell where you are adding them. It looks like the base is now shaded or something? I can send an example screen shot if you like, but this does not happen with the prior versions. Can that base shading be turned off?
Thanks
Rich
You can see an example if you take the samplerhino.stl, slice it into 3 slices, then load the first slice, make the material 4″ x 4″ then try and add tabs… you can’t see the part.
The machine region is great!! But,the define reigon polygon crashes vista. I tried both the cheesewiz and one of my stl’s. All other options seem to work.
Thanks,
Bob Stack
Rich- Can you send me a screenshot of the 3d view on your machine. I did make that bottom plane solid in an attempt to get rid of all of the lines in the 3D view and it would be that interfering with the supports.
The bottom slice has it’s own plane that is caused by all of the triangles collapsing onto the top of the bottom slice. While this may be mathematically correct, it is ugly and I’m not sure if I can leave it that way for release. If you rotate the view of the slice and visualize how they would be stacked after machining I think it may be more clear.
My problem is this- the current slicing method is very robust and correct for 3axis machining. I can make a more complicated algorithm work and it would give slices that look more like what you expect. It might be unstable for STL files that are not closed and watertight so it brings a new set of problems.
If you plan on using the slice command heavily then please let me know what you’re doing with it. Maybe I can get enough other data to make the decision easier.
Bob- Can you tell me what vertex you were on when it crashed? Was it the first, second,etc.? Does it happen every time?
-Robert
Robert,
Yes it happens everytime. Also, it dosn’t matter where I start as soon as I right click it crashes. I even tried off the model.
Also, I just installed B12 on my xp box and am getting the same behavior. Perhaps it’s me that is missing something?
Again, the machine region is a great feature!
Anywhere you left-click in polygon mode immediately causes a crash?
-Robert
No, anywhere I right click. The dialog box for the machine reighon->polygon says right click and left click to finish. The first time I right click down it goes.
Bob Stack
Build 13 is being compiled and uploaded now. I added some extra checks to see if they will change the behavior for you. Please run a “Check for Updates” in about 45 minutes and let me know how it works for you.
-Robert
Robert,
I just tried left clicking the points and finishing with a right click and it worked just fine.
I was a bit worried because i consistantly get my right and left wrong. My wife knows if I say go right while she is driving I most likely mean left.
I am sure I have right and left right this time.
Bob Stack
I do the same thing- I once wrote a big, complicated chunk of machining code with left and right switched in the code. It was almost impossible to fix because every part of the algorithm was flipped.
I just fixed the condition you outlined. Check in 45 minutes and tell me if you agree.
-Robert
Hi Robert… I will send you a screen shot later tonight, but the problem is not related to slice per-say. If a part has a flat top on it, that is when the problem arises, slicing just guarantees a flat top. When you rotate the part you can indeed see the part, no problem, but when you are adding Tabs it forces you the overhead view, so that doesn’t help.
Try my example and you will see it… take the SampleRhino.STL, slice it into 3 parts (which makes the top flat on the bottom slice), then make the material larger than the part and try adding tabs. You can’s see the part. I will try and get a screen shot later, but that will show you the same results.
Rich- I think I know what you mean but I’d appreciate the screenshot to make sure.
-Robert
Screen shots sent to support(at)grzsoftware.com
Rich.
I see now- I was looking at a different rendering effect. I’ll post a new version by tomorrow AM. Sorry for the trouble.
-Robert
Robert,
No more crashing, but I think the dialog box is wrong. It still says “Right Click along reigon. Left Click to Finish”
Thanks,
Bob Stack
I told you I had a problem with right and left.
-Robert
“Always Use Inch” is still broken. It works fine until close and restart.
Robert,
I have been out of town for the past 5 days (no computer) and am just trying to catch up. So no comments yet but…
> It might be unstable for STL files that are not > closed and watertight so it brings a new set of > problems. (aug 12)
Sends shivers up my spine, MCs ability to work with non watertight models is a major feature for me.
jeffD
Machining regions disappear on 4th axis parts. They work, but you can’t see that they’re there.
What would be really cool would be if you could snap to vertices to draw the regions.
Can you allow the region to be included with a .dxf import. Say it has to be on a layer called region or something like that. That would be really cool.
Gerry- I’ll look at the inch thing again and see if I missed something. I’ll also fix the 4th axis mode as well for the next release.
You can reload the same DXF you used for the geometry as a region if it contains 2d vectors. V4 will probably not do it in one step because that would force me to add UI elements to select individual regions from the file for machining. This is a big project so it’ll wait until V5 next year.
Jeff- That’s my opinion too. Your models always come to mind when I consider a need for watertight models- you always take great advantage open surfaces in what I’ve seen from you.
I also would not want to be forced to use a watertight model. Especially for .dxf surfaces.