Jump to content

klinzey

Vectorworks, Inc Employee
  • Posts

    2,534
  • Joined

  • Last visited

Everything posted by klinzey

  1. You need to have a 2D and a 3D representation of the lighting position. VW automatically supresses any 3D information in a 2D view when the object has 2D geometry. The lighing position object will always have 2D text so it will automatically hide the 3D. If you already have the 3D symbol, just edit the symbol's 2D view and draw a 2D representation of the position and you will be back in business. Kevin
  2. Cris, We think we have isolated some of the autolink problems mapping the fields between LW and VW. Till we work more directly with LW the autolink is going to just do it's best to match the fields. Things like Gobo 1 and Template only match the minds of a lighting designer. Autolink works great when the field names don't change, that's why you don't see any field matching problems when you use Excel.
  3. Then it's probably the light info record on the symbols. Someone has entered "Light" in the instrument type rather then the Device Type Field.
  4. Double check all your mappings, this is usyally the source of the problem. If it's just one type of instrument, check the Light Info Record attatched to the stmbol def. It may have the wrong information in it.
  5. It looks like the 12.5.1 update caused the problem. It works in 12.5.0, but not in 12.5.1 or 12.5.2. Kevin
  6. We need to do some more investigating to see what version the problem started but it looks like a Mac only problem. Unfortunatly at this point it looks like it's not a problem with the mapping file, but a problem with the import command on the Mac. Kevin
  7. Just like a Vectorworks file the file format of the plug-in is different. If you want to use them in 11 you have to create them in V11, they will also be usable in V12.
  8. In 12.5 and later you can use the FUNCTION CreateDuplicateObject(objectToDuplicate, containerHandle :HANDLE) :HANDLE; to copy an object to a new layer. In earlier versions use: FUNCTION HDuplicate(objectHandle :HANDLE; x :REAL; y :REAL) :HANDLE; Then you can change the layer of an object by VS using the SetParent call. Kevin
  9. Is the "None" class visable or are you drawing in active only calss? During object preview classes are ignored, but once the object is placed in the document class visability takes over amd may make the object vanish. Kevin
  10. It's not possible. You should use a menu command. Kevin
  11. MMLX, For any critical issues you should contact tech support. They can help you best in a timely manner. Unfortunatly it sounds like there is something specific to that one machine so that may not be able to reproduce the problem. Kevin
  12. Holly, If you have imported the LL from anoyther document they ended up at the root level of the resource browser. For commands to recognize the label legends they need to reside in the Label Legend Folder. It's the same thing with the containers. They must be placed in the Containers folder in order to see them as options in the label legend manager. Kevin
  13. The geometry in the symbols is in the None class. Unless the None class is visable the symbols wil vanish when you insert them.
  14. Tools\Options\VectorWorks Preferences...\Display\Display light objects\Never
  15. It sounds like you may have a bad font. We have seen this a lot with some of the hand lettering fonts. Try using a basic system font and see if the problem is fixed. You should also update to 12.5.2. I was a probelm with one of the versions where text appeared squares, but I cna't remember what version it was.
  16. There has been lots of clamor from Spotlight users about it, but not much clamer from Vectorworks users as a whole. Most designers demand the 2D representation, represent the 3D top view. Alowing rotation of the 3D object would break this rule. It's a long standing constraint that needs to be revisited in order to give flexibility given today's uses.
  17. You have never been able to rotate hybrid objects in 3D space. You should be able freely rotate objects that are 3D only. Kevin
  18. Layer links and viewports take the layer elevation into account. Just aligning the views does not use the layer z. Simple fix for your problem is to set all the layer Z to 0. The +-Z doesn't do much unless you are using certain tools (like walls) that look for the value as a default height. Simple explanation is that Layer Z is the base height for the layer. If you set it to 10' and draw something at Z=0 it will show in a Layerlink or Viewport as if it was drawn at 10' The idea is that in multi level buildings you can draw everything as if it was on the floor and then just set the floor height with the layer Z value.
  19. The chartacter should be a "-" (dash) not an "_" (underscore). In the screen shot it looks like an "_" (underscore). Kevin
  20. Empty fields have to have the "-" LW and VW both recognize the "-" as am empty field and do not actually use the "-" as data in the filed. In LW you have to tell it to ignore fields with a "-" in the import dialog and to use a "-" for empty fields in the export.
  21. Hey, We've found a user, Ian Forbes, who volunteered to start a user group in the Orlando Florida area. We've asked Ian assist in arranging the first meeting for the Orlando area. Vectorworks is coming down to Orlando on 13th July for an Architects Conference near Disney and wondering if it'd be worth while to come down the afternoon before to start things off for this new User Group. A meeting place, of any type (cafe, bar or some place of work, etc), has been suggested to kick things off.... although nothing yet has been thought of. It can be almost anywhere in town. If anyone has an idea of a good venue, Ian would love to hear it! Everyone has an open invitation to come along and network/learn/have a laugh (hopefully!). So.... whose got the first suggestion??? Those of you in the Orlando area that are interested please contact Ian directly at ian@offkilterpros.com
  22. If the delimiter was the problem it would not show as a device in LW4. Also update LW, I know John just releases a patch to fix some import/export problem.
  23. I'm not sure what you are trying to acheive as far as label placement, but if the bounding box of the symbol in the legend, the bounding box of the symbol you are using are what you expect, and you have not rotated the symbol in the label legend everything should work. Biggest source of problems with labels being out of place is some extra geometry in the symbol that you con't find unless you look for it. Select the symbol and use fit to window to see about how big the bounding box is. You're label positions may not update if you have manually moved them. You will need to delete and reassign the label legend to the instrument if my have manually moved the labels.
  24. RP, Did you place them with the accessory insertion tool? Just setting them as static accessories does not make them associate themselves with an instrument. If you mave the instrument does the accessory move too? If not, then the accessory is not inserted as an accessory. When you export do you have the export to LW4 box checked?
  25. The label legend resizes based on the bounding box of the symbol. Your symbol probably has some geometry that makes the label legend think the instrument is larger then it really is. The fixture in the LL must not be rotated, it must face the top of the page in order to work. Also, what version are you using? 12.5 has a few oprions that may help you out.
×
×
  • Create New...