Time to complete a job (lol math)

[Kick_McCan]

How much real world time is it going to take to do some job? Work with me and tell me if my math's whacked

assume: 1000 mile job
assume: avg 60mph speed

1000/60 = 16.666 so let's round down to 16 in-game hours to drive 1000 miles at 60mph
16 hours x 60 minutes per hour = 960 minutes

(this is where it gets weird)
assume: 1 game minute = ~3 seconds (I haven't measured, that's just what it seemed like when I counted it off)
960 game minutes x 3 real world seconds per minute = 2880 real world seconds to drive 1000 miles
2880/60 seconds per minute = ~48 real world minutes to drive a 1000 mile job at 60mph


Is that ballpark or am I way off? or is there something in the game that actually tells me this and I missed it lol

[ttower]

That seems reasonable for a timeframe. The game runs at a 1:20 Scale on highways and a 1:3 scale in cities by the way. It really doesnt matter how long it takes IRL, as you can stop at any point you want and continue later, which is one reason that it does not show this information to you.

[Kick_McCan]

Right. But I'm level 24 working on 25 so I can get some sort of top end truck, so I'm looking at jobs going how long is this going to take

[Pete Gaimari]

1 game hour is 3 min in real time.

[Wolfgang]

Too complicated. Just do the following rule of thumb:
10 hours driving in game = 1 hour IRL.

Works pretty well.

[Viper]

Well... WHICH ONE IS IT? 1 game hour every 3 minutes real time or 10 game hours every 60 minutes?

[The Pitts]

Neither, because three minutes for an in game hour requires perfect conditions (open road with no city scale sections) whilst Wolfgang stated clearly that his numbers were a RoT. FWIW I use five minutes an in game hour as my RoT, so you now have three to choose from :)

[dbwhip42]

Funny how the brain works. I've done this same "math." I usually look for "mid range distance" trips (dont remember the setting in preferences). Those usually come in at 3-5 hours. I am at the point that I can guesstimate the time frame looking at the map. Using a WAG of 5 minutes real time per hour (I know thats overkill) that gives me a 15-20 minute real time session. I can knock that out on a gaming "break". occassional cross country but then all timing bets are off.

[Middleclaw]

I usually play it safe and go for One In Game Hour lasting Four Real Time Minutes to compensate for traffic, cities, weigh stations, etc. 95% of the time you will arrive before the time is up, unless you're doing a WOT job where you're real time limited from the time you took the job.

[Pete Gaimari]

Originally posted by The Pitts:

Neither, because three minutes for an in game hour requires perfect conditions (open road with no city scale sections) whilst Wolfgang stated clearly that his numbers were a RoT. FWIW I use five minutes an in game hour as my RoT, so you now have three to choose from :)

He asked at an average 60 mph.

[The Pitts]

and I answered accordingly.

Let's do a little experiment. Take I15 N from St. George UT and once you're up to a steady 60 MPH time how long it takes you to get to just before the southern junction for Cedar City (both in terms of wall clock time and in game time) then take those same timings from there to just north of the second Cedar City exit, still at a steady 60 MPH. See what I'm getting at now?

[Wolfgang]

Originally posted by Pete Gaimari:

Originally posted by The Pitts:

Neither, because three minutes for an in game hour requires perfect conditions (open road with no city scale sections) whilst Wolfgang stated clearly that his numbers were a RoT. FWIW I use five minutes an in game hour as my RoT, so you now have three to choose from :)

He asked at an average 60 mph.

Sure. But you aren't always driving 60 mph now, are you? And that is when this question of the OP comes in:

Originally posted by Kick_McCan:

How much real world time is it going to take to do some job?

The assumption is nice but simply doesn't hold up. Hence the rules of thumb as they give you a good estimation. You might be faster or slower depending on various factors.

[Wille Wilse]

Originally posted by The Pitts:

Neither, because three minutes for an in game hour requires perfect conditions (open road with no city scale sections) whilst Wolfgang stated clearly that his numbers were a RoT. FWIW I use five minutes an in game hour as my RoT, so you now have three to choose from :)

I do the same - its always gonna be somewhere at this ballpark.

[Pete Gaimari]

Yes, but I never do that. If i'm driving along a job and want to know how long it will be to get to the deliver point. I just look at the amount of hours are left to get to finish. If it's 8 hours I know at 60 mph it will be 24 min. I don't need exact. Just about works for me. I make small adjustments for going different speeds.

Why would someone need to know exactly how long a job takes?

[Middleclaw]

Just for comparison, I just did a 1,877 mile job and it took me 108 minutes (real time) at 65 mph. you could use that as a base line, nor not. Just trying to help.

[SoanoS]

Originally posted by Pete Gaimari:

Why would someone need to know exactly how long a job takes?

Sometimes people can not always sit full 3 hours through one delivery.
Luckily external (World of Trucks) contracts are generous with the time limit as the blue timer is RL time.