Topic: WALL_SKINS_PARAMS and Building_Material_info

This topic has 7 replies, 4 voices, and was last updated 6 years, 5 months ago by James Hoth.

Viewing 7 reply threads

Author

Posts
- May 5, 2016 at 12:48 #2443
  Joachim Sühlo
  Participant
  I try to read the surface material from a composite wall for a window, but it seems that the Request “Building_Material_info” does not work quite well.
  The Material is shown in 3D Window of GDL-Editor correctly as well as in the Lib-Part-Preview, but not in the 3D Window (AC 18 and 19). See attached Scrennshot.
  
  My script is as following:
```
DIM wand_fill[], wand_fill_pen[], wand_back_pen[], wand_cont_pen[], wand_thck[], wand_cont_pen_unten[], wand_mat[], mat_index[]

FOR ii=1 TO ski_no
	wand_fill[ii] 			= WALL_SKINS_PARAMS[ii][1]
	wand_fill_pen[ii]		= WALL_SKINS_PARAMS[ii][4]
	wand_back_pen[ii]		= WALL_SKINS_PARAMS[ii][5]
	wand_cont_pen[ii]		= WALL_SKINS_PARAMS[ii][9]
	wand_cont_pen_unten[ii]	        = WALL_SKINS_PARAMS[ii][7]
	wand_thck[ii]			= WALL_SKINS_PARAMS[ii][2]
	wand_mat[ii]			= WALL_SKINS_BMAT_NAMES[ii][1]
	x = REQUEST{2} ("Building_Material_info", wand_mat[ii], "gs_bmat_surface", mat_index[ii])

NEXT ii

MATERIAL IND(MATERIAL, mat_index[1])
```
  Attachments:
  REQUEST-WALLMAT.png
  GDL Object Developer
  b-prisma
  MAC OSx 10.14
- May 6, 2016 at 07:20 #2445
  
  Gergely Fehér
  Keymaster
  
  How do you get the ski_no value?
  
  Gergely Fehér
  Team Leader, Library Team
  GRAPHISOFT SE
- May 6, 2016 at 16:39 #2446
  
  Joachim Sühlo
  Participant
  
  ski_no = WALL_SKINS_NUMBER
  And the REQUEST was not correctly copied (Array-Index) was missing:
  x = REQUEST{2} ("Building_Material_info", wand_mat[ii], "gs_bmat_surface", mat_index[ii])
  This seems to be prohibited by the forum software (square brackets where left out)
  
  GDL Object Developer
  b-prisma
  MAC OSx 10.14
- May 9, 2016 at 08:00 #2449
  
  Gergely Fehér
  Keymaster
  
  I corrected the codes: please use ohter variables than i for the loops in this forum. “i” in square brackets is for italic in BBCode, that’s why it is eliminated from codes.
  
  Gergely Fehér
  Team Leader, Library Team
  GRAPHISOFT SE
- May 20, 2016 at 13:08 #2478
  
  Joachim Sühlo
  Participant
  
  Gergely, did you find out anything about this issue?
  
  GDL Object Developer
  b-prisma
  MAC OSx 10.14
- May 24, 2016 at 13:22 #2481
  
  Gergely Fehér
  Keymaster
  
  WALL_SKINS_BMAT_NAMES did not work in 3D views in AC18&19. It will be corrected for AC20.
  
  Gergely Fehér
  Team Leader, Library Team
  GRAPHISOFT SE
- May 29, 2018 at 01:01 #4097
  
  Kristian Bursell
  Participant
  
  Hi Gergely (and Joachim),
  I thought i would add this question here as it is related.
  I have a problem where the WALL_SKINS_PARAMS is not working in the 3D script but works in the 2D script.
  I am creating plaster returns for my windows and the 2D works fine but the 3D is acting as if the wall is a single skin saying the index is greater than the array dimension.
  
  SCRIPT (identical in 2D and 3D)
  if WALL_SKINS_NUMBER > 1 then
  !!——————————————-INTERNAL
  SKINFillInt = “”
  SKINThickInt = .010
  SKINPenInt = 1
  SKINPenFillInt = 1
  SKINPenBGInt = 1
  if GLOB_CONTEXT # 5 then
  SKINFillInt = WALL_SKINS_PARAMS[WALL_SKINS_NUMBER][1]
  SKINThickInt = WALL_SKINS_PARAMS[WALL_SKINS_NUMBER][2]
  SKINPenInt = WALL_SKINS_PARAMS[WALL_SKINS_NUMBER][9]
  SKINPenFillInt = WALL_SKINS_PARAMS[WALL_SKINS_NUMBER][4]
  SKINPenBGInt = WALL_SKINS_PARAMS[WALL_SKINS_NUMBER][5]
  endif
  material WALL_MAT_A
  
  CADSWIFT
  Australia
- September 20, 2018 at 23:00 #4270
  
  James Hoth
  Participant
  
  I have a related issue, I assume that the limitation or the wall_skins_number is only the skins that are being cut in the 2d plane? or is there a way to get the info for all the skins cut and not?
  
  AC 22, Twinmotion 2019, Macbook Pro 2017 w/ 3.1ghz kabylake, radeon 560 pro, radeon rx vega 54 egpu, Xkeys 68 jog & shuffle, wacom intuos pro m, better touch tools
Author

Posts

Viewing 7 reply threads

The forum ‘Doors and windows’ is closed to new topics and replies.

Attachments: