Confusingly inconsistent units - "/sec" vs days?

[baldamundo]

So we've got:
- Days, for:

• the regular flow of the game in the top right corner
• research speed

-Years, for:

• most or all economic statistics?
• ship maintenance
• diplomacy trends

-5 year period, for:

• trade income in the diplomacy screen

-Unlabelled:

• population growth [probably annual?]
• most economic statistics

-"sec" [presumably seconds?], for:

• mining rate
• estimated resource demand
• construction & repair time/speed
• everything in the ship design menu other than maintenance

Most of this is probably fine. It could do with a lot more tooltips for the economic statistics and for planetary growth, but I'm assuming it must all be annual. Probably the trade statistics in the diplomacy screen ought to be changed to an annualised figure for ease of comparison too. And, yeah, it makes sense to use days for research when times are short.

But what on earth do the "per second" figures mean? I assume they can't be game-time, because then you'd need to multiply every figure by x86400 to work out how many days it is and give you a figure that means something in the context of the rest of the game. But it can't possibly be real-time either, because there are 5 different speed settings for the game, and even at normal speed, the game will run faster or slower depending on your hardware, the size of the galaxy, how buggy it is, etc etc.

So is the use of 'per second' just a mistake/oversight? Should it be "per tick" or "per day"? And if the former, how many ticks are there in a game-day? As it is, there are vast swathes of crucial data in the game that are completely impossible to contextualise.

[kanliot2]

Bump. Game is running good, but I often want to know how long it takes for my fleet to travel.

"Good" hyperdrives are 400K in speed, but I've speed tested it in game, to .65M per day. What gives?

Cheers

**edit: I'm thinking the game started out as day = second, and it just got tweaked a bit to make the gameplay a bit faster. B/c that's what I would do & I'm very smart. So really, there is no answer, there's just a line of code that updates location and it reads (newx=x+hyperv * days*1.6)