Jump to content

Patrick Fritsch

Member
  • Posts

    635
  • Joined

  • Last visited

Everything posted by Patrick Fritsch

  1. Thanks, exactly what I needed. Some GC's will love that I dare give them quantities!
  2. How to create a "Wall Schedule" or "Finish Legend" from DATA TAGS TOOL ???? If possible at all, documentation is poor on this. I currently use the Callout tool...but my VW Roadmap understanding is that we should be migrating away from this process? Thanks,
  3. Would like to be able to rotate it so I can use it in roof plan views (ya I know I can decompose and group it but that's not a time saver). Also need more control to stop the rounding especially for roofs that are below 1:12"
  4. Well this post is from 2012...but WE STILL HAVE UGLY UNRESOLVABLE STAIR GUARDRAILS AND HANDRAILS....pretty simple basic stuff a BIM software package needs to be able to do. RANT OVER,...NUF SAID! BLA!
  5. @Wes Gardner Another problem with the Wall component offsets in the OIP is that what is allowed is different weather the wall has a Slab object bound to it or Not. 1. If the Wall has a slab bound to it YOU CAN ONLY OFFSET THE BOTTOM NOT THE TOP. BUT 2. If the wall is not bound to a slab you you are free to offset top or bottom. This renders the slab bounding function useless and it should have the same flexibility as the unbounded wall. Not to mention it confuses everyone why their able sometimes to offset wall tops and not another as it not obvious a slab is bounded or not to the walls...This should be filed as a bug IMO.
  6. @Wes GardnerI have a question regarding how VW handles worksheet calculations for component areas of the same Wall Styles with DIFFERENT component offsets in the OIP . The fact that the most obvious shown wall height in the OIP is not accurate will bring all users to hesitate and question VW when we try to use it's BIM data. In your Split Level Model both main floor walls (shorter and taller ones) show up in the OIP as 9'-0" height...when they are clearly not the same height? So my question is; Despite this OIP wrong information will VW calculate component areas accurately in a worksheet? This stuff need to be CLEAR AND ACCURATE as Serious monetary consequences will result in sharing data. Thanks
  7. VW needs to have a setting in VW Preferences so that when I import anything, let's say a "Material", I am able to have mapped that it's dependent sub-orjects like Texture and Fill will land in a preselected "Texture Folder" and "Fill Folder" as opposed to creating a new folder (in this case a zNested Folder). Because my files keep getting messy and I feel like the maid wasting a lot of time re-organizing. ....will be funny in 20 years from now for me to revisit this wish and still nothing done.
  8. Maybe VW should just ditch their Family product Redshift for AMD Radeon ProRender....https://architosh.com/2021/11/amd-supports-hip-based-rendering-for-blender-3-0/ Using GPU & CPU to it's max! Many plug-ins available already here https://www.amd.com/en/technologies/radeon-prorender ....but not for VW unfortunately More AMD ProRender info here: https://www.amd.com/en/technologies/radeon-prorender I'm fine to use Redshift...but you gotta make it work with AMD on PC
  9. @Matt HagenGot it, 2 WinDoor objects far in space. Deleted and all good now.
  10. @Matt HagenGotta run get my Daughter...but pretty sure your problem is that there are stray items floating off in layer space, super far from the origin. That always causes problem. turn on all layers and classes, do "select all" from the edit menu and then zoom to selected items and you'll see how far out things are spread. Just unselect the required model geometry and delete, should do it for you.
  11. Is it something like this problem with Redshift?
  12. To expand on this request I am finding that the New Materials vs using Component Classes (as previous VW method) there are some limitations in "Materials" visual control in Viewports on a per item basis. Example, I often need to show multiple Exterior Cladding Schemes to clients, With the classes method I need to have several wall style for each cladding type and then override the viewport Class to do iterations. Now with Material, I still need to create several wall types using a specific cladding Material for each but my options now to control iterations in Viewports is to either; Use the new Data Visualization feature to override each specific Material, OR Link each Materials Fill and Texture to a Component Class...but this would just end up as previous VW method (and would be incredibly long to re-setup all the Materials already provided in the Library) What is odd to me is that with the new Materials method, I am saving on adding classes but I now have Many Materials to manage. If Material will have further implementation uses then it makes sense but not currently IMO. One thing that materials need is the ability to be used in Section Details in Viewport Annotations, as you can see in the attached screenshot we need to be able to select which Material Part we want to use (Fill, Texture or Hatch) AND we must be able to control the selected parts Scale/Rotation/offset(alignment). With such a system then we could use the same Materials at deferent scales in Layers AND Viewports.
  13. When I want to switch the TBB Style in the OIP the Sheet Layer page size should be synced automatically. Since the Sheet size is already set in the TBB Symbol Style edit dialog box, it seams redundant to have to set this twice! Currently, Visually the sheet will not be resized until you edit the page setup in the "Sheet Layer" so I would just be shifting the setup work elsewhere and not automating. What I think needs to be done is flip it! Add a "fit to TBB Style sheet size" option in the "Sheet Layer" page setup options so that everything is controlled by the "TBB Sheet Style". I think this is a legacy quirk as "TBB Sheet Styles" are fairly recent. See further discussion in forum here:
  14. @Nikolay ZhelyazkovExactly! This way when I want to switch the TBB Style in the OIP the Sheet Layer page size is synced. Since the Sheet size is already set in the TBB Symbol Style edit dialog box, it seams redundant to have to set this twice!
  15. @Nikolay ZhelyazkovNot quite, as Visually the sheet will not be resized until you edit the page setup in the "Sheet Layer" so I would just be shifting the setup work elsewhere and not automating. What I think need to be done is flip it! Add a "fit to page" option in the "Sheet Layer" page setup options so that everything is controlled by the "Sheet Style". I think this is a legacy quirk as "Sheet Styles" are fairly recent.
  16. @Rob NykolaishenNo I am on Win 10 Pro, just updated my old signature...I guess we could blame my GPU as it's 12 years old now....so it could be system based maybe. New computer arrives next week so i'll know for sure then. Thank you
  17. @Pat Stanfordif the VP's are set to 300 DPI and their fine, might be just a Bug for PC?. My GPU is up to date but an old EVGA GeForce GTX 570, I have a bunch of new computer parts in the mail. I submitted link to this post as a Bug so maybe someone at VW will be able to check it out... Thanks for trying to help out Pat...again!
  18. There appears to be a replicable bug with Materials, if you take any Library Materials and change the Texture and Fill to be "by class" the Materails updates correctly. But if you go back and try to specify the Texture and Fill only the Texture can be changed back to it's initial state...Material's Fill remains sticky...I have attached a sample file and I have replicated on blank test file. come on V Dev's Materials sticky FILL.vwx
  19. Many good requests, with a 2012 Vintage! Import Stories and Levels from one project to another seems reasonable….if l have already setup a split level on another project, I should not have to copy it manually to a new project just because my template file is setup differently!
  20. @Pat StanfordI just checked and they were at Low (Shaded render mode). Artifacts still present if I change to High or Very High. I have attached the file.VW BIM TEST walls slabs layers stories.zip
  21. I just ran into this on a test file, I simply changed the DPi of my Sheet from 72 to 300 and the viewport update renders artifacts. I repeated the process and same. But if I go down to 100 DPI it's ok, at 200 DPI the artifacts come back. Let me know if this is a known Bug. Thanks
×
×
  • Create New...