Jump to content

drelARCH

Member
  • Posts

    388
  • Joined

Everything posted by drelARCH

  1. It is really quite useful. I have learned this from virtual design summit form last year ... or at least i got courage to give it a chance ... I was bit afraid of reliability of crossing resources between files.
  2. Thanks @Pat Stanfordfor looking into it. To be precise I get mixed results... I see that when I add new item to main structure of record format this works fine both way...but when I add new item to existing pop-up list (i use pop-up types quite a lot) it doesn't work reliable. Sometimes changes get through but most of time not...Most of the time I need to send back changes to origin resource, rarely other way round. I thought that in order to make it work i must every time attach referenced record format to at least one object in file. I think in past I didn't always attached referenced rf to a object in project file and tried to edit it right after resource was successfully referenced into file to see if it is working.
  3. Ok. I see I should not include second sentence in my initial post. I think it cause confusion. Anyway my intention was to describe my general workflow and approach with resource library. So is this case with record format. So back to issue I am seeing with record format. I have record format XY with some structure and data in it. I store it in my record format library file. Now I want to utilize this record format in one of my project file. So i referenced it (not imported) in project file hoping that whenever I change something in record format (because it is still in development) in project file those changes will be reflected in library file where original record format reside. And the issue is it doesn't reflect changes ...so it is not sending changes to source record format....? Hope this is more clear now. Thanks
  4. Hello, I am experiencing since version 2020 (If I remember correctly) that from time to time section viewport (horizontal section) change randomly to regular viewport creating viewport with orthogonal view: custom view resulting in some kind of mix of previous floor plan and added elevation(upside down) after viewport update...see attachment screenshot. Anybody seeing this issue too?
  5. Hi all, I dont see effect of changing referenced record format to source resource.... When I am in phase of development of any resource I prefer to have it referenced to actual file and later when fully developed I break reference a do import to individual file Am I missing something? Or is this bug as other resources likes wall, slab, roof styles when referenced works fine both way....? Thanks.
  6. Thanks @Robert Anderson for quick response. I understand where this tool is really usefull. As I said in previous post i especially like that I can hide objects one at the time. It was just me playing with the tool and I had one file opened right on sheet layer so I tried to hide viewport... I think I have fixed those viewports by creating new sheet layer and duplicating those viewports onto it. Thanks anyway!
  7. @Robert Anderson it is really useful tool to hide unneeded or objects standing in the way one by one! Unfortunetly I have used it on sheet layer with viewports and they behave out of control now (only on layer I cant select them with cursor though OIP show viewport selection, ...also they all just disappear...if I use bring forward command they all appear, but the moment I hit update for any viewport they are gone again. Same with accesing annotation space...once entered all viewports are gone and staff is too...hidden Any idea how to fix it? I deleted script, restarted vectorworks, restarted computer but still the same...?
  8. go to 'Graphic Attributes' and look for 'Stair Structure' Attributes
  9. Thanks @Matt Panzer I suppose We are getting closer to track down issue ...and I see in which area I have to be more careful... But than one thing that bother me is why section-elevation line style was deleted...? And the moment I realized lines are unstyled there was no line style resource in RM to be replaced with. This is something that wasnt only seen in last file but in every file since introduction o s-e line style...
  10. Thanks @Jeremy Bestfor looking i I have followed your instructions. New file with only 4 columns (structural member) in it. and viewport with perspective view (normal) and screenshots taken while attempting to tag objets in annotation space: I have checked position of user origin and it is the same as internal origin in both files. So I guess bug need to be submitted. My first one... Thanks.
  11. things to check: - viewports settings 'detail level' to be at least medium - class/es of components is/are visible - in advanced properties i attributes tab check 'use attributes of original objects' and maybe other things, but would recommend to check these first
  12. My latest observations: I m seeing that I have section-elevation lines in horizontal section viewport (In this case viewport name: POD-1NP-30-AS-2) that in OIP show this: Styled as expected and linked correctly to a section viewport. Now i use 'Navigate to Viewport' button to get to related viewport. In section viewports selected i go to 'section line instances' and I dont have any checkmark assigned.....? However when I place checkmark to relevant viewport (In this case: POD-1NP-30-AS-2) it creates new section-elevation line (on top of previous one) in that viewport in unstyled way. I dont know if this behaviour is related to issues with styled and unstyled section line but it might shed more light...If I can recall I would select multiple section viewports and assign 'section-elevation lines' at one go to horizontal section viewport...but I dont remember having duplicates of section lines for any given viewport...so not sure .... Ok, after all...writing this post and going over and over the described process I see that there are two types of section-elevation lines first as marker connected to any selected viewport and second as line that actually define viewport itself. I knew that already but am surprised that I having section-elevation line markers in my file. Never deliberately created one. But I guess it is effect of duplicating sheet layers/viewports and real section-elevation lines (ones that define section viewport) becoming markers...? One note after all this: I dont see much indication in OIP of section-elevation lines being marker vs real section-line and to clearly see difference... Look forward hearing your opinion. Thanks in advance.
  13. Thanks @Matt Panzer and others, I will definitely look closely if I can spot specific case and report back if find something.
  14. Ok. I see that I am able to tag obejcts when 3D view is strictly orthogonal. Issue occur when viewport is in any perspective view. Is this 'work as designed' or bug?
  15. Hello, Am I missing something obvious... when trying to data tag objects (with record format attached) on annotation layer of viewport with 3D view I see highlighted eligible objects absolutely off rendered ones. You can see in background all three posts and other parts of structure scaled down and forming some kind of different view... My viewport use hidden line renderer and is up to date. Any clue?
  16. Thanks all for the effort to find issue. I am 100% sure I accidentally didn't hit delete button on confirmation. Actually never had it presented. I do use purge function but it was definitely not the case of my last file as I try to be very disciplined about only having needed resources and If there are few uneeded I delete them in RM. My feeling is that it occurs somewhere in process of duplication of existing section viewports and correction and manipulation of section lines instances... My workflow over last couple of projects: I would have set up of few sheet layers with plans (horizontal section viewports with section lines present), sections (section viewports some connected to section lines ), elevations (sometimes section viewports [some connected to section lines] and sometimes regular viewports) and 3D views viewports. Then I duplicate at once all sheet layers and create another set of sheet layers with viewports with different set o design layers for project version 2 later if needed project 3...4etc if needed. I then need to go and correct section lines instances so there is not crossing in between versions. Normally I have one custom section line style that I use across all project files. Then typically over the time after the project is developed further I add more section viewports within one version of projects by duplicating existing section viewports and correcting position of section line in horizontal section viewports... ... well all this steps seem to me as standard workflow and shouldn't cause issues...but but
  17. I suppose when deleting any resource one should be presented with dialogue box asking confirmation? but i wasnt .....or not? can i delete resource definition in RM without confirmation? @Pat Stanford I do have couple of scripts in this file (no marionette objects) but I cant remember using any of them before problem occurred. I have scripts like 'show all', hide unselected, hide selected ...but as stated in my previous post this is happening at some point in my every file of different projects and I am sure I don't have in all of them scripts or marionette objects and literally i am starting to use scripts more often since only last few weeks.
  18. when you are on design layer and you have any custom perspective view you can correct verticality by selecting any standard view: Left, Right ... This approach is useful if your custom view is close to any standard view...then by panning you have little freedom to position view point and still keep standard view verticality ...Yes you are restricted to the standard view but still there is at least this possibility. Hope this make sense.
  19. @MGilcthis might be not accurate to your situation as I dont have time to read all the posts but I thought I share my experience. If you have gable roof and want to offset individual components from all edges then I would definitely go for slab with drainage settings applied. It might sound scary at first but it really works. Here is example of two slabs forming gable roof, one with big openning to accomodate staircase. 119% = 45 degree slope
  20. Hello vw community, Since introduction of section elevation line style I am continuously seeing some unpleasant behaviour: styled lines turn into unstyled ... accross all file. Are we aware of some bug that cause this issue? At some point in every file it always happens...and whenever i spot this just happend and want to replace back unstyled with styled line resource browser is empty of previously used section elevation style line....I have to bring that style anew from my library file ...strange My section lines are always present only in sheet layer viewports (section and horizontal section). I wonder if it has something to do with duplication of viewport with section line already present...? Is there something to be aware of...? @Matt Panzer has somebody already come up with this issue? Thanks in advance for your help.
  21. I think it has to do with Graphic Attributes: 2D top tread > tread > solid line. Try to change it there and see if it helps.
  22. what about using new function (in vw 21): ImageByDataVis Might be what you are looking for...
  23. @Mark Aceto maybe this is something that might help you.
  24. Hope soon is really very soon. All work that went into setting up surface hatches for many materials textures in plan view is useless now.
  25. Ok, it is actually not texture mapping that is causing lines of extrudes in autohybrid to disappear but wrong data visualisations settings. I am using materials across all possible objects/components in model, extrudes included and have many data visualisations set-ups based on materials. I havent payed enough attention to attribute values for pen(see attachment). Mine was set to 'none' instead of 'retain original pen'. So section viewport with <none> data visualisation drew everything correct but with data vis. applied visibility of pen line of extrudes went off. Thanks @jeff prince and @Matt Panzer for all your effort to investigate more where might be issue. Although I have found mistake there is still clue to me why all my extrudes in autohybrid have perimeter texture mapping....?
×
×
  • Create New...