Jump to content

Phsion

Member
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Phsion

  1. That option was NOT checked. Not sure why but I'm sure the originator had a good reason. It seems to have added 3MB on a 500MB file, so no big deal. Opens like I expect now, thanks for the help!
  2. Now that you say that, I misspoke it seems. I was duplicating viewports and moving them to new sheets, adjusting cameras, etc. I wrongly assumed it was every change. That being said, it seems to take an awful long time when opening the sheet layer the first time, or creating/changing a viewport enough to trigger the process. Can anything be done to speed it up? I timed it, since I saved my file view the sheet layer selected, it took 4.5 minutes to reopen the file Laptop specs: AMD Ryzen 9 5900HX with Radeon Graphics, 3301 Mhz, 8 Core(s), 16 Logical Processor(s) 64 GB RAM M.2 NVME storage AMD Radeon RX 6800M
  3. All the layers are set to 300dpi, and once updated they look fine on screen and after export. This is before they are updated, where I normally see a wireframe preview and a red dotted box, I now see a weird render and the red dotted box, and it takes 10 minutes to switch to a sheet layer.
  4. I've got what seems to be a recent issue, or a feature I didn't know about. On one particular drawing, VW is taking forever generating viewport previews for every change. EDIT: I was incorrect, creating new viewports, editing render modes and perspectives, and opening sheet layers for the first time after restarting VW. It's a large drawing, so I'm not surprised, but I don't believe I've ever seen VW try to generate actual renders for the viewport preview (I'm seeing very low quality 3D shapes), instead of the simple wireframe preview. The viewports are in using Shaded Background Render, no colors or textures, just very basic. I still need to update the viewport after the preview in generated. Can anyone point me in the right direction for the Viewport Preview Quality setting I never knew existed? Thanks!
  5. Thanks for all the help, figured it out. @JBenghiat was right, but not in anyway I was expecting! I was changing DMX Address and Universe fields and watching them, but it turns out Vectorworks calculates the separate DMX and Universe fields from the Universe/Address string. Setting the unique fields appears to work until a refresh, then they're recalculated from the Universe/Address field
  6. Thanks for the responses! @JBenghiatI'm updating a variety of fields, but mostly setting the Universe and DMX Address. I wouldn't assume those would be calculated? And not calling vs.ResetObject after updating each Lighting Device lets me see that the new parameter values are shown in the Object Info, until I use the menu command to Refresh Lighting Devices. Otherwise, the parameters are cleared before I can look in the Object Info. @Jayme McColgan I don't see that function anywhere? I've looked in the Function Reference wiki and vs.py in the SDK
  7. Hi all, I'm updating Lighting Device properties via a script and the changes aren't sticking. I can see the updated values in the Object Info panel when I click on the objects, but as soon as I refresh the objects, or call vs.ResetObject(), the Object parameters change to what they we're before. The code below loops over every "Lighting Device" in the document, checks if the channel field matches one stored in a dict, then updates each parameter from the dict. vs.ForEachObject( update_from_data, "( (PON='LIGHTING DEVICE') )") def update_from_data(h): objinfo = vs.GetCustomObjectInfo(h) recordHandle = vs.GetParametricRecord(h) recname = vs.GetName(recordHandle) local_fixnum = vs.GetRField(h, recname, "channel") local_vwid = vs.GetRField(h, recname, "uid") if True: # update by channel for fixnum in import_fix_list_chan: if fixnum == local_fixnum: settings.message_append("TEST PASSED" + str(fixnum) + " " + str(local_fixnum)) set_fixture_data(h,recname,import_fix_list_chan[fixnum]) def set_fixture_data(h, recname, fixdic): for key, val in fixture.parameters_for_import.items(): if val and key: #data = getattr(self, key, data) data = fixdic[key] settings.message_append("(" + val + " = " + str(data) + ")") vs.SetRField(h, recname, val, data)
  8. Hi All, I've recently upgraded to Vectorworks 2012 Spotlight w/ Renderworks, and I'm haveing a very annoying issue I hope someone can help me with. When using the marqee selection tool to drag and select multiple symbols, I have to make my selection box very large to grab the fixture I want. For example, to select the Source Four Leko symbol I made (color added to the stock symbol), the selection box needs to be about three times as high and five times as wide as the actual symbol before the selection box will actually select the symbol. When I edit the symbol, the bounding box seems normal, but once inserted into the drawing, I have the issue. Any fix or work around? Thanks for the help. Vectorworks 2012 Sp2 Build 151150 Windows 7 Pro 64bit
×
×
  • Create New...