Morph to railing post 2d view problems

[Anonymous]

Hi all,
I made a morph for a custom railing post. I added it to the Object Library and I can select it with the railing tool.
It works OK in 3-d but the plan view is not working.

If I keep as how it defaulted, there is no post showing on the plan.
I looked around online and in this forum and fiddled with the 2d script. (up till now the 2d script was empty) I got the posts to show by doing this, but then the plan view showed the posts offset (both x and y) and rotated 90.

I really don't have the time to learn scripting. Can anyone just make this thing work normally for me?

Thanks,
A-Cad 21

[Bruce]

I haven't played around with the behaviours of a railing post, when created in this manner - but instead of trying to create a 2D script (leave it empty), go to the 2D Symbol instead. Then you can just draft what you want.

[Anonymous]

Hi and thanks for the reply.
Here is what is in the 2d symbol. Nothing shows on plan, just an empty space where the post should be between the glass panels.

When I did manage have it showing in plan, these posts were offset and rotated from the rest of the railing graphic. I think it needs some script to show, I just can't find anywhere in the one-line scripts I used that would cause offset and rotate.

[Anonymous]

Here is what my 2d railing shows in plan:

[Anonymous]

You can see that the original (morph) post is at the end, and the rest are located but don't show.

[Anonymous]

And here is what shows in 3d. Note that the first post is the original, and the rest are within the railing tool and are all rotated 90.

While the 3d is nice to look at, what i really need is the plan view to work.

Still optimistic . . .

[Bruce]

I'm still figuring out the intricacies of scripting the 2D for posts, but what I've worked out so far:

It seems the 2D Symbol part is a bit screwy - it scales the symbol by a funny number; don't know why.

However, to get around this, paste this code into your 2D script

FILL gs_fill_type

PROJECT2{3} 3, 270, 3 + 16 + 32, 1 + 2 + 4 + 8, gs_back_pen

Then unhide (click on the red X beside the parameter so it's off) the following parameters:
gs_2D_representation
gs_fill_type
gs_back_pen

Keep in mind that the axes running vertically on your screen in plan (the Y axis) represents the railing reference line (I'm deducing this). So if your posts are rotated 90° to what you want, rotate the geometry you use to create it before saving as an object.

What I can't figure out is how to get the post to be 'hidden' beneath the top rail, but I hope this helps.

[Barry Kelly]

I am only just starting to play with all this myself.
I think the reason the 2D script for a post is blank is because the plan representation is controlled from the master railing object settings (see attached image).

It seems that by adding your own script it overrides these automatic settings?
I haven't tried scripting my own 2D script yet - but I have created my own post object (with no 2D script) and just used these default settings.

This is incorrect.
In the 2D script there is a macro CALL that adds the floor plan representation features.

call "RailingPostSymbol_m" parameters all

See later post.


Barry.

[Bruce]

So how did you create your own post, give it a 2D representation, and maintain those options you've highlighted?

[Barry Kelly]

Bruce wrote:
So how did you create your own post, give it a 2D representation, and maintain those options you've highlighted?

Sorry I wasn't thinking clearly that you would not see this when saving a morph as an railing post object.

I actually just took the 'railing post 21' object, saved as with a new name and replaced the 3D script with the script for my post.
I am sure you could just copy in the morph script and adjust the material and pen variables to suite the parameter variables in the original post object.

In the 2D script it CALLs a macro that has all these options - so there is something in the 2D script.
You might also be able to add the CALL into your morph object but you would also need to create all the necessary parameters for use in that called macro.

Barry.