Jump to content

All Activity

This stream auto-updates

  1. Today
  2. There are a number of different types of clamps, stands and so on for mounting fixtures in our library, mostly in either the ent lighting accessories folder or the ent stage folder. I have no idea whether they are as specified in the DIN spec but there are both generic options and manufacturer specific symbols. If you know the manufacturer try searching the library to see if there is something appropriate
  3. Hi, I am using student version. When creating a folder in user library this message popped up. I'm not sure how to understand it. Does it mean that when I get professional version, my created user library folders and objects from student version will not be transferred to professional version? I hope this is not the case 🙂
  4. I have explored Landscape areas with components recently. My test terrain is burning! I really prefer using LA in many situations, especially if the perimeter is curved and/or the surface shape is twisted. To paraphrase Douglas Adams narrator in The Hitchhiker's Guide to the Galaxy: Landscape areas are almost, but not quite, entirely unlike Site Modifiers. For example, the LA with component(s) excavates the terrain if the datum is set to Top of the component stack. But if such an LA is then hidden to reveal the excavation, the contours do not flow into the hole. Instead, they float at the implied terrain surface. If there is some desire to show the contours bending into the excavation, then apply site modifiers as needed to sculpt the terrain and place the LA at bottom of the excavation and set the datum to Bottom of the stack. Either way works fine. Which is to say that strategy is in play for many aspects of LA application rather than hard workflow rules. Classing of the components, the container LA, any site mods, etc needs focus to achieve the desired outcome. -B
  5. It looks like you are in the USA, so contacting Vectorworks Inc themselves is the way to go. However, as you're a member of Vectorworks Service Select, you will get priority support if you cite your VSS number when submitting. It looks something like USA 1234 1234 123. Contact options are listed in the 'Support' section of the Vectorworks Customer Portal. But before you do: I highly recommend you make use of the information in that discussion. It will almost certainly resolve this issue for you as it has done for everyone else I've helped with these symptoms. See the main article, then my comment that has refined instructions.
  6. That worked. Why the excel didn't I have no idea. As always - thank you! ...now if they would only get that column label correct - I guess it's not like the 'Organization' menu gets used very often!
  7. Export your .xls file to tab or comma deliminated values before importing. That's usually a sure fire way to identify .xls import issues, especially with new versions.
  8. Yesterday
  9. I've had my difficulties with the import tree survey tool, but I thought that was behind me after it's worked as expected the last couple times ... I watched @Tamsin Slatter 's gotowebinar on it and the cleared up a lot of issues that were not clearly covered in the help pages - like making sure each layer is activated for GIS in the Organization menu - and I have had some luck importing surveys. Thanks again Tamsin! But I can't seem to get it to work lately, and I have no idea what I'm doing wrong. There are no errors or hints from VW - it just doesn't do anything at all. I can go to "landmark/existing trees/import tree survey file..." and select the survey file and click open... But absolutely nothing happens. The menu doesn't even open. I can't even get old surveys I've used before to open now... I have GIS enabled for the file and for the layer. I entered the lat/long of the survey so they won't be created way off screen. Any thoughts? Here is a screen capture: import tree survey.mp4 Oh yeah - the GIS header on the organization menu STILL says 'elevation' instead of 'GIS' as it's supposed to...
  10. Thanks! This is great workaround and it works fine
  11. I don't think that works either. Design takes place away from the desk as your responsibilities increase, it doesn't go away... unless you take on 100% admin roles within an organization.
  12. Hi, I'm searching mounts for fixtures like specified in german DIN 15560. Does anybody know, if they exist in an library?
  13. There came a VW 2022 SP4. That seems to address some memory problems, like for Viewport updates. Will test tomorrow.
  14. DomC

    use matrix

    Haha - I think the highest level somebody reach if he can trigger others to do the work 🙂 OK, I did it with the crowbar. The script now works so: 1. Always move the points virtually on center before calculations 2. getting zangle from p1-p2 > Easy Peasy 3. for vertical segments taking p1-p3 3. I take the 3 points and turn them mathematically aligned with first segment on x-axis of the standard-coord-system. 4. then i look from coord center (from left) and geht the rotation angle by using z-difference as y coord to get xangle 5. y angle is build from turned p1-2 segment and the xdiff of that segment and the height of that segment. Try to provide a node create EM form 3d points node anytime. I imagine we can create wonderful stuff with that. placing object on faces of objects! For the moment my own need is nursed to hav a corner vertex matrix plane for the pipe-project. planes.mp4 #just crude test-coding import math sqr2 = 0.41421356237 PI = 3.141592653589793239 kRadiansPerDegree = PI / 180.0 kDegreesPerRadian = 180.0 / PI kNearlyEqualEpsilonForDoubles = 1e-13 def point_on_line_3D(p1, p2, d): #3d Points d = distance from p1 to p2 x1, y1, z1 = p1 x2, y2, z2 = p2 c = vs.Distance3D(x1, y1, z1, x2, y2, z2) new_pt = ((x2 - x1) / c * d + x1, (y2- y1) / c * d + y1 , (z2 - z1) / c * d + z1) return new_pt def DoublesAreNearlyEqual(n1, n2): epsilon = kNearlyEqualEpsilonForDoubles abs_n1 = abs(n1) abs_n2 = abs(n2) abs_n1n2 = abs(n1 - n2) if ((abs_n1 <= epsilon) or (abs_n2 <= epsilon)): # if either is very nearly zero, don't take the magnitude into account return (abs_n1n2 <= epsilon) else: temp = abs_n1 if (abs_n1 > abs_n2) else abs_n2 return (abs_n1n2 <= temp * epsilon) def DoubleIsNearlyZero(n): return DoublesAreNearlyEqual(n, 0) def DotProduct(p1, p2): return (p2[0] * p1[0]) + (p2[1] * p1[1]) + (p2[2] * p1[2]) def Magnitude(vec): return math.sqrt( vec[0]*vec[0] + vec[1]*vec[1] ) nurbsObj = vs.FSActLayer() # take care to select a NURBS curve radius = 100 segments = [] points = [] segmentCnt = vs.NurbsCurveGetNumPieces(nurbsObj) #[(xoff,yoff,zoff),(xrot,yrot,zrot)],[...]] for segm in range(0, segmentCnt): # python range is always one less than pascal pts_infos = [] vtxCnt = vs.NurbsGetNumPts(nurbsObj, segm) num_knot = vs.NurbsNumKnots(nurbsObj, segm) vertex_plane = [] for vtx in range(0, vtxCnt): # python range is always one less than pascal v = vs.NurbsGetPt3D(nurbsObj, segm, vtx) if vtx < vtxCnt - 1: p1 = v p2 = vs.NurbsGetPt3D(nurbsObj, segm, vtx+1) p = point_on_line_3D(p1, p2, radius*sqr2) points.append([p,1]); pts_infos.append([p, 'control_end']) #vertex_planes.append(False) p = point_on_line_3D(p1, p2, radius) #start radius point points.append([p,10]); pts_infos.append([p, 'segment_start']) #vertex_planes.append(False) p = point_on_line_3D(p2, p1, radius) #start radius point points.append([p,10]); pts_infos.append([p, 'segment_end']) #vertex_planes.append(True) p = point_on_line_3D(p2, p1, radius*sqr2) points.append([p,1]); pts_infos.append([p, 'control_start']) #vertex_planes.append(False) pts_infos.append([p2, 'vertex']) segments.append([segm, vtxCnt, pts_infos]) def rotate2d(degrees,point,origin): x = point[0] - origin[0] yorz = point[1] - origin[1] newx = (x*math.cos(math.radians(degrees))) - (yorz*math.sin(math.radians(degrees))) newyorz = (x*math.sin(math.radians(degrees))) + (yorz*math.cos(math.radians(degrees))) newx += origin[0] newyorz += origin[1] return newx,newyorz def get_angle(p1, p2): diffx = p1[0] diffy = p1[1] p2 = p2[0]-diffx, p2[1]-diffy x2, y2 = p2 a = vs.Vec2Ang(x2,y2,0) return a for i in range(len(segments)): segm, vtxCnt, pts_infos = segments[i] p1 = pts_infos[2][0] #start p2 = pts_infos[4][0] #corner if i < len(segments) - 1: segm2, vtxCnt2, pts_infos2 = segments[i+1] p3 = pts_infos2[1][0] #start next segment x3, y3, z3 = p3 x2, y2, z2 = p2 x1, y1, z1 = p1 zangle = get_angle(p1, p2) if (x1,y1) == (x2,y2): #vertical > no zangle from p1 - p2 zangle = get_angle(p1, p3) p3_1 = rotate2d(360-zangle, p3, p1) p2_1 = rotate2d(360-zangle, p2, p1) p3_1_angle = get_angle(p2_1, p3_1) if p3_1_angle >= 0: cw_seg_2 = False #counter clockwise else: cw_seg_2 = True #clockwise diff_y = p3_1[1] - p2_1[1] diff_z = p3[2] - p2[2] xangle = vs.Vec2Ang(diff_y, diff_z,0) diff_x = p2_1[0] - p1[0] diff_z = p2[2] - p1[2] #vs.AlrtDialog(str([diff_x, diff_z])) yangle = vs.Vec2Ang(diff_x, -diff_z, 0) vs.Symbol('Symbol-1', p1, 0) sym_h = vs.LNewObj() vs.SetEntityMatrix(sym_h, p1, xangle, yangle, zangle) vs.Locus3D(p1) vs.Locus3D(p2) vs.Locus3D(p3) vs.ReDrawAll()
  15. @MHBrown We just released Vectorworks 2022SP4, I suggest you updating Vectorworks, and if the problem persists, feel free to contact me directly at jalmansa@vectorworks.net and I'll be happy to connect you with one of our support specialist to check your files or see if there is anything else we can do. It would be ideal if you could provide as part of your signature, computer specs, and operating system.
  16. Thanks Jeremy. I've never heard this before and have been pretty lost with all the issues and crashes I've had. How does one find and contact our local distributor? Also is this connected to Service Select or would it be a different service?
  17. SimA

    use matrix

    Hallo Zusammen Nun zu der Matrix kann ich nicht mehr viel beitragen, das Thema scheint über meine Gehaltsstufe gewachsen zu sein. Anwendungsbeispiele nehme ich weiterhin gerne entgegen. Mit der Datei im Anhang finde ich meine Punkte im freien Raum. Dabei verwende ich jeweils einen fixen Startpunkt und einen veränderten Endpunkt. Betreffend Trigonometrie verwende ich meistens diese Seite https://www.matheretter.de/wiki/dreieck-berechnen-abc Zwei der drei Rotationen bekomme ich so hin. Wenn nun jemand die passende Mathematische Vorgehensweise liefert, dann benötige ich die Matrix nicht mehr. https://www.meccanismocomplesso.org/le-rotazioni-in-3d-e-gli-angoli-di-eulero-in-python/ Now I can't contribute much more to the matrix, the topic seems to have grown beyond my salary level. I am always happy to receive application examples. With the file attached I find my points in free space. I use a fixed starting point and a modified end point. Concerning trigonometry I mostly use this site I can do two of the three rotations that way. If someone now provides the appropriate mathematical procedure, then I no longer need the matrix. Nurbs und Trigonometrie.vwx
  18. It would be handy if we could view a VW model on iPad WITHOUT any online connection or 3rd party software (.usdz or sim are not VW export options)
  19. It is still lagging in 2022 sp3.1. It is a problem with the VW 2022 software. In my case--also on an i9 16" MacPro with similar specs as the OP--it is horribly slow with any 2D images. This includes small jpegs and png files up to large PDFs. Doesn't seem to matter. There are other serious lag problems, but this inability to handle 2D files is absolutely fundamental to any CAD program and I find it hard to believe that the VW staff (overworked since going to a yearly subscription model) simply can't keep up. What used to be a rock-solid CAD app is rapidly losing its reputation as these basic problems are released, unsolved. It's really unfortunate, especially since the rendering quality is now at a very high level. MHBrown
  20. 2022 SP4 is live now for all non-localized English versions
  21. I have still no clue if more memory would really eliminate my largest and worst Projects lacking on my M1 Mini 16 GB, as soon as memory pressure goes yellow. Do you have to also deal with non optimized drawings by Revit or IFC imports ? Does your memory pressure always stays green with your largest projects ?
  22. How many RAM do they use so far, maxed out to 128 GB RAM ? (or are these later Mac Minis ?) Nevertheless, the M1 GPU performance is much much better than the onboard Intel graphics in Intel Minis. If they are really still ok with 2014 Minis, I see no problem with the Studios and M1 Max. But if they will run these again another 8 years, it might be worth to add some more memory ....
  23. Apple ARM has shared Memory. This uses fast RAM modules, not as fast as typical VRAM, but on the other side there is no need the CPU calculate in RAM and send the result back to VRAM for the GPU via PCI, which is faster. Also theoretically M Macs can use nearly the whole shared memory for the GPU, if needed. (Where do you find a PC GPU with about 96 GB of VRAM !)
  24. After reviewing the response from @Amorphous - Julian it sounds like his 2D Marionette solution works (because the issue reported earlier cannot be reproduced, it is likely caused by something else). As for a 3D solution: It’s been years since I worked with Marionette but I expect it would be relatively easy to convert the result it produces to a 3D object after the desired pattern has been generated.
  25. When the M1 Mini was new I was so happy at first that I can open even my largest Projects. They need some time to load but view navigation is fluid. Just when I do some work, change visibilities, do selections, go into edit modes, memory pressure gets higher and it starts to lag. But 2D Software like Lightroom, Final Cut, Browsers or sound Editing Software does not seem to have problems with swapping memory. Everything gets a little bit slower when you access or reactivate things from SSD swap memory. There was never much speed difference between a 8 GB Macbook Air or a 16 GB Mac Mini. Exactly. For moderate to standard VW projects M1 was always super snappy.
  26. Vectorworks, Inc. has released its fourth Service Pack (SP4) for the Vectorworks 2022 product line. This update includes the following improvements and bug fixes. For a full list of improvements in the 2022 SP4 update, please visit this page. Improvements and Fixes Wall geometry Fixes issues with wall component wrapping Fixes crashes and delays that occurred when opening older files Restores the proper display of side-by-side windows inserted in a wall Rendering Fixes an issue when rendering wall components Resolves memory errors that occurred during viewport rendering Vision has resolved the network connection issues that limited the number of connected lasers on the Mac Spotlight Resolves issues with power calculations for circuits containing overcurrent devices Fixes truss corner block connections Restores the ability to create and update schematic views Resolves lighting device duplication problems ConnectCAD Correctly displays equipment symbols in a 3D rack Fixes socket labeling issues Restores the ability of non-administrative users to save changes to numbering systems Resolves errors when binding a layer to a GIS feature service in Landmark For data visualization overrides, properly applies textures per face Resolves issues with importing DWG and DXF files Fixes exporting issues with Unreal Datasmith Fixes exporting issues with worksheets to Excel® Resolves memory issues when creating section viewports Fixes problems when pressing the Delete key while editing parameters of plug-in objects Installing the Service Pack This service pack is available as a downloadable updater for all U.S. English-based versions of Vectorworks 2022. To install the service pack, please select Check for Updates from the Vectorworks menu (Mac) or Help menu (Windows). Contact us at tech@vectorworks.net if you have any technical questions or problems during this process.
  1. Load more activity
×
×
  • Create New...