taavilooke

Member
  • Content count

    35
  • Joined

  • Last visited

Community Reputation

1 Neutral

About taavilooke

  • Rank
    Greenhorn
  1. Hi! Is there any way to choose how custom sash windows are displayed in 2D plan view? I have windows with multiple columns and 2 rows of sashes and the openable sashes are always in the lower row. It seems that VW only displays the openable sashes in the upper row, in the example below the openable sash does not show up in the plan view at all. Is there any way to fix that? I tried playing around with the options in the window setting and also the layer cut plane, but it did not change anything. Thanks, Taavi
  2. I got in touch with the local support and figured out a solution for one of the problems: It is possible to add line breaks to worksheets as carriage return characters ("\r") and they will show correctly if Wrap text checkbox is checked in the Format Cells dialog for this column. Does anyone have recommendations about the hatches and world units? Is it possible to scale the hatches inside viewports in any way, to allow creating drawings in different scales?
  3. Thanks! That did the trick.
  4. Hi! I'm using scripts to write data into worksheet database cells with Runscript() function. Every time the worksheet is updated a dialog shows up that asks if the execution of the script should be allowed or blocked. I accidentally clicked on block all. Now the the dialog does not even show up and none of the scripts run in worksheets. How can I re-allow or unblock scripts to be run with Runscript() ? Thanks, Taavi
  5. That was actually quite easy. This script will output all the wall or slab component names and widths to one cell. It is run with =RUNSCRIPT('ScriptName') in the worksheet header. There is a weird problem though: all the components are on one line when the worksheet is place on a sheet layer. Any thoughts how to fix that? EDIT: the line wraps work if the line break character is "\r" and Wrap Text is check for this column. See the next post. wallObj = vs.WSScript_GetObject() (a, numComp) = vs.GetNumberOfComponents(wallObj) comps = [] for x in range(1, numComp+1): name = vs.GetComponentName(wallObj, x) (a, thickness) = vs.GetComponentWidth(wallObj, x) comp = name + " " + str(thickness) comps.append(comp) str = "\r".join(comps) vs.WSScript_SetResStr(str)
  6. @JMRI actually figured out an even better way. In the Format Cells > Images dialog you can change the Image Type to Thumbnail. Then you get an image of the same length in the same scale for all the walls. It even works for slabs as well, you get a section of the style. There is a weird problem though: the worksheets mess up the scale of the hatches that are set to page units. The hatches are way too small for the rest of the geometry. It seems to display these hatches as if they were in 1:1 scale. Does anyone have an idea how to change that? For the component list, I'll try to create a better solution that would list all the components automatically in one cell.
  7. Aren't we talking about different things? I want to make a schedule describing styles (see the image that I attached). Now we are placing a piece of the wall into the model space and making a viewport out of that. That at least saves us the hassle of redrawing all the styles, but we still have to add the text by hand. But since we have about 90 different wall styles in the project, it is a lot of work to update the annotations if we change something.
  8. Hi! Does anyone have recommendation how to make automatically updating wall and slab style schedules? Yes there is a default schedule for wall styles, but that doesn't really do all the things that we need. We are doing it manually at the moment, but I'm wondering if there's any way to automate it. I need a schedule that includes at least an image of the style as it would appear on the drawings (short section of the style in 2d plan view with hatches in the right scale). I can put an image of wall styles in the schedule (but not slab styles), but the hatches are not scaled right and it doesn't look like the walls in the drawings. a field describing all the component names and thicknesses in the wall/slab Has anyone tried making anything like this? At the moment we are manually placing a section of all styles somewhere in the model and creating viewport of them to annotate and place them on the drawing. I'm wondering if there is a way to automate this or is it better to do it through worksheets. Can more detailed images of the elements be placed in worksheets somehow? For the components I imagine I have to write a short script to extract all the information? Thanks, Taavi
  9. The issue was that in some cases if components are assigned to classes, VW will only export some components of the wall to IFC and others go missing completely. Also when combined with offset wall component heights, the class (IFC layer) of the PIO object is replaced with the class of the first component. I attached the test file that I made, that has 4 walls (with and without component classes, combined with component height offset). I submitted it to Vectorworks through VSS, but as usual I haven't gotten a response about that. In general exporting walls to IFC worked okay, as long as you don't use component classes or wall caps. Wall features and component offsets mostly worked, but needed jumping through some hoops. seinte_komponendid.vwx
  10. Do the wall component classes help with the wall finishes in any way? Or is it just a general tip? We were assigning components to classes earlier, but in some cases it seemed to mess up the IFC export and we had to forgo that. That was on 2017, so it might be fixed now, I have to check. This is annoying, in Revit-land there are some much more appropriate tools for defining finishes.
  11. Could you explain that a bit more in detail? Do you mean I should assign the wall to a different class based on the finishes?
  12. Hi! I find it difficult to model finishing layers (components) for wall. Sometimes the finishing layers are up to a few cm thick and should be modelled for accuracy. However when the same wall construction can have different finishes, it can get complicated really fast. If I model the finishes as separate walls, I have to duplicate all the openings in the walls as well and keep then in sync when I change the wall itself. If I put the finishing as a component into the wall type, I will end up with many duplicates for the same wall style (wall type without any finishes, with plaster on one side, with plaster on two sides etc.). Are there any good principles to get around this problem? Is there another way that I'm not seeing? Regards, Taavi
  13. My impression was that that the symbol definition has to have a tag. Then it will export as one element/component. Otherwise the behaviour was inconsistent. Also, I could not find any way to export solids and symbols into IFC so that they would have subtags (like the way walls decompose into components or curtain walls into plates and members). For the other things I don't have much experience with those.
  14. In the Default library at Reports_schedules/Architectural Reports.vwx there is a worksheet Objects without IFC Entity that lists all object without an IFC tag attached. There you can right click on the row header (the gray color thing on the right with the worksheet row number on it) and click Select item. This is only useful for solids, autohybrids and some PIOs that cannot be styled (railings and stairs). Adding data to windows, doors, symbols, walls and slabs should go through the Resource Browser.
  15. It would make a lot of sense that all objects would have some IFC type attached already (like IfcObject). Then they you could see that something some data is missing or erroneous and make the appropriate changes. At the moment these objects just do not appear in IFC and unless you intentionally look into it, no-one will find out that something is missing. The workaround that I found is to make a worksheet that looks up all symbols without an IFC type attached... Also, weirdly, if I assign the type IfcObject to an object, it does not show up in the export at all.