Jump to content

gester

Member
  • Content Count

    629
  • Joined

  • Last visited

Community Reputation

7 Neutral

1 Follower

About gester

  • Rank
    500 Club

Personal Information

  • Occupation
    architect / 2d-animator
  • Homepage
    www.gesterworks.net
  • Location
    poland / austria

Recent Profile Visitors

1,058 profile views
  1. hi, 1. is there a way to store the alternative cooordinates' system (the alternative angle) for future use? 2. is there a way to block the z-direction in perspective view (leaving only two vanishing points x, and y)? thanks rob
  2. the trouble is that i can adjust the spaces that are completely under the roof, spaces that are partially under it i cannot 😞 edit: i've found out: it's the height and the bounding objects combined 🙂 it works 🙂
  3. thanks, wes, cool 🙂 again, the darkest area is under the street lamp ;) i thought, though, i could start my conceptual model with the spaces, but for the slopes i need the roofs first. ok, i can live with it. thanks again for pointing it out. rob
  4. hi, i believe to have read about a possibility to have space objects with slanted "roofs" in 3d view. does anybody know how's about it? we'd need it for macro bim (factor calculations by cubic metres of raw volume) along with the differentiation of spaces above 220cm height, between 140 and 220 cm (counted with 50%), and below 140 cm height, not counted at all for the finished space volume. or should i post it in the wishlist? bye, rob
  5. hi, i remember to have read about a vectorworks ability to render images with two styles that merge into each other in a gradient mode. i think it'd be two images on top of each other that have the opposite transparency gradient. not the one present in the jonny pickup's vectorworks tip #437, but the one that comes from 100% transparency to the 100% of the image (_not_ of some mask !), in order to let the bottom layer to show up in the reversed way... it this possible for a rendered viewport on a sheet layer? thanks, rob
  6. i have checked the bounding box, and it displays proper values even for rotated objects (i.e. it doesn't simply take carthesian values)...
  7. ok, 1. the result is the wall not having the components in the model tree (solibri model viewer), but the wall itself is getting all materials listed. i'll have to check if the components list correctly in 5d applications for cost calculations. 2. as a general notice: yesterday i was giving a workshop with somebody showing the ifc data mapping in archicad. the overall impression i've got from the participants was the simplicity of ifc assignment and mapping in vectorworks compared with archicad. of course, if you want to have it in a sophisticated way, the possibility to attach data is more developed in archicad, but it's a steep way to get acquainted with the procedure. you have to grab and insert data in many locations in the software. 3. btw, is there a way to reduce the amount of decimal places in the bounding box's x/y/z values? now i get 6 of them... thanks, rob
  8. thanks, mihail, it makes sense 🙂
  9. one more question: how to remove a custom pset (based on record) from the ifc data mapping list completely? the more new records i use for psets, the more messed up the overall list gets... rob
  10. i take it back, this with the bounding box. it calculates the values _correctly_, not according to the carthesian system. how about the components' listing?
  11. hi mihail, thanks, i see this, too 😉 as for the bounding box: the trouble is that only recognises carthesian dimensions (x/y/z), so if the wall is horizontal and vertical, the values are different for the length and thickness (they are swapped). i don't even try to think of walls under different angles 😉 polish window is a bit different as the us one, and it doesn't use styles. unfortunately the parametric object parameters' list is very short, way shorter than the us one. but here's another thing: the wall style. i have a style with 3 components that i want to extract in the 'material' pset automatically. everything that the style can understand is the component, the first component. or am i missing the right formula? i've tried with component(x).name, componentx.name, all to no avail. is there a solution for those 3 (different) values? and is there a chance to map a thickness value afterwards in the same data row? i'm gradually getting nuts with it... thanks, rob
  12. hi, for some workshop i'm just adding a custom pset made from a record. the issue is to make a pset field for the wall with the value of all window openings. the window gets a separate custom pset. is there a way to connect those values? i know the records are not that sophisticated as the database reports, but they use style and object data, maybe there's a way to solve this? the window-record.field-value doesn't work in the wall pset... thanks for any clue. rob
  13. i've just experimented with separate records, attached as psets. there in a possibility to insert any data to any object. rob edit: 'any data to any object' under the condition that these are manual values. some field values can be retrieved from objects automatically, but i can't figure out the rule behind.
  14. here we go a different route, the polish version has another window and door tool, coming from the design express one, and used in the dutch, french and polish versions. we have other parameter fields that we can display both in the automatic schedules (there's a special tool for it) and in the database search. but i hear you here nevertheless. rob
  15. is the plugin version too old?

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...