exocubic

Add my vote to this one...

Hear, hear. I'm with Bruce on this one. Fundamentals should not equal crippleware.

That is exciting news. Could you provide any more information?

Wow, Charles, this is awesome. I am testing it a little now. Thanks for your efforts, it's really appreciated.

Robert and I worked through this a bit, and did determine that a bug exists in the current fillet tool - but one that is already fixed in the next version. Quote from Robert: Mark, your particular file poses some interesting issues for VectorWorks and how it deals with arc-smoothed polyline files. It's clear from the way you've described your problems online that you've experimented fairly thoroughly with the workflow to accomplish what you want, and in the doing you've hit on a precision bug (the one that is causing your large-radius arcs to vanish). As it turns out, this precision bug has already been fixed in an upcoming release, but that does you no good, because the upcoming release is available only to official beta-testers. The bug is that, when filleting a very large-radius arc with a small-radius arc, the fillet tool gets confused and deletes the wrong portion of the large arc. As you probably have seen, it doesn't happen on all vertices, only some.

I've sent along the file. Thanks for trying to help me out, Robert.

Either I am insane, inept, or completely misunderstanding the fillet tool. When attempting to create a fillet between two arcs (who share endpoints, are planar, and are created in VW itself by tracing over imported .DWGs from SketchUp), the tool fails in strange and unpredictable ways. Sometimes the fillet simply is not created, with no visible output from the program as to why. Other times one of the original arcs disappears, having been replaced by the fillet arc and a line on the wrong side of the fillet. I am operating under a tight deadline and just wanting to fillet a few hundred corners without too much stress. To test my sanity, I tried exporting a .DWG and importing it into ViaCAD (a $99[!] 2d and 3d package now sold through Punch! software). Every single intersection which failed to fillet in VW (I have Fundamentals - $995?!) was flawlessly created. Why? For $896 I would hope VW would be more robust, easier to use, and more informative to the user. (Can you tell I'm getting just a bit miffed?)

That helps quite a bit - thanks Katie. It would be very handy to be able to fillet every corner in the drawing, however - I'm making tool paths for a CNC laser cutter, where every sharp corner needs to be filleted at .015" - and there are about 750 said corners.

I'm needing to apply the same fillet to all corners in a drawing. Is it possible to do this in one fell swoop via a script or some other arcane voodoo?

Pete - that works nicely. Thanks!

Update - changing the class in the OIP works (the attributes update the way I expect them to) when offsetting an ARC, but not a line. Tell me that isn't weird.

Thanks for the input, Don. I have been doing as you outline: hitting the OIP right away, but for some strange reason I then have to go to the attributes palette and switch the pen color to "class color" in order to get the offset line to change to the default pen color for the class - and I do have "use at creation" set for that class. Tedious as hell, and I only have 366 more lines to go.

I am tring to offset a path for laser cutting. I want the line created by offsetting a duplicate of the original line to be part of the active class, with that class's attributes. I can't seem to make this happen, regardless of the "use at creation" setting. Is this me being dense or is the offset tool not able to do what I want?

OK, more VW-related oddities with icons. Check out these Spotlight data importers... which have nothing to do with VW, sporting the VW icon. What the...?

Thanks for the tip, that should work when saving newly created files. But with already extant files, I am unable to hide extensions (the checkbox is grayed out in the Get Info window) via the Finder. All other files, besides those with the .mcd extension, are able to be hidden this way.

On my iMac G5, I am unable to hide the extension for .mcd files. Why? And can this be remedied in some way?

Peter- I had this problem on my 12.0.1 install, but it seems to have stopped in 12.5.

Yeah, they're tiny- but disturbing. Nicholas, your sig indicates you're using 12.0. Does that mean this isn't a new-to-12.5 display bug?

When trying to trim some arcs (created with the arc by three points tool), I discovered that each of them, when zoomed WAY in, contained a freaky little zig-zag at the midpoint. Upon executing the trim, the weirdness multiplied to each endpoint of the trimmed arc. Is this just a display oddity, or what? The drawing is to be sent to a laser cutting machine, so any screwy geometry will hose the toolpath.

Would adding a "snap" column to the navigation palette and organization windows simplify things? As a new VW user, I am continually getting confused by the different visibility/snapping settings for layers and classes. The wording of the layer options is responsible for some of this confusion. A simple visual cue in the form of an added column might lessen it.

I hate to be one of "those" kinda people, but there is no such word as "alot" in the English language. End nitpick.

I tried again, after quitting Launchbar, which was still running previously. The installation completed succesfully (no, really). I think it may have actually just been a bandwidth issue with NNA servers.

Doh... spoke too soon. The installer made it further into the process, but failed again with the following error: There was an error in GetAndInstallUpdates. Exception Type: exceptions.UnboundLocalError Exception Value: local variable 'zipObj' referenced before assignment Exception Stack: File "InstallerScript.pyc", line 1238, in GetAndInstallUpdates File "InstallerScript.pyc", line 826, in OpenZipFile

I was able to complete the upgrade. Go to the "Sharing" system pref pane and disable your firewall.

I also have received this error. iMac G5 running OS 10.4.7.