Jump to content


  • Posts

  • Joined

  • Last visited


148 Spectacular


Personal Information

  • Location
    United Kingdom

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks Nikolay, the below works perfect. Leaving here in case anyone elses searches for this. hProjData = vs.GetObject('Title Block Project Data') str_PName = vs.GetRField(hProjData, 'Title Block Project Data', 'Project Name')
  2. I'm exporting some data out of VW via script and would like to include the project name, ID, client etc, and other custom project data fields I've added. Currently I ForEachObject through title blocks and grab the project record data, but it would be nice to access it directly. Maybe I should grab the 'first' TBB in the file and use that, but ideally I can just locate the data directly.
  3. At the moment, my approach is to manually sum the weight of the ladder components themselves and everything hanging on it, and set that as the weight of the rigging Point Load object. The interconnection of ladders to truss (actually, the interconnection of various different sub-structures/hanging positions to truss) is an existing request logged at the moment. The ability for hanging positions to report their total weight including symbol-based metalwork components is also logged as a request.
  4. Personally, I don't use the Lighting Pipe Ladder tool. It seems more theatre-focused, and can't hang on truss. It can't use actual ladder products either. If I remember correctly, I think the alignment of a fixture on the rung might use the Vectorworks 'theatre' alignment (at the geometric centre of the tube) and not the Braceworks alignment - underside of the tube, like a Truss symbol. So, I could to make a separate copy of my fixture symbols with a 24mm offset so the clamp attaches naturally, but I don't really want to. I add a point load to the truss and 'Show Symbol' with the manufacturer symbols of the ladder - multiples nested in to a larger symbol if needed, with some master snap points for fast assembly. This isn't ideal though, as moving the truss doesn't take any of the fixtures with it. It's still the best option right now IMO. I've experimented with making my ladder symbol and it's fixtures a hanging position (which I don't use very much), but the hanging position doesn't include the weight of the ladder, so that's not much use at the moment. In the future, I'd like to see hanging positions able to report the weight of rigging components inside them in the total, and for a new connection object that can connect a hanging position to a truss using a chosen symbol (like the two couplers in the image above).
  5. Basically, yes. - Create your devices, with their physical attributes (HWD, Power, Weight) ideally. - Create Equipment Items from your devices (Create Equipment command) - For any equipment you didn't specify physical attributes for on the devices, change these on the matching Equipment Item now. - For any Equipment Item you want to look more realistic and not just the default grey representation, tick 'use symbol' and point it towards the relevant black (or blue) symbol with the geometry in. Note that this does not 'convert' your equipment to a 3D model - it just 'uses' the appearance of the chosen symbol. Functionally, it's still a ConnectCAD Equipment Item. IIRC there is a way for the Create Equipment to scan libraries and grab something other than the default 'Grey Box' equipment item, but I can't remember what it is. Have a search of this forum. I don't use it much as I don't have much decent 3D geometry of the equipment we use at the moment. I don't like the look of photos on equipment, and some of the rubbish CAD geometry that comes out of manufacturers isn't worth bothering with. I would love to use more of it, if it was decent solid models, when I get round to modelling more of it.
  6. I didn't actually VE this in the end as it was easy to solve with a worksheet with the same data, and I presumed it was just me with a somewhat niche request. But if there are multiple of us, I'll put a VE in now.
  7. I don't know what the roadmap is and what Vectorworks and the GDTF developer have in store. But I would hope that GDTFs are not something that is inserted instead of a lighting device - since it would lose a lot of the functionality of the current lighting device symbols. Rather, I think there is hope from some of us in the user base that it will just be easier to use GDTFs in their current way - rather than having to download, import and link them, they are somehow accessible more directly. Something like this is mentioned on the public roadmap here: https://www.vectorworks.net/en-US/public-roadmap
  8. Use the lighting device tool to place a Viper symbol (not the GDTF) from the Vectorworks fixture library. Then select it and in the Shape pane of the OIP, use the GDTF Fixture: drop down. Any GDTFs present in this file will be available for selection - one entry in the list for each mode in the GDTF. IIRC it'll be basic and extended for the Viper. Pick which one you need. The fixture will then use the symbol geometry but inherit the mode name and footprint from the GDTF. Any MVR exports would take the GDTF as well.
  9. Depends if you're using the spotlight cable tools or plan to make circuits in ConnectCAD. By the sounds of it, you want to make circuits in ConnectCAD. To interact with ConnectCAD cable routes/planning, you'll need equipment items, but you can 'link' the two. so if you draw a blank default equipment item and drag it's blue grip on to a spotlight object, that will link the Equipment Item in ConnectCAD 'world' to the Spotlight object - whatever it may be. The Equipment Item then becomes the thing that can interact with cable routes, drop points and report lengths. To generate schematic devices, ConnectCAD can't guess what sockets are required on the device - does the fixture have an EtherCON socket as well as it's 5-pin? Does it have a mains link out or just the in? Therefore, you should make a device symbol for each thing with the correct make and model, with the sockets you need. Make this through device builder, and it will then exist as a symbol in your file (I store all my ConnectCAD devices as symbols anyway). I'd then make a worksheet with a database row reporting equipment items with their make, model and name. Then, you can run the Create Devices From Worksheet command, which will find the make and model in your device symbols and place them, with one placed for each Named equipment item. The CDFW command can't use a database row as it's source, so I copy the database results in to a second worksheet with normal rows and use that as the source for the CDFW. Really, this increasing link between spotlight and connectcad could do with a generational advancement on both sides to the point where connection objects/definitions in spotlight objects could logically translate to sockets in ConnectCAD, spotlight objects had embedded equipment item functionality, Create Devices from Worksheet expanding to be Create Devices from Selected Spotlight Objects/Selected Equipment Items etc and other such things. To get to that point, I think the spotlight object model would need to be refined as well - so instead of just an 'input 3D' block in the Lighting Device 3D component, it works closer to the distributor arrangement where there are discrete objects for mains in, data in and out etc, so they can be duplicated to an extent not possible with fixed fields in the OIP. This is how a similar platform works - I can add three input blocks to a symbol if I want.
  10. Thanks so much. I'll have a dig through and get my head in to it.
  11. I'm quite comfortable now creating scripts with custom dialogs that execute some kind of process and distributing them as VSMs. But as much as I read the function reference, I can't get my head around creating a basic parametric object. Like with menu command scripts, I think once I've got a small simple example I understand, I can expand it up to useful applications. Is there such a think as a boilerplate example, please, that can do something simple like draw an 'example' object from a tool, that has one or two parameters to adjust in the shape pane? Thanks
  12. Thanks - the SetRField works great. I should have thought of that really, maybe I subconsciously assumed it would just try and place the string and it wouldn't know what to do with it. But that's great.
  13. I'm trying to write a script that will insert some Hoists ('BrxHoist'). The hoist is not a styled PIO but rather one that uses a symbol and inherits the record data to populate it's params. I can insert a hoist fine with this: p = (100,100) h = vs.CreateCustomObjectN('BrxHoist',p,0,False) But I don't know how to insert it with a given named symbol from the RM, or how to make it inherit a symbol after the instance is created. I.E. the stock symbol 'Hoist 1 Ton Stagemaker Down' I've used Pat's PIO field script, which shows the required field as: Hoist Symbol 'BrxHoist'.'SymbolUsed' Static Text If I just use vs.Symbol to insert the hoist symbol, this just inserts a vanilla symbol, as expected. This would also apply to the ConnectCAD Equipment Item PIO. I don't have an immediate need to programmatically insert them, but I will so, so hopefully the solution is the same. Thanks
  14. Doh - Thanks, I can't believe I didn't try that. Never twigged the hoist tool had a preferences button.
  15. In my template, I need to find a way for any inserted hoists to automatically have their assignable parts classed as below. Right now, for each inserted new hoist, I have to come in to this dialogue and change it from <Object Class> to 'Use Standard Classes'. I've tried starting a file with my template, adding a hoist and configuring the classes as shown, then re-saving my template and using that. No effect. This is also applicable to Point Loads, which I would really like to have their label classed automatically. If anyone knows how to configure this, I would like to know. Thanks.
  • Create New...