[Bug?] Common edge of two objects do not display

[Hoa Tu]

Hi All,

I have problem with some objects when joined together the vertical joining edge do not display.

I have narrowed down to the test case shown in the attached file.

The object has a very simple prism:

PRISM_ 5, 1,
0, 0, 15,
0.6, -0.6, 15,
-0.6, -0.6, 15,
-0.6, 0, 15,
0, 0, -1

Any one has a solution or work around ? Please help.

Regards,
Hoa

ArchiCAD 8.1 R2
Windows XP Professional

[Vitruvius]

I've had that problem very infrequently when using POLY_ . The objects will look fine in photorender but I like to use a lot of Hidden Line persectives so you could try one of the two workarounds:

1. To get the vertical join at the elbow use LIN_ to draw it. Very fast & easy.

-- or --

2. You could play with the masking values - try substituting 13 for 15 on one of the POLY objects to see if that prevents one vertice from "cancelling" the other.

Cheers, Cameron

[Anonymous]

There is a similar feature with windows using walhole or wallniche command.
If an edge of the frame overlap an edge of the hole, when material is the same, lines don't show.
You have to play with masking code values to delete one of the two lines.
Check any window library part with non orhogonal shape, in such situation.
This is not important, just annoying.

[Hoa Tu]

Thanks Cameron and Olivier for your suggestion.

I understand the work around by drawing a line in the object.

The solution by changing the masking code of the edges of the object will not work because the intersect are of the same object.

But things like the intersection of 2 mouldings with curvy surfaces will be very hard to overcome the problem.

Has this bug been reported to GS?

Thanks,
Hoa

[Anonymous]

Hoa wrote:
The solution by changing the masking code of the edges of the object will not work because the intersect are of the same object.

You can add a new parameter "msk", put it to 15, and when objects are joining put it to 13 in the second one.

But things like the intersection of 2 mouldings with curvy surfaces will be very hard to overcome the problem.

For cornices, better to use the Tube command, try the mask value 64 for angles.
If the path has sharp angles, depending of the profile of the cornice, photorealistic results may be bad,
even with msk=64. In such situation cut the tube in several parts.

Has this bug been reported to GS?

Of course they know. I don't have access to the bug database, so i am not sure if it is a bug or a feature,
because it looks so much with global reactions between walls, slabs and edges visibility.

[Anonymous]

Another way, may be easier, if you need to use prism_ command.
Make a copy of the first material, and use it for the second object.
Lines will show, without changing any code.

[Hoa Tu]

so i am not sure if it is a bug or a feature,
because it looks so much with global reactions between walls, slabs and edges visibility.

This is not true. The visibilty of the reaction between walls, slabs do behave logically. Eg. 2 walls meet in the corner the edge will show up.


The workaround I found most effective is to:
* change the prism to EXTRUDE in case of the curvy object.
* add an extra PLANE to the surface where I want the intersection shown.

[Anonymous]

Hoa wrote:
This is not true. The visibilty of the reaction between walls, slabs do behave logically. Eg. 2 walls meet in the corner the edge will show up.

I was pointing the particular situation of windows using wallniche or wallhole command and prism_ for frame.
I first thought to a normal reaction between a wall and a slab. That's why i was not sure.
There is no problem with other windows in such situation, so this may be a bug.
These situations did not occur in AC7. Neither prism_ junction nor windows.

On other hand, since AC8, some strange reactions happen with edges visibility.
Wallhole command works the inverse it was before, for masking code values.
Same thing for cutpolya, but this is another story. (wallniche is only AC8)
I was told that this has been entered in the bug database. Not sure if this concerns
the cutpolya feature only, or the wallhole feature too. I don't know more.

I admit this is a minor bug, workarounds are easy and various, they are only tedious.
Difficult to maintain my own libraries, when i don't know the release date for these fix.
Can someone tell me if this is fixed in AC9? Thanks.

[Hoa Tu]

Olivier Dentan wrote:

Difficult to maintain my own libraries, when i don't know the release date for these fix.
Can someone tell me if this is fixed in AC9? Thanks.

Unfortunately, it has not been fixed in AC9 (beta version)


For the circular window or similar object, my workaround is move the window in a fraction. (eg. addz 0.0002)

[Laszlo Nagy]

Hoa wrote:
Olivier Dentan wrote:

Difficult to maintain my own libraries, when i don't know the release date for these fix.
Can someone tell me if this is fixed in AC9? Thanks.

Unfortunately, it has not been fixed in AC9 (beta version)


For the circular window or similar object, my workaround is move the window in a fraction. (eg. addz 0.0002)

Another workaround is to duplicate the Material you use for the Window's Wall piece and apply this newly created material to it. This way you will have two identical Materials which have different index numbers so ArchiCAD will consider them different and will not remove the common edge.