Jump to content

TiTaNiuM sAMuRai

Member
  • Content Count

    510
  • Joined

  • Last visited

    Never

Everything posted by TiTaNiuM sAMuRai

  1. TiTaNiuM sAMuRai

    VW10 users: tell me your grievances!

    Does VW10 fix that stupid display glitch that crops up at zooms over 1000% ?
  2. TiTaNiuM sAMuRai

    Can VW be hosted on a Server?

    Can I run VW -- or a an image of it -- on a server (specifically OSX Server)? We have enough licences for all the clients, but VW updates, Standards folder updates, Plug-ins updates etc. would be simpler if I had to do them to only one copy (server) instead of on all the client machines.
  3. TiTaNiuM sAMuRai

    Wall Join Changes

    But until you're finished the drawings, you don't necessarily know which wall will be constructed continuously...
  4. TiTaNiuM sAMuRai

    STRANGE DATA BAR DISPLAYS

    Odd. I haven't had this happen in a while. I can recall only a handful of occasions when it did occur. I'll vouch for your observations, though.
  5. TiTaNiuM sAMuRai

    symbol referencing

    It gets pretty messy. If you have symbols that are referenced but not italicized, it is almost certain that a local copy of those symbols were made, either because some stuff was copied into the drawing before the wref was performed, or the symbol was 'imported' before the wref was performed. Even though this results in a local copy (no italicizing), it's also listed in the wref, so it cannot be edited. Don't worry about it; the symbol definition should follow what is in the ref'd drawing.
  6. TiTaNiuM sAMuRai

    Exporting images

    6900 bytes sounds wrong. Was it 6900 kB (kilobytes)? Check Document Preferences -> Raster Render set Printing to 200 dpi (Pict Export also if you wish) In the Export Image dialog, set the resolution to 200 dpi. As KT alluded to, the application you use to open the file may use just the dpi to set its display or just the pixel size. For example, one app might look at two files, both at 72 dpi, and show them the same size even though one is 10x10 and the other is 1000x1000. 640 x approx.480 is a good size, leave jpg compression at Medium.
  7. TiTaNiuM sAMuRai

    symbol snapping

    I'm guessing that all of your groups and symbols are 2D. You can't snap to 2D elements when in a non-plan view (must be PLAN; top view won't suffice).
  8. TiTaNiuM sAMuRai

    VW10 users: tell me your grievances!

    Is this PIO issue inherent to PIO's in general or to the PIO's that came with VW? The only PIO's we're now using are ones I made from scratch; will they be okay?
  9. TiTaNiuM sAMuRai

    symbol snapping

    Sorry, should have mentioned that the fix for rectangles is to convert them to polygons.
  10. TiTaNiuM sAMuRai

    symbol snapping

    Remember that you get Align V and Align H when trying to snap to the endpoints of RECTANGLES and various parts of a CIRCLE (and perhaps ovals) when they are parts of symbols. (VW953)
  11. TiTaNiuM sAMuRai

    Is this a new error message?

    AWESOME! That would be the handiest thing to have, just like a save reminder! Instead of guessing, or using my psychic connection with the computer to determine when it's going to die, I'd actually be told! I don't know why the message -- written to say that something is wrong with the APPLICATION -- was intended to indicate a problem with the OS, but the app has problems 2000 times more often than the operating system. Can you guys implement this as a feature? Please?
  12. TiTaNiuM sAMuRai

    Errors in Vectorworks 10.1

    BTW, 9.2.1 works dandy, but I've had some troubles with 9.2.2. Stay away from 922 and stick with 921.
  13. TiTaNiuM sAMuRai

    VW10 users: tell me your grievances!

    Thanks a million! Keep the feedback rolling! I especially need more Mac people posting. I have to finish switching the office to OSX before migrating users to VW10, so I'm glad I have at least that delay to work with while VW10 is fixed.
  14. TiTaNiuM sAMuRai

    Errors in Vectorworks 10.1

    When the workstations here were on OS9, they had 128MB physical, and I had VW set to use 32MB minimum / 200MB maximum. Worked quite well, although one couldn't do much else at the same time.
  15. TiTaNiuM sAMuRai

    HP 500PS Plotter

    Supposedly, setting up the 500PS using the 800PS drivers works. I never got it to work with either X.1.x or X.2.x, VW9, so that machine is staying OS9. As I said though, a few people have claimed success with the 800PS description file.
  16. TiTaNiuM sAMuRai

    lines disappearing

    We've learned to live with it; I think many are aware of it in v9. I, also, am curious if it was fixed in v10.
  17. TiTaNiuM sAMuRai

    layer scale printing problems

    OSX.2.6 VW9.5.3 Printer:any Yeah, someone here can't get 10% to show.
  18. I've read posts regarding VW10's scroll support, and posts indicating that in VW9.5.x the scroll wheel should be mapped to the zoom in / zoom out aliases. I can do this, but does 9.5.3 (under OSX.2.x, incidentally) have no explicit support for the scroll wheel?
  19. TiTaNiuM sAMuRai

    -fsopen error: cannot open file

    Okay; I fixed the problem. The busy/locked status of the file when checked by Retrospect essentially tied Finder's shoelaces. I logged everybody out, shut down network apps, but when I tried to shut down the server, I get a Finder error -11 bomb. A simple soft boot restart solved the file open/closed status. All is well and good now, AFAIK.
  20. TiTaNiuM sAMuRai

    -fsopen error: cannot open file

    Someone here was doing an overnight rendering of a model (VW9.5.3) on his machine (MacOSX.2.4) although the file itself was on a networked drive (MacOS9.1). The scheduled overnight backup (Retrospect) tried to read the file for copying, but found that it was busy/locked, so it didn't copy the file. Not quite, anyway; a new copy was made, 0 kB (stupid Retrospect). This morning, the operator tried to access his file, but with no response, had to do a force-quit. The current copy of the file is still 4.4MB, but both the OS9 host and OSX client indicate that the file is in use, since VectorWorks never closed the file stream. Why oh WHY does VW keeps its grubby hands on the ACTUAL file? Good practice is to work on a temp file stream, eh? Anyway, I can't open the file by any means I know, so does anybody have any ideas?
  21. TiTaNiuM sAMuRai

    Image import: how big is too big?

    So an image can be 4096 wide, huh? Very good to know. Is there a limit on height?
  22. TiTaNiuM sAMuRai

    Image import: how big is too big?

    5100x3300 x 300 dpi x 24 bit. VW 9.5.3 croaks when it tries to import (Mac OSX.2.4 on a G3 w/ 512MB)
  23. TiTaNiuM sAMuRai

    Script for Printing?

    send a blank message to dclarke'at'aciarchitecture'dot'com and I will send mine.
  24. TiTaNiuM sAMuRai

    OSX.2.4 Right-click craps out in VW (953) only

    yep.
  25. Disk permissions have been fixed, Logitech's latest driver has been installed. A fellow user has reported the following. The right-click functionality of the mouse becomes disabled in VW only, after several usages. It still works in Finder and other applications, and is restored after some manual cmd-C and cmd-V commands, but restored for only 4 or 5 usages before it craps out again. thoughts?

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×