Design forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Project2{4} Usage

Lingwisyer
Virtuoso
Hi all,

When using Project2{4}, is the second set of definitions the infinite cut plane settings as in the guide it says "...(numCutplanes+1)"? Anyway, I am trying to get a projection at a defined height through my object, but I seem to only get the uncut projection...

PROJECT2{4} 5, 90,					!projection_code, angle,
	0, 1+2,								!useTransparency, statusParts,		
	1,									!numCutplanes,
	b/2 + gs_fw_lower - gs_fw_upper,		!cutplaneHeight1, ..., cutplaneHeightn,

	2, 1+2+4+8+64,						!method1, parts1,
	gs_fill_type,							!cutFillIndex1,
	gs_fill_pen, gs_back_pen,				!cutFillFgPen1, cutFillBgPen1,
	0, 0, 0,								!cutFillOrigoX1, cutFillOrigoY1, cutFillDirection1,
	gs_cut_pen,	1,						!cutLinePen1, cutLineType1,
	65,									!projectedFillIndex1,
	19, 19,								!projectedFillFgPen1, projectedFillBgPen1,
	0, 0, 0,								!projectedFillOrigoX1, projectedFillOrigoY1, projectedFillDirection1,
	gs_pen_2D, 1,						!projectedLinePen1, projectedLineType1

	2, 1+2+4+8+64,						!method1, parts1,
	gs_fill_type,							!cutFillIndex1,
	gs_fill_pen, gs_back_pen,				!cutFillFgPen1, cutFillBgPen1,
	0, 0, 0,								!cutFillOrigoX1, cutFillOrigoY1, cutFillDirection1,
	gs_cut_pen,	4,						!cutLinePen1, cutLineType1,
	65,									!projectedFillIndex1,
	19, 19,								!projectedFillFgPen1, projectedFillBgPen1,
	0, 0, 0,								!projectedFillOrigoX1, projectedFillOrigoY1, projectedFillDirection1,
	gs_pen_2D, 4						!projectedLinePen1, projectedLineType1

Also, how do I go about defining the wall closure? Even just simple closing lines matching the wall cut lines.


Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200
20 REPLIES 20

Lingwisyer
Virtuoso
I suspect that the cutplane function in this command is purely to create contours, and not actually cut anything...
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Lingwisyer
Virtuoso
There is also the wall beyond which appears to get excluded from the cut...
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Lingwisyer
Virtuoso
Using WALL_SECT_PEN and WALL_VIEW_PEN I figured I could manually draw the wall but it would appear that that lines drawn do not follow the pens lineweight. Also, the earlier Project2 does not use fills, so the wall line below is not hidden by projections beyond the face of the wall... Though this might be due to the workaround to getting a plan section through the object.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Lingwisyer
Virtuoso
Hm. The wall beyond does not show in section either... So I am guessing that the default windows draws a plane around each of the wallhole sides which can be chosen to match the wall side or wall edge material, and it is this that is seen beyond in plan and section.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
If we leave you long enough, it looks like you might work it all out.

What is the 3D part that you are trying to project?
I have never used Project2{4} but if we know what you are trying to project and what you are expecting it to look like, then maybe someone can offer some advice.

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
It is the same object I was previously working on. Creates horizontal or vertical user defined battens or louvres within a frame. It was initially only used as a custom door leaf or a window sash, but I thought I might try to make it into an actual window. I decided to not try and add it into the door script itself, rather than a custom leaf, as though that would allow per instance modification, it would require a lot of digging through the macros and the need to rework the Interface Script at some unknown stage in the macros...

So now I have run into all the issues with it's 2D display. I could possibly draw the plan manually ignoring any custom profiles which would probably be easier. I have gotten the section working minus the wall beyond.

Project2{4} does not work how I initially thought it would. The result for my object is the same as using Project2... At the current time, I have created my plan view using the method in thread. This might be the cause of the lack of cut fills...


The Section with the vertical option looks how I want the Plan with the horizontal option to look like short the wall beyond.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
I just had a look at PROJECT2{4} - good luck.

Maybe this will help.
It is the best example I can find so far.

http://gdl.graphisoft.com/tips-and-tricks/using-project24-command

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Barry Kelly
Moderator
Is it the opening lines that you are worried about?
The PROJECT2 should be able to have a fill that hides those lines.
I think even the PROJECT2{2} would work with a SET FILL before it.

Those lines can be turned off in the window plan settings, but you probably don't want to do that as it wouldn't be a correct representation of the brickwork below.

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
Those lines are drawn manually in 2D. Project2 does not seem to show the edges of the Wallhole. I have manage to get a workable display of the Wallhole edges using a set of Planes to case the hole. They also allow me to set the material of the Wallhole. The down side of this is that these planes conflict with the wall itself in 3D...

In plan, the frame does not use the Cut Pen nor does it show a Cut Fill.

Project2{4} has been used as a Project2 as the features of {4} are not needed. Thread topic is no longer accurate...



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Lingwisyer
Virtuoso
Those lines are drawn manually in 2D. Project2 does not seem to show the edges of the Wallhole. I have manage to get a workable display of the Wallhole edges using a set of Planes to case the hole. They also allow me to set the material of the Wallhole. The down side of this is that these planes conflict with the wall itself in 3D...

I have now toggled these to show only in 2D. The wall hole has been resolved using the WallNiche command. Script can be found on this thread.

I found an page about the Project2{3} command on the page before the Project2{4} command. By the explanation provided it sounds like it is designed to work with a Cutplane and by the example object linked on the page, it is what I am wanting, though I cannot seem to get it to work...

fill gs_fill_type
pen gs_cut_pen

Project2{3} 5, 90, 3+32+4096, 1+2+8,
	gs_back_pen,
	0, 0, 0



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
In your 3D script have you set up the cutplane and SECT_FILL before the elements you want to project?
Make sure the cutting plane is in the correct position, angle and direction.

The example object in the HelpCenter works fine.

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
Their object works fine for me. I have attempted to match my equivalent sections to no success so far.

IF GLOB_CONTEXT = 2 THEN				!Plan view
	SECT_FILL gs_fill_type, gs_fill_pen, gs_back_pen, gs_pen_2d
	CUTPLANE 0, (gs_fw_lower + gs_int_fw + 2*gs_louvre_width)

	If abs(gs_louvre_opening_angle) > 0 then
			If abs(gs_louvre_opening_angle) < 90 then
					gs_louvre_opening_angle = 45
			endIf
	endIf

	If LouvreOri = "Horizontal" then
			Louvre_over = 0
	endIf

ENDIF

That is the code at the start of my 3D Script.




Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
GLOB_CONTEXT has been deprecated since version 20, so I wouldn't use it.
GLOB_VIEW_TYPE is the new command.

But I am not sure that will work because it is in your 3D script, and the 3D script is not used in plan view.
Yes the PROJECT2 is a projection of the 3D script, but I am not sure if it will invoke the GLOB_VIEW_TYPE = 2 in the 3D script.
If that makes sense.

Comment out that line and you should see if the PROJECT2 is working as you want it to.

I am not sure how you can invoke the CUTPLANE without experimenting myself.
In the example they have a manual switch which I guess you want to avoid.

I think this might be why there is the PROJECT2{4} where you set the cutplane and height in the command itself.

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
GLOB_CONTEXT in the 3D script is executed before the Project2 in the 2D script. If GLOB_VIEW_TYPE is the successor, I would assume I should work as well.

The Cutplane is defined at the start of the 3D script, same as in the example object. The only difference there, is that mine is only active in plan view, but even disabling that limitation does not solve the issue.

Project2{4} creates contours at the heights defined in the script rather than an exclusion zone. That is all I have manage to get and how I have interpreted the introduction page.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
I just tried this in the sample object and it works fine.
IF GLOB_VIEW_TYPE = 2 THEN
!IF GLOB_CONTEXT = 2 THEN		!!this one works as well but is deprecated
!if bUseCutPlane then                        !!comment out the manual cutplane option
	addz A/10
	cutplane{2} 60, bUseSameSurface	
	del 1
!endif                                                     !!comment out the manual cutplane option
endif
Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
The Cutplane works fine, but I cannot find a way to get cut fills to show...

It would appear that Project2{4} does not take into consideration the Projection Code when making it's cuts. When the Projection Code is set to 3 (plan), it works as expected. When Projection Code is set to 5 (Side View 2) you instead get a contour along the object as if you are looking at a cut from the side, hence why it was not working for me before.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Barry Kelly
Moderator
I believe it is all correct.
The cut planes are measured vertically from the X-Y plane regardless of the projection code, so you are seeing a side view with the horizontal cut planes.
Try it with a projection code of 6 (front axonometry) and you will see what you will see from the side.

Barry.

One of the forum moderators.
Versions 6.5 to 25
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10

Lingwisyer
Virtuoso
I have managed to get Project2{4} to produce the desired plan view by including a Rotx 90 in my plan view part of the 3D Script. Just have to get it to use the right line colours for the wall closure now.



Ling.
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Lingwisyer
Virtuoso
Back to fiddling with this window.


Projection on the left, symbolic on the right.

So I have managed to get the symbolic representation to show the correct lines but the lines are all shown hairline... The pens used are the same between the Projection and Symbolic views. The Wallhole created by the window tool also takes the Cut Pen used in the script resulting in the wall closure using the pen of the window instead of the wall...

On a side note, I am not sure why the wall beyond in the Projected view is not shown. Is it due to the interaction with the Wallhole command?



Ling
AC18-23 AUS 7000
Self-taught, bend it till it breaks.
Win10 | E5620 x 2 | 24GB | K2200

Didn't find the answer? Start a new discussion

Still looking?

Browse more topics

Back to forum

See latest solutions

Accepted solutions

Start a new discussion!