THE FORMIDINE RIFT MYSTERY (Part 4)

eVZbocI.png


what does it means ''destination Arc xxxxx'' ??
 
My theory about experiments and experimental tech gone awry could still fit?

***Tin foil hat time***

Sirius Corp (Funded by The Imps and Feds) were joint field testing with prototype meta-drives based on alien tech (discovered UA's or UP's). Maybe beacons were set up in 3 far away regions (conflux/gap/rift) for these prototype drives to lock onto for initial testing (see if they can jump that far?). Once the drives were charged and jump initiated, something went horribly wrong.

Ships with these prototypes in the bubble went "missing", and the exit point at the other end (in the rift/conflux/gap) opened up but something else came out (aliens, lurking evil etc.) causing equipment malfunctions and general shenanigans for hundreds of light years around these exit points, eventually costing everyone their lives. Since then they have tried to cover it all up. whatever came out the other side might also be what the old woman was afraid of in the rift.

Fast forward to more recently and Kahina has now learned the truth (holofac docs and also what she saw herself in the rift) and is being hunted/persecuted by the Imps/Feds to silence her.

The alliance also got wind of these experiments and are trying to either reproduce, or produce their own version. This is why the Alliance has such an interest in regions where meta-alloys and UA/UP are found (Hence Mic Turner Base way out in the California nebula). Raan Corsen came across these secret archived reports of what happened 30 years ago while an employee of Sirius Corp, dug deeper, and discovered the Alliance's secret project regarding Meta-drives. Horrieid by the events of what happened before, and determined not to let it happen again, he stole the docs and the new prototype ship the Alliance had and attempted to flee, crashing somewhere in Alioth system.

Since honking UP's disables ships, fits that equipment malfunctions in these regions where tech based on said alien technology was being deployed.

Since the Alliance has started up these experiments again, and this alien based technology is active again after 30 years. these aliens have returned looking for their technology (hyperdictions) in an ever expanding area. Also explains the hyperspace interdictions, weird lights, etc from the data logs 30 years ago.

Some realms in space and time we are simply not meant to visit, and these Aliens/thargoids are meant to keep us in our own dimension, by force if necessary. (explains previous wars maybe? how long have we been experimenting and using frame shifting drives? where exactly is "hyperspace" when we are between folds in space? seeing as FSD works by folding space in front of the ship, and uses thrusters to "hop" from one fold to the next moving forward.

Sorry for the rant...

This is my attempt to tie everything together...
Wouldn't mind some feedback... not sure if I'm close or way off base..
There's A LOT of details and story-lines to keep track of...

As a matter of fact, this is largely my theory as well. I for one don't find it tinfoily at all. +rep to you
 
http://i.imgur.com/eVZbocI.png

what does it means ''destination Arc xxxxx'' ??

I checked this theory earlier today... check all these gates at all bases and the markings are identical on all of them. Looks like its just part of the graphics model used to create the bases in game.

It says:

CAPY. 3229088999
DEST. ARC-18788
RE-BUILD 49-001

If anyone in the bubble could check one of the abandoned bases there and confirm it's the same, we can put this to bed 100%

- - - Updated - - -

As a matter of fact, this is largely my theory as well. I for one don't find it tinfoily at all. +rep to you

Thank you sir, glad you enjoyed the wright-up :D
It's the only way I can think of where everything fits and makes sense and ties in all the current story-lines
 
So I've been thinking about the missing step(s) that could have helped us find the bases in the Rift and still could help us find the remaining bases in the Conflux and the Gap.

We found the beacons while taking part in the CG, so perhaps the next step was for us to return to the Children of Raxxla station in HR 6421 and whatever the system was for the Federation CQ (I can't remember the name, anyone else able to fill in the blank?) to claim our rewards.

What I'm thinking happened is, we found that one site but the crash to desktop bug meant it was impossible to investigate and distracted us. With the mystery then on pause over Christmas, we forgot all about the CG and jumped into the brute force approach once the bug was fixed.

So I'm wondering if the next clue was meant to be at HR 6421 and the other system and we missed it, either thinking we couldn't progress until the bug was fixed or because whatever clue was meant to be there was also taken down while everything was on pause?
 
I think these bases may help but you can still solve the mystery without them and hence Horizons.

Sorry for another theory mode on :)

I think Rift mystery is about specific system/systems or things we can find in it. just by exploring map/space ingame.
clue types we have:

Constellations: Clues relaying on constellations can give us only direction of looking. Propably some stars from this constallations can be located in Rift/Eafots region - but did't find any.
Those constellations are: Casiopeia, perseus, camelopardis

RR line: It think its also direction clue. Its hard to tell how accurate this line is projected on short Reorte Riedquat distance.

Local POI's:
H&S Nebula, strange cluster of stars, galactic plane, other ? Maybe we need to move to system from which POIs creates an image of something.

Galnet: From backgroud story to very specific informations (Tionisla example) very important.

I think POIs are very interresting, because they can be joined with mythology, and satisfy the condition of finding something just from cocpit of your ship.

And some tinfoil for your hats:

We are searching for system. The only thing we need is up to 7 characters/numbers as system names are EAFOTS AA-A A11-1 (and region is given by OW Cobra)
 
Dunno, it's a bit old capacity though... Generation ship?

- - - Updated - - -

I typed ARC into the galaxy map and it went to this system. Looks like it's unrelated but I thought it seemed very odd to have a system named like this in the middle of a nebula and with such a random, 'proper' name. Anyone been here/know if it's anything interesting?

http://imgur.com/a/GgJrM

Dunno, it's a bit old capacity though... Generation ship?

take a look at my post on previous page, this has been looked into today over the last few pages
 
Last edited:
Yea, Drew mentioned we missed clues to figuring this out, and the brute force method was circumventing using the in game mechanics/clues...so take that for what it's worth.

If the game had proper mechanics for finding stuff... Not random clues in systems that are like, you know, 12k LY away...

Z....
 
The ex-Employee was Raan Corsen. The only person in Alioth to witness Corsen's crash was CMDR Ashley Wilkinson. I participated in the event vicariously as I was winged up with CMDR Ashley Wilkinson, CMDR Moonweb and Raan Corsen but I was at Jaques at the time. Everything I know about Corsen's last moments before the crash comes from monitoring the even over The Earth Defense Fleet's Teamspeak. Corsen never chatted to the wing so we only have Wilkinson's reports to tell us what was said and seen.

Wilkinson reported his take on the events in the Oct 12, 2016 edition of Lave Radio.

The only clue that the Corsen investigation gave, iirc, was the "Exodus" code word used to unlock the message of the beacons (though I think someone worked out the code word by brute force prior to it being published in Galnet). It does present possibilities that there is a connection between Metadrive, Sirius Corporation and the settlements in the Rift, Conflux and Gap.

Ok I've summarised the logs from the private data beacon wrecks below (in a semi-logical order), because they are certainly relevant to strange things happening with FSDs and, well, Sirius is the number one suspect for some of this stuff. In particular, see the section labelled "We've found it", which has this little gem:

Abnormal compact emissions data
We can finally prove it! The drive manufacturers won’t know what’s hit them when we release this data.
The proof is all in here: [Compact emission data].
We just need to make it public before one of their agents catches us.

“RECON”
=====
Atypical Disrupted Wake Echoes:
Here's my recon log. The intel is correct, someone is travelling through this sector. I'll maintain watch and report when I've identified them.
File attachment: [Wake echo track data]
Note that I've also included comparative scans.

Atypical disrupted wake echoes
Attached analysis for system entry and access
[Wake echo data files]
Unusual entry recorded and highlighted in supplementary files
Missing files…

“PATROL”
======
Exceptional scrambled emission data
Full range emissions scan data...
[Source Scrambled]
Sector sweep partially complete.
Datastore integrity report 100%.

Exceptional scrambled emission data
Patrol sweep emissions report
[Source Scrambled] Requires access key
Patrol partially completed. Data error!

Exceptional scrambled emission data
Secondary emissions report
[Data Scrambled – Key not present]
Report integrity report 100%. Point of origin unknown

Irregular emission data
Patrol emission scan report
[Archived emission data tables]
Secondary verification unavailable
System back-up damaged


“TESTING”
=======

Eccentric hyperspace trajectories
Hyperspace traffic monitoring
Automated generation of [Hyperspace trajectories analysis] on secure channel
Target indicators are all nominal and correctly sequenced. Warning: This is proprietary data and must not be shared!

Modified consumer firmware
Consumer System Firmware Patch:
This update patch requires a full reset of the system to take effect.
[Firmware updated files]
Ensure to follow the attached instructions when installing this patch.

Eccentric hyperspace trajectories
Stage 3 Sensor Upgrade Test Report
[Hyperspace trajectories analysis]
Pattern match 99.97%
All systems go for stage 4 test.

“WE FOUND IT”
==========

Abnormal compact emissions data
System wide emission check initiated…
[Compact emission data]
System snapshot complete

Attached emission scan table:
[Compiled emission data scan]
Anomaly in data set detected. Full forensic scan of data recommended.

Unexpected emission data
Scan data from emissions scan.
Auto generated files for [full emission data]
Invalid system error…

Irregular Emission Data
This is what we were looking for!
[Archived emission data]
Archive key embedded.
Transmission protocol override corrupted.

Abnormal compact emissions data
We can finally prove it! The drive manufacturers won’t know what’s hit them when we release this data.
The proof is all in here: [Compact emission data].
We just need to make it public before one of their agents catches us.

Abnormal compact emissions data
Full net syncing of emissions data complete
Attaching [Compact emission reports]
Information package ready to go, we’re just waiting on the secure connection.

Local emissions scan archive
[Archive data compressed]
System transcript error
Logging protocol inactive

Decoded emission data
Decoded emission data package attached:
[Decoded emission table]
Secure protocol active.
System override detected.

Decoded emission data
Decoded emission data sequence
[decoded emission data package]
Data source tracked with unknown response type…
Secure integrity failure…

“BAD THINGS HAPPEN”
==============
Anomalous FSD Telemetry
Emergency response FSD telemetry
[FSD telemetry table] for tracked object
Ship ID unknown...
Weapons fire detected...

Priority FSD telemetry log
Generated [FSD telemetry archive]...
Invalid data connection detected...
Transmission failure...

Invalid FSD checksum
[Didn’t record the full message sorry, but a bad checksum indicates that the data has been modified or corrupted]

“SURVIVORS”
========
Exceptional scrambled emission data
Here’s hoping this data gets out…
[Scrambled emission data]
I hope someone can make sense of it!

Exceptional scrambled emission data
This data needs to get to the right people
[Scrambled Emission Data]
Track solutions in place and included in the attached data.

Unsorted
======

Irregular emission data
Emissions scan archive
[Archive data compressed]
Transmission log unavailable
Secure protocol inactive.

Specialised legacy firmware
System firmware version 0.41.03
[Firmware upgrade setup]
This firmware is now out of date and should not be used.

Specialised legacy firmware
Legacy firmware 0.23
[Install package]
User of this software on unauthorised systems is prohibited by law.

Atypical disrupted wake echoes
Automated wake scan data archived…
[Wake echo data log] attached
Possible system error detectecd…

Linked to

Exceptional scrambled emission data
Full range emissions scan data…
[Source Scrambled]
Sector sweep partially complete. Datastore integrity report 100%

Modified consumer firmware
Flash upgrade for consumer firmware
File archive for [Firmware update patch]
This firmware update is not suitable for use on secure of military grade devices!

Unexpected emission data
Another day and another emissions data scan.
Attached data contains the full scan data for this patrol:
[Full emission data table]
Irregular communications handshake received

--
Eccentric hyperspace trajectories
Local Hyperspace Solutions Data
Embedded files: [Hyperspace trajectories] for local traffic in 12 hour time box.
Targets identified. Full analysis of data to be completed on return.

Unexpected emission data
Another day another emissions data scan
Attached data contains the full scan data for this patrol:
[Full emission data table]
Irregular communications handshake received
--

“FIRMWARE OR MALWARE???”
==================

Decoded emission data
Decoded emission files
Attached files exceed operational protocol size: [Decoded emission tables]
Possible cyber threat detected within this data – open only within a secure environment!

--

Decoded emission data
Patrol emission data decoded:
[Decoded emission data stream]
Invalid resource present. Possible malware – open this file with caution!

There was a separate thread on these wrecks called "WIP", I cannot find it right now but some of this material comes from there and it's worth a read.
 
Last edited:
Not sure if this was answered by anyone. But if we are missing another location for settlements, then it would make a square'ish zone around the bubble.
Either a search area or communications center.

Or I'm just missing something in general...


Interesting, That's right out near the Perseus Transit (Bordering on the Perseus Fade)
Has there been any mention of anything in that area though?
Out of all the clues we have I thought I remember the name "Perseus" coming up...
It's VERY late, I'm Very tired, so my memory is failing me,,,,
 
Just a slight plot-point... The old woman said she'd lost someone and then went out to the rift. I'd suggest it was more likely that her husband had been on the mission and somehow had managed to send her some form of communication including some of the details we now have. She grabbed her old Cobra and went out there looking, found something and had her memories erased.

I have not read any of the books, so I may be misinformed.

This makes more sense to me. The "Galaxy just hanging there" comment was not hers, it was amongst the last words penned by her husband - and that is stuck in her mind.

Z...
 
Last edited:
Looks like it could read "DEST.ARC-t8788". Not sure if it means anything.

exgoaltender just answered to my question in the previous page in a very exhaustive way, i guess.

bytheway... Drew didn't said that arc are portals ? or maybe i misunderstood something ?




edit correction: the page where exgo answered me is the same one here. just look up a little bit.
 
Last edited:
hey rifters, may not be relevant to the search, but some news from the permit-locked Col 70 sector.

Since this is a long forbidden and mysterious sector, Drew's hand may be at work here.

Galactic News: Body Found at Wreaken Construction Site

https://community.elitedangerous.com/en/galnet/uid/588b1e769657ba121799dc8e

An unidentified individual has been found dead at a Wreaken Construction site in the COL 70 sector. The body was disfigured as a result of radiation exposure, and identification has so far not been possible. System authorities are conducting an investigation.

A representative of Wreaken Construction responded to the discovery with a statement:


"There have been several incidents of individuals trying to break into our facilities. This is an unfortunate event, but frankly the victim brought this accident on themselves. Our facilities are secured for a reason – manufacturing is a dangerous business."


Meanwhile, independent pilots have reported that Wreaken Construction sites are heavily guarded, and that approaching ships have been aggressively warned away by Wreaken-owned vessels.
 
Last edited:
hey rifters, may not be relevant to the search, but some news from the permit-locked Col 70 sector.

Since this is a long forbidden and mysterious sector, Drew's hand may be at work here.

Galactic News: Body Found at Wreaken Construction Site

https://community.elitedangerous.com/en/galnet/uid/588b1e769657ba121799dc8e

An unidentified individual has been found dead at a Wreaken Construction site in the COL 70 sector. The body was disfigured as a result of radiation exposure, and identification has so far not been possible. System authorities are conducting an investigation.

A representative of Wreaken Construction responded to the discovery with a statement:


"There have been several incidents of individuals trying to break into our facilities. This is an unfortunate event, but frankly the victim brought this accident on themselves. Our facilities are secured for a reason – manufacturing is a dangerous business."


Meanwhile, independent pilots have reported that Wreaken Construction sites are heavily guarded, and that approaching ships have been aggressively warned away by Wreaken-owned vessels.

And that's a permit locked sector... Ha ha frontier
 
hey rifters, may not be relevant to the search, but some news from the permit-locked Col 70 sector.

Since this is a long forbidden and mysterious sector, Drew's hand may be at work here.

Galactic News: Body Found at Wreaken Construction Site

https://community.elitedangerous.com/en/galnet/uid/588b1e769657ba121799dc8e

An unidentified individual has been found dead at a Wreaken Construction site in the COL 70 sector. The body was disfigured as a result of radiation exposure, and identification has so far not been possible. System authorities are conducting an investigation.

A representative of Wreaken Construction responded to the discovery with a statement:


"There have been several incidents of individuals trying to break into our facilities. This is an unfortunate event, but frankly the victim brought this accident on themselves. Our facilities are secured for a reason – manufacturing is a dangerous business."


Meanwhile, independent pilots have reported that Wreaken Construction sites are heavily guarded, and that approaching ships have been aggressively warned away by Wreaken-owned vessels.

Hmmm, interesting... The sector is permit locked by Wreaken Construction maybe?

Not sure how relevant it is to the Rift mystery, but it might be one for Canonn for the time being?
 
Last edited:
hey rifters, may not be relevant to the search, but some news from the permit-locked Col 70 sector.

Since this is a long forbidden and mysterious sector, Drew's hand may be at work here.

Galactic News: Body Found at Wreaken Construction Site

https://community.elitedangerous.com/en/galnet/uid/588b1e769657ba121799dc8e

An unidentified individual has been found dead at a Wreaken Construction site in the COL 70 sector. The body was disfigured as a result of radiation exposure, and identification has so far not been possible. System authorities are conducting an investigation.

A representative of Wreaken Construction responded to the discovery with a statement:


"There have been several incidents of individuals trying to break into our facilities. This is an unfortunate event, but frankly the victim brought this accident on themselves. Our facilities are secured for a reason – manufacturing is a dangerous business."


Meanwhile, independent pilots have reported that Wreaken Construction sites are heavily guarded, and that approaching ships have been aggressively warned away by Wreaken-owned vessels.

It's funny that people get blown up in the galaxy every second and yet the discovery of a body makes galaxy-wide news!
 
Back
Top Bottom