RickR

Member
  • Content count

    551
  • Joined

  • Last visited

Community Reputation

18 Good

1 Follower

About RickR

  • Rank
    500 Club

Personal Information

  • Occupation
    Theatrical Consultant
  • Homepage
    www.lts-nw.com
  • Hobbies
    Theater, hiking, sleep

Recent Profile Visitors

982 profile views
  1. I'd be happy if there was just a space. Readability is a major factor for anyone doing CAD.
  2. I've had IFC file imports take many hours (3-10) so exporting could easily be similar. My only thought to help would be to break it into many smaller parts (by floor??) but still not a good solution.
  3. A colleague is getting this as well. Not sure of his system specs, but I know he called tech support without good results.
  4. I've got a pretty large file in hand at the moment. 1GB+ on disk. And I've been crashing out trying to import the 260MB rvt source file. This is while viewing the whole thing in OGL.
  5. FYI I too have no way to change the display. I often use a dual monitor, but also frequently use a single. No saving, closing, workspace anything will let me re-set the basic palette size and location.
  6. I just sent a file to tech support that wouldn't import. Granted it is 200MB+ and will grow fast as we are just in SD. I suggest calling them! Also your signature line says you are on VW2016.
  7. Sheet viewport enforce "unified view" they must all be in the same view orientation as well as scale. If you have a 2D design layer viewport showing in a Section viewport you can't make a sheet viewport that shows that. My workaround is to stack up viewports on the sheet. Align them carefully and everything is fine.
  8. Well, there are usually 3-30 ways to do anything. I can't think of a way that involves sheet layers or detail bubbles, but someone else might. You may have already done some of this with layers. Can your BOMs be segregated by the layers? If so then you can just use that in each worksheet criteria. Or you can put things into counting classes and do it that way. (BOM1, BOM2... or Hardware-A, Hardware-B, Platform-A, etc.) In this case layers and classes are interchangeable. For most folks Layers are where something is and classes are what it is. OR use a record to build a worksheet. Do you know much about records and worksheets? A simple version would be to create a record with 2 fields say "Name" and "Unit". The idea is the name is what the thing is (hinge) and the unit is where the thing is (SL wagon wall.) So then your worksheets can have a criteria that looks for the record and that the Unit field matches whatever you want to include in that BOM. With this the possibilities are nearly endless. I use worksheets for all sorts of things so I've gotten pretty comfortable with them. The drawback to this method is that if you don't attach the record and enter the proper data then stuff gets missed, so it works best with symbols that have the record already attached, like the lighting stuff.
  9. Great info! I was just wondering if I should upgrade. But (you knew that was coming) I'm a bit confused by the terminology in your post vs that in Cinebench that I just downloaded and ran. No GPU number unless you mean the OGL fps. From my system: From your post If this is all right then my system is 7ish times faster rendering but about twice as fast in basic navigation. Therefore it would rank low in your "good" range unless I was doing mostly rendering work. I also have had to turn my graphics compatibility preferences down to get certain functions to show properly. From your discussion I'm thinking this is VRAM related rather than speed related. Is that how to use this info?
  10. I think you are misunderstanding what sheet layers are and the objects normally placed there. I know some folks draw directly on sheet layers, but those are usually extremely simple projects that don't involve scale in any way. Either that or we have a terminology problem. Maybe you can elaborate on how your file is set up? If you are drawing with viewports on the sheet layers then the objects are not really on that layer, just the viewport is, and maybe a few title blocks and notes items. So trying to sort things by sheets is nonsensical. I recommend using design layers and/or groups of classes to separate the items you want to include in the worksheet. Note that if you list multiple layers or classes in the worksheet criteria they use OR logic rather than AND logic. Naturally nothing can be on multiple design layers or in multiple classes. I'm completely confused in how a Detail Bubble would be involved in this. Best I can say there is to repeat that viewports don't 'contain' objects.
  11. Note further: if you place 2D elements on the 'layer plane' rather than 'screen plane' so that they are considered 3D you can include things like text, dimensions, hatches that are technically 2D.
  12. I'd like to see this tool upgraded to have Spotlight Label Legend type of function. Maintaining the simplicity of the legacy is important, but features like renumbering, auto numbering, skipping, custom containers, multiple numbers, alpha-numbers and maybe even record integration would be incredibly useful.
  13. I can't imagine importing with layers is any different than copy/paste. I too have DWG import, that's what all my ref. files are for. I do the shuttle file with the architects drawings. There are things I'd like to improve, but generally it works pretty well.
  14. I'm pretty sure it's not an upgrade issue. This file and it's referenced ones were started in 17 but the main file was based on a template file that goes way back but upgraded each year. I worked on it for several months in 17. A few weeks ago they all got upgraded to 18 and all was fine until last week. Interestingly I did some testing of 18 with this file early on, but deleted those upgrades. Other news is that it seems that I can work in my main layer but only have issues when the referenced file is on. I'm going (eventually) to do some testing to see if it's just this ref, or all of them. I'll be calling tech support soon.
  15. New info. I managed to get to a different view and things were fine, till I went back. The one that worked is a 3D only wireframe. The one that didn't is 2 layers in different orientations. A top plan in a viewport referenced to another file, a top plan of my theatrical stuff that I then managed to get to a front view. More as it happens!