Sebastiaan

unfortunately it is not possible to change the channel field in lighting device record to number. This is somehow restricted.

Hi all, I am trying to make a database row based on Lighting devices and I want to set a criteria on the Channel field. In the lighting device record this is a text field. I want to set a filter to show only the lighting devices with a channel number between 1 and 100. But since it is a text field, the criteria field value '<=' and '>=' do not work. I tried to use a value function in the database formula but this does not work when I try it. Is it possible? Or am I doing it wrong? This is how I tried to use the value function in the formula: =DATABASE((NOTINDLVP & NOTINREFDLVP & (PON='Lighting Device') & (VALUE('Lighting Device'.'Channel')>='1') & (VALUE('Lighting Device'.'Channel')<='100'))) This way gives the desired result, but is a very long formula to edit: =DATABASE((NOTINREFDLVP & NOTINDLVP & (PON='Lighting Device') & (R IN ['Lighting Device']) & (('Lighting Device'.'Channel'='1') | ('Lighting Device'.'Channel'='2') | ('Lighting Device'.'Channel'='3') | ('Lighting Device'.'Channel'='4') | ('Lighting Device'.'Channel'='5') | ('Lighting Device'.'Channel'='6') | ('Lighting Device'.'Channel'='7') | ('Lighting Device'.'Channel'='8') | ('Lighting Device'.'Channel'='9') | ('Lighting Device'.'Channel'='10') | ('Lighting Device'.'Channel'='11') | ('Lighting Device'.'Channel'='12') | ('Lighting Device'.'Channel'='13') | ('Lighting Device'.'Channel'='14') | ('Lighting Device'.'Channel'='15') | ('Lighting Device'.'Channel'='16') | ('Lighting Device'.'Channel'='17') | ('Lighting Device'.'Channel'='18') | ('Lighting Device'.'Channel'='19') | ('Lighting Device'.'Channel'='20') | ('Lighting Device'.'Channel'='21') | ('Lighting Device'.'Channel'='22') | ('Lighting Device'.'Channel'='23') | ('Lighting Device'.'Channel'='24') | ('Lighting Device'.'Channel'='25') | ('Lighting Device'.'Channel'='26') | ('Lighting Device'.'Channel'='27') | ('Lighting Device'.'Channel'='28') | ('Lighting Device'.'Channel'='29') | ('Lighting Device'.'Channel'='30') | ('Lighting Device'.'Channel'='31') | ('Lighting Device'.'Channel'='32') | ('Lighting Device'.'Channel'='33') | ('Lighting Device'.'Channel'='34') | ('Lighting Device'.'Channel'='35') | ('Lighting Device'.'Channel'='36') | ('Lighting Device'.'Channel'='37') | ('Lighting Device'.'Channel'='38') | ('Lighting Device'.'Channel'='39') | ('Lighting Device'.'Channel'='40') | ('Lighting Device'.'Channel'='41') | ('Lighting Device'.'Channel'='42') | ('Lighting Device'.'Channel'='43') | ('Lighting Device'.'Channel'='44') | ('Lighting Device'.'Channel'='45') | ('Lighting Device'.'Channel'='46') | ('Lighting Device'.'Channel'='47') | ('Lighting Device'.'Channel'='48') | ('Lighting Device'.'Channel'='49') | ('Lighting Device'.'Channel'='50') | ('Lighting Device'.'Channel'='51') | ('Lighting Device'.'Channel'='52') | ('Lighting Device'.'Channel'='53') | ('Lighting Device'.'Channel'='54') | ('Lighting Device'.'Channel'='55') | ('Lighting Device'.'Channel'='56') | ('Lighting Device'.'Channel'='57') | ('Lighting Device'.'Channel'='58') | ('Lighting Device'.'Channel'='59') | ('Lighting Device'.'Channel'='60') | ('Lighting Device'.'Channel'='61') | ('Lighting Device'.'Channel'='62') | ('Lighting Device'.'Channel'='63') | ('Lighting Device'.'Channel'='64') | ('Lighting Device'.'Channel'='65') | ('Lighting Device'.'Channel'='66') | ('Lighting Device'.'Channel'='67') | ('Lighting Device'.'Channel'='68') | ('Lighting Device'.'Channel'='69') | ('Lighting Device'.'Channel'='70') | ('Lighting Device'.'Channel'='71') | ('Lighting Device'.'Channel'='72') | ('Lighting Device'.'Channel'='73') | ('Lighting Device'.'Channel'='74') | ('Lighting Device'.'Channel'='75') | ('Lighting Device'.'Channel'='76') | ('Lighting Device'.'Channel'='77') | ('Lighting Device'.'Channel'='78') | ('Lighting Device'.'Channel'='79') | ('Lighting Device'.'Channel'='80') | ('Lighting Device'.'Channel'='81') | ('Lighting Device'.'Channel'='82') | ('Lighting Device'.'Channel'='83') | ('Lighting Device'.'Channel'='84') | ('Lighting Device'.'Channel'='85') | ('Lighting Device'.'Channel'='86') | ('Lighting Device'.'Channel'='87') | ('Lighting Device'.'Channel'='88') | ('Lighting Device'.'Channel'='89') | ('Lighting Device'.'Channel'='90') | ('Lighting Device'.'Channel'='91') | ('Lighting Device'.'Channel'='92') | ('Lighting Device'.'Channel'='93') | ('Lighting Device'.'Channel'='94') | ('Lighting Device'.'Channel'='95') | ('Lighting Device'.'Channel'='96') | ('Lighting Device'.'Channel'='97') | ('Lighting Device'.'Channel'='98') | ('Lighting Device'.'Channel'='99') | ('Lighting Device'.'Channel'='100')))) Any thoughts?

I am very happy that all of you are here! All of you have inspired me to follow an online Python course, and now I am trying to use that basic knowledge to make my own magic and it's going quite well! But I would never be able to, without all the helpful users, information and example code in this forum!

Sorry for the late reply, but thank you! This works well. No wonder I could not find it, not only is the naming convention different than the other functions, but also the sum values operatortype 2 is not explained in the developer page? https://developer.vectorworks.net/index.php/VS:AddWSColumnOperator

Hi all, I'm taking my first steps in to Python scripting in Vectorworks. My first project is a worksheet script to create some database rows in a worksheet. What i could not find in the function reference is how to set the 'sum values' option for a column in a database row. Is there a script function for that? I found 'SetSprdSortSumColumns' to set summarize and sort, but could not see how to set 'sum values'. Thank you, Sebastiaan

Some Icons are also hidden in individual plugin files in the plugin folder within the application folder. for instance many spotlight tool icons are hidden in spotlight.vwlibrary (richt mouse click 'show package contents' on a mac). Any .vwlibrary file could have some images in it, many don't but some do. A lot of work to check them all I know 😉 Also there are a couple of icons that I couldn't find anywhere that where hidden somewhere deeper. In that case I made a screenshot of those.

You’re welcome. Individual tool icons can be found in the VW installation. Jim Wilson explained in this topic were they can be found. I have not extracted the new 2020/2021 tool icons yet. So you would have to get them yourself. Also in the topic below you can learn how to get the toolset icons from a workspace file. hope that helps you!

BTW for maintenance of old files I could imagine the need to edit you could try to edit the field in The recourse manager. If you right click the lighting device in the recourse manager and click ‘attach record’, look up the Light info record, and then edit values. There you can edit the field.

It is a field containing a string value that acts as a filter for VW to find a fixture mode. Simply said it contains the fixture name it used to be visible in the OIP, but was placed in the background in vw2020. there is no need to edit it, it does it’s work in the background. The name fixture ID is often mistaken as channel number or fixture numnber as these terms are often used in the field. But that is not what it is in VW.

by the way. In Label legends I do place the circuit name and circuit number next to each other. It works fine the only downside is that you can not center the two fields as one. also did you know that in the label layout you can group all fields together? This wil make your label behave as one object.

I agree this should be possible. Especially when you use multiple fields next to each other then the alignment in the legend becomes much better. There are two things you can do at this moment. use a data tag. In data tags there are dynamic text fields where you can combine mutliple fields into one. Which you can then center align for instance. also you could use a script to concatenate the desired fields into one. In the AutoplotVW Plug-ins there is a menu command called copy field to field which will do exactly what you want. but this will require you to run it each time you make updates to your plot. what we really want is dynamic text fields in label legends!

Hi, I just tried the link and it still works. Maybe try it from a different browser? Did you upvote the request? (little black arrow at the left upper corner of the topic, will turn green when you click it)

Hi, I recieved the following answers from tech support. The issues did not make it to SP4, my workaround is to not use schematic views until they work as desired ;-): That is correct, currently it unpacks the schematic at the origin, piling elements on top of one another. If not using hanging positions It’s best to select individual pieces of truss 1 by 1 and create schematics of each separately and then arrange them. This workflow is being worked on and will be improved shortly. My apologies, completely forgot to answer the other questions. I think the orientation of the schematic is hopefully going to be adresed in SP4 the other issues… A lot of movements of devices in the schematic views leed to out of date schematic view geometry? This is correct you can use the select similar tool to select all of the schematics and click update on the Object Info Pallatte. And also it is not possible to move a device in the schematic view from one truss to another? This is also correct, fixtures should be moved on the truss not the schematic. However if you insert a new lighting device into a schematic it will spawn that fixture on the truss. I think this should be on the feature request list.

You need to apply a texture. This is done in the object info palette. I would advise you to check out one of the free courses in the online vectorworks University. There are some basic rendering courses there that will help you on your way.

I believe you should be able to add IES files to a lighting device from the edit light button in the OIP. I have not yet gotten around to do this myself yet but I think that should bring some improvement.

As to your question why. I always explain it like this. If I delete an object. And then change view. Then after that I want to undo the delete. Wouldn’t you want a visual confirmation that the deleted object is there again? I find the undo view change very reassuring for that reason.

Hi All, I've been testing my workflows on the schematic views. I ran into some issues, I am working on 2020 SP3. I did not convert to hanging position. The file is a new 2020 blank metric file. I have 4 sticks of truss each truss has 1 fixture attached to it. If I make a schematic view from those, the placement, rotation and order of the fixture gets messed. This happens both in top and front view the first image below is the actual truss and fixture geometry, the second and third is the schematic view made from it. If I put all 4 lighting devices on one piece of truss then the order and placement is correct, but the rotation is wrong. The first image below is the actual truss and fixture geometry, the second is the schematic view made from it: A lot of movements of devices in the schematic views leed to out of date schematic view geometry. And also it is not possible to move a device in the schematic view from one truss to another. Again the first image below is the actual truss and fixture geometry, the second is the schematic view made from it: Is there a workaround to avoid these issues? I did try to use a hanging position but that led to a very long conversion time and this schematic view also had issues. I did not continue testing those as I understood the truss system workflow is the way the program is headed now. The VWX is attached.Schematic test.vwx

SP3 is running quite well here. Have been doing al lot of training sessions on it and 1 actual real life project since the mayhem started. There is a thing here and there but I am happy with it now.

in 2020 this functionality was added to Universe and DMX address. This is great already! The universe can increment upon the restart of the DMX address. I would love to see it extended to at least the circuit number and Circuit name. They are related to each other just like universe and DMX address.

Thank you!

thank you. I just submitted a support request.

Hi All, I hav been experiencing an issue with the rendering of lighting devices. The light from the lighting devices does not render unless I perform a 'refresh instruments' or turn them off and on again. If I open the file then they do not render, If I refresh and then save again and reopen the file then the lights still do not render untill refreshed or toggled off and on. This also means that cloud renderings return without the lighting rendered as the refresh is not performed in that case. Is this an issue or do I have a setting that I have missed? It only happens to spotlight lighting devices, I tested it with a light from the light tool and then then the lights render without issues upon file open. Attached is a file, created from a blank metric file, where it happens Thank you and regards, Sebastiaan LIT FOG TEST.vwx

The field in the lighting symbol maintenance that appears in the instrument summary is the model name.

thank you for sharing these. This was on my lockdown learning list too!

I have a razor naga trinity with 12 macro button under my thumb I have: duplicate array Move by points select similar Normal perspective view orthogonal view paste in place OpenGl Wireframe Custom renderworks set lighting options. Spotlight numbering Find an Modify after some practice I can find those buttons without thinking now. it has left, down and right scrollwheel click and I put spaces and Expose under that. So it can do everything the Magic Mouse can do. Spacemouse and streamdeck on the other side.