Jump to content

jfitch

Member
  • Posts

    44
  • Joined

  • Last visited

Everything posted by jfitch

  1. 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.
  2. 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.
  3. 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?
  4. 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.
  5. Thanks to daithid - resizing the window seems to reset the offset. Much quicker than saving and reverting/reopening.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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....
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. "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.
  16. I just loaded VW2010 including the SP1 update. I am running on a MacBook Pro, OSX 10.5.8. Anytime a zoom followed by a pan is done using the trackpad, the display tears, producing an incoherent graphic display. It does this on drawn objects, the print boundary, the grid, everything. I had a somewhat similar issue with 2009 and there was a script to run which more or less fixed it. Still a bunch of display anomalies remain, but it was useable. I ran the same script on 2010 with no effect. Toggling the Quartz imaging setting makes no difference. To duplicate, simply pan so that part of a drawing is off screen, zoom using a two finger gesture, then pan back using the hand tool (all on the track pad). A redraw usually straightens it up again (but not always). Example screen shot attached. There must be a fix for this?
  17. It seems to depend on the layer. I have not been able to determine any common feature among the 16 layers that did not import, that are not shared by layers that did. Some of them are not at all complicated. All of them were cut/pasted into the blank layer the import created (which at least gives you the name, Z offset, etc.) after a select all. I am going to have to assume that those layers that did import, did so without error - that is a very difficult thing to check. The newly created file, with imported and pasted layers, does print. I had to recreate the view using viewports since layer links are no longer supported. (Recreating the view in the old file using viewports did not correct the printing problem.)
  18. Tried deleting, then individually re-importing the layers that imported empty. No dice, nothing comes in on those layers. On layers that import blank, I can "select all" then paste in place, works OK. Why won't it import? How do I know that it imported all the objects on other layers, if it can pick and choose? Edit: of the 40 or so layers, 16 imported empty and do so on repeated attempts. I cannot see any difference between ones that import correctly (I assume...) and ones that are empty. I can "select all" on a layer that will not import, and "paste in place" with no problems.
  19. Console print logs are unenlightening. It says "completed" every time - never an error. There is no difference in anything I can see when it works (new file with pasted data) and when it doesn't. Takes about the same amount of time, logs look identical. Only difference is, when it doesn't work, no paper comes out. Got calls into Epson, my guess is they are going to say since it works with every other application, it must be the app. Printing to the RIP server works (it prints through the same driver, the RIP server and driver are running on the same computer).
  20. More: I can import the layers a few at a time without crashing, however there seems to be multiple bugs in the process. The "Import Objects" checkbox for example sometimes greys for no reason, reselecting the layers several times will fix it. Then some layers import with no objects on them at all. Trying to set up the same view I wanted to print ends up crashing during a resection of visible layers in the viewport. This view was previously done with layer links, of course those are now gone. I cannot import those layers with links, not legal. So far, not much luck with this 2009 upgrade....
  21. OK, I tried this. First were a large number of dialog warnings about layer links not being pastable. I dismissed them all, figuring I would have to recreate them. Then it crashed VW with an "unexpected error". Maybe this feature doesn't work?
  22. VW2009 seems to have a problem updating old files, resulting in printing problems with my Epson 3800 printer (see the topic in Printing). I doubt anyone will look into this since it seems to only occur at the cross section of: a larger than A size sheet, a file created in an older version of VW, and an Epson printer. I discovered that if I copy and paste the same data into a fresh file, the print problems seem to go away. However a simple copy/paste results in everything copied ending up on the same layer. That means to recreate the drawing requires a copy/paste of each layer, a very tedious process in drawings with a large number of layers. Is there a way to copy and paste an entire drawing to preserve the layer structure?
  23. Not that anyone is listening, but some additional info: Problem does not seem to occur in a newly created VW 2009 file. Also perhaps not in a file updated from VW 2008. However if the file is older (I have a file originally created in Modelshop 3, continuously upgraded, another created in 10 or 11 that exhibit the problem) then the problem occurs. If I take the same components and copy/past them into a new file, works fine. While that might be a workaround, it is an extremely tedious one since to preserve the layering and class structure each layer must be individually pasted for each class - literally hundreds of operations.
  24. A little more info: VW 12.5.2 - same thing. Every other app I have tried seems to work OK. For example, photo programs, Microsoft office, etc.
  25. Just installed Epson 3800 Stylus Pro, trying to print from Vectorworks. Sometimes small pages will print (US Letter size). Have not been able to print a US C size. Print monitor says "printing" briefly, then "completed" but nothing comes out. Print the same view to a PDF and print from Preview, works fine. Other applications work fine. VectorWorks 2008 seems to have the same problem. Any suggestions? MacBook Pro Intel, 10.5.5, print driver 6.11.
×
×
  • Create New...