Boh

Member
  • Content count

    89
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Boh

  • Rank
    Apprentice
  1. Hi Bruce. One reason could be that the walls that aren't rendering have wall style "by-class" settings for fill and the class you have placed the walls in does not have any fill. This is similar to an extrude not rendering because it's fill style is "none". Give it a soild fill and surfaces are then avialable for rendering. Perhaps when you place the walls in a different file, that file has the same class but with a solid fill instead of no fill, hence they render in that file but not the other.
  2. Did you check your z height of thr DLVP? It's not floating around above out of view? Or does the DLVP have a crop? If so try deleting the crop object.
  3. This sounds like exactly the scenario where you should be looking at bim modeling. Both formats ex and importing info to the same model.
  4. I have another little issue with class/design layer/sheet layer description... I really like how the class/design layer/sheet layer description pops up when you hover over an item in the navigation palette. You can see quickly what a class or layer is intended to be used for. A great feature I thought so I diligently started adding descriptions to the classes in my template file. However I've just discovered that this description does not pop up in the OIP class or layer drop downs when you are looking to change the class or layer of a selected object. I.e. you have selected an object and are scrolling through the "class" or "layer" drop down in the OIP looking for the class or layer to allocate to it - no pop description is available. This is precisely the time when the class or layer description is most needed, especially for someone such as a new user working on someone else's file. To have a little prompt available in the OIP would definitely help objects be classed correctly. Incorrect classing of objects is one of those things that can really make file structure breakdown. Do others agree? Can we please include this little feature in a future release? Thanks!
  5. Adding 3d loci to the site model source data works for me and I am using VW2016. Maybe what is happening is that you are trying to make the site model bigger by adding 3d loci beyond the boundary of the current site model but not updating the site model crop object? VW by default creates a site model crop around the boundary of the original site model source data. I've quickly tested and found that adding 3d polygons to the source data will automatically redefine the extents of the site model crop, however adding a 3d loci does not. I.e. the site model crop does not change if you add 3d loci beyond the extent of the current site model but it does change if you add 3d polygons. I suggest that you try, (after adding the 3d loci), right clicking on the site model, click edit site model crop, and delete the crop object.
  6. Ok cool. Thanks Gerard. I hadn't imported a plug-in before so have learnt something new today! Bonus is that it actually works!
  7. Thanks for that. Yes I wouldn't normally use this but I am reworking a symbol library and template files from scratch so I thought this might be useful. I have a lot of light symbols for example that I would like to set default records for. With that being the case, for me it would be better suited as a script command contained only in the symbol library file rather than as a menu command.
  8. Hi Gerard. I tried downloading the file, unzipping, copying contents of file into a new script and it didn't work. I'm clearly doing something wrong? Can you point me in the right direction?
  9. Under "tools" menu there is a rename classes tool. You can add a prefix or replace certain text in many different classes in one go. You can add a prefix with a "-" to create a hierarchical class naming structure. Ideally however, if you are doing similar projects using the same classes you would create a template file with classes already created instead of creating them as you go. This is fairly standard practice. Your suggestion of having a group class - a class in which groups are placed so that you can control visibilities of the variously classed objects contained within the group in one go is another option however it does mean that in order to see the objects contained within the group both the object and group class need to be set to visible. I've used this technique and it is o.k. however it can get confusing for another user trying to work with your file as occasionally they wil lbe stumped as to why certain objects aren't visible even though their class is set to visible - not realising of course that these objects are in a group class which is turned off.
  10. Hey TKA. Yes that is the "hierarchical" display mentioned as attached screenshot: In addition to the viewport class visibilities dialogue it would also be great to see hierarchical display used in the "new class" dialogue. Currently I have to scroll down through dozens and dozens of template file classes to find the one I want to import. This would be a lot quicker if an option to show in hierarchical display was provided. Btw there was a recent post about setting up viewport templates and using the eyedropper tool to transfer visibilities from one viewport to another:
  11. I understood it to be about hierarchical display of classes in the class visibilities dialogue of viewport settings.
  12. Yes, this would be handy. Meanwhile there is this script from @Pat Stanfordthat will update all viewports on a sheet: Procedure UpdateSheetLayerVPs; {Selects, Updates and Deselects each viewport on a sheet layer} {Revised to handle both sheet layer and section viewports} {? 2008, Coviana, Inc - Pat Stanford pat@coviana.com} {Licensed under the GNU Lesser General Public License} Begin DSelectAll; SelectObj((ST=REGVIEWPORT) or (ST=SECTVIEWPORT)); While FSActLayer<>Nil do Begin UpdateVP(FSActLayer); SetDSelect(FSActLayer); End; End; Run(UpdateSheetLayerVPs);
  13. Nice! It would be great if this was available straight from the selected object right click context menu rather than have to go to the nav palette.
  14. Yes there is similar control in the edit class dialogue which is great for Turing on or off a class in all viewports or saved views in one hit. I have a "NonPlot" class for drafting lines or anything I use that I don't want printed. I use the edit class control to turn it off in. All viewports before printing. Very handy.