Jump to content

Jeremy Best

Member
  • Content Count

    159
  • Joined

  • Last visited

Everything posted by Jeremy Best

  1. Jeremy Best

    Polygons with Hatches are un-selectable

    Thanks @Andy Broomell, I've added this info to the bug report.
  2. Yes this is interesting. Can you expand on this a bit, please? Do you mean that beach balling occurs whenever you connect a USB-C peripheral while other USB-C ports already have devices connected to them? So connecting the same peripheral does not cause beach balling if no other USB-C devices are already plugged in? What are the devices that do cause beach balling when/after they are plugged in?
  3. Jeremy Best

    Polygons with Hatches are un-selectable

    Bug report submitted: VB-158101
  4. Jeremy Best

    Polygons with Hatches are un-selectable

    Hi @Patrick West, I work for the New Zealand distributor of Vectorworks providing Tech Support for our users. While investigating a different issue involving Hatches in a users's file, I experienced this same situation. After verifying it was only affected certain Classes my expectation was that this behaviour was due to a random corruption, but because of your report (and despite my inability to reproduce the problem from scratch) I will submit this to engineering. I expect Engineering will face a similar challenge recreating the conditions that cause this problem. So if you are aware of how to recreate this issue it would be extremely helpful. If you have a file you're happy to contribute that would be great (message me privately) or post your proven sequent/conditions here. Thanks!
  5. Jeremy Best

    Object info palette flashing / blinking

    That's great news Laura. If/When you make the move to Vectorworks 2019 it should be better still.
  6. Jeremy Best

    Object info palette flashing / blinking

    For the benefit of anyone searching this forum for issues encountered while using Vectorworks on a Microsoft Surface: This issue is likely due to Vectorworks being run on a tablet instead of an industrial grade computer, which is warranted to run industrial grade software... Because the Object Info Palette is visually built on-screen every time its content must change, I expect this behaviour occurs on all Windows computers but it just occurs fast enough for this to not be so noticeable. Having said that, the efficiency of the Object Info Palette has been reengineered and drastically improved in the Windows version of Vectorworks 2019.
  7. Jeremy Best

    macOS Mojave (10.14) Compatibility

    Hi @brentf and for the attention of anyone else who is experiencing beach-balling with Vectorworks 2019 on macOS Mojave. I provide Tech Support for customers of the New Zealand distributor, Megabits and have encountered one user with very similar symptoms. (Click something or place something on the drawing area causing beach balling for a long time). The solution in that case was the widely prescribed process Resetting Vectorworks Preferences. In an earlier attempt to help this user I experimented somewhat by only retiring their Vectorworks User Folder only and not the complete process above. I tried this because it had been migrated from the previous version which sometimes goes awry in some way that can result in one or more symptoms of differing variety, but as it turned out the full process is what's proven to be necessary. (Creating an additional Mac login/user account effectively creates this same result). There are a few different items within the Vectorworks User Folder (and hidden Vectorworks system files) that can become corrupt/problematic at random and are responsible for a variety of symptoms. The Resetting Vectorworks Preferences process is commonly prescribed because it quickly deals with all components at once that could be the cause. While there seems to be an apparent correlation with the adoption of macOS Mojave and Vectorworks 2019 take note that I have encountered these symptoms on prior operating systems and they have often been remedied using the Resetting Vectorworks Preferences process. I'm just pointing out correlation does not equal causation, so Mojave may not be the cause in this instance. But it might... 😜
  8. I note that the missing text/record items are different colours (which I thought denoted different line weights in DWG native software). Which makes me wonder if your Saved View just has the Classes of these items 'invisible,' while in your Sheet Layer Viewport those same classes might be visible. If these Classes are visible in both your Sheet Layer Viewports and the Saved View, then this might be a bug in which case I suggest you submit it to Vectorworks or run it by Tech Support for your region. At the moment I can't warrant the time to get my head around the layer scale results you're getting (but it sounds like it might be working as intended considering DXF/DWGs only support one scale at a time) so I suggest you run this one by Tech Support too.
  9. Exporting the content visible in a Saved View will always be smaller than a Sheet Layer Viewport showing the same view because (as per my earlier post) when you export a Sheet Layer with Viewports, it exports the Sheet Layer content but also exports - separately - all the content present in the Design Layers shown in the Viewport. Please see the explanation above for why this is the expected result.
  10. Jeremy Best

    Save on Dropbox, Publish in Cloud = FAIL

    As per these instructions, have you first done the steps to activate the Dropbox integration specifically?
  11. Jeremy Best

    Back Referencing

    Time to stoke this fire… I reckon good will still goes a long way because we are still [stuck] being human. To this end I assert that we can improve Vectorworks presence and regard in the world by supporting not just users of the software but those who must work with its output. i.e. Builders or construction managers or council workers etc who must work with plans produced in Vectorworks. Imagine what effort could be saved, what ease could be enabled and what good will could be conveyed if back referencing was made available for those at the end of the line who would benefit from well-designed documentation facilities in Vectorworks. Conversely, imagine what resentment might exist in the industry towards Vectorworks if it is the only software producing documentation without these benefits. (I've read all major competitors have this facility). I think the potential benefits of back-referencing to anyone producing or using architectural documentation are obvious. And even those in the USA who are used to the absence of this facility would surely be pleasantly surprised by the ease offered by back-referencing if implemented. After all, going beyond what is expected is what creates excellent user and customer experiences. I've been told 50% of an architect's time is spent on documentation. Surely any feature that can significantly assist with hastening documentation is a no-brainer worth implementing, let alone the ensuing benefits to all who use the documentation thereafter. (Yes, this is a repeat of my comment elsewhere as it should be more effective here).
  12. Time to stoke this fire… I reckon good will still goes a long way because we are still [stuck] being human. To this end I assert that we can improve Vectorworks presence and regard in the world by supporting not just users of the software but those who must work with its output. i.e. Builders or construction managers or council workers etc who must work with plans produced in Vectorworks. Imagine what effort could be saved, what ease could be enabled and what good will could be conveyed if back referencing was made available for those at the end of the line who would benefit from well-designed documentation facilities in Vectorworks. Conversely, imagine what resentment might exist in the industry towards Vectorworks if it is the only software producing documentation without these benefits. (I've read all major competitors have this facility). I think the potential benefits of back-referencing to anyone producing or using architectural documentation are obvious. And even those in the USA who are used to the absence of this facility would surely be pleasantly surprised by the ease offered by back-referencing if implemented. After all, going beyond what is expected is what creates excellent user and customer experiences. I've been told 50% of an architect's time is spent on documentation. Surely any feature that can significantly assist with hastening documentation is a no-brainer worth implementing, let alone the ensuing benefits to all who use the documentation thereafter.
  13. Issue: When adding Layers to a document by way of importing them from another saved document, it is not possible to import layers that have the same name as a layer in the destination document. To import these layers requires possibly unwanted changes to the receiving document or to the source document (which is a also little convoluted considering...) See attached screenshot excerpt from this Vectorworks Help page. Proposed Solution: Have a name-edit dialogue appear under applicable circumstances that offers to prepend or append the names of duplicate layers being imported. - I expect this would be better than asking to rename every applicable instance, because if a user is importing many design layers that have duplicate names it would be a cumbersome process to address them all individually.
  14. Jeremy Best

    Problems importing large DWG files

    Because I've not heard/read any other reports of this issue and in light of the above I would prescribe: Resetting Vectorworks Preferences, and if that didn't resolve it: Uninstall then Reinstall Vectorworks 2019 SP2 (excluding your Vectorworks User Folder at least initially). Be sure to temporarily disable antivirus during the installation too. If you know of others experiencing this then again it becomes more likely to be a bug and I'd continue with a submission to Tech Support.
  15. Jeremy Best

    Problems importing large DWG files

    Knowing that a counter stops on a particular number I'd take as a good indication it's stuck/frozen or 'looping' on a process. If you're in New Zealand I can warrant doing a test import of this DWG for you, but if not please get in touch with Tech Support for your region and request they do so. This might be a bug and should be determined if so.
  16. Cool, thanks. I'd prefer to be wrong in this instance! 😁
  17. Hi @erminio, Perhaps exporting only Design Layers would work for you? And then exporting Sheet Layer contents to 2D graphics? The following is meant for anyone else searching the Vectorworks Forum for information relating to this behaviour: This is an intentional change in behaviour and implications are explained in the Vectorworks 2017 Help manual pictured below. Understandably, this will create a larger file as the Design Layer content is populated in the DWG export for each Sheet Layer Viewport included. In the Vectorworks 2019 Help manual suggests one could change their workflow or the export options to create the desired info for the end user.
  18. I've just verified this feature has not yet been added to Vectorworks. (As at Vectorworks 2019 SP2) Hey @Jim Wilson, if you think it might help, can you please reignite or bump this feature request? It seems like a pretty small/easy think to implement and offers great potential benefits / time savings of work lost.
  19. Jeremy Best

    Window / doors wont bind to wall object

    Have you checked whether the 'Wall Insertion Mode' button is ON in the Tool Bar?
  20. Hi @Sky, this symptom is related to setting the Vectorworks Preference 'Default Compression' to JPEG. Change it to PNG and they will no longer finish up all-white. Seeing as the 'memory leak' is happening on both your computers it might be file-related or particular to one or more resources/objects present in those files. So, if you haven't already tried Resetting Vectorworks Preferences or a clean installation of Vectorworks or macOS, first pass your file on to Tech Support with steps to reproduce what you encounter.
  21. Jeremy Best

    VW 2019 Render not stopping

    Thanks @TimC. I've verified that this works. Also realised reactivating even the same render mode will stop it and render in Wireframe.
  22. Jeremy Best

    Stop seeing grid through objects

    Cheers @nwfonseca! Thanks to your input I've now confirmed the reference grid appears in front only when Unified View is OFF.
  23. Jeremy Best

    Problems importing large DWG files

    Does it "freeze" as-in 'hang' (can't do anything thereafter and must force quit Vectorworks) or does it just indicate "Not Responding?" If it's the latter, if you wait long enough it might complete the process. Assuming it isn't hanging; Do you have a sense whether the accumulative time it takes to import the smaller chunks is about equal to the time of the whole import when left to complete? It might be that when importing the whole file your computer uses a lot of its available RAM and has to use virtual memory to help. Assuming your hard drive is a mechanical one (and not an SSD) this would significantly slow the import process. This would also explain faster import times (even when added up) when importing smaller chunks. To help determine whether Vectorworks hangs or what's happening when trying to import the 'whole' DWG file, open Task Manager (Windows) or Activity Monitor (Mac) and note the following measures before the import starts and during: CPU activity What percent is being used by Vectorworks over time How many cores are being used Memory Does consumption get really high? (70%+) Does virtual memory increase significantly comparing 'before' and 'during'? In Task Manager this is the numerator readout for 'Committed' In Activity Monitor this is the readout for 'Swap Used' Disk Activity/Percentage changes over time My expectation is this operation is a single-core process too, making it seem unusually slower than other [possibly] bigger/more complex operations that are multi-core.
  24. Jeremy Best

    Stop seeing grid through objects

    Hi @nwfonseca, I provide Tech Support for New Zealand users and am currently assisting someone who has provided me with a file that exhibits this too (the Reference Grid displays in front of all objects even when rendered in OpenGL and despite the objects being above the ground plane). This issue does not occur in any 'new blank document' even if I mimic the file settings nor if I paste in the entire contents from his document, nor if I import them via Design Layer import, so I think their file (and likely their default or template file) is corrupt. I presume you've resolved this issue by now, so I'm commenting here in case this info benefits you or other users in future. Have you since resolved this? What worked for you? If this grid issue persists for your please open the test file I've attached and see if it occurs with that then report back. Thanks! Jeremy Superimposed Reference Grid verification file.vwx
  25. Jeremy Best

    VW 2019 Render not stopping

    Bug submitted: VB-157103

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×