Can't reach a destination for fullerene ...

You should have stuck with 4 fuel tanks, the extra weight actually reduces your max. distance.

More fuel adds weight as well. Fill the last fuel and o2 tank with 598 kg each.

Spoiler

This tool might help:

https://oni-assistant.com/tools/rocketcalculator

You don't get the point.

The gilded asteroîds need a thrust for 130 000 km.

I don't want to go to 110 000 km. As I said, before putting these new tanks, I managed to get there.

 

A standard petroleum engine don't seem to be able to get this far with a cargo bay on the rocket.  

Confirmed by the tool you linked.

Edited September 5, 2019 by Gwido

While having the only fullerene source so far away is really hard, its not impossible. You are able to make LOX, what you´ve already done. Now you need LH for the fuel tanks. While its not convenient at all, its possible to make it. It involves a lot of work and other problems, but you may be able to produce enough LH to reach your destination, and then make super coolant. 

 

Your screenshot shows: Gilded Asteroid with Fullerene at 110 000 km, unreachable with the current rocket.

My answer shows how you can get there with a petroleum rocket. My screenshot also shows that the rocket includes a cargo bay to bring Fullerene back.

I don't get why you'd need to go 130 000 km.

1 hour ago, Yalp said:

Your screenshot shows: Gilded Asteroid with Fullerene at 110 000 km, unreachable with the current rocket.

My answer shows how you can get there with a petroleum rocket. My screenshot also shows that the rocket includes a cargo bay to bring Fullerene back.

I don't get why you'd need to go 130 000 km.

It's not a gilded asteroïd at 110 000.  

I don't know why, but the destination infos are those of the asteroïd pointed by the arrow on the screen.

If you look closer on the upper right corner of the info, it's about one of the two gilded asteroïds at 130 000.

Oh well, the 2 big icons that usually indicate your selected item are very very confusing then. Maybe Klei should fix that visual bug as well, while they are at it ...