Jump to content

David S

Member
  • Posts

    347
  • Joined

  • Last visited

Posts posted by David S

  1. Morning Mr Cadplan. I've often wondered how one can see what versions and graphics others are using because we fill that data in but I can't see it? I'm on 2019 SP2 Architect. I try for a bespoke watercolour effect so that our clients do not get distracted by photo realism when we are trying to get them to buy into the space and design we are creating. First off, any textures used I dumb down by exporting to Photoshop and adjusting the hue & saturation and re-import back. The windows are on Glass figured light blue. Ambient Occlusion on high. The render settings are attached....Other than that the real devil is in the detail! And the heliodon shadows of course. I can't take the credit for the render it was created for me by @Tamsin Slatter

     

    I have not included the bush which enabled the scheme to get planning for fear of embarrassing our local planning department because as everybody knows, common or garden bushes are really important to any design acceptability 🙂 

     

    I'm still none the wiser regarding the create roof rendering.  😞

     

     

    D

    renderset.JPG

  2. In previous iterations of the very helpful create roof tool it is possible to add components so you could effectively depict a thinner tile layer on top of roof rafters, AND enable the tile component to protrude beyond the eaves. However if you ungrouped the roof to redesign it the programme would assume every side of each sub roof face required this protrusion which is not the case, making for a very messy roof.After 3 years I re-attempted this operation today and pleased to discover this issue has been fixed, saving me hours of time in the future using 2 roofs to achieve the same effect.   However when I attempt to render the tile (only) element the entire roof renders (understandably) and when I try to render the component only which the programme allows you to do, the operation does not seem to work? Or am I missing something? The effect I'm after is in the roof images to the right (just got planning permission after 8 weeks of planning department hell involving us having to depict a bush! A BUSH ! This was achieved with 2 separate roof faces per roof) and the operations I have been describing are in the image to the left. Any feedback gratefully received. D

    roof 2.JPG

    129.JPG

  3. The single biggest (internal) benchmark is very simple: does this release make my client's workflow easier and quicker, and how? In addition, to recognise that your clients have files that have lengthy tenures (often 2 yrs plus) and that the introduction of advancement needs to take that into account because these files will have and will be. worked on. As a 3D designer the biggest impact in the last 3 years IMHO has been the clip cube and its associated ability to see the insides of a building and generate sections and elevations. Brilliant. So, for example (there are many but this is a good one) The slab tool now renders the "floor tool" as a legacy tool. I can see many benefits in the slab tool and use it when we can, in 3d. But we have been using the floor tool for years all over our files for many things including floors. TBH the slab tool is not anywhere as easily manipulable as the floor tool in 2/3D (see forum posts) so this makes it very frustrating and a constant concern in our on-going workflow. Often its easier just to start again. An example of a much wider issue: we need easily transferable AND better tools.  The benchmark should be make our workflow easier and quicker not more complicated! HTH   

    • Like 2
  4. @digitalcarbon Sounds amazing. so how come so many simple things never ever get fixed? I keep a log now of my bug submissions. It's sadly 2 years old and I'm still waiting. Unless I ask it disappears into the ether and my day to day business takes priority and I forget. I love my software, but I have a business to run. Most of our projects/workflow rely on a consistency tenure of 2 years, we have to work with what we've got,  so we can't just drop everything and work to a new standard/way we were not expecting to unless it actually works.  So frustrating.   We always upgrade but never before SP1. The bugs I have identified are big bugs which are preventing the software delivering simple things and what it says it should do.  We have a right to say this because we are not beta testers we are software pioneers: we actually want it to deliver. This is what I have wanted to say for some time.

    • Like 4
×
×
  • Create New...