Network Specs/Individual Network RULs

This file contains information related to the individual Network RULs.

Network specific RULs

Each individual network, including waterpipes (but not powerpoles), has two RUL files. One is the main RUL file for a given network, while the other is a supplementary RUL for a given network. RULs ending in odd values are the main network-specific RUL. While RULs ending in even values are the supplementary Rul for a given network. This covers RUL files from (address) 0x0A5BCF4B/AA5BCF57/00000001 to 0x0A5BCF4B/AA5BCF57/00000018.

Format

#HighwayRules#

#Header# -This basically contains #NetworkTypeRules# here name. The engine recognises the different names used in the header section here, and does have an impact/influence on the network tool(s) used.
A typical sample portion of rul code for individual networks may look something like the following (this was taken from a Highway RUL file)
1,0,0,1,3
2,5,1,0,2,4
3,0,0x2001800,0,0

Version/Type:Value1/Value2/Value3
Different Versions/Types have different number of Values following after them, with differing purposes.
Format is broken up into parts below, and is as follows;

For Type 1 lines

1,0,0,1,3
1[Type],West,North,East,South
West/North/East/South use the following CheckFlag values;
00 -no connection
01 -sloped connection-to the left
02 -straight connection
03 -sloped connection-to the right
04 -shared median
11 -sloped connection from an intersection
13 -sloped from an intersection
## ~ There is quite a lot more number designations for some of the more complex stuff (such as Rail). The above ones are just the basic types that cover & work with most networks.

For Type 2 lines

2,5,1,0,2,4
2[Type],X,W,N,E,S
X = See table further below.
WNES = West/North/East/South ~ uses the same CheckFlag values as above. “?” (without quotes) is also valid though for Type2 lines as a wildcard.

For Type 3 lines

3,0,0x2001800,0,0
3[Type],X,FSH/Path/ExemplarReference,Rotation,Flip
X = See table further below.
Rotation: 0-3. Rotate piece:
0=No change
1=90 Degrees right
2=180 Degrees
3=270 degrees right/-90 degrees left.
Where an Exemplar exists for the reference, the Exemplar subsequently points to a S3D file [NOTE: Referenced Exemplar files follow a specific GroupID format, for the different network types].

Table for Type2 & Type3 lines

X = Reference in relation to the tile being referenced. For Type3 lines, zero is also valid reference & denotes that the image being loaded into the tile. The same also applies to other (non-zero neighbouring) tiles as well. Zero is the centre point, or the primary tile being coded for for the Type1 line, to which all other tiles are referenced in relation to.
(each box/number here represents an in-game tile)

Further explanation of CheckFlags:

Setup

Imagine yourself at the centre of this transit tile at point E, looking North to point 2. Segment AB is the side for which we are trying to determine the border type.

Explanation

The RUL entries dictate the centre point of the network (in this case, roads) along segment AB, and the direction the network is going, in comparison to segment E2. If the vector of the transportation tile is parallel with EA, the angle would be -45° in comparison to E2. Likewise, if the vector of the transportation tile is parallel to EB, the angle would be +45° in comparison to E2.

Table

The Pixel position is based on the 128 pixel wide zoom 5 textures, with pixel points 0-127. Also, the pixel values might be off slightly due to anti-aliasing in the textures.

The simpler table, showing absolute positions only:

The more complex table, showing the relative offsets as well as absolute positions:

That about covers it. As mentioned, there are more rul designations than just those mentioned here. Most other rul designations though are more complex. For this reason it’s advised to try & grasp the concepts of the above items first.