Jump to content

michaelk

Moderator
  • Posts

    6,388
  • Joined

  • Last visited

Everything posted by michaelk

  1. Yes it will. I don't think you can have two different standards in the same document. (Maybe someone else will know better.) mk
  2. Duplicate the file. In the duplicated file - from the resource browser, delete one symbol at a time (starting with the accessories) and choose delete every instance of this symbol. After each deletion do whatever makes it crash. For me it's usually zooming or fly over. Rinse and repeat until you find it.... Good luck mk
  3. File > Document Settings > Units... > Set units to Feet and rounding style to decimal. hth mk
  4. Lee I'm sure Steve Shelley has a something better, but your welcome to this one. No guarantees about the photometrics. Not sure how the calculations even work w/ LEDs.... mk
  5. I've had occasional problems with old symbols - created in VW 9, 10, 11, 12, '08, etc. (mostly my own, but occasionally a stock symbol) - causing problems like debilitating lags and crashes. Deleting the offending symbol or replacing the offending geometry in the symbol immediately made the program happy. Usually the problem was self-intersecting geometry (like a sweep or EAP) in the symbol that, perhaps, was tolerated in an earlier version but not in 2010 or 2011 (when these issues started coming up for me). Not sure what to make about Lightwright exchange solving the problem temporarily.... good luck mk
  6. Funny. I also thought of =1.* last night. The script is a very nice touch. There still may be a way of using the INT(VALUE( )) in the criteria, but my head's not up to it... mk
  7. Hi Jane - (I didn't realize you were that Jane.) Are the objects in a .sta file (in which case you should be able to select them) or in a referenced design layer viewport? ie referenced from another file. mk
  8. Make sure all the layers are the same scale. No matter what the layer / class view options you can't select something on a different layer with a different scale. If all layers are the same scale: Try right clicking on an object and choose force select. Try holding down the option key and dragging across the object. Try select all. hth mk
  9. I agree. The UI for entering criteria is too clunky. It's often easier to just type it in. mk
  10. James I suspect that a repeated application of head to wall would make that work. But perhaps we are over thinking it.... Attached are two methods that might do the trick.... hth mk
  11. Click on the little triangle and choose Database Headers. Row 4 (with a diamond next to it) appears. Click on the row header and you will see the Sum tile Pat mentioned in the B column header. You can drag it around or drag a new sum from the tile "garage" above the A column. Then close the database headers again... hth mk
  12. James Look at column C. It returns an integer instead of text. It will take a little contemplation to figure out how to use it as a database criterion...
  13. Right idea, but lighting objects can't be edited by double clicking. Right click the position in the RB and change the line to the correct class. hth mk
  14. James If I'm understanding what you are trying to accomplish, it sounds like a great idea. Have you tried a Value( ) call? ie, If INT(Value ( ) )= 7..... I *think* something like that might do what you want... Can you post a lineset and piece of a database to look at? mk
  15. I'll take a stab at a couple: 1. Option 1: Make sure the Selection Tool is in Disable Interactive Scaling Mode (so you can't accidentally resize one of your objects) and make sure you have Smart Points turned on. Grab one of the objects by a handle and drag it to a handle on the second object - hover long enough to acquire the smart point - and a red dotted line will appear to help you place object. If you have "Show SmartCursor Cues" selected [Tools > SmartCursor Settings... > General], it will walk you right through it. Option 2: To make the objects meet at a specific coordinate - place a 2D locus that has the X value you are interested in. Select the locus and the left shape Modify > Align > Align/Distribute... > Align right. Select the locus and the right shape Modify > Align > Align/Distribute... > Align left. One of the cool things about 2D loci, is that they won't move when you use the align command on them. 4. Play around with the smart edge constraint. Make sure it is on. Draw a line (unconstrained mode) at a nonstandard angle. With the line tool still active, "gesture" along the line. A red dotted line will appear. When that line is visible start drawing another line. Hold down the shift key (or have the angle constraint on) and your line will snap to 0?, 30?, 45?, 90?, and parallel to the first line, and perpendicular to the first line. Works with almost any object. 3. I think the news is all bad about the fillets. It's been a longstanding wish item list to have fillets keep their history like solid additions, subtractions, and intersections. hth mk
  16. Benson Nice catch! ...and I thought your workaround was clever... mk
  17. What are you using for criteria? I just tried it with both roof objects and roof faces. =DATABASE((ST=ROOFFACE)) does exactly what it sounds like you need. =DATABASE((T=ROOF)) does only roof objects. If you are using both, you would get the double results you describe. hth mk
  18. Yep. It's very possible. It's what makes VW so powerful for projects like this. It's not clear from your post whether each instance of each symbol will have it's own unique data, or if each type of symbol will have identical data.... You'll want to create a database. Right click on a row header and choose "database" For the criteria choose something like Record _______ is Present, or use a class for the symbols, etc. Then in the database header (the row with the integer row heading) enter what you want each column to be. You can create your own by selecting a symbol in the drawing, then clicking into a cell, then click the triangle in the worksheet and choose "Paste Function", then pick a function, then "Paste Criteria" and pick a critera. The paste functions will enter commands into the database header row. The functions available tend to not be comprehensive, so I've found it easier to just enter what I want directly into the database header. I'll attach a couple examples you can take apart to see how they work. -1 is an example if all the data is unique. -2 is an example with identical data for each type of fixture. Each will have a "database" worksheet that just shows raw data. In -1 you can enter data directly into the database and watch it appear in the drawing. And, yes, the worksheets, symbols, and record formats all live in the resource browser. You only have to do this once and you can then import them into any other drawing. I agree about the documentation for worksheets - not super helpful. But once you get the knack of it, it's a huge productivity booster. Let us know if you get stuck. mk
  19. Petri I've been doing that for a couple years. (I think I learned it from you!) But my wish is that I didn't have to close the file and reopen it in another duplicate app - just so I could continue working on another file. What I really wish for is the ability to start a render - say in a SLVP - and continue working on other SLVPs, or pop back to a design layer and continue working during the render. ...or make the render time trivial. mk
  20. Yeah........ I've done that in the past. And I'll probably do it again very soon. It can get confusing. Sometimes files want to open in the duplicate. It feels messy. Probably not NV's preferred method of solving the problem. I'd like to have a way of solving it that doesn't involve closing the file and opening in a duplicate. mk
  21. ...or an option for "background" rendering in VW that quietly plugs away while other work continues. mk
  22. ...or drop by here.... Most of my posts are a result of either waiting for RW to render or sincere procrastination. mk
  23. This is an old request, but.... please, can we have a way to keep working while renderings are going on? This is doubly problematic when working on two or more projects at once. While one project is rendering all work stops... mk
  24. There are a couple 2011 unnecessary redraws: 1. When a scene is rendered and a light properties window is open, the scene redraws after each parameter is changed. So even if only one parameter is to be changed, one has to wait until after the redraw before hitting "OK". Please provide an "Update" button or wait until "OK" is clicked before redrawing. 2. Scenes redraw every time a resource is imported. Even if the imported resource is not replacing one in the current scene. No need for a redraw. mk
×
×
  • Create New...