Jump to content

Sebastiaan

Member
  • Posts

    305
  • Joined

  • Last visited

Everything posted by Sebastiaan

  1. 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.
  2. 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!
  3. 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)
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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
  9. 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.
  10. 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.
  11. 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
  12. The field in the lighting symbol maintenance that appears in the instrument summary is the model name.
  13. thank you for sharing these. This was on my lockdown learning list too!
  14. 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.
  15. I would be apprehensive to change the user folder to the same location as the workgroup folder. The user folder also holds the licensing information files etc. I's rather have that hidden somewhere in the application folder. My workaround was to place an 'alias' quicklink from my personal workgroup library folder and I put that quicklink in one of the VW specified folders. That way I can now always acces my own folder structure in the Resource Selector (with one extra click). But I believe that difference between the RM and the RS should not exist.
  16. mine too so a copy and paste of your example was a good starting point 🙂
  17. Thank you so much! I now have what I want. With this highest value with criteria I am now able to make a helper database row. Where I use the cell with the returned value by your custom function in the database formula as field value criteria for the DMX Address field. This gives me a single row with just the highest DMX adress in the desired Universe. I can then just add up the DMX Footprint column with the DMX address column giving me the last free DMX adress of the Universe. I know have a fully dynamical DMX patch sheet that I used to make in Excel where I needed to do lots of manual thing and now it comes straight out of VW. And I learned a lot from worksheets. Thank you very very much.
  18. Got it! Semi colon in between record and field too I now get 498 as return value which is the highest value of all the lighting devices.
  19. If I use a comma between the record and field then the formula reverts it back to period automatically. Could that be a mac vs windows thing? But still see the -9 value. What I would like to know is the highest DMX Address in a used Universe. For instance the highest value of lighting devices that have '1' in the Universe field could be 450. the highest value of lighting devices that have '2' in the Universe field could be 475. I would like to be able to return 450 by adding the criteria "1" to the universe field.
  20. I'm pretty sure I got the capitals right. i copied them from an existing formula generated by the create report wizard =RUNSCRIPT(MaxForField; 'Lighting Device'.'DMX Address') Would be amazing to be able to use a variable to this function. I'll PM you the file i'm practicing in. Thank you!
  21. Thank you @Pat Stanford for your effort. Will try the value function in the database formula. I tried to use the custom function. It runs without errors. But it returns a valua of -9 in stead of 450 which is the highest value in this database row. Also when I think about is. I think function returns the highest value of a field of all the lighting devices in the document. Where I would only want the highest value of the database row that I created with the the criteria on the universe field. Not of all the lighting devices in total. So only the highest value with the extra criteria, would that be possible? Do you think in the future they will make more worksheet functions available?this could be so useful. Also does the value function also work in a conjunction with a database formula? Tried the value function both in the database formula as in the row formula, but it does not chance the outcome. I am trying to use a nummeric criteria for a record field that is text. Could that criteria ever work then? the database formula looks at the record field?
  22. Hi all, I have been trying to increase my worksheet skills and came across the following challenge. So this question is about learning more about worksheets. Not about finding alternatives outside of Vectorworks worksheets. I have a data base row that has a range of values that are sorted ascending. They are actually the accumulative values of the column next to it. They represent the DMX Addresses and DMX Footprint of lighting devices. The database row is filtered based on the value of the universe field of the lighting device record.. I would like to learn if it is possible to create a sort of last free DMX address value. This would be the highest value in the DMX Address field plus the corresponding DMX Footprint value. In this case 425 + 47 = 472. I tried to use the MAX function, but that returns 2159 the sum of all fields in the address column. See picture below. Is there a possible way of returning the desired values with a worksheet function? BTW you would say that my value would be the sum of the DMX Footprint field +1. But if there is a open gap in the DMX addressing that would return a faulty value. I have a second question too. I tried to make a list based on the lighting device channel numbers too. I wanted to create a database for each range of 100 channel numbers; 1 - 100, 101 - 200, 201 - 300 etcetera. I was not able to use the < > = characters to create this criteria on the channel field. I think this is caused by the fact that the channel field is a text type field and this can not be changed in the spotlight preferences. Is there an 'ISNUMBER' sort of function or other workaround to do this in the channel field? BTW i did manage to get what i want using a combination of excel an a texteditor to create the following database formula. It works, but is a little crude to say the least :-): =DATABASE((NOTINREFDLVP & NOTINDLVP & (PON='Lighting Device') & (R IN ['Lighting Device']) & (('Lighting Device'.'Channel'='101') | ('Lighting Device'.'Channel'='102') | ('Lighting Device'.'Channel'='103') | ('Lighting Device'.'Channel'='104') | ('Lighting Device'.'Channel'='105') | ('Lighting Device'.'Channel'='106') | ('Lighting Device'.'Channel'='107') | ('Lighting Device'.'Channel'='108') | ('Lighting Device'.'Channel'='109') | ('Lighting Device'.'Channel'='110') | ('Lighting Device'.'Channel'='111') | ('Lighting Device'.'Channel'='112') | ('Lighting Device'.'Channel'='113') | ('Lighting Device'.'Channel'='114') | ('Lighting Device'.'Channel'='115') | ('Lighting Device'.'Channel'='116') | ('Lighting Device'.'Channel'='117') | ('Lighting Device'.'Channel'='118') | ('Lighting Device'.'Channel'='119') | ('Lighting Device'.'Channel'='120') | ('Lighting Device'.'Channel'='121') | ('Lighting Device'.'Channel'='122') | ('Lighting Device'.'Channel'='123') | ('Lighting Device'.'Channel'='124') | ('Lighting Device'.'Channel'='125') | ('Lighting Device'.'Channel'='126') | ('Lighting Device'.'Channel'='127') | ('Lighting Device'.'Channel'='128') | ('Lighting Device'.'Channel'='129') | ('Lighting Device'.'Channel'='130') | ('Lighting Device'.'Channel'='131') | ('Lighting Device'.'Channel'='132') | ('Lighting Device'.'Channel'='133') | ('Lighting Device'.'Channel'='134') | ('Lighting Device'.'Channel'='135') | ('Lighting Device'.'Channel'='136') | ('Lighting Device'.'Channel'='137') | ('Lighting Device'.'Channel'='138') | ('Lighting Device'.'Channel'='139') | ('Lighting Device'.'Channel'='140') | ('Lighting Device'.'Channel'='141') | ('Lighting Device'.'Channel'='142') | ('Lighting Device'.'Channel'='143') | ('Lighting Device'.'Channel'='144') | ('Lighting Device'.'Channel'='145') | ('Lighting Device'.'Channel'='146') | ('Lighting Device'.'Channel'='147') | ('Lighting Device'.'Channel'='148') | ('Lighting Device'.'Channel'='149') | ('Lighting Device'.'Channel'='150') | ('Lighting Device'.'Channel'='151') | ('Lighting Device'.'Channel'='152') | ('Lighting Device'.'Channel'='153') | ('Lighting Device'.'Channel'='154') | ('Lighting Device'.'Channel'='155') | ('Lighting Device'.'Channel'='156') | ('Lighting Device'.'Channel'='157') | ('Lighting Device'.'Channel'='158') | ('Lighting Device'.'Channel'='159') | ('Lighting Device'.'Channel'='160') | ('Lighting Device'.'Channel'='161') | ('Lighting Device'.'Channel'='162') | ('Lighting Device'.'Channel'='163') | ('Lighting Device'.'Channel'='164') | ('Lighting Device'.'Channel'='165') | ('Lighting Device'.'Channel'='166') | ('Lighting Device'.'Channel'='167') | ('Lighting Device'.'Channel'='168') | ('Lighting Device'.'Channel'='169') | ('Lighting Device'.'Channel'='170') | ('Lighting Device'.'Channel'='171') | ('Lighting Device'.'Channel'='172') | ('Lighting Device'.'Channel'='173') | ('Lighting Device'.'Channel'='174') | ('Lighting Device'.'Channel'='175') | ('Lighting Device'.'Channel'='176') | ('Lighting Device'.'Channel'='177') | ('Lighting Device'.'Channel'='178') | ('Lighting Device'.'Channel'='179') | ('Lighting Device'.'Channel'='180') | ('Lighting Device'.'Channel'='181') | ('Lighting Device'.'Channel'='182') | ('Lighting Device'.'Channel'='183') | ('Lighting Device'.'Channel'='184') | ('Lighting Device'.'Channel'='185') | ('Lighting Device'.'Channel'='186') | ('Lighting Device'.'Channel'='187') | ('Lighting Device'.'Channel'='188') | ('Lighting Device'.'Channel'='189') | ('Lighting Device'.'Channel'='190') | ('Lighting Device'.'Channel'='191') | ('Lighting Device'.'Channel'='192') | ('Lighting Device'.'Channel'='193') | ('Lighting Device'.'Channel'='194') | ('Lighting Device'.'Channel'='195') | ('Lighting Device'.'Channel'='196') | ('Lighting Device'.'Channel'='197') | ('Lighting Device'.'Channel'='198') | ('Lighting Device'.'Channel'='199') | ('Lighting Device'.'Channel'='200')))) @Pat Stanford Would you know this?
  23. I see now, the old style gobo insertion is still in the 'light information' tab of the edit light window, thank you for pointing my error, I guess I should change this topic to a wishlist request for us to be able to use the provided vision gobo? Notice now it was the same in 2019 too. Feels slight shame for having had this blind spot 🙂
×
×
  • Create New...