Difference between revisions of "User:Brickblock1"
Brickblock1 (talk | contribs) |
Brickblock1 (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Standardized Roadtype Scheme== |
==Standardized Roadtype Scheme== |
||
| − | The main reason for the creation of this standard is to allow for better |
+ | The main reason for the creation of this standard is to allow for better compatibility between road and vehicle sets. It's also made with the intent of limiting the amount of necessary hidden roadtypes this is mostly accomplished by moving the roadtypes for compatibility away from the vehicle sets to the roadset. |
== What the standard does not do! == |
== What the standard does not do! == |
||
| − | The standard is not made to make different roadsets work |
+ | The standard is not made to make different roadsets work together |
== The Label Scheme == |
== The Label Scheme == |
||
A roadtype label consists of four characters. In this scheme, each position has a different purpose: |
A roadtype label consists of four characters. In this scheme, each position has a different purpose: |
||
| − | # |
+ | # Surface and type class (ee.g. Road, water, ice) |
# Speed and id Class |
# Speed and id Class |
||
| − | # Tier class (e.g. |
+ | # Tier class (e.g. Off-road, Road, Highway/Motorway) |
# Energy source type class |
# Energy source type class |
||
In the next sections, each of the four positions will be explained. |
In the next sections, each of the four positions will be explained. |
||
| − | === |
+ | ===Surface and type class [X***]=== |
| − | The first position in the |
+ | The first position in the roadtypelabel defines surface and/or road type class. The following classes are currently defined: |
{| |
{| |
||
| − | ! !!Road |
+ | ! !!Road surface/type |
|- |
|- |
||
|R ||Road |
|R ||Road |
||
| Line 31: | Line 31: | ||
|W ||Water |
|W ||Water |
||
|- |
|- |
||
| − | |X ||Water and ice ( |
+ | |X ||Water and ice (probably hidden) |
|- |
|- |
||
|X ||Ice and road (probably hidden) |
|X ||Ice and road (probably hidden) |
||
| Line 37: | Line 37: | ||
|X ||Water and road (probably hidden) |
|X ||Water and road (probably hidden) |
||
|- |
|- |
||
| − | |U || |
+ | |U ||Universal (probably hidden) |
|} |
|} |
||
X is undecided |
X is undecided |
||
| − | + | Road sets don't have to define all of the types, this means that the vehicle set might want to use an undefined road type. If that is the case those vehicles wouldn't be available which can be mitigated by falling back to another appropriate surface type. For example a bike using BABN would reasonably be able to run on regular roads, therefore making it fallback is complete reasonable. |
|
=== Speed and id class [*X**]=== |
=== Speed and id class [*X**]=== |
||
| − | This |
+ | This character can be anything which the roadtype set author wants but there must always be one road type with A in it as it is what all road vehicles should use. |
=== Tier class [**X*]=== |
=== Tier class [**X*]=== |
||
| − | There are three possible |
+ | There are three possible characters here: |
| − | # A |
+ | # A Off-road/rough terrain |
# B Regular city/county road |
# B Regular city/county road |
||
# C Highway/Motorway |
# C Highway/Motorway |
||
| − | B should be made compatible with both A and C while A and C are only compatible with B. When not all of the tiers are provided the ones that aren't should be in the alternative_roadtype_labels list, that way vehicles defined for them will still be able to run on the most |
+ | B should be made compatible with both A and C while A and C are only compatible with B. When not all of the tiers are provided the ones that aren't should be in the alternative_roadtype_labels list, that way vehicles defined for them will still be able to run on the most similar type of road. Similarly when the roads have different amount of tiers B should be considered the main one. |
| − | === Energy source type class [** |
+ | === Energy source type class [***X]=== |
| − | + | Currently the only standard types are E and N, Where E is electrified and N is not. |
|
=== The standard label (ROAD)=== |
=== The standard label (ROAD)=== |
||
| − | It is up to the roadset artuor to decide what label this should replace but it is |
+ | It is up to the roadset artuor to decide what label this should replace but it is recommended to chose either RABN or RACN. |
| − | + | Vehicle set authors will need to add this as a fallback or else their vehicles won't show up on the default roads. |
|
Revision as of 17:42, 16 March 2023
Standardized Roadtype Scheme
The main reason for the creation of this standard is to allow for better compatibility between road and vehicle sets. It's also made with the intent of limiting the amount of necessary hidden roadtypes this is mostly accomplished by moving the roadtypes for compatibility away from the vehicle sets to the roadset.
What the standard does not do!
The standard is not made to make different roadsets work together
The Label Scheme
A roadtype label consists of four characters. In this scheme, each position has a different purpose:
- Surface and type class (ee.g. Road, water, ice)
- Speed and id Class
- Tier class (e.g. Off-road, Road, Highway/Motorway)
- Energy source type class
In the next sections, each of the four positions will be explained.
Surface and type class [X***]
The first position in the roadtypelabel defines surface and/or road type class. The following classes are currently defined:
| Road surface/type | |
|---|---|
| R | Road |
| B | Bike |
| I | Ice |
| S | Snow |
| W | Water |
| X | Water and ice (probably hidden) |
| X | Ice and road (probably hidden) |
| X | Water and road (probably hidden) |
| U | Universal (probably hidden) |
X is undecided
Road sets don't have to define all of the types, this means that the vehicle set might want to use an undefined road type. If that is the case those vehicles wouldn't be available which can be mitigated by falling back to another appropriate surface type. For example a bike using BABN would reasonably be able to run on regular roads, therefore making it fallback is complete reasonable.
Speed and id class [*X**]
This character can be anything which the roadtype set author wants but there must always be one road type with A in it as it is what all road vehicles should use.
Tier class [**X*]
There are three possible characters here:
- A Off-road/rough terrain
- B Regular city/county road
- C Highway/Motorway
B should be made compatible with both A and C while A and C are only compatible with B. When not all of the tiers are provided the ones that aren't should be in the alternative_roadtype_labels list, that way vehicles defined for them will still be able to run on the most similar type of road. Similarly when the roads have different amount of tiers B should be considered the main one.
Energy source type class [***X]
Currently the only standard types are E and N, Where E is electrified and N is not.
The standard label (ROAD)
It is up to the roadset artuor to decide what label this should replace but it is recommended to chose either RABN or RACN.
Vehicle set authors will need to add this as a fallback or else their vehicles won't show up on the default roads.
