Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by MattG

  1. Not sure how I just saw this but this is awesome. I know I posted a "wish list" for something like this integrated into VW a long way back but just this is great. Long story short for me it helps in consistency when getting files from other incorporating into yours and suddenly text from .dwgs or other items don't all match. Super nice.
  2. @ScottLebsack Yep totally doable just more curious now to what that actually is because I'm sure that info is accessible somehow. Thanks @Pat Stanford Matt
  3. Yes on a index, no on the title block for this particular thing. That is where I am stumbling. I have done the above before but without too much explanation I'm not doing that here. Hoping to just get the actual Sheet Layer fields out. Matt
  4. I know I've seen this before and cannot find it for the life of me. I'm trying to make a report of all my sheet layer numbers and titles. What database record/fields would I use for that? This is not the drawing border option. Thanks, Matt
  5. I tend to draw a portion of a system to start and then get all my viewports set up for things. I often will do say a 3D view of some type of a truss or something that is more just for visualization not really for "rendering". I tend to just do these in a variant of open GL. My understanding is open GL uses a max of 8 lighting devices and gives priority to the last 8 light objects. My question is if there is a way when I add a new lighting device to a drawing to have the default on/off set to off for all existing viewports. The reason being that if I already set up the look for a viewport and it is good but I add a light that may be on in a layer or class that already exists it appears to start factoring into the rendering of that viewport and depending on the quantity take priority over existing devices. I feel like there is a setting for this I am missing but maybe not. Anyone have a solution for this? Thanks, Matt
  6. Side not CP's site has good .dwgs as well for this and most of their products. We are working on building some into some set pieces so I generally prefer the manufacturer's drawing to be sure clamps and spacing are a bit better and CP probably has the "cleanest" dwg that come into VW.
  7. @JBenghiat thanks that is very helpful info and I would have never found that. I wish there was somewhere that documented those fields, I can see real use for it. Thanks, Matt
  8. Man this program drives me nuts sometimes. Thanks! I did a dummy report with every field hoping to find the secret field that may store the units but no luck. Just really odd. I do that using some of the braceworks stuff to make custom things manipulating that data, but it seems really odd that is a hard value. Either way for now that works. Thanks as always. Matt
  9. I have been okay doing this in the past but am noticing an issue now in 2021 but unfortunately have not been doing as much lighting in VW these days with the pandemic. It appears I am having trouble dropping the "lbs" from the fixture weight in a worksheet that pulls the data from the lighting device criteria. I used to be able to do =Value() and it would bring back the number, and my secret if I wanted it there was that I could then just put the lbs in the cell formatting as a suffix, but everything I have tried seems to be unable to dump the lbs suffix off that. Any help is appreciated. I feel like @Pat Stanford has probably already solved this...... 🤣🤣 Thanks, Matt
  10. Hi @Mark Aceto or @JustinVH I am messing around with many of the same things here at the moment. Did anyone ever come up with a way to see the data tag layout in design layer scale so I can actually make my data tag for a hoist and use real numbers like the scaled layer I'm in? Right now that is a real joke to try to make some stock tags that line up.
  11. I don't believe that is working as intended. See video. I also filed a bug. If this is something I'm doing wrong let me know.
  12. Does that file get overwritten with any updates etc?
  13. I am working on switching my workflow from what is now the "legacy Hoist" tool to the current hoist tool (2021). I see the field for Connector Type. We use the very standard P14 type of connector for our chain hoist power distribution system. I don't see anything that obviously jumps out as being that in the connector type. Am I missing something? What connector type should I be using? https://shopmtn.com/products/p14-motor-cable-16-7
  14. I'm playing catch up on some of my reports and worksheets in VW and converting from the now legacy hoist tool to the new version. I know it is a bit like an apples and oranges comparison. Is there an equivalent of the rounded dimension check box from 2020 and earlier in the hoist tool in 2021? I've looked and I cannot seem to find it. I like this for me personally because I used that field in reports to avoid fractional values without needing to adjust anything in the document unit settings. I tired finding something but have not been able to find that similar option, any help is appreciated. Thanks, Matt
  15. Well I consider myself a fairly advanced user and I have never really realized this is an option. Not really what I am looking for but good info. I am for simplicity sake just looking for something that takes a viewport on a sheet layer and lets me have a viewport at 30% opacity. I feel like there should be a simpler way to do that then doing that in the design layers etc. In the end I can do it in a adobe program after the face quickly, but I just have to believe there would be a simple way to do that.
  16. I tried but there is nothing in the Image Effects for opacity, but I really think there should be at some point because that or just being able to use opacity in the attributes pallet would do the trick. Matt
  17. Nope I lied. I am trying to recreate it in my Titleblock. I don't think you can use data vis on a sheet layer title block? Basically the current workflow for these PPE style shields goes. 1 - I draw the shield on a design layer. I have 10 or so design layers already set up in the drawing. Each design layer is a line item on a PO 2 - Make 3-4 viewports depending on what it is on a sheet layer showing different views. 3 - fill out the title block with appropriate info. Project data = purchase order info sheet data = line item specific info. My whole point for this is to highlight the things that are different from line item to line item for the guys pulling the items to catch it. I don't think I can do that on sheet layers?
  18. @markdd this last one "Title Block with Data Vis with data tag.vwx" is essentially what I'm trying to do. I never really thought to use data vis in a title block I think that was my road block but I guess it makes sense. Thanks!
  19. Cool, kind of what I was thinking. I do use the dropdown in title blocks from time to time, but more what I was looking for was something where I can show existing text and have a check mark or x or something fill in a box like a form based on that selection. Kind of taking that to a second step. Almost like conditional formatting in excel. Basically in the pandemic here we have been pivoting to doing some custom cutting of polycarbonate panels for barriers for buildings. I have a little drawing template I have made for individual orders. We offer lets say 6 variants of shield material. I have the list of 6 items on the side in my title block with currently an open rectangle for a check box (I made this for the guys to take to installs and be able to fill out). When we actually fill that out and I choose item 2 of my 6 variants of shield material I am hoping that I can generate a check or something in that box or link it somehow that way. Reason being the next step we currently do is hand that to our guys pulling the material and I think visually that helps them if they see it that way. Any other thoughts? Matt
  20. No, do you have any resources you can share that might show what you are thinking? What I am currently doing is not what I am "generally" doing, so I may not be thinking of the best options. Matt
  21. I am wondering if I can have something function similar to a radio button or check box in a title block. Does anyone have any experience with this? Basically I am drawing a product. The product has different field with different variables. So I am hoping I can somehow create a field that would have "option 1" "option 2" option 3" "option 4" etc to and I can click one of those. That would then be linked to some geometry on the title block that would fill in a fill color or something similar. I'm fairly sure there is not a real way to do this in the title block and right now I'm just manually doing this. However I have been surprised to learn things in the past and would not be totally surprised if someone had a good work around. Ideally trying to keep everything in the title block to streamline the data on a project. Thanks, Matt
  22. Is there a way that someone here has come up with to make a viewport have opacity to it? Basically I have two viewports of the same thing stacked on top of each other. I want the viewport in the back to be able to have the equivalent of a 30% opacity, all other rendering settings the same. Right now I'm playing with render styles to accomplish this but it is not really getting the desired effect. Anyone have any advice? Thanks, Matt
  23. I have a drawing I am working on with a bunch of symbols made up of other symbols. I am making a report to show me all the info on the symbols. Is there any function or way of showing a field that shows what symbol a symbol is in? For example I have 5 of symbol A and 8 of symbol B put together to make a thing. I make that thing a symbol and call it symbol Z. I have a report that now shows all the symbols and their record format which is what I am really trying to get out of this. However they are just all in one big list. Is it possible to put in a field/column that shows the parent symbol and then summarize by that field/column? Not sure that totally makes sense. Matt
  24. Yeah I am not sure what the best option is. I hate to dig too deep because it should be a rare occurrence. However the first option of a self script would probably work.
  • Create New...