Jump to content

Dieter @ DWorks

  • Posts

  • Joined

  • Last visited

Everything posted by Dieter @ DWorks

  1. I never had any symbols like that. I have used those that come with VW once long ago, the ones Vincent C talks about. I do have made 3D trees myself for fast rendering, but they don't render like that. The best option for those trees are image props.
  2. Auto classing should be done right, as I think it would be a hugh time saver in teams! Then they can't set the wrong class.... A cad manager need to be able to set the preferred class for each object etc....
  3. I have tried many thing, and this is what I find most usefull: You can then have the story at the z-level of the finished floor to easier work with heights. Exterior walls will go from bottom to bottom of the structural slabs, interior walls will go from top to bottom of the structural slabs, etc....
  4. Option 4: Create the floor plan with roof planes and create the rest of the roof planes on another layer, much much easier to do and you will have what you are looking for.
  5. You need to use the SetRField function to persist the values in the pio, so it can use them with PMyParam in the redraw round. You can always find more info on the developer site: http://developer.vectorworks.net/index.php?title=Main_Page
  6. Works REALLY well Dieter thanks again, the symbols are actually much easier to edit than the wall recess objects, pity we can't 'see' other objects (as a reference) when editing the symbol though. I never used the wall recess object as it's not complete. Always used the hybrid symbol approach. And you can actually 'see' other objects if you use 3D loci as a reference, though it's not the same.
  7. That depends. The time that you don't have to invest in something is time you can invest in other things you can't get from someone else, so eventually, you'll still learn and get more at the end. -just a thought.
  8. It sounds like you are trying to create a legend. If so, then you could take a look at this plugin: DLegend
  9. yes you can. Select 'pick boundary' and immediately after that, start selecting the walls. You can't do anything in between, or it will not work. Here's a picture of what I mean. If you need more details, just ask, or post a file with what's not working. I know this can be hard to grasp at first. Sorry if my explanations are not always that good.
  10. You can also combine multiple handrail pios to form more complicated fences/railings, even whole screens...
  11. When you select a slab, you will see of the slab perimeter is manually done or created by the walls it is bounded to. If you click on this, you can choose to bound to walls. I have a Dutch version, so it can be that my translations are wrong. Sorry for this. When you then set the components of the slab correctly (the setting to where it must go relative to the bounded walls), then they will cut out the wall. If it is not yet clear, I can make a picture of it. Just let me know.
  12. You can bind slabs to walls. You bind your structural slab to the outer walls, and your finish slabs to the walls surrounding them. If you set the components correctly, the slabs will follow the walls and cut them out at the correct places. You will need to add pieces where there are doors, or cut out at stairs, but it's the way to go.
  13. You could use hybrid symbols instead. Having 2 2D loci will have nothing changed in the 2D wall presentation, and be cut in 3D, if you make the cutout long enough, you will not need a lot of symbols.
  14. You need to use two slabs, one for the construction slab and one for the finish. Then you have to BIND them correctly with the right settings for both wall and slab to be able to let the walls cut out the slabs. It works, but you have to do it like VW expects.
  15. lol, as far as I know, those .py files can be read by the user, so your script won't be encrypted. Or am I missing something? It would be very helpful if someone from NVW could tell us best practices on encrypting and protecting plug-ins.
  16. I also have seen this from time to time, and it isn't a big deal as they will render just fine. It's just the wireframe that isn't correct.
  17. Ohw, I didn't know about that. If the code was inside the vsm/vso/vst file and not through an include, then this is a serious bug and it should be reported. You are sure that the code was inside the plug-in file and not through an include function?
  18. You can use a design layer viewport to show your building model on your site rotated and moved where it should be. That's the easiest way to do it if you already have drawn it.
  19. Is all of your code in the vso/vsm/vst file? Encrypting a plugin doesn't automatically include your .py files like .px files are. So you will need to make it one file and put all that into your vso/vsm/vst file in order to encrypt all. I know this sucks, but I have never got an answer from anyone on how to encrypt this in a good way. I personally think .py files should behave like.px files while encrypting.
  20. you can access all things in VW with python like VectorScript can, so also the symbols in a drawing. You can find more info on the developer page: Vectorworks developer page
  21. Use a 3D symbol with auto-hybrids. Then you can have a different horizontal cut plan on each design layer.
  22. And being able to just choose the language on localized versions...
  23. BeginXtrd works fine and you should use it if you are just creating extrured rectangles, that is if they are extruded on the Z axis. You have to keep it simple. If things are getting too hard, look at it another way...
  24. If it's just 3D points, why not make a structure with an x, y and z field and use that in an array?
  25. IMHO, palette positions should just save automatically on a replacement. The user should not have to worry about restarting VW or running the command to save, hoping it will not crash...
  • Create New...