Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by line-weight

  1. Try re-snapping them to each other, and check they are exactly aligned above one another.


    There shouldn't be a line there but VW doesn't always behave 100% reliably in removing it.

    • Like 1
  2. 1 hour ago, drelARCH said:

    Hi @line-weight i iust checked it and it works same way for styled objects. Unstyled you control trough context menu.

    It took me quite some time to understand and navigate through all these settings but really worthy... for instance class assignment is really big one ... great time saver with organization of objects.



    I think I'll have to come back to this next time I'm setting up a window style. The multiple settings locations are very confusing.


    For example, I haven't got my head around why there are two sets of settings for a window style. If I look at the window style in the resource manager, then I can either choose to "edit" which brings me to a dialogue box of settings called "Window Style" with my window style name at the top - or I can choose "plug-in object style options" in which case I get a dialogue box called "Plug-in Object Style Options" but this dialogue box has no style name in it - so what am I actually setting here? Am I still adjusting settings for the "window style" or is the "plug-in object style" something different?

    • Like 3
  3. 7 hours ago, drelARCH said:

    You can make it by style. You have to select your styled window/door in RM and then under 'Plug-in Object Options' set to settings you prefer: insertion location, offset, wall closure etc.


    This works for 'standard' VW doors & windows, but not for the new Windoor doors & windows - have I got that right?


  4. 36 minutes ago, Mark Aceto said:


    You just reminded me of something. I have this issue with the LED video screen object in both v2021 and v2022. When I'm zoomed in, it looks great. But when I zoom out, it looks like your example above. That to me sounds like a VGM LOD issue (lower res for objects further away). @Josh Loy what do you think?


    Yes I think it is. I already saw it in 2021 but only when using "narrow perspective" for a kind of telephoto view of something. In 2022 something has changed and it is happening in "normal perspective" views.

    • Like 1
  5. 49 minutes ago, Julian Carr said:

    You can select multiple WinDoor/Window/Door instances, then right click on one on the selected objects, choose Plug-in Object Options, turn on Use Wall Closure and it will be applied to all selected objects.

    Ok, thanks.


    I don't understand why this can't be set by style and/or in the OIP box, but in any case I think it needs to be made clearer on the VW help page, because it says this:




    You have to read the green text very carefully to understand that you need to go to the "plug-in options" dialogue, and not to the "Wall closure" button on the OIP to get things to work:




    Because that's where most people will expect to find settings that apply to a particular object.


    I bet that 90% of Vectorworks users who want to try this out will spend quite some time fiddling with wall closure settings in the Wall and Window object OIPs, find that they have no effect, and give up or assume something isn't working.


    • Like 1
  6. @Julian Carr thanks very much for that video - I would not have managed to get anything working without it.


    A critical point is that you have to turn on wall closure for the individual window instance, and you have to do it via "plug in object options".


    As far as I can see, this is not explained in the most obviously relevant help page:




    Doesn't this need to be made clear in here?


    I don't really understand why I change this setting in this separate dialogue box, rather than the OIP for the window instance, which would seem more intuitive.


    Also, do I have to go round every single window and change this "use wall closure" setting? I can't choose it per window style, for example?



  7. On 9/15/2021 at 6:28 PM, EAlexander said:


    I have to dig deeper, but at first glance - SHADED (formerly OpenGL) gives me a lot of lines and hatch artifacts (there is NOT overlapping geo), but as I zoom in more, it clears up.  Haven't tried this yet in a Viewport, but I hope I can sort this as screen grabs of wide views to send to my designers is my all day every day 🙂








    I see big problems with this in VW2022 too. It might be helpful if you could report this on this thread to increase the chance of something being done about it:




    Changing the "crease angle" improves things a bit but it doesn't make the problem go away. It seems to be worse in more complex models. And is present in perspective but not orthogonal views.

  8. Is it on a single line path or a polyline?


    When you have a single line, you can set a different elevation for each end.


    When you have a polyline, it has to be level.


    So if you want it to follow a non-straight line on sloping ground, you have to make each section individually and manually adjust the elevations of the ends of each to match its neighbours.

    • Like 1
  9. I agree it's not really good enough that you have to add detail in 2D linework (which has to be manually updated at every revision), in a "BIM" workflow.


    Have a look at the approach explained at the end of this thread


    I still want to look at this more closely to understand how it works but in principle there might be a way of using this type of method to get your overhead lines.


    • Like 1
  10. Hm, here is my test on what is a fairly complex file (some quite complex geometry rendered as a glassy material).


    Left - renderworks (my custom settings) - render time 4:32

    Middle - redshift (default 'exterior final' settings) - render time 16:44

    Right - redshift (settings adjusted so that ambient light is on, and 16 rather than 4 bounces, which matches more closely my custom renderworks, and some adjustments to light intensity) - render time 24:25





    An enlarged portion of each version:





    Of course I would have to fiddle with the settings in redshift more, to get something closer to what I want. I can see that perhaps it is picking up some complex internal reflections more than renderworks does... but it is at a high time penalty, with the redshift renders taking 4x and 6x as long as the RW one.

    • Like 3
  11. There are two major (for me) issues that mean I can't use 2022 as it stands.


    Firstly this one makes my primary mode of interaction (openGL/shaded view, perspective, draw edges) unusable thanks to wildly flickering artefacts.


    Secondly this one means that I lose important visual cues in shaded mode that my workflow relies on. It's been recognised as a bug so hopefully will get fixed.


    Then all the other changes that could have been good seem to be compromised:

    - redshift is there but appears to offer no advantage over renderworks at all

    - twinmotion direct link is nice but bugs in the datasmith import process that have been present since it was introduced, are still not fixed

    - wall component wrapping is very welcome, as is Windoor...however, as far as I understand, we can't use them together, so it's not possible to realise the benefits of both.


    So I don't feel too positive about VW2022 right now. Maybe future SPs will change things.


    Perhaps if it weren't for some of the above problems, I'd have spent a bit more time using VW2022 and enjoyed some of the general improvements mentioned. Perhaps some annoying general bugs have disappeared. However, I've just successfully replicated problems with the push-pull tool that have existed since at least 2017 and have supposedly been logged as bugs. This is one of those general-use bugs that doesn't make VW impossible to use, just frustrating. There are others which I've not tested yet but my guess is that many of them still won't have been fixed.

  12. On 9/16/2017 at 4:11 PM, line-weight said:

    This is a continuation of an issue that I was already having in 2017. Mentioned in a couple of threads by me and others previously without much response.


    Essentially: the push pull tool (a) struggles to select faces, (b) fails completely to select faces, or (c) causes a freeze with spinning beachball when there are moderately complex objects in the drawing.


    As far as I can work out, it happens as soon as one of those objects is behind whatever face you are trying to select.


    This has been a big problem in a drawing where I had a few imported symbols (from BIMobject and elsewhere). It became impossible to use the push-pull tool to edit simple objects in the drawings, unless I hid all of those complex objects. To make sure this isn't a problem specific to that drawing file, I've created a new and fairly simple one in VW2018. If anyone would like to see if they can replicate this, here is what I did:

    - new blank file.

    - go to BIMobject download. I downloaded fairly much at random a server unit casing, in SKP format. If you type "sr25ub" into the BIMobject search bar you should find it.

    - I placed two of these units next to each other

    - then I drew a simple extruded rectangle, sitting next to them. See screenshots below.

    - one of the screenshots has a viewpoint with the extruded block to the left. using this viewpoint, the push-pull tool will select any face on the white block easily and correctly, and function as expected.

    - however - the other screenshot has a viewpoint with the server units hiding behind the white block. using this viewpoint, the push pull tool struggles to select the face of the white block at all, and I get freezes and spinning beachballs.


    This doesn't seem like an overly complex drawing. My machine specs are posted down below. It's a refurbed/upgraded mac pro.


    I've attached the drawing file too.







    I can also replicate this problem (posted in 2017) in VW2022. So, again, not fixed.

    • Like 1
  13. On 3/12/2021 at 8:36 PM, line-weight said:

    I have isolated two walls into a single file. The file is attached. There's one saved view which should replicate what you see in the screen recording below.


    I'd be interested if anyone could replicate the troublesome behavior of the push-pull tool you can see here:



    PPT.vwx 74.43 kB · 9 downloads


    Having just tested this, it seems not to be fixed in VW2022 as I can replicate it exactly.

    • Like 1
  14. 1 hour ago, zoomer said:

    - sometimes when I want to draw an Arc in Extrude Edit Mode, it shows only a Marquee

      where I snap but draws the Arc several meters away outside my Screen Area




    I have not tried to do much 'real' drawing in 2022 yet - but I was quickly able to reproduce the above by:


    1. Draw rectangle

    2. Extrude rectangle

    3. Rotate extrude by arbitrary amount

    4. Enter extrude edit mode

    5. Try and draw arc


    One thing that I have noticed happening in 2d (but on sheet layers) is that if I scale a viewport by x,y% it scales to the new size but appears at a new location on the sheet, offset from the old position.

    • Like 1
  15. @Jesse Cogswell how do you find render times compare?


    I had got the impression Redshift would let us produce renderings that weren't quite as good as full renderworks, but could be done much more quickly.


    This is what it says on the promo page



    Every designer seeks to optimise their time when designing, and what better way than through our fastest rendering option yet. In partnership with Maxon, Vectorworks 2022 introduces a new GPU-accelerated mode called “Redshift.” Redshift speeds up rendering time without sacrificing the quality of your design by using features like lighting, reflections, volumetric effects, camera effects, and anti-aliasing.


    But my limited testing so far indicates that Redshift takes much longer.

  16. On 9/16/2021 at 9:45 AM, line-weight said:


    Hello @Dave Donley


    It's good to see that VW2022 has a direct link to Twinmotion, which will make it a lot more useful.


    Are you able to update us on whether the various bugs have been fixed in VW2022?


    Having had no response to this I thought I'd try things out.


    I think that some things may have been improved but within a few minutes of testing, I find:


    - VW glass material is imported as opaque.

    - I can override that with one of TM's glass materials, and that works fine...

    - until I try making some edits in the VW file, click the update button, the TM scene updates with the geometry changes  but the glass material reverts back to the wrong, opaque version.


    NB the edits I made were nothing to do with the glass object, they were edits to other objects in the model.


    So, still not practically useful for me. Ho hum.

  17. Well, i often grumble that we are asked to submit bugs when all the info is laid out already in a thread like this.


    Nonetheless I thought I'd try submitting a bug for this issue - partly to see if it actually caused anything more to happen than when I report something on the forum here.


    I just spent 15 minutes of my own time doing this, preparing and uploading a sample file, filling out all the fields in the form, describing how to replicate step by step, and so on. Then I press submit, and the form deletes everything I've just written, giving me an error message relating to the number of digits in the serial number I entered.


    So that was a waste of my time and I'm not going to type everything out again.


    Maybe if any Vectorworks staff are reading this thread they could acknowledge the issue.

    • Like 2
  18. 21 minutes ago, zoomer said:


    I think it "should" do the same in VW 2022.

    As it works for your extrudes.



    I can get my Walls white when I switch OIP Render back to "by Object"


    And I tested Shaded without Textures but Color on.

    And I can confirm that it will show Class colors for many Object Types - except for Walls ....

    (Maybe more Types ? But my Columns look OK)


    Thanks for the confirmation.


    It does seem it's specific to walls. I've just tried with a slab object, for example, and it behaves as expected.

  19. I'm also trying to figure out whether Redshift is any use to me. First experiments aren't promising - I have compared render times and results on some viewports in already existing files. The "renderworks" settings I'm using are custom ones that I have tweaked over time to get the results I want, but they are effectively "final" quality ones. These are essentially exterior renderings:


    Rendering A - quite a lot of glassy/reflective/transparent material - time to render:

    Renderworks custom final quality: 1:51

    Redshift "exterior fast": 2:41

    Redshift "exterior final": at 5:00 it was still going and appeared only to be halfway through.


    Rendering B - pretty basic materials without reflections, transparency etc:

    Renderworks custom final quality: 0:15

    Redshift "exterior fast": 0:20

    Redshift "exterior final": 2:15


    So the Redshift renderings seem to take significantly longer than the regular Renderworks ones. The images they produce are notably inferior to the RW ones. The comparison may not be entirely fair because of course, I could probably improve the quality of the Redshift ones by fiddling around with settings for a while. But I don't see why I'd bother doing that if they are even slower than RW to render.


    I may be missing something.

  20. 1 hour ago, zoomer said:

    Sorry, I meant my Renderworsk Materials.

    All set by Class and Components for PIOs.


    Ok - as in your Renderworks Textures?

    So you choose what texture each wall component has by class, and render the wall "by component".


    This works for me, if I have the wall components set to classes which have textures.


    However, the problem is when the class has no texture. So, say I have a class called "red fill class".

    Under its "graphic attributes" I set its "fill" like this:



    But then under its "textures" I assign no texture, like this:



    In previous versions of Vectorworks, this would result in the wall component in OpenGL view being shown in the "fill" colour.


    In VW2022 this seems to result in the component just being shown as white*.


    In other words, if I want to control the appearance of a class-controlled wall component in "shaded" view, then I have to assign a texture to it, rather than just a fill colour.




    *in fact, further experiments show that it will not always default to white, but to some other fill colour that I previously assigned to that component when I gave it a "fill" attribute directly, and not controlled by class.




    • Like 1
  • Create New...