Jump to content

Gilbert Osmond

Member
  • Posts

    120
  • Joined

  • Last visited

Posts posted by Gilbert Osmond

  1. 5 minutes ago, digitalcarbon said:

    I made this a long time ago and it was very very very involved.

     

     

    Right... that's why I was hoping there was some way to just do a magic text label that could be applied as a a "wrap" or "send to surface", behaving exactly like a Texture Bed ... but retaining its characteristics as a fully-editable normal text field...

    • Like 1
  2. This seems relevant to this topic --

     

    In VW Designer 2023, is there any way to actually wrap editable text labels directly on a 3D surface such as the outside of a pipe?

     

    I know this can be simulated using Textures but that's a round-about way which doesn't allow easy, direct editing or arbitrary drag/drop movement of the resulting label. Textures are really optimized for repeating patterns, not single label locations...

     

    How do I do a label that looks like this... but is in fact fully wrapped / placed on the 3D outer surface of the pipe, not just "hanging in space" as a planar text label that doesn't show correctly when changing 3D perspective?

     

    ScreenShot2023-05-27at8_35_57PM.thumb.jpg.b0a44c546bd5d5daba80fba162af2114.jpg

     

    ScreenShot2023-05-27at8_36_38PM.thumb.jpg.02ed7c48889aae381b61ff2f0419ba19.jpg

     

  3. This is a massive thread necro, but I'm posting it anyway because this discussion appears close to the top of current (2023) google search results for "vectorworks viewport crop not working."

     

    Be sure that what you are trying to crop is in fact on one or more design layers.  In my case, for various other reasons I had carefully traced out quite a few 2D design layer objects (building outlines, parcel outlines, etc.) as viewport annotation objects.   Viewport crops do not apply to viewport annotation objects!  

     

    I burned half an hour trying everything else (checking class visibilities, viewport object types, viewport & sheet naming conflicts, etc.) until I finally realized --- DUH! -- that what I was trying to crop out was objects in the Viewport Annotation itself.  I just needed to delete the unwanted Viewport Annotation objects (outside my desired Viewport Crop area) to realize that viewport crops had been working fine / properly all along.

  4. Actually, nevermind, I think I figured out my problem.

     

    I had attempted to add Record data to the raw object instances within a Viewport Annotation -- so the objects themselves did have Record Data associated.

     

    But there was no Record Data attached directly to the original 2D symbols themselves.

     

    Since I was using the symbols as the data source for the Graphic Legend, there was no data to pick up.

     

    By properly attaching to & editing the field values for the Record Data on the 2D symbols, Graphic Legend now works as-expected.

    • Like 1
  5. I am trying to create a graphic legend, using a few simple 2D symbols, to which very simple 2-field Record Formats have been applied.

     

    When I go to edit the Cell Layout for the Graphic Legend and create a "dynamic text" item, when I select the symbol's Record Type & Field and try to create a dynamic text component as part of the Graphic Legend cell layout, the Graphic Legend appears to simply ignore the item entirely. It doesn't show up at all in the layout, even as an empty place-holder.

     

    When I change the data source for the dynamic text item to be an Object Function (such as "Area"), then everything works fine.

     

    Is this a bug, or am I doing something wrong?

     

    Note that the Cell Layout is identical in both examples.

     

    Here's the PROPERLY WORKING example:

    2023635721_ScreenShot2023-03-13at2_42_28PM.thumb.jpg.40a71043ef496b0e22a9140b9d3675fc.jpg

    1982223693_ScreenShot2023-03-13at2_42_46PM.jpg.1863c0503cf575ed8e3cb6c0591cb8b1.jpg

     

     

     

     

    And here is the NON-WORKING example:

     

     

     

     

     

    596385184_ScreenShot2023-03-13at2_43_45PM.jpg.896efc7a6518bc427b868a1cab25aaa7.jpg

     

     

    Screen Shot 2023-03-13 at 2.43.25 PM.jpg

  6. @Bruce Kieffer, thank you very much for posting the .vwx file for that. It's exactly what I needed, I was able to resize it in one direction by dragging & then just duplicate it along the other axis to get the full dimension of the piece I needed. Then applied a water texture to it which was sufficient to give it a good-enough approximation of the translucency of the sheeting.

     

    Regards & thanks

  7. Replying specifically to the "Mac Mini M2 better?" question, based on the MM M2's specs, it's only an incremental performance bump, not a step change. So, only incrementally faster.  

     

    Not sure whether someone's later reply concerning a Mac Mini M2 possibly throttling (due to heat) on a long render vs. a Studio is on point. Has anyone tested this head-to-head? Seems to me the M2 architecture in general is vastly more efficient than the prior bloated Intel junk, so that heat buildup on long renders may not be an issue? 

     

    ----

    Overall I think that for the majority of VW of users, the current gen. of  M1/M2-based hardware is getting close to "good enough," and "fast enough," I.e. there comes a point in photorealistic rendering when the resolution, lighting, level of detail etc. is approaching the max reasonable limits of human perception, beyond which there is no need to go. Dep. of course on size & complexity of the models. 

     

    Sort of the way smart phone camera tech has ramped exponentially over the past decade, and it's getting to a point at which there are only incremental gains left to be extracted, not massive step-changes in quality / usability.

    • Like 1
  8. 7 hours ago, markymarc said:

    Any update on this Gilbert ? 

    Cheers

     As it turns out, I cancelled the M1Max 10-core / 32GPU core / 64GB and went for a lesser-spec'ced M1 Pro 16" Macbook with 32GB RAM. It's not due to arrive until mid-late Dec. My reason for going lower-spec was that after reading an Anandtech deep-dive on the M1 Pro vs. Max CPUs , it became clear to me that there's hardly any difference in single-threaded performance between these CPUs. It's only in very intensive multi-threaded and/or GPU-intensive workflows that an M1Max is justifiable.  For my needs, the step-up from a core i7 2.6Ghz to an M1 Pro / 32GB  ram is likely to fill my needs for at least 3-4 years.

    • Like 2
  9. 26 minutes ago, dtheory said:

    I'd snap up a Mini with an M1 Max and 32-64GB RAM in a heartbeat..  my M1 Mini (with Monterey) has been so great, I'd love to see what even more headroom could do..

     Unfortunately that probably won't ever happen as it would severly undercut Apple's high-end price points on the new M1Pro/Max Macbook Pros while also pushing the Mini in the wrong direction (from Apple's perspective) toward the performance tier(s) of forthcoming MX-powered Mac Pros.

  10. M1Max has 10 CPU cores, 32 GPU cores. I went for the 64GB RAM option. 2021 MB Pro 16". Looking forward to seeing how some of my more complex models run on this, compared to my 2019 MB Pro 2.6Ghz core i7 / 16GB RAM.

  11. Is anyone else getting a "Product update check failed.." error when manually selecting Vectorworks --> Check for Updates in VW 2021 SP4.1?

     

    I know my internet connection is working fine. I'm thinking maybe it's a temporary server glitch on Nemets / Vectorworks side because other updates (for example Resource updates) are working fine, and my recent update to SP4.1 a couple of weeks ago also worked fine. I did already try rebooting my MacBook Pro & the problem persists.

    Screen Shot 2021-10-01 at 10.13.27 AM.jpg

  12. I'm experiencing this exact same issue. I'm trying to do a simple Taper Face on a plain rectangular 3D solid. Some faces can be tapered normally, but others -- in this case, the face I want to taper -- cannot. The OIP shows Extrude - Locked. I've tried Unlocking the object multiple ways, to no avail. I think this must be some kind of bug because I never had this problem tapering any face of a simple rectangular solid in the past.

     

    I'm using VW2021 SP4.1 under OS X 10.14.6.

  13. 9 hours ago, Jesse Cogswell said:

    Glad to hear that this worked.  ....

    ... It's less complicated than what's above but still not all that intuitive.

     

    This is fantastic work. If you accept donations via cryptocurrency or some other online tips platform, consider posting it so I can compensate you for what this is worth to me. At least $50 USD.

     

    Thanks again & I look forward to ongoing refinements time-permitting.

    • Like 3
  14. 1 hour ago, Jesse Cogswell said:

    I could write a script...

    ...Let me know if this works for you or if this totally breaks something.  It worked in my admittedly brief amount of testing on VW2019, but there's no reason it shouldn't work in VW2021.

     

    I just added this to my Resources in VW Designer 2021. An initial test shows that it works pretty well. Thanks very much,  learning to program with Vectorscript exceeds my time/attention budget for the forseeable future.

     

    609111276_ScreenShot2021-06-08at9_45_15PM.thumb.jpg.7aa65c0cbb56bd7b31290c741e631123.jpg

     

    475602813_ScreenShot2021-06-08at9_45_34PM.thumb.jpg.72b7236a3b405bf8b4efd1ee3b3ea417.jpg

     

    317563112_ScreenShot2021-06-08at9_49_05PM.thumb.jpg.11d1b405857b1f3d04d76a3e6ac74fb8.jpg

    • Like 3
  15. Just now, Benson Shaw said:

    Not sure if this accomplishes anything desired, but ...

    The vwx site model (DTM) from 3d loci produces a point to point perimeter, plus the interior topography. If the raw data is somehow delimited, eg if provided with separate layers or classes for roads, beds , creeks, paths, etc, then a separate DTM for each will produce separate perimeters. 
     

    and contour interval adjustments might be useful in some way for this 

     

    -B

     

    That's an interesting round-about way to achieve a similar result. I wonder if it would work for "1-dimensional" site models, i.e. where the "site model" is just a single  line of points with no width (i.e. no cross-slope area.) Maybe I could use this to create 2D figures and then just convert the site model  (in 2D plan view) to lines, and throw away the site model. Roundabout method...

  16. Not sure if any do. I am not a licensed surveyor but I do a fair amount of informal surveying using GPS equipment to capture client landscapes. The workflow is easy -- shoot points, download a .CSV file of coordinates, import it into VW, and it's ready to use  -- just need a way to connect dots semi-automatically to expedite linework.

  17. Maybe there's some plug-in or 3rd party script that will turn up to help me do this.

     

    As a CAD platform that aspires to be survey-ready I find it hard to believe that VW doesn't include this feature as part of its basic functionality.

     

    The very nature of survey work is point collection, and it's frequently thousands of points, many of them marking out non-rectilinear 2D features such as paths, roads, irregular garden beds, etc.

     

    I spent nearly 1.5 hours since I first posted this question here, laboriously clicking from point.. to point.. to point.. to point.. to point... with the Polyline tool.. to connect over 2,400 roadway survey points from raw survey data that were imported as 3D loci.

  18. 23 minutes ago, Boh said:

    I use the 3d polygon tool

     

    I know how to use the polygon tool to draw lines by hand.

     

    What I want to do is select a group of 3D loci (in this case, a roadway alignment from a survey I just imported) and have Vectorworks automatically connect all the points with a polyline or NURBS curve. If there was a menu command "Connect Points into Line..." I would use that but as far as I can see there is no such command or anything similar.

  19. How do I select a group of 2D or 3D loci and then create a polyline (or NURBS curve, if 3D) from them?

     

    I just want to select a group of properly-arranged 2D or 3D loci (i.e. they are all in a proper linear or curvilinear arrangement, there are no path crossovers or branches) and do something like "Create Line from Points..."  but there is no such command?

     

    VW Designer 2021 SP3.1

  20. Bump. I can't believe VW doesn't have a catenary-curve tool in it.

     

    There must be 100 uses for it for all kinds of design problems. Utility wires, zip lines, clothes lines, indoor & outdoor decorative swag lines/ropes/wires, rope barriers, indoor & outdoor hanging lights, rope & cable suspension bridges, etc.

    • Like 1
  21. 16 hours ago, Christiaan said:

    P.S. you should be able to delete your post by clicking on Options

     

    Hmm. For some reason, "Options" doesn't show in my list of available items, thus I have no way to select "Delete"  Perhaps it's something to do with my access "level" on the VW support forums?

     

    691002812_ScreenShot2019-12-09at5_39_53PM.thumb.jpg.4e7f3100820c224f8baf273a4e2cf215.jpg

  22. It looks like the vision panel you had defined was too wide for the leaf width, when taking into account the 120mm offset from the strike.

    By making some changes to the panel dimensions I was able to get a panel to show as-expected.

    You might also want to un-check "Show leaf as solid slab" in 3D detail levels, although by default this only occurs if the overall view level  is set to "Low" detail.

    (Note: I made these changes on a door which I had converted to Unstyled.)

     

    2073039030_ScreenShot2019-12-06at6_10_39PM.thumb.jpg.5c7a057763ba1aa6bf406f7180e7ce2c.jpg

     

    95947227_ScreenShot2019-12-06at6_10_56PM.thumb.jpg.e26be7057c84a41a7d93fe112317e2d2.jpg

     

     

    1617767612_ScreenShot2019-12-06at6_11_02PM.thumb.jpg.30331972f83e90caaf3c862c5e0807fd.jpg

     

    Screen Shot 2019-12-06 at 6.10.56 PM.jpg

    • Like 1
×
×
  • Create New...