Skip to main content

Roof types

In K3.veranda we not only support classic mono-pitch roofs. There is also the option of displaying cubic roofs, carports and slatted roofs.

Technically, these roof types are implemented differently:

  • Classic patio roofs are the commonly known monopitch roofs.
  • Cubic roofs offer basic framing with an internal roof pitch (possibly also 0 degrees). Therefore are a roof type in their own right
    Enterprise
  • In K3.veranda, we consider slats to be a covering. This sounds strange at first, but it becomes understandable, when you realize that there are systems of classic monopitch roofs with slats, but also cubic roofs with slats Roofs with slats
    Enterprise
  • Carports do not require any special construction. Ultimately, we offer the technical possibility of all roofs in a special location (i.e. not on the terrace, but on the side of the house) and with a suitable orientation. For example, a carport can be configured as a monopitch roof to the right of the house
Pro
Enterprise
info

A real change in construction only occurs with the cubic system.
Louvred roofs are either classic patio roofs or cubic roofs with a louvred covering.
A carport is a roof (pent or cubic) that does not stand on the terrace, but on the side of the house.

Characteristics of the roof types​

The different roof types are controlled in most configurators via the model selection. This model selection is the <Liste> "Modellauswahl" [typ] feature. In the standard template, it is located in the first step Construction.
To add new models, you should add new values to this feature.

tip

You can create any new steps in the configurator and move the characteristics. Our customers have so far all left the model selection at the very front on Construction.

The new model values require special keys and additional attribute settings:

Available keys for model selection​

  • Pitched roof: Does not require an assigned key - simply create a model selection value without a key.
  • Cubic roof: Add a value "Kubisches Dach" [qubus] - i.e. with the name "Cubic roof" and key qubus.
  • for other model selection values, use the key to decide whether a roof model is constructed as a mono-pitch or cubic roof.
    Example: if you create "Carport" [qubus], your carports are created as cubic roofs. If you do not create a key for a Model selection value, it will be constructed as a monopitch roof.
tip

As you are already using the classic patio roofs in the standard template, these do not need to be added. All model values without keys are classic patio roofs (monopitch roof).

Attributes​

You need additional attributes in the value table, which are read out by the 3D scene.

info

An attribute is an additional column in the value table of a feature. Attributes can have different Types and can be used for different requirements. In K3.veranda, for example, the model selection not only the name of the model, but also, for example, post dimensions, in order to generate the dynamic 3D model model.
You add an attribute using the "New attribute" button. When creating the attribute, make sure that the attribute has the correct type and key.

The following attributes of the model selection values control the display of your roof types:

  • Attribute <nicht übersetzter Text> "Pfosten" [log] (as a reminder: i.e. an attribute called Post of the Type non-translated text with the key log ):
    • This attribute is entered in the format numberxnumber - e.g. 13x13. By entering this attribute, you control the widthxdepth of the mullions of your roof, measured in cm.
  • Attribute <nicht übersetzter Text> "Rinne" [bar]:
    • This attribute can be entered in the format numberxnumber. For example, 17x15. By entering this attribute, you control the depthxheight of the gutter on your roof, measured in cm.
  • Attribute <nicht übersetzter Text> "Sparren" [roofBar]:
    • This attribute can be entered in the format numberxnumber. For example, 10x5. By entering this attribute, you control the heightxwidth of the rafters of your roof, measured in cm.
  • Attribute <nicht übersetzter Text> "Aufliegende Sparren" [coverStrips].
    • This attribute can be entered in the format numberxnumber. For example, 1x5. By entering this attribute, you control the heightxwidth of the overlying rafters, measured in cm.
  • Attribute <nicht übersetzter Text> "Wandanschluss" [attachedBar]:
    • This attribute can be entered in the format numberxnumber. For example, 15x10. By entering this attribute, you control the heightxwidth of the wall connection, measured in cm.
  • Attribute <nicht übersetzter Text> "startPoint" [place]:
    • This attribute can be entered in the format numberxnumberxnumber. For example, 1x2x3. The entry controls the starting position of the roof in the scene as X, Y and Z coordinates, measured in meters.

Carport and slatted roof​

The carport and the slatted roof do not have a special key in the model selection.
This means that carports and louvred roofs are always classic patio roofs or cubic roofs. You can therefore design them as you wish.

Carports​

  • Carport as a monopitch roof variant with sliding and alignment adjustment
    Pro
  • Carport as a cubic system, with corrugated and trapezoidal sheet metal roofing
    Enterprise

If you would like to offer carports, the following procedure is recommended:

  1. Add a value for the model selection. Assign keys and attributes as described above according to your specifications.
  2. For the carport, the attribute "startPoint" [place] is of particular interest, with which you can move the roof - ideally to the driveway to the right of the house to the driveway to the right of the house. You can achieve this for the standard house model by setting the attribute value for "startPoint" with the attribute value "-12.3x0x5". This shifts the carport 12.3m to the right and 5m in the direction of the road.
  3. Create a <Liste> "Ausrichtung* [alignment] attribute - this may already exist, first look in the "Control parameters" step.
  4. Assign two characteristic values for the "Alignment" characteristic you have just created:
    "Längs" [laengs] for a course of the roof width perpendicular to the house wall and
    "Quer" [quer] for a course of the roof width parallel to the house wall.
    If you now change this feature in the configurator, you will see that the carport does not move with "lengthwise", but rotates by 90 degrees with "Transverse". In combination with "startPoint" [place] as the attribute value attribute value of the model selection.
  5. You should generally hide the "Orientation" attribute and use a validity rule to ensure that (if the carport is selected) the rotation is carried out as desired. Also make sure that the Rotation is not executed if no carport is selected.
    You link the "Ausrichtung" [aligment] of the carport with the "Art des Aufbaus" [attachment] via a Validity rule that permits these two variants:
  • Type of structure = wall-mounted, alignment = longitudinal
  • Type of structure = free-standing, orientation = transverse
  1. If you want to offer this feature to your customers for selection, you should move it to the "2nd construction" step step (options/step).

Do you only offer freestanding carports?​

This is perfectly feasible. The flexible control system of the K3 provides a solution:
You create a validity rule that specifies that the "Art des Aufbaus" [attachment] is always "Freistehend" [freistehend] if a "carport" is selected in the model selection.

Would you like to rotate the carport?​

You can do this using the "Ausrichtung" [alignment] feature described above: either leave the selection to the user or the user the choice or (and we strongly recommend this) you specify the orientation.
If you only offer one variant, you can also only create the characteristic value that you want. Don't forget to hide this characteristic if you don't want the user to see it.

Does your carport have several supports?​

It could be useful to use the "Anzahl Tragbalken" [roofLogAmount] cover feature for the carport. This is described in more detail in im nächsten Abschnitt.

Slatted roofs
Enterprise
​

If you would like to offer slatted roofs, the following procedure is recommended:

  1. Add a value "Lamellendach" to characteristic "Modellauswahl" [modellauswahl]. Assign either Key either [qubus] for cubic basic construction or leave blank for pitched roof.
    For most of our customers, the slatted roof is based on the basic cubic type. For this, you should fill in the "Mullion" and "Rafter" attributes (see above) and, if required, add the "startpoint" [place] so that the roof is in the garden - this fits, for example, with a place value of "0x0x-7". For monopitch roofs as a construction base, the "Rinne" [bar] attribute should also be filled in.
  2. To display the slats, you must add the corresponding covering. To do this, add Add a value "Lamellen" [lamelle] to the attribute "Eindeckung" [glassDensity]. Set the following attributes to "0" for this value: Glas, Opacity, glasdicke, Roughness
  3. Create a validity rule that specifies that when selecting the model of your slatted roof only the new cover value "Lamelle" [lamelle] is valid.
  4. Add a line to the "Number of rafters" validity rule that specifies the covering "Lamellen" combined with the possible width (e.g. 0-1200) and the corresponding number of rafters (fixed value 2).
  5. Add a line for the covering value "Lamellen" to the "Covering - Validity" rule.
  6. On the "Model selection" feature, remove the tick from the "Hide if only one selection is possible" option.
  7. Move the minimum/maximum values of feature "Dachneigung" [angle] from feature to a validity rule for the roof pitch and covering. There you can set the usual validity for the "normal" Roofs you can define the usual validity of 8-15 degrees and for the louvred roof you can define 0 degrees.
tip

Sie finden im nächsten Abschnitt More detailed explanations of the coverings.

Further linked features​

The model selection is a central element of your configurator. Each model selection naturally interacts with the general roof construction. This is not only made up directly from the model selection, but also but also from many other features.
Our customers still use the following selections:

Product selection​

Do you offer different lines per model selection?
For example, manufacturers offer several roof models ("Trendline", "Profiline" or similar), which are assigned to our classic patio roof. However, you want to give your end customers a basic selection in advance, in which you ask, for example
Which product are you interested in?
Possible selections would be Klassisches Terrassendach, Kubisches System, Lamellendach or Carport.

You then list the various possible options in another selection and narrow down the models further the models further. You do not need any keys for this. This logic is purely via a new characteristic <Liste>"Produktauswahl" and a validity rule (which then defines the model selection values valid for the product selection values) Model selection values).

tip

If you want to define this characteristic via a URL parameter when calling the configurator, add keys to this characteristic and its values, e.g:

  • Feature: <Liste>"Produktauswahl"[art]
  • Value: "Carport"[carport]
  • Rule: Produktauswahl Carport -> Modellauswahl Carport
  • Hiding product selection: via the option Ausblenden, wenn nur eine Auswahl möglich ist
  • Call for pre-assignment with carports would then be: https://<konfiguratorurl>&art=carport

Profile color​

The profile color can of course be configured.
This is possible with the <Farben> "Profilfarbe" [color] feature.
The profile color is automatically read out by the 3D scene and set in the model.

tip

Our customers often use the RAL color display type for the feature. The RAL selection is standardized and offers a large selection of defined color tones, which we approximate using RGB. In rare cases it may be that the RAL selection does not offer the desired values.
In this case, you can fall back on a direct color selection and enter RGB values (expressed in decimal or HEX) are specified. You can choose the names of these colors as you wish, e.g. according to your supplier's specifications.

Eaves​

You have already hier the roof overhang in the first Tutorial series.

This feature regulates how far the front support posts are set back from the front edge of the roof, as follows:

  1. Create a characteristic <Ja/Nein> "Dachvorsprung gewünscht?" [dachvorsprung].
  2. Adjust the <Zahl> "Einzug des Dachvorsprungs" [eaves] feature to your minimum/maximum values.

The rule "Eaves with/without retraction" in the standard template ensures that the characteristic "Indentation of the eaves" is hidden if the "Eaves required" is set to "No".

info

For example, if you have roof models for which no eaves are permitted, you should this feature accordingly. The downstand beam that is installed with a roof overhang, refers to the feature Statikträger.

Height​

You have already learned how to enter the height hier in the first Tutorial series.

The characteristic for this is <Zahl> "Höhe" [height] and is interpreted in cm.

tip

If your different roof models allow different roof height intervals (max & min), remember to limit the Feature height accordingly in a rule instead of using the minimum/maximum values of the feature.

Width​

You have already learned how to enter the width hier in the first tutorial series.

The corresponding characteristic for this is <Zahl> "Breite" [width] and is interpreted in cm.

tip

If your different roof models allow different roof width intervals (max & min), remember to limit the Limit the feature accordingly in a rule instead of using the minimum/maximum values of the feature.

Depth​

You have already learned how to enter the depth hier in the first tutorial series.

The characteristic for this is <Zahl> "Tiefe" [depth] and is interpreted in cm.

tip

If your different roof models allow different roof depth intervals (max & min), remember to limit the Limit the feature accordingly in a rule instead of using the minimum/maximum values of the feature.

Dimension input types​

tip

You can set up the configurator so that the end user does not have to enter the roof pitch Roof pitch, but a rear height and a front height of the roof. Details on this can be found hier

Type of superstructure​

You have already learned about the possibility of wall mounting or a free-standing construction in the first first tutorial series hier.

This is controlled via the feature <Liste> "Art des Aufbaus" [attachment] with the values:

  • "Freistehend" [freistehend] for a free-standing construction and
  • "Wandmontage" [wandmontage] for a construction on the wall

These values are assigned the attribute <Zahl> "StartPoint" [startPoint], which specifies the distance of the roof from the Roof from the house wall (in m). Accordingly, this attribute should only assume non-zero different values if the construction is free-standing. You can achieve this using a Validity rule that combines "Art des Aufbaus" with values for "startPoint".

tip

As described above, there is often a connection between carports and the free-standing construction. Make sure you describe the validities that apply to you correctly with rules.

Post types​

You have already become acquainted with our available posts in the first tutorial series hier.

The mullion selection is controlled via the <Liste> "Pfostentyp" [pfostenart] feature with the values:

  • "Eckig" [eckig] for square mullions
  • "Rund" [rund] for round mullions
  • "Klassisch" [klassisch] for classic mullions - these are clearly rounded square mullions.
tip

Most of our active configurators do not offer the user a post selection.
This feature should then be hidden and controlled by the model selection via validity rules.

Rain gutters​

You have already become acquainted with our available rain gutters in the first tutorial series hier.

The gutter selection is controlled via the feature <Liste> "Typ der Regenrinne" [rinne] with the values:

  • "Eckig" [eckig] for square gutter
  • "Rund" [rund] for round gutter
  • "Klassisch" [klassisch] for classic gutter
  • "Kasten" [kasten] for a box gutter
tip

Most of our active configurators do not offer the user a gutter selection.
This feature should then be hidden and controlled by the model selection via validity rules.

Static beam​

The structural beam offers the option of reducing the number of posts at the front.
You can offer the structural beam with a visualization.

The structural beam selection is controlled via the feature <Liste> "Statikträger" [staticLogPos] with the values:

  • "Mit Statikträger" [true] if a structural beam is to be installed.
  • "Keine Angabe" [$noSelection] if feature "Statikträger" is to allow optional values (The <Zahl> "Size" [size] attribute controls the height of the structural beam in cm.
info

You can create several values with the key true, which then only differ in name ("Display") and size

  • i.e. different sized static supports.

Static carrier back​

In the same way as the static beam described above for the front, you can also define a static beam for the rear Structural beam for the rear. This allows you to reduce the number of mullions on the rear side. This option only makes sense for free-standing roofs and should be calculated accordingly.

The structural support selection is controlled via the <Liste> "Statikträger Rückseite" [staticLogBackside] feature. You use the values of the characteristic to control the cross-section to be used
- in the attribute <nicht übersetzter Text> "Größe" [size] attribute, you specify the cross-section in cm as "height x width", e.g. "8x12". Typical values for this attribute are then

  • "Mit Statikträger Rückseite" [true] and attribute "Größe" [size] = "8x12" if a structural beam is to be installed.
  • "Ohne Statikträger Rückseite" [$noSelection] if not. The attribute "Statikträger" must be "optional".
info

As with the front static carrier, you can create several values with the key true, which then only differ in name ("Display") and size - i.e. different sized static supports.

Threshold​

The sill is the beam at the front to which all the rafters are attached. The size of the threshold can be Be adjusted in size.

This property is controlled via the <Liste> "Schwellenauswahl" [staticLog] feature. If it is not is created, a default value is used. Possible values are:

  • "Ja" [ja] - if a threshold with non-standard dimensions is to be installed. In addition, the attribute
    <nicht übersetzter Text> "Schwellenprofil" [schwelle] is also used, which defines the profile cross-section (width x height) in the format "number x number" in cm.

Number of rafters​

You have already seen the settings for the number of rafters in the previous tutorial series hier tutorial series.

The number of rafters is controlled via feature <Zahl> "Sparrenanzahl" [polesTopNumber]. The value range results from the "Number of rafters" rule, in which the number of rafters is defined as a Is defined as a function of covering and width.

Number of mullions at the front​

You have already seen the settings for the number of mullions at the front in the previous tutorial series hier tutorial series.

The number of posts at the front is controlled via feature <Zahl> "Pfostenanzahl" [polesNumber]. The value range results from the "Number of posts" rule, in which the number of posts is defined as a function of the width Is defined as a function of the width.

Number of posts at the rear​

The number of posts at the rear is controlled via feature <Zahl> "PfostenanzahlHinten" [polesNumberBackside] feature. The value is normally calculated (Options/Calculated) as the formula
Pfostenanzahl-1 <=2 ? 2 : Pfostenanzahl-1
This formula expresses the fact that if more than 2 posts are installed at the front, the number of rear posts is the number of posts at the front -1. Otherwise, the number of posts at the rear is always 2. You can of course adapt this formula as you wish. learn more about Hier More about expressions in K3.