Jump to content

Art V

  • Posts

  • Joined

  • Last visited

Everything posted by Art V

  1. @TID Regarding the healing, some CAD programs have a repair function though it can be named differently that checks the geometry and fixes it where possible so that it become usable again. Sometimes it is possible to "dissolve" and object to make it a generic solid and then convert it back to a mechanical object again and parametrize it to make it a fully functional mechanical object. What STEP version did you use for export? Can you share an example STEP file that would show the issue? ODA is working on a STEP engine that should allow for sharing of mechanical models with functionality more or less intact, somewhat like what IFC is for BIM. Until then you have to expect that functionality that you have in one program may get lost when exchanging to another program through STEP if it cannot interpret it. For more info on ODA's plans with STEP you can read this article: https://www.upfrontezine.com/2021/11/upf-1111.html
  2. That would be nice, especially on high DPI monitors set to 100% display scaling it would be nice if e.g. the object info palette could display text a bit larger for e.g. 27" 4K displays whereas it will probably look ok on 32" or larger monitors.
  3. This is true to some extent, except that Bezier control points in DTP software have point/handle manipulations options that Vectorworks doesn't (yet) have and are therefore easier/smoother in use whereas it is a more tedious experience in VW. E.g. where in DTP software things can be accompished by rotating and extending the control points you have to move the control point in VW until it matches what can be achieved quite a bit easier in DTP software. Especially with curved lines a bezier pen tool with associated controls like in DTP software would be really nice to have as you can create curved lines quite a bit more efficiently, not just for those coming from a DTP background.
  4. Not a braceworks user but I did have a similar issue of differences between calculated and real world. One thing to check with the manufacturer's tables is whether these are calculated or measured data. In my case the supplier was using calculated data and there was a rather significant difference with measured data in this particular case even though their and my calculated data (based on theoretical values) were basically in agreement. With things like trusses I would assume that the manufacturer has done load tests etc. and use that for their tables but you never know for sure until you ask.
  5. So far I'm not noticing much difference compared to V21 when it comes to stability. Are you perhaps using add-on applications? Sometimes those can cause some stability issues with BC by itself or conflict with another add-on application and then cause stability issues. Or it could be something from other installed software/OS updates that is causing a glitch. Refreshing the OS install may get rid of some of those things causing problems. I know it did solve some issues in the past on my Windows machine, including issues with VW This might be worth trying if you have done update over update over update on the OS and/or software.
  6. @Martyn Horne Thanks for the invite. I noticed you are using zoom for this summit which unfortunately is a bit tricky to use on my setup as it seems to confict with some other installed software. By the time that gets solved the summit is probably over so I'll use the forum roadmap section for this 3D constraints topic.
  7. Didn't get to it last time but this time I did an audit with fixing errors in the drawing and that solved the dependencies viewing issue. This basically requires having a DWG based CAD program because VW cannot do this upon import as far as I am aware. ODA (Open Design Alliance) has a viewer and converter on their website for Win/Mac/Linux, if I recall correctly the converter can do an audit to fix issues when converting to a different dwg version (or even the same dwg version). https://www.opendesign.com/ @Olivia-OBryan maybe this ODA viewer and/or converter might be an option to install on your machine to view/fix DWG files if they cause issues upon importing in VW2020.
  8. @Olivia-OBryan Attached is your uploaded dwg file with the self-referenced dwg xref removed and the drawing file audited (169 errors fixed). It is now also possible to look at the dependencies without freezing BricsCAD so it was probably some corrupted data inside the DWG file that may have been causing issues during import in VW2020. Could you try importing this file to see if it works now? LENXR1 (audited).dwg
  9. @zoomerRemoving the self-referenced xref worked just fine on my measly Windows laptop. Did you try it on your Mac or on your Linux machine?
  10. Doesn't crashing imply that it is lost so that in essence you did get rid of it? 😁
  11. Or... VW could license the Parasolid kernel 3D constraints/parametrics so that it is a bit easier to create straightforward parametric objects without having to get into Marionette or scripting. For more complex objects scripting will still be necessary though.
  12. As well as OpenType feature support for e.g. real fractions beyond the standard 1/2, 1/3, 1/4 etc. that even not every font has.
  13. This is one of several reasons why, as I already mentioned, I don't like using viewport annotations. I'd classify the OP's issue as a bug in this case as it is not working as it should. Even if it would align with the design layer and stakes would report correct coordinates anything that would extend the viewport size would then alter the coordinates and when one is not aware it is a recipe for trouble.
  14. You would need either a DWG based CAD program to view, and fix if necessary, these things or a viewer that can do the same. I doubt that VW would recognize a self-referencing dwg file upon import. Regarding the depencies, it could be anything from fonts to textures, (missing) external references etc. and with 400k+ objects it will take time to find out what object(s) might be causing the issue. Generally speaking any non-readable (or corrupted) data should simply be skipped on import and a message should be shown that data/objects were skipped on import because it couldn't be read/interpreted, without crashing the program. VW does tell things didn't get imported but that is usually non-compatible things or missing references etc. If it crashes VW but opens apparently ok in a DWG viewer/CAD program then it is most likely that some geometry or data is at fault and then having a DWG based program would be handy to have to be able to dive into the file and fix it. It is too bad that there is no longer a free version of Draftsight as that might have been a suitable option to have alongside VW.
  15. There is at least one issue with the dwg file, it is referencing to itself twice With the bind external references it will import 900k+ objects, with ignore external references it will import 475k and something and at first overall glance both imports look the same. Both imports hang a little while around the 80-88% mark but complete the import. The 2nd import is faster than the 1st import though. What happens if you import with the ignore external references selected instead of binding external references? Another possible issue is with the dependencies, Vectorworks might be ignoring those but BricsCAD becomes "not responding" when trying to list them in the drawing explorer. All of us who have replied so far are at least on VW2021 and those of us who could import the dwg are all on VW2022. VW2022 has apparently better dwg/dxf import than VW2020 so it could be that there is something in the file that causes VW2020 to not complete the import and/or crash where VW2022 will continue.
  16. Of it also happens on your windows machine (the Alienware 17") what you could try is to refresh Windows. I had a program that wouldn't even start up properly and another one crashing quite often. Because of a big crash causing Windows to become unstable I did a refresh and sudden that one program could be installed and run properly and the other one had far less crashes. All those windows updates and semi-annual upgrades do create quite a bit of junk, include software updates etc. and there may be clashes in the background. Or it could be just one program that you use that just throws a wrench into the VW operations, that is also possible. The refresh basically creates a clean slate to start working from. I assume it is possible to do something similar on your Mac as well. You could try this if you don't find hardware defects, it might be just one driver causing issues but it can be hard to find out which one or it could be a combination as described above and a refresh might solve this.
  17. Or is the reference object only meant to measure the location's real world coordinates to compare with the coordinates of the stake in the viewport so that it is possible to determine the offset of the viewport's coordinates relative to the designlayer?
  18. Not related to architecture but it does give an idea of how generative design can lead to solutions that may in the end not be that practical/useful after all even if it does meet the input criteria. https://www.engineering.com/story/when-generative-design-backfires-vws-new-wheels
  19. Or you could use the vendor provided content if it meets your requirements and convert it to custom (own) content if possible, that will save you some time. Most vendor content is ok for general purposes or if it is meeting some international standard to meet that standard. But it's not uncommon to need something slightly different so the advice to build your own content is definitely a good one. That way you will get to keep "outdated" content as well in case you need to update old drawings according to older standards if required. With relying on vendor content you risk that such content may be removed when it is updated/removed if standards etc. develop further/change.
  20. @Matt Panzer Thanks for the clarification, so moving something by (0,0) causing object attributes to change to default atrributes is a bug in itself though it is in this case it happens to solve an issue with another bug if I understand this correctly.
  21. That worked. Does that mean that whenever I move a wall it will change attributes based on default attribute settings? In theory moving an object should not reset/change its attributes. If this happens to a wall when moving it by (0,0) are there perhaps other objects where this could happen as well? If so is this by design for a movement by (0,0) or could this also happen with e.g. duplicate in place?
  22. Well... this would be another reason to avoid putting annotations inside a viewport. I used annotations inside a viewport for only a very short while because it was just too cumbersome for my use case so don't know how much putting annotation inside a viewport would affect the center location. In DWG based software the annotation on a layout (sheet layer in VW) is on top of the viewport and not within the viewport so the viewport itself is never affected by annotation on the layout. If putting annotation inside a design layer does change the boundaries and therefore also its center point then imo it is not a good design as it could cause unwanted side effects. Yes it needs to be made clear to the developers what is needed and how it should be implemented/work. Especially the latter can be quite important as it may make the difference between somewhat useful or really useful. E.g. in my other CAD program they implemented something that solved a quite major issue but the implementation while not bad in itself causes a new issue that needs to be solved. Had I known in advance how they would be implementing it then I could have mentioned that and they could have made a change in the implementation to avoid that issue. Software developers are not always aware of how things are done in practice so they need to be made aware how you would like it to work.
  23. Without knowing how the solid was created my guess would be that there might be underlying geometry that extents into both sections and causes the two sections to be treated as one object. I've seen similar behaviour in other software for that reason. But there ungrouping solves the issue. What happens if you convert the solid to a generic solid and then section it? Do you get two different objects in that case?
  24. In theory the 3080 should be a noticeably faster card IF Vision can and does use it to the full extent. Vectorworks system requirements advises a RTX 2070 for a mid-level profile and a RTX 3080 for a high end profile and states that in general the more powerful the graphics card the better the performance could be. Basically, based on the system requirements and without knowing what you are designing... if you have drawings loaded with Vision equipment then a 3080 would be advisible, if you have modest amounts of equipment (e.g. small to medium sized venues with modest amounts of equipment) then a 2070 might be sufficient for the near future (2-3 years). If you want to use the card for e.g. the next 5 years and expect your projects to get larger then it might be worth to invest in a 3080 anyway for futureproofing because Vectorworks will be offloading more and more to the GPU in the longer run. Having to buy two x070 cards in five years might be more expensive than buying the most recent x080 card over a 5-year period.
  25. If you really want to put the stakes in the annotation layer of the viewport then you could try to size the viewport to the minimum extent needed to show the area and position the center point of the viewport in such a way that the coordinates inside the viewport align with those on the design layer. I.e. Figure out the exact difference in x,y and relocate the center of the viewport to compensate for that difference. In theory this difference should be proportional to other viewport sizes with the same length/width ratio and same scale and a shift of the center would then be a matter of adjusting for that proportional difference. If the viewports have different length/width ratios then you would have to do the whole process of finding out the exact x,y difference and compensate the center position for each viewport, which can become quite tedious if you have a lot of viewports. In that case putting the stakes on a design layer is probably the more efficient route to take.
  • Create New...