Calculation Question

shepard_3 · Post by **shepard_3** » Sat Nov 05, 2011 7:36 pm

Recently I've tried to make a quick calc how long the travel will take (Evochron Mercenary). But I couldn't figure out the rigth units...

#1 Is your velocity displayed in Miles per second, or Meters per second?

#2 Let's say my Nav marker is 50K away. That means 50'000 km or miles or anything other?

#3 Now if I travel at 558 Meters/Miles per second (whatever the answer to question #1 is), how long would it take me to get there?

I thought the formula is Time=Distance/Velocity! But without right units it won't help me.

[Edited on 5-11-2011 by shepard_3]

SeeJay · Post by **SeeJay** » Sat Nov 05, 2011 7:51 pm

Hi Shepard.

I do like math myself and your formula for speed/time and distance are correct.

However, in space things are a bit different in my opinion.

I make it really easy for myself and only calculates the time/amount of jumps it takes
to get from A to B.

It all depends on what jumpdrive you have.
The only thing you really need to calculate is your travel distance (sectors) using Pythagoras theorem
and then devide it with the max jump available. (Mantis = 10).

If you are not into math, I'll be happy to create a spreadsheet doing it for you.

/SeeJay

Busch · Post by **Busch** » Sat Nov 05, 2011 8:16 pm

Okay, Shep, I'll give it a shot.

1. Velocity displayed is in meters per second (mps). Same with altitude.

2. If you have a way point marker that tells you on your HUD, that it's 50k away from you, it's 50 kilometers away.

3. Well, it seems your question addresses speed in IDS, probably IDS 1 for your frame and engine set. The IDS speed is scalable through two toggles. "IDS Increase", "IDS Decrease", and can be found on page three of the configure controls screen in options menu, in-game. Speed percentages in IDS can also be adjusted by using the numbers 1 thru 0 keys on your keyboard. Now, having said that, most pilots either aim for the way point directly, or off-set their heading a bit. Then, fire F2, and you should end up near to your target. Sometimes, it takes a bit of flying/coasting (IDS or Inert) before the red/pink/salmon/purple blip shows up on radar. The blip is your quary, usually. Hope this helps.

[Edited on 11-5-2011 by FADM Busch]

shepard_3 · Post by **shepard_3** » Sat Nov 05, 2011 9:19 pm

It looks like my question was a bit misunderstood.

Actually, I wanted to know the time it takes to travel to a point in 100% IDS Speed (which is 560 with my current engine, just started career).

So 50000/560=89.3 which are about 1.29 minutes. And that concludes my big calculation!

And don't worry, I wont travel around with IDS Speed. I was just wondering how long it would take in real...

So thanks for the help.

[Edited on 5-11-2011 by shepard_3]

Post by **Marvin** » Sat Nov 05, 2011 11:54 pm

Easiest way to get a handle on it is to set a waypoint that's exactly 10 sectors away. Then head for the waypoint at 1000 "units of speed" and time it. From that you can determine how big the sectors are and how they jive with the speed indicator.

Maarschalk · Post by **Maarschalk** » Sun Nov 06, 2011 12:10 am

From post: 118838, Topic: tid=8108, author=shepard_3 wrote:It looks like my question was a bit misunderstood.

Actually, I wanted to know the time it takes to travel to a point in 100% IDS Speed (which is 560 with my current engine, just started career).

So 50000/560=89.3 which are about 1.29 minutes. And that concludes my big calculation!

And don't worry, I wont travel around with IDS Speed. I was just wondering how long it would take in real...

So thanks for the help.

[Edited on 5-11-2011 by shepard_3]

Ahem, it is all relative.

First of 89.3 seconds is aproximately 1.49 minutes and not 1.29 minutes
1.49 minutes is aproximately 1 minute and 29 seconds!
1.29 minutes = 1 minute and 17.4 seconds!...just some relative corrections....don't want things to be confusing....

:P:P:P:P:P

shepard_3 · Post by **shepard_3** » Sun Nov 06, 2011 7:05 am

Uups.... Well, I meant the right thing...

Maarschalk · Post by **Maarschalk** » Mon Nov 07, 2011 6:02 am

Well, that is what counts, the intend, relatively speaking that is!......

:P

[Edited on 11-7-2011 by Maarschalk]

shepard_3 · Post by **shepard_3** » Mon Nov 07, 2011 5:02 pm

I tried it out myself and the previous calculation was wrong.

I will not reach a point 50K away in 1.29 minutes. Never. Ever.

So I tried out some different things and found out the following:

I think the speed indicator doesnt show up meters per second! I don't know if it was a game designing choice or whatever.
But if I use 55 meters per second (which are about 200 kmh) the time and distance works right.

So heres my conclusion:

Speed: indicated in (meters per second)*10

Distance: for example 50K = 50 km

Time: self explanatory

So if I want the flight time the formula is Time (seconds) = Distance(m) /Speed (mps). For my example: 50'000m/55mps = 909s /60 = 15 Minutes

I hope its right now. From my testing in game this should be right. YAY

The only thing I'm wondering now is why the idication for the speed was altered. Of course 558 looks better than 55.8 but it doesnt really make sense to me.

shepard_3 · Post by **shepard_3** » Mon Nov 07, 2011 5:15 pm

Oh and if anyone wants an easy cal without having to recalculate all the units: http://www.csgnetwork.com/csgtsd.html

Its nearly too easy with it.

Post by **Marvin** » Mon Nov 07, 2011 7:58 pm

Now that you've made an issue of it, I think I'll use "sub-sectors per second" (SS/S) as my speed designation.

Maarschalk · Post by **Maarschalk** » Mon Nov 07, 2011 8:03 pm

From post: 118935, Topic: tid=8108, author=shepard_3 wrote:I tried it out myself and the previous calculation was wrong.

I will not reach a point 50K away in 1.29 minutes. Never. Ever.

So I tried out some different things and found out the following:

I think the speed indicator doesnt show up meters per second! I don't know if it was a game designing choice or whatever.
But if I use 55 meters per second (which are about 200 kmh) the time and distance works right.

So heres my conclusion:

Speed: indicated in (meters per second)*10

Distance: for example 50K = 50 km

Time: self explanatory

So if I want the flight time the formula is Time (seconds) = Distance(m) /Speed (mps). For my example: 50'000m/55mps = 909s /60 = 15 Minutes

I hope its right now. From my testing in game this should be right. YAY

The only thing I'm wondering now is why the idication for the speed was altered. Of course 558 looks better than 55.8 but it doesnt really make sense to me.

This indeed does not sound right!. Space is huge so 50km is nothing. I think when you talk about 50K in the game for distance in Space it is 50000km and 55km/s for speed!

Now for Planetary distances and descent it is 50km and 55m/s
I think! anyway the time is the same.....

:P

shepard_3 · Post by **shepard_3** » Tue Nov 08, 2011 5:58 am

Right, so now we figuered it finally out!

50K = 50'000km
550 velocity = 55km/s

50'000 / 55 = 909s / 60 = 15 min

So why is everywhere written meters per second? It should be kilometers per second and the number indicated would is wrong too!

Anyway, looks like we solved the hole thing.

Thanks for everyones help.

Post by **Marvin** » Tue Nov 08, 2011 6:22 am

From post: 118995, Topic: tid=8108, author=shepard_3 wrote:Anyway, looks like we solved the hole thing.

You may have solved the whole thing but the hole thing requires a shield upgrade, proper orientation and perfect timing.

shepard_3 · Post by **shepard_3** » Tue Nov 08, 2011 9:15 am

ups... again!
I could edit it, but that would ruin your good joke!

[Edited on 8-11-2011 by shepard_3]

Maarschalk · Post by **Maarschalk** » Tue Nov 08, 2011 5:24 pm

From post: 118997, Topic: tid=8108, author=Marvin wrote:
From post: 118995, Topic: tid=8108, author=shepard_3 wrote:Anyway, looks like we solved the hole thing.
You may have solved the whole thing but the hole thing requires a shield upgrade, proper orientation and perfect timing.

You forgot to add to the list: "Correct coordinate caculation input".........another relatively related relative part of the equation to solve the hole in the whole thing. Or you could just simply leave the w out!.....

:P:P:P:P:P:P:P:P

Post by **Marvin** » Tue Nov 08, 2011 6:42 pm

From post: 119042, Topic: tid=8108, author=Maarschalk wrote:You forgot to add to the list: "Correct coordinate caculation input" ....

I was in a hurry ... I was afraid he'd catch his mistake and correct it before I could post a "gotcha."

shepard_3 · Post by **shepard_3** » Thu Nov 10, 2011 5:22 am