User:Maqifrnswa - Revision history

Maqifrnswa at 01:00, 9 August 2016

2016-08-09T01:00:32Z

Maqifrnswa: /* cargo delivery to stations */

2016-07-30T09:50:51Z

‎cargo delivery to stations

Maqifrnswa: /* cargo delivery to stations */

2016-07-30T09:45:55Z

‎cargo delivery to stations

Maqifrnswa: /* vehicle loading rates */

2016-07-30T09:12:18Z

‎vehicle loading rates

Maqifrnswa at 09:10, 30 July 2016

2016-07-30T09:10:39Z

Maqifrnswa at 08:25, 30 July 2016

2016-07-30T08:25:55Z

Maqifrnswa at 18:52, 28 July 2016

2016-07-28T18:52:02Z

Maqifrnswa at 18:50, 28 July 2016

2016-07-28T18:50:36Z

Maqifrnswa at 18:43, 28 July 2016

2016-07-28T18:43:31Z

Maqifrnswa at 18:42, 28 July 2016

2016-07-28T18:42:07Z

@@ Line 2: / Line 2: @@
 = game mechanics =
 == cargo delivery to stations ==
 Every day is 74 ticks. every 256 ticks cargo is delivered to stations (8 or 9 times a month, every 3.5 days). The default amount of cargo produced is in src/table/build_industry.h. The amount delivered can be 1/8, 1/4, 1/2, 1x, 2x, 4x, or 8x of the default value, depending on level of production.

@@ Line 7: / Line 7: @@
 Coal 15, Wood 13, Oil rig 15, oil well 12, livestock 10, Grain 10, copper 10, bank 6, gold 7, diamond 7, iron 10, water 12, maize 11.
-So the max an industry can produce is ~1100/month (coal). More precisely, 0.46875 per tick = 18.75 per 40 ticks (one train load cycle). With 5 cargo loaded on to one train car per 40 ticks, 4 loading train cars (2 tiles) are needed to keep up with production. Those 2 tiles need to be constantly occupied, so parallel tracks are needed. Therefore, a station of 2 tracks for a train length of 3 should keep up with demand (although require a constant stream of trains!). To burn down demand, more tracks (or longer trains) would be needed.
+So the max an industry can produce is ~1100/month (coal). More precisely, 0.46875 per tick = 18.75 per 40 ticks (one train load cycle). Assuming 100% delivery (which never happens...) and the default 5 cargo loaded on to one train car per 40 ticks, 4 loading train cars (2 tiles) are needed to keep up with production. Those 2 tiles need to be constantly occupied, so parallel tracks are needed. Therefore, a station of 2 tracks for a train length of 3 should keep up with demand (although require a constant stream of trains!). To burn down excess supply at a station, more tracks (and/or longer trains) would be needed.
 == vehicle loading rates ==

@@ Line 3: / Line 3: @@
 = game mechanics =
 == cargo delivery to stations ==
-Every day is 74 ticks. every 256 ticks cargo is delivered to stations (8 or 9 times a month, every 3.5 days).
+Every day is 74 ticks. every 256 ticks cargo is delivered to stations (8 or 9 times a month, every 3.5 days). The default amount of cargo produced is in src/table/build_industry.h. The amount delivered can be 1/8, 1/4, 1/2, 1x, 2x, 4x, or 8x of the default value, depending on level of production.
 == vehicle loading rates ==

@@ Line 13: / Line 13: @@
 !Type
 !Ticks per Load
-!Units Cargo Loaded Per Tick
+!Units Cargo Loaded Per Load
 |-
 |Train
@@ Line 57: / Line 57: @@
 |}
 source: https://newgrf-specs.tt-wiki.net/wiki/Action0Cargos and  src/table/cargo_const.h
 = notes =

@@ Line 6: / Line 6: @@
 == vehicle loading rates ==
-When a vehicle is loading, cargo is loaded every: 40 ticks for trains, 20 ticks for planes/road vehicles, or 10 ticks for ships (src/economy.cpp "const uint gradual_loading_wait_time[] = { 40, 20, 10, 20 }", order is enumerated in src/vehicle_type.h). Using default rules, 5 units of cargo are loaded per vehicle per tick ()
+When a vehicle is loading, cargo is loaded every: 40 ticks for trains, 20 ticks for planes/road vehicles, or 10 ticks for ships. Each individual train car adds cargo every loading event, so longer trains load more per tick than short trains. The default amount of cargo loaded is seen below:
 {| class="wikitable"
@@ Line 29: / Line 29: @@
 |Air
 |20
-|20
+|20 for all except mail (5 for mail)
 |}
 From: (src/economy.cpp "const uint gradual_loading_wait_time[] = { 40, 20, 10, 20 }", order is enumerated in src/vehicle_type.h)
-src/tables/engines.h
+src/tables/engines.h. NewGRFs define the loading_speed property which is not visible in the client (maybe it should be?). It is in the item "property" or "graphics" setting. for example, brickwalker in NUTS has a loading_speed=2.
 unit of cargo is defined in the default OpenGRF as:
 {| class="wikitable"
-! Cargo slot !! Default cargo in this slot !! Property 1D !! Meaning
+! Cargo !! Multiplier !! Meaning
 |-
-| 00 || PASS || 0x400 || A vehicle carrying 1 ton of coal, can carry 4 passengers.
+| PASS || 4 || A vehicle carrying 1 ton of coal, can carry 4 passengers.
 |-
-| 02 || MAIL || 0x200 || A vehicle carrying 1 ton of coal, can carry 2 bags of mail.
+|  MAIL || 2 || A vehicle carrying 1 ton of coal, can carry 2 bags of mail.
 |-
-| 05 || GOOD, SWET || 0x200 || A vehicle carrying 1 ton of coal, can carry 2 crates of goods/sweets.
+| GOOD, SWET || 2 || A vehicle carrying 1 ton of coal, can carry 2 crates of goods/sweets.
 |-
-| xx || (everything else) || 0x100 || All other slots default to 0x100, i.e. 1 unit of cargo equals 1 ton of coal.
+| (everything else) || 1 || All other slots default to 1, i.e. 1 unit of cargo equals 1 ton of coal.
 |}
-https://newgrf-specs.tt-wiki.net/wiki/Action0Cargos
+source: https://newgrf-specs.tt-wiki.net/wiki/Action0Cargos and  src/table/cargo_const.h
 = notes =

@@ Line 1: / Line 1: @@
 See my [[New Player Pointers]]
-research:
+= game mechanics =
-* 2 ticks per day
+== cargo delivery to stations ==
-* 12 kL oil per tick
+Every day is 74 ticks. every 256 ticks cargo is delivered to stations (8 or 9 times a month, every 3.5 days).
 rate equiations

@@ Line 21: / Line 21: @@
 * start with furthest station, make all other stations merge with sideline with priority given to furthest station
 * optimize flow from furthest station (overload with trains such that waiting cargo goes to 0, and overflow is full. wait for steady state
-* when at steady state (i.e., multiple round trips of trains generated on demand) delete excess trains in overflow from furthest station. this station now generates trains on demand. Excess trains mean the total trains servicing the station should be round trip time times industry generation rate
+* when at steady state (i.e., multiple round trips of trains generated on demand) delete excess trains in overflow from furthest station. this station now generates trains on demand. Excess trains mean the total trains servicing the station should be round trip time times industry generation rate. At steady state, a train is returning to station as often as it is being generated, so any train in overflow is excess!
 * move to next closest station, repeat.
 * at end, each station will generate trains on demand. If, in steady state, on track never moves (because it has worst priority) - that means you need a second sideline. Start it from there, and all later stations merge with this new one.
 * repeat
 * if you added sideline out, will also need to add a new sideline in

@@ Line 15: / Line 15: @@
 Drop off station size
 * limited by input capacity, which is = number of input tracks * max track capacity
-** number of
+** min number of  stations tracks determined by number of input tracks (make unload capacity = loading capacity)

← Older revision		Revision as of 18:42, 28 July 2016
Line 1:		Line 1:
	See my [[New Player Pointers]]		See my [[New Player Pointers]]
		+
		+	research:
		+	* 2 ticks per day
		+	* 12 kL oil per tick
		+
		+	rate equiations
		+
		+	pick up station
		+	* generation rate
		+	* loading rate * station size
		+	* what limits: track capacity, loading rate or generation rate?
		+	** ideal, limit by generation rate. Generation rate determines min number of station tracks, and number of station tracks determines sideline size
		+
		+	Drop off station size
		+	* limited by input capacity, which is = number of input tracks * max track capacity
		+	** number of
		+
		+
		+	clearing sideline jams:
		+	* start with furthest station, make all other stations merge with sideline with priority given to furthest station
		+	* optimize flow from furthest station (overload with trains such that waiting cargo goes to 0, and overflow is full. wait for steady state
		+	* delete excess trains in overflow from furthest station. this station now generates trains on demand.
		+	* move to next closest station, repeat.
		+	* at end, each station will generate trains on demand. If, in steady state, on track never moves (because it has worst priority) - that means you need a second sideline. Start it from there, and all later stations merge with this new one.
		+	* repeat
		+	* if you added sideline out, will also need to add a new sideline in