Markus Barrera-Kolb

  • Content count

  • Joined

  • Last visited

Community Reputation

4 Neutral

About Markus Barrera-Kolb

  • Rank

Personal Information

  • Occupation
  1. 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
  2. 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
  3. ...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
  4. 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)...
  5. 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
  6. ...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
  7. 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);
  8. 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
  9. 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);
  10. 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
  11. ...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.
  12. 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!
  13. ...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!
  14. Thanks Nikolay, that does display the revision information, however, none of the information here is actually linked to the data fields, doesn't update automatically, and certainly can't be used to update or enter revision information. It also doesn't give me any clues as to how I might be able to list the revision information in the revision fields separately in my own worksheet. Here's a screenshot of drawing set management worksheet we've developed for 2018, where we can enter most of the data directly and manage the whole set in one place with a complete overview. We use a boolean to indicate whether a title block is just a placeholder for a sheet actually provided by others, so that it'll show up in our sheet index, our own boolean that indicates whether the sheet is part of the current set (can be toggled right in the worksheet), and our own combined issue/revision fields, which can be entered directly here as well. It'd be great to be able to use the built-in system in this fashion, without having to click through individual dialogs for each sheet, but alas...
  15. Hello Nikolay, The Sheet Revision Log that the 'Issue Manager' (which really only creates a report – it doesn't help you manage your sheet issues) produces doesn't actually report any of the Revision Data fields, only the 'Current Revision' field for each Issue. Please see the attached screen shot. Again, when I try to display the actual revision data fields (as per the other screen shot of the Revision Data tab of the Title Block Border Settings dialog, all of the data for the individual revisions is strung together, per my post above. I think a real Issue / Revision manager would allow us to directly enter data in a matrix (presumably in a worksheet) with a single-view overview of the whole drawing set, rather than having to click through dialogs for each and every sheet. I'm ditching the built-in system and using our own fields within the Sheet Data form, allowing us to do exactly that. Moreover, we'll use our own boolean field for indicating which sheet is part of the current set, so that we can also toggle this from the same drawing set management worksheet rather than having to do this individually on each and every sheet layer & title block... Cheers, Markus