# My space travel

#### Keatah

##### Active member
Are you periodically saving the scenario?

#### vinny5000

##### New member
Hi, Keatah!

Yes, I periodically saving the scenario. I quick save the scenario about every 6 hours and real saving the scenario about every 24 hours.

Cheers,
Vincent

#### Scav

##### Mostly Harmless
Hehe. I was going to say . . . if there was a power outage, would that be considered LOC/V, or just LOS?

#### Keatah

##### Active member
Do you have a chronological list of scenarios? I mean could you go back 6 days ago for some reason? Or perhaps 6 weeks ago?

#### vinny5000

##### New member
Hi, Keatah!

It took me about 5 months to get to the distance of 2,605,800,000,000 kilometers or 17,419 AU away from the sun and the speed of 401,692 kilometers per second which the spacecraft would get to the moon in 1 second!! i'm using real time (no time acceleration at all! Like I said in my previous posts, my goal is to get to the distance of about 200,000 AU or about 30,000,000,000,000 kilometers or about 18,000,000,000,000 miles away from the sun by the new year of 2015!

Cheers,
Vincent

Last edited:

#### vinny5000

##### New member
Hi, guys!

I'm now 2,855,275,000,000 kilometers or 19,087 AU away from the sun and moving at the speed of 420,200 kilometers per second!!

Cheers,
Vincent

#### JonnyBGoode

##### Sky Marshal
The edge of the orbiter universe is at 999999999 AU from the star of whatever solar system you use.

By my calculations, that's a radius of about 15812.5 light years. That seems a bit much - or I figured wrong.

#### vinny5000

##### New member
Hi, dgatsoulis!

Holy mackerel! 999,999,999 AU or about 149,599,999,850,400,000 kilometers away from the sun to the edge of the orbiter universe? I guess I got plenty of space to travel!!

Cheers,
Vincent

#### garyw

Tutorial Publisher
Except that once you're out past Pluto there isn't anything in the orbiter universe. no other planets, nothing to do and you can't even dock with anything.

#### JonnyBGoode

##### Sky Marshal
Well there are the various Kuiper belt add-ons. But some of the MFDs stop working correctly out that far.

#### vinny5000

##### New member
Hi, JonnyGoode!

Luckily, the MFDs in my spacecraft is still working right that far out!!

Cheers,
Vincent

#### JonnyBGoode

##### Sky Marshal
Last time I was out that far, I recall having serious difficulty plotting a course to Sedna, and the Orbit MFD only showing a part of its orbit.

#### vinny5000

##### New member
Hi, JonnyBGoode!

How far away from the sun when you start having difficulty plotting a course to Sedna, and where is Sedna located? Thanks!

Cheers,
Vincent

#### vinny5000

##### New member
Hi, JonnyBGoode!

I don't understand why orbiter starts to get inaccurate when got out past Neptune's orbit. I think the orbiter needs to be fix so it can be accurate when as far out as past Neptune's orbit, since the universe in orbiter is 999,999,999 AU from the sun to the edge of the universe in orbiter.

Cheers,
Vincent

#### Ghostrider

##### Donator
Donator
Last time I was out that far, I recall having serious difficulty plotting a course to Sedna, and the Orbit MFD only showing a part of its orbit.

Last time anyone was out that far, we lost both ships.

#### garyw

Tutorial Publisher
I don't understand why orbiter starts to get inaccurate when got out past Neptune's orbit.

Because of the distances involved. Remember that Orbiter simulates the solar system with some decent accuracy - including distances - so when ranges out to Neptune start to get involved the simulation has a few issues handling the huge numbers involved. Essentially, the sun is 0,0,0 in terms of co-ords. Your ship is still bound to the sun so check out the RPOS in your scenario.
I have a probe that's just out past Earth which shows this: RPOS 124800241358.647 -4105180826.724 31978803327.806 and that's a large set of numbers for the simulation to cope with.

I think the orbiter needs to be fix so it can be accurate when as far out as past Neptune's orbit, since the universe in orbiter is 999,999,999 AU from the sun to the edge of the universe in orbiter.
For me, having all the planets to explore plus a bunch of asteroids is more than enough entertainment, once you're out past pluto that is it. There is nothing else to see.

#### orb

I don't understand why orbiter starts to get inaccurate when got out past Neptune's orbit. I think the orbiter needs to be fix so it can be accurate when as far out as past Neptune's orbit, since the universe in orbiter is 999,999,999 AU from the sun to the edge of the universe in orbiter.

Floating point numbers used by Orbiter and FPUs have a limited precision. The precision for 'double' variable is 53 bits or around 15-16 decimal digits.

It isn't broken or bugged. It was designed this way, and nowadays PC processors don't support quadruple precision floating point numbers yet, only double (and 11 bits more precise 'extended', but only if you write in assembly).

A "fix" could be changing arithmetics used by Orbiter to arbitrary precision (or somehow faster double-double / triple-double / quad-double), but it would make all add-ons incompatible, and it would be much slower than operating on numbers purely native to hardware.

And then somebody can say: "Orbiter needs a fix because it's too slow".

#### Face

Beta Tester
I always wondered what happens with gbody-relative coordinates (as in VESSELSTATUS) vs. "global" coordinates in the numerical error regions. Of course the gbody ones are much more precise due to being closer to the origin, while the global ones have to deal with the huge offset.

If I set a vessel to a fine-tuned position around a far-out gbody, would Orbiter round it to the less precise global position before calculating the new positions? I guess physics calculation can be done gbody-relative, while rendering will suffer from the need of a global coordinate system due to the way DX works.

#### vinny5000

##### New member
Hi, guys!

I'm now 3,116,000,000,000 kilometers or 20,830 AU away from the sun and moving at the speed of 439,041 kilometers per second!

Cheers,
Vincent