Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by herbieherb

  1. After some research I think the info may be stored in one of the UserDataNodes. Is there any way to read this data with Vectorscript?
  2. Is there a way to find out if a light source is visible in a certain viewport? (The value that is set in the visualize-palette when the viewport ist selected)
  3. I describet the project here: Im trying to program the function with basic math but its a huge project and not very efficient in python/vectorscript. So i just asked myself, why the tool command isn't accessible via script and if it woul'd be that hard to make it accessible. Or if there is another way to get to the code of the tool so i don't have to rewrite it with my very basic skills. 🙂
  4. Is there any chance of adding the paint-bucket mode of the polygon-tool as a marionette-node? The idea is of having an input pt and the node fills the area with a polygon as if it would, when i use the polygon paint bucket at this place.
  5. Is there any vectorscript-command that lets me create a polygon the way as if it is created with the inner boundary mode of the polygon tool? I have a huge amount of polylines. And a database with coordinates and class-names. I want to execute the inner boundary polygon command at the coordinate so i have a bunch of polygons in the specified classes. This is what the geometry data looks like:
  6. Is there really a way of having parallel vertical lines when your camera is angled up or down? For example the vertical correction in Photoshop has the exact same effect like if you took the picture with a horizontal view. Even the effect of a tilt-shift-objective uses no alternative rules of perspective viewing. Still keeping the camera horizontal to get parallel vertical lines but moving the borders of the picture up or down. You can simply get that effect by having a horizontal camera and moving the border of the viewport up or down.
  7. Here is a script that automaticaly corrects vertical tilt.
  8. Use this python script to perform an automatet vertical tilt correction on the current view. Or use it this way to correct the view of a viewport: Right click at the viewport. Edit camera Run the script exit edit mode xAngleR, yAngleR, zAngleR, offsetPt = vs.GetView() vs.SetView(-90, yAngleR, 0, offsetPt[0], offsetPt[1], offsetPt[2]) Don't forget to set the script-language to python in the script editor.
  9. This is a real game changer to get all the data of the site. How does it get the data? Can we connect Vectorworks to wms, wcs and wfs servers? Can we have import options like: downsample LIDAR-data and use it directly to create a site model. Import georeferenced images as texture and map it on a site model. Import LIDAR-data as a pointcloud and use the georeferenced image as colorsource to get a colored point cloud.
  10. You can disable the hierarchical view in the class-organisation dialog with the button on the bottom right. After that you can also delete classes independent of the hierarchy structure.
  11. Normally making a process multi-threaded means you have to rewrite almost every single line of code. Also there are lot's of things that you can't make multi-threaded. For example, in all calculations where a part depends on the result of the last part. Such calculations are very common in CAD. All tools/modules/processes will never be multi-threaded capable.
  12. I woul'd only use one project file. You need to choose one cloud service. Also every user has to use exactly the same vectorworks version. That means you have to coordinate and update new servicepacks all together. Be sure to send all changes first. It's impossible to use VW2018 projectsharing with VW2019.
  13. The German support once told me that it only works on Mac. Is it possible that DialogBuilder can only be activated in the Designer version? I always get an identifier not declared error when i try to activate. Am I doing it wrong? 2019-08-21-10-27-24.mp4
  14. Ok, understood. Very frustrating that enabling the debug-menu only works on MacOS.
  15. Thx a lot. That worked fine. What exactly does the .aux method? Btw. here is the Tool where i needed the code:
  16. The tool draws foils as intelligent objects. They can be drawn, edited etc. like a polygon. Thanks to additional snap points, several layers of foils can be easily drawn on top of each other. Foils can be mirrored to the other side of the control geometry via the flip checkbox in the info palette. Download: Folie Plus 0.2.zip
  17. Is there a way to get the handles of the geometry of complex line styles? I need to get the thickness of these lines.
  18. Thx for the bugreport. I'll check it out when I have some free space.
  19. Just as a comparison value between desktop and laptop: For the price of the marked MacBook Pro you get a (Windows PC) with the multicore performance of the top computer in your screenshot. (While the single-core performance would be about the same.) A desktop will give you no improvement for site models. Single-core performance is crucial. Laptops today are as fast as desktops at these tasks. I would rather recommend you to optimize your models. Use max. 5000 points as model data. Simplify modifiers with curves etc. Even terrain models of very large areas need only a few seconds to update, if you handle it correctly. Now to the original question: The idea with the external graphics card seems impressive at first glance. Unfortunately, the cases are so expensive that it's hardly worth it in your case. Important for the decision is what exactly you do in Vectorworks. If you render often, you need a lot of multi-core power. That's where you're most limited with a laptop. If you're doing other things on the go, a gaming laptop with a good graphics card will do. Depending on the size of your models, you may need a better graphics card. For a clearer recommendation, we need information about your current computer. Graphics card, processor, RAM, etc. Then we need to know how busy your RAM is when rendering etc. and your VRAM is when viewing in OpenGL. We also need to know which tasks you intend to do at home and on the go.
  20. Im trying to modify the node, so the marionette is also able to scale the symbols. The new node works fine as long as i don't use it with symbols that contain image-props. When i use them the texture is not scaled. As a workaround i can duplicate the marionette object. As soon as i delete this duplicate all the textures are scaled correctly in the original marionette object. It's like they redraw when i delete the duplicate. I also had this issue with image props within scaled symbols in a converted file from vw2018. I suspect that something with the display of image probs in scaled symbols is not yet correct. Here is a sample file of the marionette object: fill area with scaled symbols.vwx I also tried to implement the workaround into the marionette-node. When i use this script on a symbol with an image-prop inside it reproduces the issue. hSym = vs.GetObject('test') vs.SetObjectVariableInt(hSym, 101, 2) vs.SetObjectVariableReal(hSym, 102, 10) When you add these two lines. It works correctly. hSym = vs.GetObject('test') vs.SetObjectVariableInt(hSym, 101, 2) vs.SetObjectVariableReal(hSym, 102, 10) hDel=vs.HDuplicate(hSym,0,0) vs.DelObject(hDel) Unfortunately these two lines don't solve the problem inside the marionette-object. Any help is very welcome.
  21. I made big changes to the script. It now exports any number of images and rendered viewports in a single command. You can find it at the bottom of this thread.
  22. Here is a new version of the script: New features: exports All selected viewports and images at once gives unnamed images a name within Vectorworks which is also used as filename appends a version number to every exported object enhanced error messages when invalid objects are selected selects invalid and not exported objects after execution export images 1.0 v2018.vwx export images 1.0 v2019.vwx
  23. Here is the python-script i made. It works just like the 'Make All Attributes By Class' - Button in the Attributes Palette. It's meant to add as a menu commant to allow to use it with a hotkey. #v1.3 #by Herbieherb 2019 #enhanced by MRoth def SetClassAttributes(h): vs.SetFillColorByClass(h) vs.SetLSByClass(h) vs.SetLWByClass(h) vs.SetMarkerByClass(h) vs.SetOpacityByClass(h) vs.SetPenColorByClass(h) vs.SetTextStyleByClass(h) vs.SetFPatByClass(h) vs.SetDropShadowByCls(h, True) vs.SetSelect(h) objs = [] def Count_Objs(h): objs.append(h) vs.ForEachObjectInLayer( Count_Objs, 2, 0, 2 ) if len(objs) == 0: vs.FPatByClass() vs.FillColorByClass() vs.LSByClass() vs.LWByClass() vs.MarkerByClass() vs.OpacityByClass() vs.PenColorByClass() h = vs.FActLayer() vs.SetSelect(h) vs.SetDSelect(h) else: vs.ForEachObjectInLayer( SetClassAttributes, 2, 0, 2 )
  • Create New...