Unclear script of project2{4}

[Nader Belal]

Hi everyone,

I was investigating project2{4} using the downloadable example supplied by Graphisoft in this page.

So by simple editing of the original script

for i = 1 to iCutPlanes
	put cutElevation + (i-1) * sliceHeight
next i


for i = 0 to iCutPlanes
	put 1+32,				! method
		2,					! parts
		1,					! cutFillIndex
		1,					! cutFillFgPen
		1,					! cutFillBgPen
		0.0,				! cutFillOrigoX
		0.0,				! cutFillOrigoY
		0.0,				! cutFillDirection
		1,					! cutLinePen
		1,					! cutLineType
		1,					! projectedFillIndex
		1,					! projectedFillFgPen
		1,					! projectedFillBgPen
		0.0,				! projectedFillOrigoX
		0.0,				! projectedFillOrigoY
		0.0,				! projectedFillDirection
		1,					! projectedLinePen
		1					! projectedLineType
next i


project2{4} 3, 270,						
	0,					! useTransparency	
	0,					! statusParts		
	iCutPlanes,			! numCutplanes		
	get (nsp)

It will provide this result in the 2D view

But when I reedit the script in the following way

project2{4} 3, 270,						
	0,					! useTransparency	
	0,					! statusParts		
	1,			! numCutplanes		
	5000,

1+32,				! method
			2,					! parts
			1,					! cutFillIndex
			1,					! cutFillFgPen
			1,					! cutFillBgPen
			0.0,				! cutFillOrigoX
			0.0,				! cutFillOrigoY
			0.0,				! cutFillDirection
			1,					! cutLinePen
			1,					! cutLineType
			1,					! projectedFillIndex
			1,					! projectedFillFgPen
			1,					! projectedFillBgPen
			0.0,				! projectedFillOrigoX
			0.0,				! projectedFillOrigoY
			0.0,				! projectedFillDirection
			1,					! projectedLinePen
			1,					! projectedLineType

1+32,				! method
			2,					! parts
			1,					! cutFillIndex
			1,					! cutFillFgPen
			1,					! cutFillBgPen
			0.0,				! cutFillOrigoX
			0.0,				! cutFillOrigoY
			0.0,				! cutFillDirection
			1,					! cutLinePen
			1,					! cutLineType
			1,					! projectedFillIndex
			1,					! projectedFillFgPen
			1,					! projectedFillBgPen
			0.0,				! projectedFillOrigoX
			0.0,				! projectedFillOrigoY
			0.0,				! projectedFillDirection
			1,					! projectedLinePen
			1					! projectedLineType

It simply doesn't work, the 2D space is empty.

Can someone explain me how to make this work ??

[Nader Belal]

Lingwisyer wrote:
Could you include an "If glob_view_type = 2" statement near the start of your script that will set all of your openings to the same height when viewed in plan? In this way you can cut them all with a single cutplane. No need to worry about overlapping shadings either.

Update

Just found out that you don't need a "cutplane" in the 3D Script as "project2{4}" already have it.

[Lingwisyer]

Moonlight wrote:
Just found out that you don't need a "cutplane" in the 3D Script as "project2{4}" already have it.

I was referring to the commands internal cutplane. The representation is different though as the internal cutplane will only use a single line type and weight whilst a stand alone cutplane will use the projected surfaces line types and weights. There are some other issues with using a standalone the the internal one solves, but I cannot remember what they were at the current moment...



Ling.

[Nader Belal]

@Lingwisyer

I'm aware of that, I meant that the function doesn't need the cutplane for the objects' representations, unless ofcourse it's to bypass a limitation.