Dieter @ DWorks
-
Posts
2,825 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Dieter @ DWorks
-
-
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....
-
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....
-
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.
-
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
-
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.
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.
-
Yes, but that would be the easy way out
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.
-
It sounds like you are trying to create a legend. If so, then you could take a look at this plugin: DLegend
-
there's but no way to change the manual bounding to the 'pick boundary' when the slab is already created, if that's what you mean. the selection returns to 'manual', when clicked.
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.
-
Years ago I used the Handrail (straight) PIO and configured a variety of Fence Styles. Although not perfect it made for a very quick approximation especially when stretched between Post symbols made for this purpose.
The top rail was removed by assigning to a class that gets turned off. Unfortunately this is limited to the shapes possible with the Railing PIO and no pickets or dog ears, etc.
Always wondered why something like this wasn't part of the program.
You can also combine multiple handrail pios to form more complicated fences/railings, even whole screens...
-
@dieter
i still don't get it. you bind them manually or using the components settings?
rob
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.
-
yeah, it makes sense. i have to do it for the last slab, which is bent in 3d.
btw, how do you mean 'bind them'?
i thought the construction slab is extending to the wall cores outer face (i can manage it manually, like in the 3rd shot from my post #197875), and the finish slab is being modelled when the walls are already set (like in real life), within the rooms, right?
and yes, the troubles remain with the door areas.
or do you mean the finish slab everywhere, not cut in pieces of each room size?
thanks for input.
rob
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.
-
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.
-
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.
-
I then directly emailed a contact at VW because this sounded like strange behaviour. They suggested to put the code in a py file and just ?import? and call from the script, then the code would not be possible to be shown.
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.
-
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.
-
But... Whilst demonstrating it to someone I discovered a bug which caused an error; when I clicked through the errors to the 'Edit Script...' button, my entire code was readable :-(
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?
-
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.
-
1
-
-
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.
-
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
-
Use a 3D symbol with auto-hybrids. Then you can have a different horizontal cut plan on each design layer.
-
And being able to just choose the language on localized versions...
-
(...) just 3D points (...)?
I don't understand your suggestion as the're actualy extruded rectangles, and I couldn't find a 'Draw-Extruded-Rectangle (x1, y1, z1, x2, y2, z2)'-procedure.
There also seems to be a problem with the BeginXtrd-Procedure , allthough, I actualy don't know if this specific problem applies to my situation.
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...
-
If it's just 3D points, why not make a structure with an x, y and z field and use that in an array?
-
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...
Possible to create trees like this?
in General Discussion
Posted
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.