Jump to content

Samuel Derenboim

Member
  • Posts

    379
  • Joined

  • Last visited

Everything posted by Samuel Derenboim

  1. @jeff prince , I agree, the site model needs a little work. I have learned by using the site model tool ends up being problematic when using hardscapes and actual cutouts and site modifiers that I've resorted to using Nurbs surfaces, and mapping 2 dimensional geometry on the produced 3 dimensional surface. Sure, it's not parametric, but its a solution that isn't impossible to solve. I've also had many a problems before, some severe, some, not so much. (I.e. the way vectorworks calculates surface areas for walls, windows etc..., energos, the way VW tabulates records and it's inability to divide 0 into 0 without getting an error, among many others) Tech support wasn't able to help me much either. It's ok. I still found a solution. Regarding the contour problem, let me check it out, maybe i can creatively come up with something. Regarding export to C4d and exporting alpha channels shouldn't be such a big deal. I know in 3d max and / or in sketchup / vray - you can use a single image as an alpha and as an overlay if I'm not mistaken. VW isn't meant for that type of work. Now that Lumion, Twinmotion and Unreal Engine are on the market, real time renderers and it's entourage / foliage models should be able to replace such models. All I'm saying is that, yes, work-arounds are annoying, but it is not impossible to implement. My personal preference, I just import low poly sketchup foliage, and use that instead. Much easier to transfer to other 3d programs. If polys are too high, use a poly reducer to get the results you need. I'm just happy I can produce a decent BIM model in VW, create a set of documents, label everything, use records for everything, and still be done on time. I can't say the same for any other program. Opting out of the service select might be a financial savings for one year, but you will end up paying for it when VW solves the problems you're talking about, or creates new tools that circumvents some of those problems. The tag tool for me was one such example 2 releases ago, I don't know how i worked without it before that point. In either case, what you pay in service select for upgrading VW upon release for 2 years is probably less than what you would pay to upgrade after missing the 2 years (depending on when you have service select). Financially, it works out for the better I think. Additionally, I don't think they (service select customer service) will solve alot of problems you have. They're not intended for that purpose i believe, but they certainly are useful to get some ideas on how to solve something. They're also not the size of autodesk. You're still getting updates (more than autodesk produces), and its 2 times if not 3 times less expensive for a single seat. You're getting almost everything you want out of the software. If you want to stay in the same family, maybe Archicad is better for your needs? Have you tried it?
  2. Perhaps the new material tool will be able to fix that since it is more of a material problem rather than a wall problem. Second, had they addressed that problem separately, I am sure there would be other gripes. All I am saying is that every release won't get you everything you wanted, but I know I've gotten at least one or two very useful tools or functionalities with every release.
  3. DBrown, All due respect, there's only enough things they can squeeze into a year, particularly one riddled with so many problems outside of work. You see what's going on around us. At least be a little understanding. I for one, am impressed.
  4. PS, just making friendly fun of the users willing to discontinue so quickly. For the service select price, and / or the permanent license price, Vectorworks to this day cannot be beat in my honest opinion. That, and at least we have direct access and contact with VW programers and representatives. Yes, not everything will be done in one sitting, but, i'm sure it will be addressed. Can't say the same about Revit or Archicad, Bricsad and others...i guess each have their pros an cons. But VW drawings sure are a pleasure to look at. My point is, you discontinue service select to wait it out? Ok, you will pay substantially more later on to update. You want to transition to Revit? Sure, but be ready for a headache...or multiple for that matter. Here, take a look at this. https://www.archpaper.com/2020/07/autodesk-issues-a-response-after-architects-speak-out-over-revit/ I'll be honest, this forum remind me alot of the sketchucation forum for sketchup plugins, except that the website is hosted by the company itself. Having said that....Perhaps to satisfy the user base and get comments for free, maybe there can be a beta user team to address comments on new features? Far fetched idea, i know...but still worth a shot 🙂 I for one would sign up...if the opportunity arises
  5. I think this sneak preview will be next. I certainly think this is a welcome and definitely a robust feature when textures and objects are concerned https://www.vectorworks.net/design-summit/virtual-keynote?utm_campaign=summit&utm_content=june20bldgbiplabinterview&utm_medium=worldarchitects&utm_source=intext
  6. Does this mean that you can create database files from excel to VW as well? I.E. referential database that is used for reference for objects referencing it? That would be awesome....
  7. I've been hoping to get this into the works for a while. Great for details and great for axonometric representations that are to scale. Scale is very important in architectural presentations and construction documents, and currently no isometric view can scale the presentation properly. Does anyone feel the same way?
  8. @Josh Loy Does this include hidden line processing / rendering in viewports? I know that it wasn't supported for multi threaded computation. Has that changed?
  9. Looking great! @JuanP , Would there be a capability to move the edges of geometry as well?
  10. Don't know if anyone has run into this issue before, however, data tags with text for some reason scale differently than symbols do. From what I understand, data tags scale at page scale, where as symbols scale at world scale. When I take a symbol, and at 1:1 scale w/ size 10 text, the true size of the text inside symbol at 1:10 would be 1 instead of 10. Data tags automatically adjust its size based on text size according to design layer scale, and as a result cannot be truly scaled based on its world size. Is it possible to give data tag a world scale so that the text would adjust based a 1:1 ratio in the design layer view port irregardless of the design layer view port scale? Data Tag @ 1 : 1 scale representation Real world scales
  11. Hi everyone, Don't know if anyone works with point clouds here, but it's definitely the future of surveying. There is a feature i wanted to enhance. Currently, there is only one right click option for extracting loci from a point cloud model, however it extracts from the entire point cloud model. My feature request enhancement is to selectively show where in the point cloud model I would like to extact the loci. If using the clip cube, it would be great to extact only the loci in the clip cube. If its a section for example, that has been generated from the point cloud, perhaps the same feature, extract loci from point in viewport (i.e. a viewport that has a min and max setting for below and above clipping points.) It is great to use if someone needs to model a terrain of some sort without having to regenerate the model itself. Another feature would be to generate a 3d model from a series of loci, or a 3d terrain, but it would not generate the object if it has overlapping elements / loci in it. So i.e. to generate a model from a point cloud set of points that are spherical, or vertical. Just a thought. Thought Id share these ideas in the forum in case anyone runs into similar requests in the future. Versus
  12. @Tamsin Slatter Your suggestions for the tag tool regarding the bounding boxes is an excellent idea, don't know if you already submitted this enhancement, but I second the motion to add that feature (along with @Michal Zarzecki I presume). I agree that the tag tool needs multiple additional functions in order to use some of these things properly. Particularly, the feature that is sorely missing is simply getting the tag to read the Z in reference to the story. It should also understand what level in the story it might be referencing. This pertains to one of the questions you ask - how would you do it in plan mode? In my opinion there are two ways - either copy the z value of the symbol in reference to the floor elevation (not absolute zero), or copy the elevation of the level the symbol or PIO is on - i.e. - ceiling elevation, FFE elevation, T.o. slab elevation etc.. in both a numerical format and perhaps also callout the level itself, that way if it needs to be changed from the tag level, it can easily be done so. These two things can be done in plan mode without going into 3d or providing a working plane for the object you are referencing. This might be particularly useful since i have a feeling you guys might be integrating levels in symbols as well (or so i presume) Just a thought. What do you think?
  13. Hi everyone, I know there is a simple fix to do this, but wanted to inquire within. The chart below shows Areas UA and UA averages. In order to get UA average formula looks like UA / Area. The bottom (totals) row returns the correct value, however the table cells in the database return the incorrect value. I know a conversion must be made or something like =value () or num2int or something. Does anyone know the correct formula to do the math properly ? (the UA column are summarized by sum) Here is another example. The Table columns showing wrong are doing the math in the table cells because they are summarizing and adding the values. Formula under the 1st (from left) column with the word wrong above should calculate 433.2 / 8374.571 = .0517. It shows 4.3038 because it summarizes and sums all the criteria for the values. The same issue is the other columns. The totals cell at the bottom has the correct answer because it is not using a database header.
  14. Would it be possible integrate an option to modify edges of 3d geometry ? Seems like a standard option in various 3d programs. Though it could be useful here. Now it is only possible with taper edge, which can be quite confusing to use. What does everyone else think?
  15. No problem. Here is a sample file. They try to do the same thing, but the format by which the table is laid out from the above excel file would not be possible. If you set up columns for each of the cardinal axes, they will return 0 because each record is counted only once per row. Thank you again @Pat Stanford Test Worksheet_Geometry Method.vwx
  16. Thank you @Pat Stanford You're right, I didn't get into detail of how it worked and checking part of the file. My concern is if there is a single crash or problem on one computer, how would the information be saved and would it affect the integrity of the master file that is being worked on. I also noticed that the larger a file gets (annotation + BIM model), the harder it is to work on because more ram is required not withstanding any other unknown conditions. The more gears involved ,so to speak,, the easier to cause problems. Hence the solution for referencing information and using reference files to do annotation in a separate one.
  17. @jmanganelli What you say makes 100% sense. That is why i bypass the guess work and do the calculations from wall areas and other tricks with different types of geometry with records referenced in the file. However, even the areas of exterior walls are very difficult to get given different conditions of wall types and walls. Wall surface areas still cannot be calculated properly (curtainwalls in particular). I would even go so far as to say I'd be happy if VW got out of the energy modeling department, and simply fixed the current toolbase in order for the community to assemble together and make one that suits our needs.
  18. @matteoluigi no, was referring to project sharing (where two users can work on the file simultaneously. I thought that was what you were referring to.
  19. We haven't implemented that yet as I've head many complaints about projects not getting saved, problems assigning layers, etc... How is your experience with sharing a single file with multiple users?
  20. I came across this problem recently and I think adding these two functions into tags would be the solution. Let me explain : There are numerous times when we as professionals need to provide information on construction documents that reference a specific element inside a unified workspace. I have been trying to unify various different code references to a single type of space object reference system without re-creating the their ID's from scatch all over again. Let, for example, take building code and lighting areas. 1. For building code - in order to analyze any spaces, i have come to the conclusion that a space would be described the envelope the building code dictates. In commercial spaces, this can be resolved by creating a space of all tenancies into the design layer, or into another design layer overlaying the plans. However, this is where the challenge comes in. Let's say you need to calculate the number of fixtures (i.e. takeoffs) by space. Or more importantly, let's say you need to provide a tabulation of the individual spaces for energy code - note by tenancy, but by rooms. What do you do? a. Option 1 - provide a single space for every room. That is the easier solution to showing on a worksheet the number of objects in a room. But, what if you also want to use those spaces to calculate occupancy for every tenant for the building code? You would essentially have to provide a record tenancy for every room that is in said tenancy space. However, for buiding code purposes, you would eliminate the ability to create a unified tag that summarizes the occupancy for the entire tenancy. Instead, you would only be able to do it room by room. Overall tenancy would then have to be on a worksheet level. Unifying and combing different elements like building code, energy code, zoning, and program would be easy on the one hand, on the other, checking the number from a plan examiner standpoint - would be a nightmare - the worksheets would be tremendously long. b. Option 2 - provide an overlay of spaces governing their own functions. If you need to provide an overall area for a space in building code - and given that the space would provide the area, it is easy to calculate the number of people for that tenancy. If you need to show the number of fixtures for each room, another space overlay would be created that can summarize the number of symbols and what symbols are in that particular room. The problem becomes - room id's. Tenancy would have one id. Space by spaces would have another, and there is no way to link them - except for location in space by ID and location in space by Name (as the function used in worksheets). This would ultimately join the complexities of different spaces that need to be shown on various drawings into a single coherent package - because these spaces ultimately overlap each other. Tags - is something that can be shown on drawings automatically, and adding just those two function would prove to be very useful especially when overlaying and unifying many different elements of construction drawings.
  21. I don't know if this was proposed earlier, and if that's the case, just putting it up again. Wanted to request the ease of importing stories and levels from another file, or as a template, or choose to import part of stories from a different file more easily. This is especially the case if a referenced file uses stories, but the annotation file requires them to be added once more.
  22. Thank you @Pat Stanford Not sure how a script would work if there are a number of database rows that would be generated for the number of records in the document per column. It's not simply a summary of one item in a database row. If that was the case, maybe there can be some kind of field entry into a worksheet that describes the criteria and the record and field information summary you are trying to pull out. My hunch though is that that information would be summarized in one table cell. (unless I'm misunderstanding something) In this case, a column could generate multiple records, maybe even dozens, the only detail is the output of database rows that it would be limited to a specific number of columns (or simply just that column). The only way (I think) it would work is if a column had a similar hide feature for database rows that would function like new type of database header for that column, or a series of columns. That way, that dummy column can set the database criteria to be pulled out and the column limit (in case you wanted the criteria to control multiple columns rather than just one). Once you set that information, then you can generate and populate the record and field name call outs in the database row header just like you normally would in a worksheet. The only difference is, it limits the information to only two columns (or the number of columns that you specify limiting the database row criteria to be populated) See below for a diagram :
×
×
  • Create New...