Return of the NaNo virus

[Xannari Ferrows]

I've a problem. It just happened, my worst fear... it's finally come true. The return of the one who puts even the Kraken to shame. The little white noise you hear whenever you clip parts together. The shadow you see moving in the corner of your eye. The o- (We GET IT!! Just move on) ...Jeez, fine.

The NaNo virus has found it's mark. I am among the first to be hit as far as I know; the first being Master Kerbalnaut Scott Manley. The NaNo virus started from within his computer, gathering strength and waiting for the right point to strike. The many glitches and bugs throughout the series? Who do you think was responsible? It got worse, until one day, during a descent trajectory with Kerbin, the NaNo virus made itself known to the world. It ruined the fuel supplies, and soon learned how to travel remotely, thanks in part to Remote Tech. With the ability to travel anywhere in the Kerbol system at light speed, it was only a matter of time...

Ships were wrecked, stations were brought down, and even the old low-tech Eeloo rocket wasn't safe. The Kerbals' only hope was to continue development on the Warp Drive, and send a group of brave Kerbals to a far, far away planet called Gaia. There, they would build a new space center, and start the program all over again. They knew that at warp speed, they left the NaNo virus several decades away... or so they thought.

However, the NaNo virus is not just another glitch in the system or a bug or something. It is an intelligence. Using the remains of the space center; now just a few piles of rubbish and a few computers running out of power, the virus worked through all the technologies, and figured out how to search space itself by using portable sub-light radio wave beaming antennae. Just soon after, a disturbance was detected within the outer reaches of the Kerbol system. Radio waves couldn't penetrate it, and sub-space itself seemed to have been damaged. There was a trail of this disturbance, perhaps leading to the new Solar system that the Kerbals have gone to, but it was concluded that it would take too long to navigate all the way down the trail without degrading.

However, reviewing through the files, there was an old experiment that the Kerbals once tried; a highly charged graviton field would create a severe bias in the sub-space continuum, and allow the pass into verteron space. The idea was scraped because of the danger it poses to the fine gravitational balance with Kerbol and the planets, but being the NaNo virus, it didn't care...

Several computational cycles have passed, the NaNo virus has synthesized enough graviton particles, and is prepared to launch them into a single concentrated point, which should have compressed the space between the Kerbol and Solar system enough to where it would take a matter of minutes to cross... but it didn't work that way. The rift was opened, but instead... it led to our world. All of a sudden, there were no limits; no game engine to power it down, nothing to give it bounds. It started to invade computers, one by one. Already, a few have been affected beyond repair, and I hope I will not be one of those. Here is proof of my experience:

Have you had experiences with the NaNo virus? What did you do to counter it?

[Slam_Jones]

I've a problem. It just happened, my worst fear... it's finally come true. The return of the one who puts even the Kraken to shame. The little white noise you hear whenever you clip parts together. The shadow you see moving in the corner of your eye. The o- (We GET IT!! Just move on) ...Jeez, fine.

The NaNo virus has found it's mark. I am among the first to be hit as far as I know; the first being Master Kerbalnaut Scott Manley. The NaNo virus started from within his computer, gathering strength and waiting for the right point to strike. The many glitches and bugs throughout the series? Who do you think was responsible? It got worse, until one day, during a descent trajectory with Kerbin, the NaNo virus made itself known to the world. It ruined the fuel supplies, and soon learned how to travel remotely, thanks in part to Remote Tech. With the ability to travel anywhere in the Kerbol system at light speed, it was only a matter of time...

Ships were wrecked, stations were brought down, and even the old low-tech Eeloo rocket wasn't safe. The Kerbals' only hope was to continue development on the Warp Drive, and send a group of brave Kerbals to a far, far away planet called Gaia. There, they would build a new space center, and start the program all over again. They knew that at warp speed, they left the NaNo virus several decades away... or so they thought.

However, the NaNo virus is not just another glitch in the system or a bug or something. It is an intelligence. Using the remains of the space center; now just a few piles of rubbish and a few computers running out of power, the virus worked through all the technologies, and figured out how to search space itself by using portable sub-light radio wave beaming antennae. Just soon after, a disturbance was detected within the outer reaches of the Kerbol system. Radio waves couldn't penetrate it, and sub-space itself seemed to have been damaged. There was a trail of this disturbance, perhaps leading to the new Solar system that the Kerbals have gone to, but it was concluded that it would take too long to navigate all the way down the trail without degrading.

However, reviewing through the files, there was an old experiment that the Kerbals once tried; a highly charged graviton field would create a severe bias in the sub-space continuum, and allow the pass into verteron space. The idea was scraped because of the danger it poses to the fine gravitational balance with Kerbol and the planets, but being the NaNo virus, it didn't care...

Several computational cycles have passed, the NaNo virus has synthesized enough graviton particles, and is prepared to launch them into a single concentrated point, which should have compressed the space between the Kerbol and Solar system enough to where it would take a matter of minutes to cross... but it didn't work that way. The rift was opened, but instead... it led to our world. All of a sudden, there were no limits; no game engine to power it down, nothing to give it bounds. It started to invade computers, one by one. Already, a few have been affected beyond repair, and I hope I will not be one of those. Here is proof of my experience:

http://i.imgur.com/pAEVDvk.png

Have you had experiences with the NaNo virus? What did you do to counter it?

I've had the virus attack on of my ships while it was on it's way to Jool. Turned it into a floating block of debris, basically. No idea how to counter it... I just avoided it until I started a new save.

[Robotengineer]

Is this a bug report?

[GiantTank]

The NaNo virus also seems to be responsible for an entirely new breed (or 2) of krakeni, modded games. The first one was shortly after I put the finishing touches on a 667,000 ton rocket (yes, that big, look in my posts) the game was crippled. Couldnt launch. Ships being built in the VAB lost parts midway through construction. Everything was bleak. It even spread through game installs, tearing into the stock game. Then, I built a 1.1 million ton rocket (yes, 1.1 million tons, RSS for you) and it ripped itself apart on the pad, throwing launch clamps on suborbital trajectories. I dont even know.

[Xannari Ferrows]

Is this a bug report?

Not really. Just in good fun. It's easy to get rid of, but I just wanted to be dramatic.

[Elowiny]

I experience the NaNo virus when I create a new planet with KopernicusTech.

I use HyperEdit to land on the planet, and suddently, the NaNo virus strike.

[Sampa]

same thing occured to me...totally ruined a test flgiht for me as it attacked my nav computers!

[bakanando]

Were you just launching?

Btw, how do you fix it?

[Xannari Ferrows]

Were you just launching?

Btw, how do you fix it?

I was just launching. To fix it in that circumstance, it would require a quicksave. No other circumstance is like this. You would need to restore your orbital parameters to a launching configuration, and possibly edit your fuel level back to normal. Basically just a hard reset.

EDIT: Though, another look at the picture, the air pressure gauge thinks I'm in space... I didn't intend to actually launch; just some seat positioning tests.

Edited April 5, 2015 by Xannari Ferrows

[Thomassino]

Yeah... I've been striken too. It happened on my ship intended to fly-by at 1 kerbol radius from the Sun. Switched to the ship in order to make a course correction to encounter Kerbin afterwards, but suddenly, the altimeter started to go crazy, everything fell into darkness and on velocity display, there was shining big NaN. But the konstructeers of the vessel were smart and had integrated auto-destruct sequence if something unexpected happened during the flight. So, NaNovirus is not a threat for now but who knows... maybe it will return in greater power.

[smjjames]

Actually, isn't that the Hell Kraken?

[Asharad]

Have you had experiences with the NaNo virus? What did you do to counter it?

Happened yesterday. I had to reboot my computer.

[nekogod]

Scott Manley encountered this at the end of his Interstellar Quest series, he had to warp to another star system to escape it!

[colonel0sanders]

I've had this happen on totally unmodded installs before. Always when switching to a ship in interstellar space

[ColourOfFire]

I had it on a couple of ships that consisted mainly of modded parts. Never encountered it in stock. For me it happened only with B9 and Interstellar combo's, I now play without both and so far so good *knock on wood*.

[Jim Kernan]

Just had it strike me, was hoping to set up a Duna base before 1.0 hit. My Kolony Control Module just got hit. I used the jump-to-ship feature of Kerbal Alarm clock. Was in interplanetary space.

[Xannari Ferrows]

IT HAPPENED AGAIN!!!

Even Kerbal Engineer doesn't know what to do!

[heng]

Well, since it is possible - and often the desired outcome - of an inclination change to give you an NaN as ascending node value, i assume it is not technically a bug per se. It seems, your ship/probe/base/planet was somehow reduced to a very very tiny version of itself... so tiny, that the resulting calculations result in either extremly high or very very close to zero results.

So in all likelihood you, sir, divided by zer... Oh Shiiiiiiii

[monophonic]

Well, since it is possible - and often the desired outcome - of an inclination change to give you an NaN as ascending node value, i assume it is not technically a bug per se. It seems, your ship/probe/base/planet was somehow reduced to a very very tiny version of itself... so tiny, that the resulting calculations result in either extremly high or very very close to zero results.

So in all likelihood you, sir, divided by zer... Oh Shiiiiiiii

Nah, dividing by zero would give +Inf or -Inf depending on whether what you divided was greater or lesser than zero... unless... that... was... also... exactly... zero..... Then you'd get #NaN.

[SAI Peregrinus]

qNANs propagate through calculations: Any calculation including a NAN yields a NAN. NAN is thus a trivial fixed point for all possible functions.

To cure the NANovirus edit your persistent.sfs file to have valid parameters for the craft in question.

[Voyager_sput]

Same thing happened to me a few times, unmodded, landed back on Kerbin, did an EVA and the second Valentina steps out and touches the surface poof! Some thing yesterday after installing some mods, landed on Minmus, did some KAS pipe attachment things with Bill, on the 3rd run back to the Cargo modules, Bill touches the surface poof! Nana-ified!

Kraken sure knows how to find me know, but I won't give up!

[Xannari Ferrows]

NaN + [[√-i]/0] • ∞

I just broke the universe again.

[CRITAWAKETS]

I got a rare occurance,when testing out a new engine that would go even faster than warp speeds based on the mainsail,the NaNovirus attacked both engines and made the new engine dissapear and the mainsail not work.

Even deleting the engine did not fix the problem,nor a game cache check.

[Steamtex]

I went into a black hole and this happened.