Jump to content

ColinW

Member
  • Posts

    145
  • Joined

  • Last visited

Everything posted by ColinW

  1. Got my vote. Hit this issue over the last week trying to replicate some historical windows, several hundred all different sizes (!). The diamond leaded glazing for hidden line renders is an extra challenge.
  2. Yes, I've seen the same behaviour. A bug has been submitted.
  3. Dave, file attachedtest render model.vwx
  4. 8:11, AMD Risen 7 7700, 64Gb Ram, RTX 3070 OC 8Gb, Windows 11 (£1,520 in 2023) 27.20, MacPro 2013 12 Core, 32Gb MacOS 12.6.4 (£4,000 in 2014)
  5. Windoor allows control of the architrave offset if you have access to it.
  6. PDF Squeezer on MacOS has been my go for years, it’s easy , quick and controllable. Oh, and good value.
  7. That’s disappointing, the Graphic Legends feature shows great promise
  8. The most straight forward work around is to use Windoor which allows more control of this. I do wonder what led to the 2 dimensions being one parameter, is this a ‘normal’ thing somewhere?
  9. Emily, Thats right, it's line control is just out of reach for now! good luck with your custom window symbol. Regards Colin
  10. It seems to use the None class, and as you noticed, doesn't appear as an option in the Window/Settings/2D visualization tab. If you don't already know, if you ever need to check these you can set up a test PIO and assign seperate classes to each category in the 2d visualization tab, then select and press Command+K, it will be converted to a group so you can then check which classes have been assigned to each part. Some groups will have a class from the visibility section of the same 2D visualization tab, so the sash swing is in a group by default in the visibility class 'Sills', but inside that group the swept arc of the sash is defined by the 'Swing' and is configured to use the class fill and line; the dotted rectangle showing the sash projection uses the 'None' class, but it's line and fill do not use the None class settings so it is preset as far as I can tell. Hope this helps (!), it's not very intuitive and the naming of the visibility classes is certainly misleading.
  11. It is surprising, I have found them really helpful. Thank you!
  12. If the window is controlled by a style, right click on the symbol defining the style in the resource browser, you will see the plug- in object options in the context menu. if it is unstyled, right click on the window PIO to get the same menu.
  13. Like Christiaan, I used to use NBS Building, that has now been replaced with Chorus which is too expensive for a couple of months use per year. The small version of Chorus doesn't use Uniclass and is too restricted for the work we get involved in, the medium and large scale versions are difficult to justify the costs for limited use. So now when we do write specifications, it is manual office standards.
  14. I usually model ridge tiles, the roof looks more realistic and of course they show in hidden line elevations and roof plans too. In areas with tight planning controls, visually appealing, accurate representations really help to sway the doubters. We have solar panels, surely ridge tiles can’t be too difficult. Space X, now that’s difficult!
  15. It excludes the sill which isn’t always what you might wish for. The worksheet can be modified so the reported height is a sum of the window frame height plus the sill height.
  16. Data visualisation is another good option if it is available in your version of VW, it can avoid creating variations of classes to control visibility. If you haven't used it already, it really is worth becoming familiar with it.
  17. I'm a Windoor user in the UK but signed up before the 'Windoor' closed!. It's a long time ago but I think it was proving too time consuming to support all the different requirements from around the globe. Whilst I like Windoor and use it almost exclusively, the answer rests with improvements to the window and door pios which are born out of a realistic and deeper undertsanding of the functionality required.
  18. This would be a very useful addition. OzCAD's Windoor PIO has similar functionality for the Aus and NZ markets so it should be acheivable with the built in Door PIO given the recognition that this an everyday requirement to comply with mobility access standards. No doubt the dimensions will vary around the world so control for localisation will be essential, similar to the stair PIO.
  19. Cinema4d has been marginally more consistent than fbx but both work well in most situations
  20. Ask the designer to export their file from VW into a dwg version compatible with your AutoCad version. VW can export to most dwg versions. It’s useful if they supply a pdf version of the file so you have a visual reference in case there are are any obvious issues with the exported file.
  21. If you've used the resource content they are probably assigned to a style, see image attached. If this is the case then to adjust the parameters which are greyed out in the information palette just select none in the style drop-down menu, that should allow you to adjust the other parameters. If you then want a new family of sizes based on this you can save it as a new style but don't set the variable parameters. to use the new style, just the elements you wish to be fixed.
  22. My 2020 installation doesn't have the Classic RAL Colours, it does list the Classic RAL Bonn 2019 version immediately below that on your screenshot. Wonder if it's and older palette? Screenshot 2019-09-24 at 14.10.02.pdf
  23. The actual opening dimensions also need to account for and extra mortar joint so it's not a pure module dimension either.
×
×
  • Create New...