The changes ''for science''

Speedrunning KSP2 has finally reached a more stable point, this being due to the introduction of reentry heating and new joint physics. This forum will discuss how changes to the game will affect the leaderboards. At the moment I got two ideas for adapting the KSP2 leaderboards to the new KSP2 v-2.0.0:

Options

1. Archiving all existing pre-v2.0.0 and starting from new
2. Separate the categories into two separate but both existing leaderboards

The benefits with (1.), runs will be preserved but won't be shown, while keeping the leaderboards cleaner. Fixing the leaderboards likely will never happen again since a gameplay mechanic like reentry heating won't be introduced again to greatly impact the game. Personally, I prefer (1.), but if anyone would like to object or come up with new ideas it would be appreciated. But most likely I will go with option 1.

Running Kerbal Space Program 2 is the same for everyone when loading or creating a new game file. This means when starting a game the planets are all going around kerbol identical to other files. Knowing this Im currently hunting in-game times that ideally get you an encounter by clicking a button and getting a perfect encounter. At the time of post, I have 3 god times and I will continue with updating this thread when discovering times. These times are necessary when completing a run. For more on how it works look at my DUNA 1:11 run. Discovered:

Mun --- 1y,1d,3h,3m,03s

Jool ---- 3y,271d,4h,14m,00s

Duna --- 1y,224d,4h,16m,00s

Eve --- 5y,205d,4h,14m,00s

All the times are wrong due to update!!!

PLEASE DM IF YOU FIND A TIME AS TO NOT CREATE SPAM

This will cover 'every' type of engine to use in differing environments: these being ATM and VAC and both. Doing research on each engine in desired situations is important, and with most runs Runners use either (Mammoth or Vector engines). To layout the foundation for which engines to use I confirmed the Mammoths to be best in terms of T/KT in comparison to other engines, the next higher performance engine is actually not the Vector, but the Skipper and Mainsail engines. Present Info on the Vector engine and the two other better engines, it is important to identify 3 values [ATM(A), VAC(V) and AAV] value. ATM is Atmospheric T/KT performance, VAC is Vaccum T/KT performance and AAV which is AvgAtmoVac which is used in environments evolving both Atmosphere and Vaccum.

The Vector Engine has an (A) value of (192.25), (V) Value of (212.5) with an (AAV) value of (202.375) performance when in atmospheric conditions.

The Mainsail Engine has an (A) value of (230.18), (V) Value of (266.66) with an (AAV) value of (248.42) performance when in atmospheric conditions.

The Rhino Engine has an (A) value of (191.83), (V) Value of (218.75) with an (AAV) value of (204.29) performance when in atmospheric conditions.

The Mammoth Engine has an (A) value of (246.77), (V) Value of (283.33) with an (AAV) value of (265) performance when in atmospheric conditions.

To conclude Vector is a hybrid of the Rhino Engine Better at ATM but worst at VAC. The Vector AAV performs worst than Rhino. This means the Rhino is better when changing ATM and when in a vacuum it is still better than the vector making the Rhino better overall it scores 2/3. What will surprise most people is the [Mainsail engine's] performance is near to the Mammoth engine and is 20%~ better than Vector and Rhino. Mainsail scores 3/3 compared to Vector and Rhino. However, it should be noted it doesn't make the Mainsail better it should be used in consideration as a second choice for landers and such. The values do not change with additional engines (all of the engines have been ratioed 1:1). Finally to state you should only use Mammoth engines if you want performance but the Mammoth will have much lower stability and in a future post I will discuss stability to elaborate on better engines to choose. Order of Engine Power [Mammoth, Mainsail, Rhino, Vector]