Jump to content

Gilbert Osmond

Member
  • Posts

    120
  • Joined

  • Last visited

Posts posted by Gilbert Osmond

  1. Query:

    What is the source of new, long, straight line display artifacts that are affecting on-screen display (not PDFs or print-outs) of drawings which have a certain Class visible, said Class using a custom Line Type resource? Is this a user error on my part due to known changes in handling of custom Line Types in VW2020 vs previous versions? Or have I come across a genuine bug?

     

    Background:

    The file is a native VW 3D model (built natively within VW2016 and then brought forward year by year, importing/updating the file to VW2017, 2018, 2019, and 2020 in successive years) All sheet layers / viewports with annotation elements which contain are set to a specific, isolated Class have developed an annoying and reproducible display artifact.

     

    Characteristics:

    See attached screen capture of a Sheet Layer with 2 separate viewports on it, both set to Top Plan view. 

    I've marked many (but not all) of the artifact lines with red dots to distinguish them from items that are supposed to be in the drawing. (Some of the shorter artifact lines I left un-marked to avoid visual clutter. The short artifact lines generally follow the direction of one or more of the large artifact lines.)

     

    These artifact lines zoom in & zoom out normally with the rest of the drawing, but they disappear temporarily during dynamic movement / zooming. (They only show up again after zooming or panning in Top/Plan view has stopped.)  The artifact lines cannot be selected or force-selected independently. They only appear in on-screen display within VW, they do not export to PDF files or print out on hard copies.   Changing VW's live rendering modes (wireframe, hidden line, OpenGL, Polygon) etc. does not affect the artifacts, nor does changing any of the many display-related settings within each viewport itself.

     

    2112047102_ScreenShot2019-12-03at7_33_43PM.thumb.jpg.bb29a9cf91ea8b69c2411034f99a0187.jpg

     

    Reproducibility:

    By process of trial & error I isolated the artifacting to a single item Class, for which the "Line Type" is set to a custom-made Line Type resource.

    When I turn off the visibility of that Class in the viewport, the artifacting disappears. (Along with the objects in the Class, of course.)

    When I change this Class's line type to a default / built-in VW line type (dashed, short dashed, etc.) the artifacts also disappear. They come back when I re-apply my custom line type. This persists even after creating a duplicate of the custom Line Type.  Changing the Line Type's settings from Page Based to World Based (and back) makes no difference in the artifacting.

     

    The shapes to which the Class is applied that has the custom line-types were added back when the file was still in VW2019 format, as was the custom line type resource itself. The artifacting only appeared sometime after converting the file to VW2020.

     

    Further details:

    Here are the details of the Class and the custom Line Type:

    867515633_ScreenShot2019-12-03at7_34_04PM.thumb.jpg.1671dd5865fed73a0a1b92b4cffed867.jpg

     

     

    2137257817_ScreenShot2019-12-03at7_34_45PM.thumb.jpg.a80890ae7d1af5cca15906f494d8c614.jpg

     

     

    Please advise whether I am overlooking something obvious, or if this is a legitimate bug in VW2020 SP2. If the latter I'm happy to assist Nemetschek/VW in further characterizing it or testing fixes if appropriate.

     

     

  2. I had a very interesting / concerning episode with annotations in a viewport. System: Mac OS X Mojave 10.14.5, MacBook Pro 15" 2017, internal display only. (No eGPU.) VW Designer 2019 SP4.

     

    Summary: Seemingly random/strange crash, followed by weird SBOD (beachball hangs), eventually seemed to be fixed by temporarily disabling network /WiFi while running VW. Unfortunately cannot reproduce or thoroughly document; sequence of events / attempted fixes too long & complex.

     

    Details: While moving a normal 2D object (just a simple overlay) in the Annotation layer in Top/Plan in a viewport, VW 2019 SP4 abruptly quit (entire app crashed out & disappeared, no hanging or delay.) This object had been added earlier in the day (a few hours) and was working as expected up to that point. (Move / adjust size / opacity / etc.)  Upon re-opening the same doc, the app crashed in the same way. I figured the file itself had been corrupted.

     

    So, I opened a recent auto-created backup of the same file (~15 mins earlier) and got the same behavior. A hard crash. I tried rebooting and chucking out VW cache folders but that made no difference. 

     

    I downloaded & reinstalled VW2019 from VW Service Select. That fixed the hard-crashing problem, but curiously, now these same files worked fine in all of the many (40 or so) sheet layers & viewports in them, but on the "problem" viewport, when I attempted to edit annotations, instead of a hard crash I would get a seeming SBOD (spinning beachball of death) hang.

     

    After poking around on the forums here I tried doing the "Refresh Library" command in the Resource Manager, along with turning off Wifi for a bit, and this seems to have completely fixed the problem. The viewport annotations in question now work as they ought to & there is no more "hanging." 

     

     

  3. 8 hours ago, Matt Panzer said:

    I think creating custom page sizes through the page setup (as Nikolay suggests) is the only place you need to add them.  You can then use "Fit to Page" in the sheet border to have it always match the sheet layer's page size.

     

    It's a bit of a round-about path to get to my real underlying goal & wish here, but the reason I've inquired about this is that when I use a linked field (in the new 2018/2019-style "Title Block Border Settings --> Edit Style --> Title Block Layout" editing area,) I want to be able to link the text parameter "Title Block Border.Sheet Size Name" to a field in my Title Block and have that field display correctly when I select a non-standard paper size.

     

    250719906_ScreenShot2019-01-16at2_24_30PM.thumb.png.9fbbf6f18f5ab6ad88a7a4330db00df7.png

     

    For example, I do a lot of small US LETTER and US LEGAL-size drawings and details and I would like the "Sheet Size: " to appear as "US LETTER" in my Title Block, rather than having it default to displaying the actual measurements 8.5" x 11", which is what it does now if there is no named preset paper size corresponding to the actual measurements.

     

    So I was hoping to add a "US LETTER" and "US LEGAL" sheet size definition to the overall VW default paper sizes and thereby fix this problem.

    ---

     

    As a work-around I've been manually entering the sheet sizes in a custom-added field in the Title Block Manager on a per-instance (not per-style) basis but this is getting unwieldy.

    • Like 1
  4. 2 hours ago, Nikolay Zhelyazkov said:

    Hello @Gilbert Osmond,

     

    You could add your size in "<VW folder>\Plug-Ins\Common\Data\DwgSizes-Universal.xml". Make sure to use the same pattern as the default fields. Also, it is not recommended to edit this file, so keep in mind that there is a chance for unexpected behaviour.

     

    Thank you, that does allow me to add page sizes in the Title Block Border Settings dialog box.

     

    What puzzles me, though, is that the new sizes I created do not show up in the regular Page Setup dialog box. Is there a way to edit this list of paper sizes as well?  I  already went in to Printer Setup... and selected "Any Printer," then returned to this screen & hoped to see the full list of paper sizes, but it only shows a truncated list. 
     

    (Screenshot from Vectorworks "Page Setup")

     

    1283960651_ScreenShot2019-01-16at2_02_32AM.thumb.png.b38ee786d3088f991fd2722325be9818.png

     

  5. Where can I add/edit/delete VW's default Sheet Sizes?

     

    For example, if I want to add MySheet X, MySheet Y, MySheet Z to the drop-down list in the screen shot below, how do I do that?

     

    I've spent 45 minutes reading VW Help, searching this forum, & digging through the VW system folders looking for defaults.

     

    Thanks in advance.

     

    2088420800_ScreenShot2019-01-15at9_55_10PM.thumb.png.7865994c9c574862d37eb9241c6df8b2.png

  6. Bumping this feature-request. Trying to do a section viewport including a DTM and it's a complete fail. DTM portion is opaque & shows no sub-surface details, e.g. footings & posts for a fence in this case.

     

    Need option in SVP to control how objects appear when a DTM is included --  totally hidden (as they are now,) or totally exposed (showing only the ground surface line of the DTM,) or dashed-hidden-line render below the DTM surface.

    • Like 1
  7. Now that VW supports multiple views / windows / open files at once it would be nice to have a way to force referenced design-layer view ports to update in real- or near-real-time.

     

    As it is now, when I make a change in referenced file (say, moving the height of a fence panel,) in order to see the change in the other file with the DLVP in it, in the main file I have to do:

    Tools --> Organization..., then select the "References" tab, then select the referenced file, then click "Update", after which the changes propagate from the master file to the DLVP.

     

    It'd be nice to have a check-box in a DLVP for "Auto-update this viewport whenever the referenced design layer changes."

     

    Is there any work around for this? Editing the workspace doesn't work as it doesn't allow for auto-navigation within the "Organization..." modal dialog box, nor for assigning a shortcut to the "Update" button in that dialog box.

     

    EDIT: this should be posted in General -- moderators, please consider moving it. Thanks.

  8. I've delved further into this issue. It appears to be an oversight in VW's development process, i.e. someone simply forgot to include the "Existing/Proposed" toggle in the parametric Hardscape object.

     

    - I called VW support & a tech reproduced the issue.

    - We tried to work-around by attempting to right-click and Edit the internal properties of the Hardscape object, but to no avail -- there's no way to display or edit the Site Modifier object that is presumably hiding somewhere inside the Hardscape Object.

    - He said he'd double-check with other support staff, then submit this as a feature request / functionality fix for a future update.

     

    Attached are screen shots:  The Site Modifier object can be set to apply to the Existing, or Proposed  site model. But the Hardscape object cannot. (!) 

    The work-around is clumsy: Set the hardscape object to be a Slab (which does not modify the site,) then copy the hardscape object shape, paste it elsewhere, Ungroup it & remove any slope tags, then use Create Objects From Shapes... to create a Site Modifier object from that hardscape object shape, then configure the Site Modifier object slope(s), & apply to Existing/Proposed site model setting, then move the Site Modifier object onto (aligned with) the Hardscape slab object & group the two together.

     

    When dealing with 10 or 15 slabs across a model this is time-consuming & a nightmare, esp. if any of the Hardscape Object slab + Site Modifier groups need editing. Requires temporarily Ungrouping the group, editing the Site Modifier object only, regrouping, etc.

     

    Attached screen shot shows where the "Existing / Proposed" exists in the Site Modifier OIP, but not in the Hardscape OIP.

     

    I can't believe more people haven't complained about this. How does anyone sanely model an as-built site without being able to use Hardscape objects and have them apply to the existing site?

     

    599ca18d72ef0_ScreenShot2017-08-22at2_07_59PM.jpg.f89936f42270c49c9375e17c8c37aa93.jpg

     

    599ca18ea7cd4_ScreenShot2017-08-22at2_15_10PM.jpg.b405cec2dd3721ba4a2dab670393a1bd.jpg

  9. SOLVED -- yes, somehow just that facet of the roof had lost its fill color in Top/Plan.

     

    Fixed as follows:

    - Go to Top/Plan

    - Select the entire roof (1 click)

    - Use Attributes panel to set fill to None.

    - Then set the fill to a solid color.

    - Then set the fill to a hatch.

     

    After that, the Class *tile* fill becomes properly visible again in 3D OpenGL view.

  10. The dormer is "part of" the roof, i.e. it was added there automatically using VW's built-in dormer-creation feature. It is not a separate 3D object.

     

    Strangely, when I select the whole roof, change the fill to a solid color, then try to change the fill back to the proper tiled fill (i.e. what it looked like before,) I now get a *reversal* of the effect. The whole roof becomes transparent, while the dormer is properly tiled (!).

     

    ?? Still lost here.

     

    598f7b4f90f0f_ScreenShot2017-08-12at3_01_44PM.jpg.bb295438f98cc35c5056dc22e6ce4966.jpg

  11.  

    Previously this roof was properly displayed, with the same tiling on the dormer as is visible on the rest of the roof.

    At some point recently (I'm not exactly sure when,) just the dormer went "transparent" and I don't know how to fix it.

    This happens in OpenGL and in Shaded Polygon modes. In Renderworks it renders normally and properly.

     

    How do I get the dormer faces back to the same texture / opacity as the roof?  Trying to re-apply using the Attributes panel has no effect.

     

    Hints please? Thanks.

     

    598f777e6360f_ScreenShot2017-08-12at2_27_50PM.jpg.1c9b10db4878e3f5bde14497c03e6df0.jpg

  12. Fantastic new feature greatly improving the flow of usable information from the designer/architect to the client and/or other collaborators on a project.

     

    Teaser Tuesdays is a great feature itself -- far better to *show* new features in action, rather than just dumping a text-only list of bullet-pointed features that aren't seen until product release. Way to keep us all interested & keep our faith up for paying annual Service Select costs. (I mean that earnestly, no snark.)

  13. I am using the Pipe Run tool in VW2017 and would like to edit & expand the items listed in the Material:  drop down of the OIP for the pipe runs I created.

    I tried going into the "IFC..." dialogs (from bottom of OIP) and digging around there but did not find what I was looking for.

     

    VW2017 online help explains Pipe Run tools but makes no mention of how to customize Materials list.

     

    Where do I edit the list of Materials for this tool?

     

    Thanks in advance.

  14. 1 hour ago, benboggs said:

    My personal experience has been pretty bad.  I experience ~5 crashes per day.  2017 seems to have more difficulty handling imported files.  It crashed every time I try to import a second CAD file into a drawing.  The import Revit file is not a very useful tool yet.  I hope this will get better as time goes on.  

     

    I also experience relatively slow imports from VW2016.  ~1 minute to convert a file of moderate complexity. (Single-family home / small garden landscape.) These same files imported from VW2015 to VW2016 in probably 15 seconds or less.

     

    Once imported, however, the files are working fine, for which I am thankful.

  15. I think I've found a bug in VW2017 Mac (initial release).

    The Constrained Linear Dimension Tool, when set to Constrained Chain Mode, seems to SKIP the 2nd dimension point.

    To reproduce:

    1) Open a new blank file.

    2) Draw any simple 2D object in Top/Plan view. (Rectangle or whatever.)

    3) Try to use the Linear Constrained Dimension tool to created a Constrained Chain of dimensions, anywhere in teh drawing.

    The first & second clicks create the first dimension in the chain. The THIRD click appears to be skipped / ignored. FOURTH and subsequent clicks (all the way up to 30, which was as far as I tested it) work normally.   So, if you are trying to create a chain of N dimensions, you always end up with N-1 dimensions because the 2nd dimension (on the 3rd click) is ignored.

    Please confirm and/or delete this thread if this has already been posted elsewhere.

  16. 17 minutes ago, zoomer said:

    Install 2017 in any case.

    The complete what's new is in the online help. Very interesting. Jim linked it somwhere.

    Thanks, here's a comprehensive list of new features & improvements, big & small, in VW 2017. (From the online help.)

    I used to be an early-adopter of everything but with age & a little patience I've seen there's really not much percentage in it for me. If a lot more people post positive experiences I may hop aboard but proably I'll just wait for SP1.

  17. 42 minutes ago, Kevin McAllister said:

    Two favourite unsung changes - all drawing numbers for SLVP can be edited via the OIP now / updated UI for Data Tab of the OIP.

    Thanks for your all's replies so far. Is there a published *complete* list of all the little "Easter Egg" improvements that have been made?

    For example in another post someone mentioned that the Property Line tool underwent extensive renovation & improvements. It'd be great to see a complete list of every  improvement in all the user-facing areas of Vectorworks. If JimW has access to such maybe he can post it somewhere?

    Such a list would help people find the little goodies that may help their personal workflow a lot, which they otherwise might not run into for weeks, months, or longer.

    -----

    EDIT: Here's a complete list of new & improved features in VW2017

    • Like 1
  18. I haven't yet updated to VW2017, waiting to hear how it's working for others. If you're using VW2017 already please share:

    Did the installation / upgrade go smoothly?

    How is it working w/ your v2016 and/or earlier files?

    Does VW2017 seem stable enough to trust your workflow to?

    I did already see the separate thread on Renderworks changes & related issues in VW2017. No need to recapitulate that here.

    Thanks!

    ----

    EDIT: Whoops, I don't know how this was posted under "Buying & Selling LIcenses". I had meant this post to go in the General forum.  Mods, if you see this please consider moving this entire thread to the main / general VW forum. Thanks.

×
×
  • Create New...