jfitch

I am modeling solids with a series of additions, subtractions, and filleting. For additions and subtractions one can double-click down into the object, but I have found no way to do that for filleting. To edit something near the bottom of the process, I have to ungroup the fillets, then remember the dimensions, edges/intersections involved, and the order applied to get back to where I was. Is there a way to extract the order of operations, or enter an object to edit without losing what was done? Right now I have to keep a separate text file edited and up to date, this is at best a poor method as it is nearly impossible to describe the edges and intersections needing to be filleted.

I did bring this workspace in from another version. That was the solution to the export quicktime thing. Do I assume that Quicktime VR objects will not display in QT 10? Only in 7? Would they display in something else? Thanks BTW.

I tried to export a quicktime movie as I have done in the past. This is VW2015 sp3 on 10.10.2. Where the menu item to export a quicktime movie was, now it says that. And doesn't do anything. I also tried to export a Quicktime VR object. This worked, produced a large file. But it will not open in Quicktime, latest version. I had to download QT 7 to play it. Can anyone tell me where to get the plugin?

This continues to happen and I wish it would get addressed. I have noticed that it will not occur for several days at a time, then for no apparent reason on the same file, occur several times in an hour.

Thanks to daithid - resizing the window seems to reset the offset. Much quicker than saving and reverting/reopening.

More information: The vertical offset of the snap grid seems to be characteristic of the file. One file when it goes bad may offset low a certain number of pixels. Always the same, when it happens. On another file, it will offset high a different number of pixels - but always the same number. Right now I have three open windows. One is correct, one is offset high about 200 pixels, another is offset low about 100 pixels. Saving the file and reopening will fix it for a short period but it happens again within a few minutes to a couple of hours.

Having this very frequently. It can happen even as you use the open and foreground window, it is not dependent on sleep to occur. To be very specific: It is displacing the snap grid and snap selection box up or down (I have never seen it left or right). The cursor point continues to point at the correct location on the drawing, the lower right indicator boxes show the correct cursor position, and the cursor position is correctly reflected on the rulers. However the snap grid, both logical and displayed on screen is displaced a short fixed number of pixels up or down compared to the cursor point, rulers, and coordinate system. The selection box and snap box are similarly displaced. Zooming does not change the number of pixels displaced. Nor does scaling the screen in system preferences. I have seen if fix itself only once. For me it happens 10 - 15 times a day, making the program very annoying to use.

I have seen this as well. MacBook pro Retina using only the track pad. It is more likely to happen after shutting the lid and sleeping, but it will happen even as you use it sometimes, so not exclusively a sleep issue. It is not file related, simply saving, closing, and reopening the same file will fix it (without quitting vectorworks). Also with multiple files open it only affects one file (or maybe more) but not all the others that are open. So something in that session with that particular file.

Here is an attached example. This is a simple extruded solid. The only edge selected for filleting is the upper left hand semicircle. Notice that it has filleted down both sides until it could find no more material to fillet. The break in the near edge shows how it runs off the material tangent to the last edge it has decided to fillet. It has similarly damaged the far edge of the left hand semicircle. If you do this same operation a few revisions back it looks very different: only the chosen left hand semicircle is filleted, stopping at the straight segments.

I am trying to the the fillet tool to do some round overs on a machine part solid model. The way it used to work is that the fillet would (usually) stop at the vertex at the end of the selected edge segment. It would stop just as though you were using a round over router bit and lifted it or pulled it away from the work at that point. Now, in 2011, the fillet continues on tangent to the last edge until it clears the part. Sometimes it just continues on around the edge of the surface regardless of whether the next segment is selected for filleting or not. The "select tangent edges" option is not selected, nor is the face option selected. I have tried every combination of these, also adding extra vertices of different types in the polyline from which the solid was extruded, etc. all without success. Can someone explain to me how to reliably get the fillet to stop? I'm having trouble reverse engineering this tool....

I'm glad you boys love your PCs. Really do wish that Vectorworks would fix these problems though. Or at least respond to the enquiry. By the way, does the same thing on OSX 10.6.

Absolutely none of that is ever necessary on a MacIntosh. If you are a long time Windows user you are used to it, if you are a long time Mac user you might look at that as an annoying waste of time. But I digress.... Search the knowledge base for "Redraw", you will find the script for VW2009. It does not work on 2010. However after a lot of experimenting I have discovered that a) any operation between the gesture initiated zoom and the pan will cause it to pan properly; and b) if the Hand tool is selected with the space bar to do the pan, it will pan properly (even if the Hand tool is already selected!). I think that gives me a useable workaround until such time as VW can properly fix the problem.

That does seem to work, though it gives poor control over where the zoom happens, and how much zoom you get. I'm not sure why Vectorworks can't get this right. Others do, even Windows apps running under VMWare. There are also continuing problems with selection highlights. I guess my preference would be to have the existing problems fixed, before bringing out new versions. To ask the customer to pay $500 a year for each new version, when some of these problems date back to at least VW12 or before, seems callous to the user base. Maybe I am alone in these sentiments.

This is an Nvidia 9400/9600. The prescribed fixes for previous versions do not seem to work on this one. I haven't tried a scroll wheel mouse, can't carry one of those around with the MacBook, so even if it worked, it would not be a solution for me.

"Updating video drivers" is something that is taken care of automatically in OSX as far as I know. It isn't like Windows where you have to poke all around the system. The system configuration is in the body of the email: MacBook Pro running OSX 10.5.8. This is the latest 10.5 OS. This is Architect with Renderworks, but none of that makes any difference, this is a Fundamental problem, to coin a pun.