1608chris

Hi Jeff, Yes - that's what I fear! It's just so irritating that I can see everything I need, but there just doesn't seem to be a streamlined way to get it on to paper. I appreciate it'll all be iFC in the future, but right now clients appreciate the ability to review these things room-by-room. KR, Chris

A cry for help here as I'm going round in circles trying to generate Room Data Sheets from information contained in the Space objects. Does anyone know if there is a straightforward way of doing this? Yes, I can generate a worksheet of all of those items but I would prefer this information to be presented on a sheet-per-room basis. The information I need is all in the Data Sheet shown in the Data Manager, but how to automatically populate a worksheet with these items based on a single input of the room's Name? ...Or should I be using an elaborate Data Tag? ...Can it only be done by exporting the database to Excel? (I'd rather not). Thanks in advance, Chris

Quick question related to use of the software, but do you use these to populate the Vectorworks Naming Standard Details? This is a feature that's only just come to my attention and I'm surprised that Vectorworks UK haven't included their own table of UK standards.

Just a quick note of thanks for the tables. Very useful as it's tedious having to format them for inclusion each and every time.

Sarah, just a quick thank you for your help with this. With a bit more sweat I got the task completed and have been able to schedule out ~1000 cavity barriers for a project, so your help was really appreciated. Out of interest is there a way to build a menu dialog with nodes? As last formatted my network would ask for 5 bits of information independently whereas it'd be preferable for this to all be set from one box.

For context I attach my work in progress. I'm also having problems with the records this produces, as although I resorted to using nodes to force input values to integers prior to them being added to the record, the resultant record just says '<field value>' rather than anything useful. Apologies again for all the questions, but I am totally new to all this. Thanks for your help so far. Cavity Barrier.vwx

Thanks for clearing that up too, I had been getting errors when switching to the selection criteria. I've another quick question about this sort of conversion of the networks in to menu commands - how do you programme the menu command to offer up the OIP input options prior to running the script? Once a menu command, my network just uses my default input values without opportunity to alter these.

Brilliant, thank you! That's really unlocked it, I was just unsure whether there was any specific syntax to these queries as I'd seen people refer to IFC Fields in quotes or square brackets. Just one last thing, is that 'Choice Item' node required?

Thanks for getting back to me. I'm using 2021 and attach a scratch file I've been using just to try to harvest the IFC information I need to generate cavity fire barriers around windows in construction. I believe I have put in the right Strings for IFC data for the 'Object.OverallHeight', 'Object.OverallWidth' and 'Object.VW_Name' but only get unknown values generated. What I'm trying to do is size the cavity barriers from the overall dimensions and to generate their names based on the window unit reference, so all can be traced + signed-off on site. I hope that makes sense? Cavity Barrier.vwx

Hi, I'm new to Marionette and am trying to get it to correctly retrieve IFC information so that I can automate the creation of window accessories. I'm using the Get IFC Property node but cannot get it to spit out the right results. I can see from the IFC Data... inspector under the AEC menu that the reference for my windows exists here "[Object.VW_Name] ELSE [Object.IDPrefix] + [Object.IDLabel] + [Object.IDSuffix] ELSE 'Window' " But this string does not work as an sIFCPropName. As a test I've also set up another node simply to look-up "Object.OverallHeight". Neither respond in the string with anything other than "<Unknown Value>". What am I missing here? I think it's a syntax issue (mine), but it's really very unclear how I can setup a successful query. Any help gratefully received! My brain hurts....🤕 Chris

Hi Max, I have not experienced it lately and note now that Vectorworks 2021 has a much improved workflow for setting-up this information in projects, importing DWGs etc. Regards, Chris

Third time unlucky it would seem.

As a record of the current state of my install I can confirm that CineRenderNEM is not present. (See screenshot) Also the repair install keeps stalling at 38%. (Twice already, am attempting 3rd).

Cinerender is not in that directory. Would it definitely be there if we only have a license for Architect without a full Renderworks license? I've updated to SP2.1 and am repairing the install to see if that helps.

@Alex Sagatov You might be on to something there as it has knocked out the same functions in VW 2019 now that I've checked. Must be an OSX level problem. Do you know if there is a way to manually prompt cinerender to load?

Right, the only place where I can still see my textures is in the resource browser, but these are labelled as Renderworks Textures. Am I correct in thinking that for the 2020 release Nemetschek have rolled back some functionality from 2019 to boost sales of Renderworks?

I'm using VW 2020 SP2 on MacOSX Catalina. All texture information has been stripped from edited wall types and Open GL rendered panes in my previously functioning 2019 files. When editing components and classes, no information is shown under the heading textures. I literally can't find a texture edit option anywhere. Is anyone else experiencing this? Seems like a major issue if so as it prevents me effectively editing the model junctions and appears to be interfering with rendering of sections.

Hi both, Thanks for your input. We believe the problems we experienced were related to the saving of files in a rotated view. If a file (A) , referenced in another elsewhere (B) , was saved in a rotated view the world references get mapped incorrectly. The process can be reversed by run rotating the view in A and updating the references in B. I believe that the process you describe effectively does as much. It’s annoying and I don’t know why the world coordinates change when you rotate the viewport. Our office now avoids rotating views to prevent these issues. Netmetschek have had ages to resolve this very basic problem.

Art V, A useful tip, but we don't need to move the original coordinates. We would simply like to use the rotate view facility to work on source files without worrying about inadvertently breaking the references to every target file. We'd also like Vectorworks to reference reliably. These are two very basic functions that every user should demand.

Alan, Thanks for the advice. After much frustration I have discovered how to reset things through trial and error in the past, but I really don't think I should have to. Rotating a view should have zero impact on world coordinates and this still needs a big fix for the software to be fit for purpose.

I'm new here, but signed up as I finally found this thread which has reassured me that I'm not doing this to my own project files! I recently isolated the problem to referenced files, where these are saved in a rotated position in the source file. When you return to the target file and this updates, the referenced drawing ends up somewhere else. I wonder whether this has anything to do with Vectorworks trying to provide a different set of coordinates when in a rotated view (highlight in blue along the viewport boundaries). I run a small practice and we pay a large annual fee to Nemetschek to remain up to date. I have experienced these problems for over 2 years on a number of jobs, losing countless man hours opening and closing files, unrotating viewports, moving references back to their original positions and re-setting the user origin. I frankly can't believe that such a basic flaw in the Vectorworks software architecture can exist, and that it has done so for 5 years! Does anyone from Nemetschek even have the courtesy to read the forums and find out about user experiences and respond from a developer perspective? - I can't see any official response to any of the previous posts. I'm not going to waste our time learning to use any enriched BIM features when you can't even trust the file coordinates! If they don't solve this by 2019 I'm taking the whole office over to another platform. Is it too much to ask for a system that can reference and rotate as well as Microstation could 15 years ago?! You may be able to tell that I've just ended another afternoon of wrangling with this deficiency... [VWorks 2018 SP2, Mac OSX High Sierra]