Jump to content

markymarc

Member
  • Content Count

    11
  • Joined

  • Last visited

Posts posted by markymarc


  1. Hello helpful people in the know. 

     

    I have never used VW scripting to date - however thought it might be useful for the following : 

    - I have a file with about 150 or so objects. 

    - They are all named

    - They all have the same record format attached 

    I would like to create an animation where they all come on one by one (basically like an installation instruction). So I thought the easiest to do that would be if I had each of these objects sitting in its own class, and then use animation works to create what I'm after. 

    From what I've read so far it sounds like it should be fairly straightforward to create a little script that: 

    - goes through all the objects , one by one, and

    - reads either (a) a field from the record format (that contains an ID number) , or (b) reads the objects name from the OIP data set , as a selection criteria, and then 

    - automatically creates a new class with (a) or (b) as class name, and then

    - puts the object into that new class. 

    - then moves on to the next object. 

    Is that easy to do ? Can anyone point me in the right direction or help me with this? 

     

    Also, can you point me to a resource pointing out the differences / thought approaches between Vs , python etc ? (I used to some pascal programming about 30 years ago so thought the vector script sounds like it may be most down my alley 🙂 ? ) Would love to play wiht all this a bit more once I get some starting points going... 

    Thanks !
     

     


  2. I've got a BIM model of a house. It's mass timber (CLT) construction and so I am trying to export just the structural components layer (the CLT) into a generic format for engineering and shop drawings, after cleaning up all junctions etc. 

     

    The problem is that one of the walls seems to 'jump' around in the exported file - it looks like it shifts from its end point to its start point , both horizontally and vertically (i.e. one point is the same but then the wall goes off in the opposite directions from there). From what I can see it's just one wall so far that does this, it's in the same class and layer and same wallt type as others in the file. I've attache a screenshot prior to exporting and one after re-importing the exported dxf to an empty file to illustrate the issue. 

     

    What I've done to avoid any potential error prior to exporting : 

    - The walls are not storey bound (but set to /offset from layer heights etc).

    - They've all been simplified, i.e. all other components deleted rather than just switched off, then converted to a wall style that has only one component (CLT) in it. 

    - I've also unstyled the walls but makes no difference in the exported file. 

    - I've tried exporting from the original file, but also copied all walls and solids over to an empty file and tried exporting from there, all with the exact same results

    - I've tried converting to generic solids prior to export (but VW doesn't convert the walls to generic solids, so again this didn't help). 


    (Btw, I've just tried exporting to SAT - that seems to work fine, but it's no good for the other parties.)

     

    Any ideas what's going on and, more importantly, how can I get a working file out of my model to pass on ? 

    Thanks ! 

    Marc

     

    Vectorworks Architect 2018 on iMac Intel Core i7, 4.2Ghz, 32 GB Ram

    Original.png

    Re-imported dxf.png


  3. Struggling to get roof component junctions to work properly - it's a fairly complex geometry

    Starting off wiht 2 parallel gable roofs that meet with box gutter in the centre. No roof overhangs, concealed gutters on the outside. Focussing on one (the smaller) of the two roofs for now with its two eaves : The geometry means the eaves junctions are different on both roof faces (eaves vs box gutter, see screenshot below). I can set up the components to work ok with the wall around the concealed gutters (even though it took a fair bit of stuffing around with it), but then Vectorworks assumes the same distances that I've set for the junctions for both eaves. 

     

    So the only way I figured to avoid that was to ungroup the roof into two individual roof faces and create a second roof style with different settings for each box gutter and eaves roof face. The problem with doing that is that then Vectorworks seems to use the same offset for the ridge, as it is not linked to the other roof face anymore (you can see the outer skin / metal cladding I've offset from the box gutter in the centre to the right point but it now also offsets that component from the ridge). Using the connect/combine tool doesn't work to fix it. 

     

    Is there a better way of doing this, or has anyone managed to create a roof with a situation similar to this ? (I'll attach a second screenshot of 3D so might make more sense then)? 

     

    Any ideas ? 


    Cheers

    Marc

    Screen Shot 2019-05-30 at 12.31.07 pm.png

    Screen Shot 2019-05-30 at 12.37.50 pm.png


  4. 5 hours ago, Andrew Pollock said:

    I will add my two cents about my iMac Pro (8 core, Radeon Pro Vega 64) experience. I mostly do 3d design work and walk throughs in open GL. The video card makes open GL work much smoother and now that its not crashing anymore (hopefully) I'm very happy with the machine. Simple 2d work is only bit faster then my old 2012 27" iMac, but when my 2D work has many bitmaps there is a great improvement in speed. Since I keep multiple programs open, some running in the background while I work on VW, I believe the extra cores are helpful. If I'm creating an animation, I can jump to Mall or Word and I'm not aware at all the a rendering process is going on in the background. This was not the case in my old machine. If one wanted to optimize the VW experience on an iMac Pro, the 10 core machine has the highest single core speed. If you are doing a lot of long Renderworks rendreings or cinema 4d work, Mac my not be your best bet.

    Thanks @Andrew Pollock ! Great summary . Now I feel like I should go back and check what the exact specs were that I've been working with to date, so I can better compare 🙂 Cheers 

    • Like 1

  5. On 6/2/2018 at 7:38 AM, zoomer said:

    The normal core speed is when all cores are working.

     

    As not all work is multithreaded often some cores are not in use.

     In this case a single (or a few) cores can run at even higher clock speeds.

    Without exceeding specced temperature or power consumption.

    That is the maximum Turbo Boost speed.

    This is normally for a single core only while others are sleeping

    (nowadays sometimes even 2 cores)

    If more cores are active that speed is reduced step by step.

     

    like you can see here in the tables :

    https://marco.org/2013/11/26/new-mac-pro-cpus

    THansk @zoomer - that makes a lot of sense of these figures finally ! Thank you so much !


  6. Thanks @JimW . I do use Renderworks, but probably mostly to present shadow studies, or in elevations etc as a white card model with hidden line rendering over the front of it, or something along those lines. These viewports usually take 1-2 minutes to render - so do you reckon that time could be increase by 10 vs 8 core, or is it too marginal to be relevant? 

    Thanks for all your help everyone , I'll let you know how I go with what I get in the end 🙂 


  7. Thanks @zoomer for the excellent thoguths and explanations. Seems to all make sense. 

    What I dont' understand is the 'turbo-speed' vs the quote speed (4.5 Ghz vs 3 in the 10 core, or 4.2 vs 3.2 in the 8 core). What does the turbo mean, and which one is more relevant? 


  8. Looking at purchasing in iMac Pro, mainly to run Vectorworks 2018.

    Small to medium architecture projects, but doing BIM, often combined wiht scanned sketches etc, so we often have very large file sizes (200-400MB) and slow performance on our iMacs, particularly in 3D and when entering viewports. So I am trying to figure out the best combination for our purposes. Thinking of an iMac Pro with

    - Vega 64 with 16 GB Graphics

    - RAM - unsure, tending toward 64 GB. Is it worth it ? Or would there be a dramatic difference even going towards 128 GB? 

    - Cores : Seems that the more cores, the lesser the clock speed is on the iMac pro? And what does the turbo mean? So I am thinking :

    either the 8core 3.2GHz Xeon with turbo boost up to 4.2 GHz, 

    - or the 10 core 3.0 GHz Xeon with turbo boost up to 4.5 GHz . What would give better performance with Vectorworks ? Is it worth spending the extra $800 on the 10 cores? 

    Really trying to find the best value for money in this and making sure I set the right priorities where the money goes :-) 

    Would love some comments from people who know more about this (or have purchased something similar) than I do !

    Thanks

    Marc

     

 

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...