Jump to content

Markus Barrera-Kolb

  • Content count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About Markus Barrera-Kolb

  • Rank

Personal Information

  • Occupation
  • Location
    Seattle, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It looks like collinear (colinear?) constraints only act on the centerline of wall objects. Given that one of Vectorworks' weak points, IMHO, is the difficulty in keeping multi-story building envelopes aligned – who here hasn't spent way too much time chasing down those horizontal lines between walls that somehow just won't stack perfectly? – it would be great to be able to apply the collinear constraint to walls based on specific wall components, rather than just the wall centerline. If all exterior wall types were exactly the same this wouldn't be an issue, but the fact is that almost every project has at least a foundation wall type and an above-grade wall type, if not more, and these are usually different thicknesses. This feature would allow you to make sure that, for example, the exterior face of the concrete foundation wall would always align with the face of stud above...
  2. Tom – totally agree with you. Without being able to have a single overview of the issue data where one can also edit & amend it, the system is just too unwieldy and cumbersome. And this should be completely separate from the title block and data field setup. Again, we're now using our own sheet-specific record fields for our issue data so we can manage it all using a worksheet – see attached. Works well for us, but it's regrettable that we don't get something like this 'out of the box'. Cheers, Markus
  3. Markus Barrera-Kolb

    Issues with Active Document / Window Selection

    I've encountered this as well, with the added gem of, on several occasions, having VW suddenly undo multiple drawings steps without the ability to redo them. Each time after this has happened I then noticed that the information displayed in the OIP referred to the other open project. Cheers, Markus
  4. Markus Barrera-Kolb

    Date in Title Block

    We're still using the Data Stamp (Dims/Notes tool set) within the title block definition (Layout) for this – seems to work OK. Cheers, Markus
  5. Markus Barrera-Kolb

    Surface Hatches not aligning with Renderworks Textures

    ...I can't imagine that the intent is for surface hatches to only align with their respective textures when in Top/Plan view rather than in a 3D view, or am I misunderstanding? Here's the file with an extrude I just created in Top/Plan view, with no H or V offset, and the hatch still doesn't align with the texture, regardless of the map type. I think this whole feature is either buggy as all get-out or insanely difficult to use correctly. Wish it'd get fixed! surface hatch alignment 2.vwx
  6. Markus Barrera-Kolb

    Surface Hatches not aligning with Renderworks Textures

    Thanks Alan, I've done that, and I often get misaligned surface hatches regardless of whether the mapping is set to auto or not. In the attached file, for example, it's set to Auto-Align Plane, but the Texture and Surface Hatch still don't align when you switch between OpenGL and Hidden Line rendering (let me know if you get a different result with it)...
  7. Is anyone else regularly having trouble getting Surface Hatches to align with the Renderworks Textures they're assigned to, in spite of them aligning perfectly within the definition? I'm getting all sorts of different results based on the object type (parametric, e.g. walls, generic solids, extrusions, etc.) and the Map Type (Plane, Auto-Align Plane, etc.). Only rarely do the geometries coincide as expected when switching between, say OpenGL and Hidden Line render modes. See the attached example with an extrusion – here the pattern jumps horizontally for me when switching between the render modes. This is really frustrating our efforts to go fully 3D and get both our 3D and 2D views from the same model, as one uses OpenGL or Renderworks, and the other Hidden Line... Cheers, Markus surface hatch alignment.vwx
  8. Markus Barrera-Kolb

    Help with a script to set Render mode & Projection?!

    ...weird, the workspaces are essentially identical – certainly both have these commands in their original menu positions – but I just loaded my home laptop's workspace on my work machine, and now the script works on both. Go figure! Thanks for your help & feedback everyone! Cheers, Markus
  9. Markus Barrera-Kolb

    Help with a script to set Render mode & Projection?!

    Kevin, et al, I'm confused – I was working on my laptop at home yesterday when I got the script to work with DoMenuTextByName (see below). Today I installed the identical script on my machine at work, also running VW2018 SP2 with the same workspace, and it refuses to run, giving an error message saying that the menu cannot be found. I have no clue what's amiss... Any ideas? Thanks! Cheers, Markus PROCEDURE PerspectiveOpenGL;BEGINDoMenuTextByName('Projection',5);DoMenuTextByName('OpenGL Render Chunk',1);END;RUN (PerspectiveOpenGL);
  10. Markus Barrera-Kolb

    Help with a script to set Render mode & Projection?!

    Thanks Kevin, your syntax for DoMenuTextByName did the trick! Now I can reliably switch from Top/Plan into my preferred 3D view even while inside a group! Cheers, Markus
  11. Markus Barrera-Kolb

    Help with a script to set Render mode & Projection?!

    Thanks JBenghiat, I gave this a try with no success (syntax copied below). Also, it seems like this function necessarily sets the view distance and crop dimensions, but I'd like to keep the ones that are already set prior to running the script... PROCEDURE ProjectionPerspectiveOpenGL; BEGIN Projection(1,11,5,-12,-12,12,12); END; RUN (ProjectionPerspectiveOpenGL); And the syntax I was trying with DoMenuTextByName was (I got these from Appendix H): PROCEDURE Perspective_OpenGL; BEGIN DoMenuTextByName('OpenGL Render Chunk',0); DoMenuTextByName('Perspective Chunk',2); END; RUN (Perspective_OpenGL);
  12. I'm trying to write a script using DoMenuTextByName in order to switch to a normal perspective and OpenGL. This is because VW seems to ignore the default render mode and projection when I switch to a 3D view while in a group, and at some other times as well. However, no matter what syntax and menu names I try (I've checked the constants for this command), I get errors saying the menu cannot be found. Any pointers? Ideally the script would then also zoom to fit objects. Thanks! Cheers, Markus
  13. ...I see this hasn't been addressed with SP2 (not that folks have been exactly clamoring for it). Would still be great though if we could set this boolean directly in worksheets; it would definitely make the new Title Block Border more usable for us.
  14. Please make it possible to toggle the 'This Title Block is Active' boolean within worksheets. Currently this is not supported, but it would make managing your active drawing set much easier, as you wouldn't have to navigate to every separate sheet layer, select each Title Block, and click on the check box in the OIP in order to change which sheets are in the current set. One worksheet, set the values there, and done! Thanks!
  15. Markus Barrera-Kolb

    Clip Cube: cut planes from the back of the model showing (ghosting) through

    ...looks like this one hasn't been fixed in VW2018 – I'm still getting these stray red planes from objects outside of the clip cube. Just submitted another bug report. ____________ UPDATE: my mistake! I was inadvertently modeling in VW2017. Opening the file in VW2018 (now SP1) shows the clip cube working great – thanks for the fix!