Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
So, (for anyone not klicking the link) the formula is supposed to be:
(0.3 + {distance in km}) * {pricing formula of vehicle type}
- Road: ticket_price = top_speed^0.78 + 4
- Rail: ticket_price = top_speed^0.86 + 10
- Air: ticket_price = -2.03*10^-5×top_speed^2 + 0.17*top_speed + 28.36
- Water: ticket_price = 0.65*top_speed
But this still leaves out a few questions though..
1. if that's the case, then why did the pricing of 1km chnage along with a change of hight? I.e. when my 70km/h bus transported people over 1km to another station on the same altitude, ticket prices were lower then when the start and the end station were not on the same altitude. The bigger the hight difference, the bigger the price difference. Is this because change in altutude creates a slightly longer route, since that's how the pythagoras theorem works?
2. if the "0.3 + distance in km" was true, then that would be equal to my initial guess, that there is a base fee to pay. But that didn't seem to add up. However, this might have also been thrown off by the random "+4" added with the "ticket price for the vehicle type". I will try confirm these things by testing them out and I will post about my findings here.
3. As far as I know, ticket prices are also affected by the difficulty. A factor which is completely absent from the redit post. Though, I have to admit that I left this factor out of my initial tests too. All my calculations were done on easy mode. I'm guessig that the data provided by the redit post is was using "normal difficulty". I will try to confirm this too.
Let's say I use the 70km/h bus. So, according to the formula, I can calculate the earnings per passenger as such:
(0.3 + 1km (the passengers travel route I set)) *70^0.78 + 4 = 1.3 * 31.49 = 40.94
In no game difficulty is this even remotely what the earnings are. I have tried easy, normal (now medium apparently) and very hard (yes, i left out hard, but I doubt this would have been the one). The lowest payment I received per passenger (in very hard mode) was 1'010. According to the formula, it should have been around 41.
I might missinterpret something or am leaving out some crusial detail, but I just don't understand the pricing system.
Any thoughts?
https://steamcommunity.com/sharedfiles/filedetails/?id=3040668938
Ticket price is explicitly quoted in 1 but not in 2 (same method though) . Here a 103mph vehicle as $2.61K so the quoted formula for price is not correct without further adjustment.
Going up elevation is a thing , I have tested it and got the 7.5* multiplier by building a massive uphill railway.
Here you go using TpF1. Looks correct when multiplied by about 66 .
Loco T/price Kmh ^.86+4
103mph 2610 64.375 35.93327724 39.93327724 2610 65.35902336
62mph 1800 38.75 23.22275112 27.22275112 1800 66.12116431
56mph 1670 35 21.27641821 25.27641821 1670 66.06948763
Also, you suggest a multiplier of "about 66", right? Howcome and how does that change?
Finally, I cannot really follow your chart at the end, what does it show exactly?
Thanks for clarifying
Train T/price
103mph 2610
99mph 2550
62mph 1800
56mph 1670
Truck T/price
31mph 723
22mph 575
so using 99mph .
(1km + 0.3 bonus km) * 2550 = $3315
and if we have 10m increase in height (10m decrease is ignored)
(1km + 0.075 + 0.3) * 2550 = $3506
Ah, so you are explaining how you can calculate it in tpf1, since the pricing is portrait in the information tab (as you showed in the picture of your first post).
So, given tpf1s Information you would calculate:
({distance in km} + 0.3}) * {ticket price portrait in information trab} * {passenger count}
Okay, I got you then. My question though is, how do I get the information for the ticket price (that you can see in your vehicle information window)? SInce this is (as you have stated coreectley in your post) not portrait in tpf2 anymore.
In your initial rail analysis the ticket price was 5198 for one test and 5226 for the other , assuming 300m free is correct.
I think in easy mode revenue may be *2 of standard perhaps as this goes back near to TpF1 fig of just over 2550 (5100 if *2) .
Maybe the distances are not perfect and flat ?
The way I understand it the 300m are not free. On the contrary, they are payed additionoally to the actual length of the journey. At least, that's what the reddit post said and considering you are adding 0.3 instead of subrtracting them, I am pretty confident in that assumption.
What price values about my tests are you talking about exactly? I have only stated two values "6'009 and 6'758". Do you mean these results? How did you arrive at "5198 and 5226"?
Anyhow, maybe doug can provide clarity with their scripting idea
So 6758 / (1 + 0.3) = 5198 notional ticket price
for 2km : $12019
so 12019 / (2 + 0.3) = 5225 notional ticket price
hence the figure is about 5200 assuming you get 300m added to the distance which would look about right.