Tom W.

Ha ha good! Out of interest when you say 'how do you turn off Light objects or the Grid when rendering', neither will display in viewports, or if you render direct from the design layer for that matter, so don't have to be turned off... But I guess you just want to view the scene as realistically as possible before creating the VP?

Quick prefs: Or 'Show Grid' check box in Grid Settings (on status bar at bottom of screen):

I believe you can use Wall Closures with WinDoor however my problem with WinDoor is that you can't class the interior/exterior separately in order to have one colour outside + a different colour inside, + likewise the threshold has to be the same class as the frame so again can't be different colours/textures. Unless someone knows different although I did post about this over a year ago + no one said anything to the contrary...

I think I tried it as a single Window object initially: it looked fine externally But not internally Because you want to show a pair of abutting jambs at each mullion: What I ended up with was my own hybrid symbol placed in an opening made by an uncased Door inserted in the Wall. This was because I was using Wall closures + wanted a shim gap: these are both provided by the uncased Door opening then the Velfac window is just placed inside it. In an earlier version of the model before I introduced Wall Closures I think I had three Window objects side by side but this resulted (I think) in lines between them in Top/Plan which didn't look good so I think at that point I grouped the three windows + inserted them in a separately-made opening. Why I then converted the grouped Windows into a dedicated symbol I can't remember but there must have been a reason! I think perhaps initially I didn't have the separately-made opening + just inserted my triple-window symbol directly in the Wall + applied the Wall Closures to it but then realised I needed a shim gap which necessitated doing it the way I ended up doing it...?

I use the VW Window tool for my Velfac windows. They are plausible enough for my purposes:

According to the posts that seems to fix it albeit temporarily. I have not experienced it myself thankfully but seems plenty of others have...

There have been a few threads about this kind of thing see this from yesterday..:

Yes I created a Wall style called 'Default Wall' as a surrogate unstyled Wall. It's a simple single-component Wall I use for concept modelling or anywhere where what the walls 'are' doesn't matter (I have a 'Default Slab' style + 'Default Roof' style as well). It has a thickness of 230mm but 9 times out of 10 I immediately change this to something else in the preferences which turns it into an 'unstyled' Wall anyway... If the Wall has a component the thickness needs to be edited in the Component Settings. If it doesn't have any components you can edit the thickness directly in the OIP.

Cast your mind back to 2007 Christiaan... 🙂

I have thought this for a while + today finally decided to post on the Wishlist about it + found this 20 year old post... I found lots of other later posts as well + the advice every time was to use Styled Walls. I do use Styled Walls in most cases but not when I'm modelling existing walls in old buildings where the thickness varies so much: I have a Wall style I use but I set the thickness each time in Preferences + so it becomes unstyled. It would be really useful to be able to edit the thickness of a wall instance + have it resize from one edge or the other rather than always from the centre. Given this wish has attracted a grand total of zero votes in 20 years I can't imagine it's going to happen any time soon but thought I'd get it off my chest all the same 🙂

The object in the video is a Rectangle which looks to have an Image Fill applied to it. These scaling methods will resize the Rectangle but not the Image Fill. To do that the resource itself needs to be edited, either in the attributes palette or the resource manager. Or extract the image from the Image Fill + import it as a bitmap which then you can resize in all the ways described. When you import an image you have the choice to import it as a bitmap or an image resource or both. A bitmap is what you want in this case. An image source will create an Image Fill which you don't want.

You can use class overrides on the container class i.e. if you turn off the components manually or by setting the Detail Level to Low to reveal the component-less wall behind. And if you leave the components visible you can override their attributes using Data Vis.

This is a Rectangle you've applied an Image Fill to...? I think the assumption was it was an imported bitmap...

Are they 2D only or hybrid symbols? Have no idea if that makes a difference. In my case my whole computer seems to groan under the strain caused by the legend... I sent an example file to @Josh Loy but not heard back

@Matt Hall another thing you can do in the same vein if you're using Materials is have the Data Tag return the 'Product Name' + (if you want) 'Product Description' + 'Manufacturer' data fields for the Material used by each component. These are the formulae: #WS_MATPROPERTYBYNAME(COMPONENTMATERIAL(1), 'materialproductname')# #WS_MATPROPERTYBYNAME(COMPONENTMATERIAL(1), 'materialproductdescription')# #WS_MATPROPERTYBYNAME(COMPONENTMATERIAL(1), 'materialmanufacturer')# This is great because you don't have to manually input component details across multiple Wall/Slab/Roof styles (I have a Wishlist item somewhere for being able to import/export components between styles...). You just set it up once in the Material then can use it across all your objects. However the major flaw in this is that it doesn't work on Compound Materials. I seem to remember posting a wish about this too... and here it is... The alternative then is to return the 'Description' + 'Mark' fields from the Compound Material using #WS_MATPROPERTYBYNAME(COMPONENTMATERIAL(1), 'materialdescription')# + #WS_MATPROPERTYBYNAME(COMPONENTMATERIAL(1), 'materialmark')#. Just some extra options to play with. Prior to Materials the only way was to use #WS_COMPONENTNAME(1)#.