Jump to content

ericjhberg

Member
  • Posts

    562
  • Joined

  • Last visited

Everything posted by ericjhberg

  1. We have resorted to using the least recommended "Align with Internal Origin" option when importing DWGs and starting to coordinate because it "locks" the internal and user origins at 0,0 and therefore creates a 0 percent chance that the two get confused when referencing together. This is means that we do not get to take advantage of modeling near 0,0 in the user origin where it works way better. I agree, this is a MUST fix problem. There needs to be a consistent understandable way of maintaining real world coordinates for geo-referenced files across a multiple reference file workflow that has a 0 percent chance for error but also allows consultants to maximize their modeling capabilities in situ.
  2. Sadly the only way I know how to do this is to place a live object into the viewport annotations as a legend symbol. In this methodology you don't use the =IMAGE function and the live object(s) will color via the Data Visualization settings. For obvious reasons, this is not ideal because if your worksheet changes in layout/dimension/# of items, the live/dumb legend objects do not update with it in spacing or layout. It is the only way I currently know how to do this though. Additionally, when is the =IMAGE function going to represent a true Vector version of the queried object/symbol? I'm tired of the poor quality, faint raster symbols created in worksheets that are hardly even legible upon export, regardless of the DPI of the worksheet or sheet layer
  3. I actually have had the exact same frustration in the past day(s) and can confirm the 32 second wait time. Frustrating. It's little things like this that make sheet setup and drawing coordination very tedious. It could be so much more fun.
  4. We have a strange occurence currently in our office. We use the Workgroup Library configuration to store collective resources, including template files. These are typically visible to every user via the Create Document>Use Document Template drop down menu. One user cannot access the workgroup templates, even though the program is connected to the Workgroup Library and all other resources located within are accessible. Every other user in the office is fine. Why would this one user not be able to access workgroup library templates?
  5. Where is your model in reference to the 0,0 origin? To me this looks like you might be working out in coordinate space somewhere and the jagged edges are the trademark modeling flaw we see in this condition.
  6. @Andy Broomell Yes, I am trying to group nested symbols with basic geometry inside the symbol, so that probably explains it. I guess for this particular issue, I don't have to put the symbols in the same group, but it does sound like a bug. Hopefully it gets fixed...some day.
  7. I am trying to group together several similar items (each in a different class) into one group inside of a symbol. This group is intended to be in a parent class that would then control the visibility of the entire group. However, after grouping the items in the symbol and placing it the desired class, when I exit the symbol, the items come un-grouped. When I reenter the symbol edit, sure enough, they are all ungrouped. Any ideas?
  8. This is because the Sheet Numbers read as text and not as numbers, which is essential to include your prefix. I have run into this issue myself and I have a workaround... Open the Titleblock Manager (File > Titleblock Manager) Go to the Sheet Data Section Click on Manage Sheet Data Add a record field...Drawing List as a text style format This record will likely never be shown in the titleblock visually, but can serve to help you sort out which titleblocks go where in your worksheets Using a "Master Worksheet" designed to pull in all of your titleblocks, add a column for the Field 'Drawing List' and start to populate each sheet with the corresponding A, B, C... You can then redesign your two drawing list worksheets criteria to look for values that = A, B, C... etc. Hope this helps.
  9. I can't say it any better than those on this thread already have...you'll be greatly missed. Best of wishes to you! -E
  10. Already using one...doesn't work. This only happens in VW2018. Doesn't happen in 2016, 2017, or 2019. Its strange.
  11. Fair enough. I don't disagree. However, you fail to convince me that it, at the very least, shouldn't be an option.
  12. @John Meunier Not that I am aware of...but this is something, along with general Text handling, that VW desperately needs. ALL CAPS is industry standard for construction documents and has been forever. Needs to be implemented ASAP!
  13. @DonnaS Yes it does, though it is a somewhat limited suite. That said, I only own landmark and was able to design a complete (albeit basic detailed concept) structure with it. The walls, windows, doors, and the roof tool all work in Landmark. I just hope it stays that way.
  14. We do, but mostly they sit off to the side in the background and are used solely for organizing callouts. Occasionally we will use them for basic callout functions, but we primarily use worksheets to organize and build our legends.
  15. @Boh We use this system extensively and it works fairly well with very few snags. If you alter the 'Callout'.'Text' field from the worksheet for a callout with text that was defined from the database, it will break that reference to the database. This hasn't really been a problem since the database doesn't affect the callouts after they are created...rather the database becomes useful for populating callouts, but not necessarily for maintaining them. When using callouts as keynotes, there is another way to pull in the Keynote ID# that you may not be aware of. You can add a column, pulling in the field 'Callout'.'__Keynote Number'). Note that you cannot change this field from a worksheet, only by reodering the keynote legend. That said it is a useful tool. We actually use this system to build all of our legends in our documents. They are all based on the callouts, not on the objects in the drawing. It has been a great way to streamline our document creation. It should be noted that this workflow will likely become null and void once we get comfortable with data tags, but for the past few years it has worked pretty well.
  16. Done! Congrats @Jim Wilson
  17. I don't disagree, but we have found that worksheets have been profoundly beneficial for other reasons too. They allow you to control massive amounts of data in one location and can be turned into legends and other reporting tools if need be.
  18. @Jens Marr You can create a database header in a worksheet that will pull in all of your callouts. From there you can add columns for the Prefix ('Callout'.'Keynote Prefix') and Suffix ('Callout'.'Keynote Suffix') and adjust them from one centralized location. You can re-add or adjust the keynote prefix as you need. The tricky one is how to return the ID#. Thanks to @Pat Stanford, he put me on to the field ('Callout'.'__KeynoteNumber') to pull that in. Note you cannot change the number of a callout from the worksheet, that has to be done in the associated Keynote Legend by re-ordering the callouts.
  19. This one has been bothering me for a very long time! Since VW2018 was released, my saved workspace will not save entirely. Essentially I have a double stacked group of tools on the left side of the screen that I prefer. In VW2018, every time I open the software, it reverts back to a collapsed version of this sidebar configuration. This only happens in VW2018. It has never happened in prior versions, and it appears to be fixed in VW2019. If VW2019 wasn't riddled with bugs and we weren't pulling back from implementing it in our office, I wouldn't mind this persistent issue, but since it looks like 2018 will be my mainstay for quite some time, I am finally adding this bug to the list. I know this is a minor thing that doesn't really affect anything, but damn it is annoying. Annoying Workspace Collapse in VW2018.mp4
  20. @jg@swcm We have created our own custom plant symbols and libraries over the years. We don't particularly care for the ones VW "provides out of the box". That said, this is your chance to streamline your workflow. We have built a system of standardized classes that help us control the visibility of the symbol in both color and in black and white. We have generally found it most useful to create classes that control the following: Tree Outline (lineweight control) Tree Canopy (color) Tree Shadow - Special trick can allow you to control shadow visibility (on/off) by class Shrub outline (lineweight control) Shrub fill (color) Interior Linework
  21. Agreed. Unless the callout is a keynote, there is no central place to affect a change in all instances of a callout from the database. When it is a keynote, that universal change can original from the Keynote Legend. ....there is another way, but I wouldn't recommend it for this purpose. You can actually control the Text of a callout object from a database worksheet designed to pull the field ('Callout'.'Text'). We have made symbols of repeated paragraphs, notes, or other text that appears multiple times, but unfortunately there isn't a great way to keep a phrase or portion of text consistent.
  22. NO, but there should be! Text objects need dramatic improvement. It has been my #1 wishlist item for years, but they haven't done anything.
  23. @Jim Wilson Just an FYI...I am still experiencing repeated crashes in the VW2018 file that I provided you. Sadly I am used to the crashes, and there are too many to report each. Additionally, the 10-15 minute file opening time compounds my day when you have to reopen the file 3-4 times a day. That's almost an hour of lost time per day. If I report each crash and research diligently, that would take up an additional hour each day.
×
×
  • Create New...