Jump to content

klinzey

Vectorworks, Inc Employee
  • Posts

    2,549
  • Joined

  • Last visited

Posts posted by klinzey

  1. The root of the problem may be that your Light Info record on the symbol has no entry in the Device type Field. It should be "Light"

    If you look at the file on your windows machine you will see that the Device Type filed for the instrument is blank, On your Mac it will show as "Light". (At least in 2008)

    In order to change it on the Mac, you have to select the instruments, change the Device Type to "Moving Light" and then change it back to "Light"

  2. "The only things visible are the symbols that indicate the instruments are on and the color of the light"

    I'm a little confused by this. What is visible that indicates the instruments are on and the color of the light?

    In a 3D view you should only see the 3D outline of the lighting instrument.

    Only other thought is that you are drawing on multiple layers and not rendering using ViewPorts or layer links.

    What does your drawing look like in a wireframe 3D view? Can you see the lights and set in a 3D wireframe view at the same time?

  3. The density of the lit fog is controled by the background texture assigned to a layer. Usually the background is named "Background-1", you can edit the settings from the Resource Drowser or you can edit them from the layer dialog.

  4. The tools in Spotlight are geared for a lighting designer. the symbols included with Spotlight have data included with them that automatically tells the rendered light the correct spread for the rendered light.

    If you are just trying to place and render a logo, I'd recommend using symbols form the ETC library. You will see instruments named Source 4 followed by a degree number ranging from 5 to 90.

    The larger the degree of the unit the larger your projected image will be for a given distance.

    So follow the steps to place, focus and assign a gobo to a light using one of these instruments and see what you get. You don't need to create a position or set up a label legend, you just need a lighting device and the focus point.

    Final Quality RW will work fine, using the Custom RW settings will speed the rendering up a little.

  5. It sounds like a bad imnport from LW where the Device Type field was matched to the Instrument Type Field.

    Find and modify will not work because it first needs to determine that the device is a "Light", it will not populate the rest of the choices till it can determine the type of device.

    If you select all of the lights you can change the Device Type back to light. If you have any accessories just make sure you don't change the device type of those.

    Kevin

  6. Tim,

    It looks like the fill on those instrument is set to None.

    You can edit the 2D part of the symbol and set the fill of the object to Solid and it should be fine.

    The library should be fixed for the next maintenance release.

    Kevin

  7. Charles,

    You should not have a problem with duplicate UID. I just pasted 346 instruments three times into the same document and no duplicate UIDs were created.

    If you are talking about other data fields, then it is possible to create duplicate data in those fields.

    But that aside, the best way to do this is to use Design Layer Viewports. All three people should be working in separate files. Then in a 4th file use design layer viewports to reference the other three files. Any edits would need to be made to the three original files, but the referencing file would automatically be updated when it is opened.

    Each design layer viewport is it's own little space. You can not edit objects in the design layer viewport, but you can control visibility and it will allow you to open the referenced document from the viewport.

    Kevin

  8. The import mapping file on the Mac does not work in 12.5.2. (You will see the message that the file is not valid.) As far as I know the rest of the command functions as it did in 12.0 and 12.5.x.

    The problem has been resolved for 2008 and the autolink function has been improved.

    If you test LW "Suggest Matches" you will see that it also fails to match up some of the field names correctly and you have to manually match the fields. Both LW and VW make every effort possible to make the transfer of data between the two applications a simple as possible, but they are still two different applications.

  9. If orphans are being created the UID\Enternal ID are not matching for some reason.

    If you are using the automated actions or a standard mapping file try doing it manually, especially if you are using ones from 12.5. Also after you click the autolink button make sure the fields actually match.

    Make sure that when you export from LW you fill the fields with a "-" and that when you import into LW you tell LW to convert "-" to blank.

×
×
  • Create New...