Biological sample = pink viper error. Anyone else?

As per title, anyone else is getting "pink viper" error when trying to scan a biological sample?

1621470111944.png
 
Last edited:
Yep same issue here. Will try restarting client.

edit: Restarted client. Still crashing upon completion of sample extraction.

edit2: I also think the codex is f'ed up. It's not logging the new entries.

edit3: It seems that all organic structures on the planet I am on are causing the crash. Will try to find more on a different planet to test.

edit4: Went to a different planet and found a different organic structure. Took samples, no crash. Odd bug.
 
Last edited:
Same here last night - I assumed it was down to the exobiology server not having started up or something, and then all the servers fell over anyway and I went to bed.

I'll see if it still happens this evening.
 
I've had the same issue with the type of flora in the attached picture.

The mini-game is also very very intensive in energy consumption, and difficult to align on a "mouse-up" trigger. I'm going through 80% of my energy just trying to scan a single flora.
 

Attachments

  • pink_viper_when_scanning.jpg
    pink_viper_when_scanning.jpg
    262.7 KB · Views: 152
Eeeeeew! Pink viper. Never heard of one of those before. And, just so you know, if I ever see a pink viper flying around in game I will put it out of my misery.
 
It's the Virtual Cache.

In the Launcher, up at the top-center, click the arrow down, go into Settings, then Options, then uncheck 'Virtual Cache.'
I don't know how, but it messes with it. Others in my squad have been saying it makes turning in missions, bounties, and cartographic data take upwards of 30 seconds. Per Submission.
 
Can confirm, scanning on one body, pink viper, tried all sorts, jumped to another system, tried scanning flora again, same result.
Virtual cache off doesn't help here either.
 
Same problem. This is the first time I have encountered this. Turning off Virtual Cache does not help.
V
Just had this on two planets in a system on the first one I successfully collected samples 2 and 3 but then the error for two other bios on that planet and one on a neighbour.

Confirmed the issue.
 
Last edited:
Odd with such a deluge of additional reports. I wonder if they changed something in the restart a few hours ago ...
 
Last edited:
Back
Top Bottom