Is it a long term lose to transmit experiment data in KSP .23+?

Is it a long term lose to transmit experiment data in KSP .23+? - Photo Of Sound Engineer On Sound Studio

We have a question that is almost the same as this one...but the question and answer both pertain to an earlier version (< .23), and note that the specific answer was to change with the newer version.

I know that if I do an experiment and recover the data by bringing the ship back to Kerbin and recover the ship, I get 100% of the experiment value. I also know that if I transmit the data back, I get a smaller percentage (which can vary, depending on various things).

Also, experiments can be repeated, but their value decreases with repeated runs.

So the question is: is it fine to transmit science experiment results back, and not have to worry too much about losing potential science gain in the long run?

(The answer to the earlier question was that it was fine; regardless of how you did it, you ended up with the same amount of science in the long run, for the most part, if you ran all experiments until they returned nothing. But, again, the answer also mentions that this was to change in some way with .23+, but it didn't say in what way.)






Pictures about "Is it a long term lose to transmit experiment data in KSP .23+?"

Is it a long term lose to transmit experiment data in KSP .23+? - Engineers in Sound Studio
Is it a long term lose to transmit experiment data in KSP .23+? - Photo Of Female Engineer Doing Tests
Is it a long term lose to transmit experiment data in KSP .23+? - Woman in Brown Coat Holding A Blue Book



What is the easiest way to get science in KSP?

In the Science mode, the game's goal is to essentially unlock the entire tree through gradually advancing launches and experiments. The primary way to get more science in the game is to use Kerbals to perform experiments and surveys, then send that data back to the space center (KSC).



8 STUPID MISTAKES everybody makes in Kerbal Space Program




Sources: Stack Exchange - This article follows the attribution requirements of Stack Exchange and is licensed under CC BY-SA 3.0.

Images: ThisIsEngineering, ThisIsEngineering, ThisIsEngineering, Andrea Piacquadio