The Formidine Rift - Part 2

Status
Thread Closed: Not open for further replies.
I am afraid I have to point out that this is not true. As someone has already pointed out over at the Discord group, the etymology of the name Kahina has nothing directly to do with the historical fact that there was a 'Berber queen' called Kahina. The etymology points to the linguistic meaning(s) of a name, not its historical bearers.
Thus, the etymology of Kahina does not provide a tangible link to Kassiopeia. The history, so to speak, does, but that's not what Drew pointed out, right?

Good point - although I thought etymology (the 'meaning of names') included historicity?

So, as we all know the meaning of 'Kahina' is priestess/fortune teller - is it not also relevant how the name was used? The source for this information was this site here: http://www.behindthename.com/name/kahina

- - - - - Additional Content Posted / Auto Merge - - - - -

And BTW - no problem at all with pointing out misinformation where it's being used - this is the point of us all working together to puzzle through it. I'd rather be corrected than left to continue believing something that's false. This is the first time I've heard that concerning the name.
 
Last edited:
Last edited:
This morning, based upon suggestions in this thread, I visited Persephone and Ereshkigal.
.
At Lombardelli's Legacy, orbiting the planet Kore in Persephone, I noticed two slightly unusual things, though I do not think they are related to the puzzle: the exterior lighting of the Coriolis station is a blue-green colouration I do not remember seeing before (although I have been out of the bubble for the last three and a half months so that might be more common than I remember) and there was demand for a commodity called Moissanite, apparently produced by Planetary Mining and consumed by Service (orbital) and Tourist economies. There were no local Galnet articles at this station and no unusual missions on offer.
.
Ereshkigal has five stars and one planet, a class V gas giant in a 0.3-day orbit of the third star. There are no stations.
.
I'm burned out a bit. My only remaining idea is that Kahina's name's etymology provides a name that transforms via a ROT13 cypher into a sector name, with the cluster EB-P needing to be searched. I think I'll take a break until 2.1, now. Good luck everyone!
 
I've noticed eco mode is better at finding routes too. If fastest has already jumped a star in it's search it doesn't go back to double check

In my rift surfing (another rift) I didn't notice a difference between fastest and economic. Not saying there isn't, but there is striking similarity in that the route plotter seems to ignore the web of routes. Why it can't plot a route to any star that has route lines to it I do not know. Why bother drawing the lines if it is going to ignore them?
 
Historical in as 'how it evolved through time', not related to historical events people were involved with.

One last punt with this: but it is my understanding that the name 'Kahina' was first used in relation to a 7th century Berber queen. It began as a nickname for her. i.e. the name was a title given specifically/made for Dihya. Is this not relevant to the history of the name itself?

- - - - - Additional Content Posted / Auto Merge - - - - -

In my rift surfing (another rift) I didn't notice a difference between fastest and economic. Not saying there isn't, but there is striking similarity in that the route plotter seems to ignore the web of routes. Why it can't plot a route to any star that has route lines to it I do not know. Why bother drawing the lines if it is going to ignore them?

Wondered this myself. How I can fly to a star 10-20ly away and then the plotter starts working again. Surely it should have seen the route between them? Perhaps it's still a bit buggy when there aren't more than a couple of options available.
 
Last edited:
Guys.

Something to make our lives easier.

Download Stellarium.

Download all the extra catalogues from inside the program. (All 9 of them) Restart.
Switch constellations and everything else on. Hit the pause button. (Distracting)

Switch location to Cambridge and time to 27.03.3301.
Not only can we now see all constellations, a massive amount of stars too, but we can switch to Azimuthal grid. And guess what? There is a in game star dead centre above Cambridge that night. Headed there now. 730 LY trip. Back in a jiffy.

Gypsy.

Ps -its got Tychos star and Cas A too. Might help with finding them if we can identify a nearby star at a similar distance.
 
Last edited:
Historical in as 'how it evolved through time', not related to historical events people were involved with.

This. (By the way, was it you, Marc, who pointed out the etymology/history problem over on Discord?)

- - - - - Additional Content Posted / Auto Merge - - - - -

One last punt with this: but it is my understanding that the name 'Kahina' was first used in relation to a 7th century Berber queen. It began as a nickname for her. i.e. the name was a title given specifically/made for Dihya. Is this not relevant to the history of the name itself?

In a broader sense, yes, but it would be a rather liberal use of the word etymology on Drew's part (yeah, yeah, misdirection and all that). I think it more plausible that he meant etymology in its stricter sense - but hey, it's not impossible.
 
Somebody pointed out earlier in the thread that during Kahina/Salomes visit to earth on the 27/03/3301 that a certain astronomical event occurred?

Earth was at ...?

Darned if I can remember the name of it... Anyhow...

I need to find the exact time of this event.

Can someone please help?

Cheers,

Gypsy.
 
Guys.

Something to make our lives easier.

Download Stellarium.

Download all the extra catalogues from inside the program. (All 9 of them) Restart.
Switch constellations and everything else on. Hit the pause button. (Distracting)

Switch location to Cambridge and time to 27.03.3301.
Not only can we now see all constellations, a massive amount of stars too, but we can switch to Azimuthal grid. And guess what? There is a in game star dead centre above Cambridge that night. Headed there now. 730 LY trip. Back in a jiffy.

Cool! Nice app.

One thing though - isn't the ED galactic alignment meant to be the same as ours right now but simply with a different date?

I mean - it's 2016 now, but 3301 in ED, but the galactic alignment is as per now in 2016 (to some degree)?

Also, Kahina was in Cambridge on 20th March. Though I wouldn't expect a huge shift in star alignments by the 27th.
 
Last edited:
So, having reviewed the first post again (kudos to Acheron for doing such a great job of collation), I'm wondering about this comment by (the other) Drew:

"The Engineers expansion may make it easier, but it's been possible since launch back in 2014."

Previously, I'd been assuming (like most of you, I suspect) that this is going to turn out to relate to an improvement to the FSD drive.
However, having checked the original context, whilst at first glance it seems to refer to fitting out a ship, I think it actually relates to the comment:

"Whether it is found or not depends entirely on who goes looking"

Now the 2.1 update is apparently going to change the way that space POIs are discoverable - via scanning or the Nav Beacon, if I remember correctly - which means a persistent object in, for example, the Persephone system, is going to show up immediately, rather than having to fly around and investigate. Consequently, I'll be flying around all the 'interesting' systems as soon as the 2.1 update drops.
 
It's funny how Cassiopeia A is almost exactly on 130º when viewed from Greenwich Observatory on the vernal equinox (20th March) this year. Sigh.

(Isn't 130º the approximate direction that the RR line points?)

KIYCYBg.png
 
Here's a pic when I was interested in the Reorte-Diso line, it's smack on top of the Cassiopeia-Camelopardalis delimiter. Cas A is very close to the Cassiopeia-Cepheus line (queue tinfoil). The red line is essentially the RR-Line. The little squiggle of blue is where I hit a some systems 11K out and then headed off to the far end of the RRLine out toward the last Graeh waypoint.

GVLPQ8i.png


I was pretty interested in CasA both as an *IT* target and in RL (Radio Astronomy). The ED-Discovery map shows me traveling along the RD Line and then I shifted to a point about 5KLY along the Cas A line. CasA's distance is somewhere between 8K and 11KLY. It's angular position is well known but not its distance. Once I hit 8KLY my method was basically:
  • Generate spread sheet with points on the line. Scan along line and find star close to that line.
  • Plot 1K route from there, repeat every 500LY or so.
  • Jump to star, scan and view system map for neutron stars as secondary stars (ie not primary)
  • Fly out 1K LS or so from star to get away from illumination, use Andromeda and other galaxy to find bearing and look for halo, which, while too diffuse to view from earth in 3300 might still be visibile from a few 100LY.
  • Every 5th star look around in galmap for neutron stars or black holes nearby
  • After 11Kly jump continue on for a bit and look back to see if the disk would illuminate anything

Couple of other points:
  • Cas A has a relatively low proper motion (http://arxiv.org/abs/1307.3539) somewhere between 0 and 800Km/s (400 +/- 400).
  • That works out to 0 to 3.2e+16 meters or 0 to few LY max by 3300.
  • I checked a couple of well known objects like the bubble nebula to see how FDEV might have factored in proper motion and to see how accurate the game was for that kind of object at that distance out. Their visual center in the galmap is a few to 10 LY from what current measurements would indicate which suggests the locations are accurate and proper motion is either ignored or is a small effect. Given real world coordinates I canfly to within 5LY of the center of the Bubble nebula.
  • One arc second accuracy equates to error bars smaller than the standard star separation at that distance. In other words if a star is on the line then an adjacent star perpendicular to the line 20+ LY away can't be the object since it's outside the cone. I was actually pleasantly surprised to see that accuracy held that far out.

In short if CasA is out there in a scientifically meaningful way I should have seen it.

Once I got to 11Kly I poked at some of the nearby stars as well.

I found 4 previously untagged neutron stars but all were too far from the line (100 to 300LY) and when examined had nothing interesting to show. There is one NS at 11KLy out which is within 200Ly of the line but others have scoped it out and I did too, nada. For my part, while I still find the idea of Cas A intriguing I don't believe it's *IT* or in fact even in game. It's on the wrong side of the rift for one thing so while it matches some in game (cambridge), mythological and etymological hints it doesn't match actual hints.

Note I'm not asserting it doesn't exist or that it's not *IT*. I certainly did not do what could be considered an exhaustive search. It's entirely possible I missed a star that's dead on the line say 9400 LY out that has a secondary neutron star in it.

For my part though I'm done with it. If it turns out I just missed it and it's truly *IT* I'll happily bang my head on my desk and fly out and honk at it.
 
Last edited:
Here's a pic when I was interested in the Reorte-Diso line, it's smack on top of the Cassiopeia-Camelopardalis delimiter. Cas A is very close to the Cassiopeia-Cepheus line (queue tinfoil)..

I'm curious (but not curious enough to search this entire threadnaught ;) ), what was the theory behind Reorte-Diso?
 
Wondered this myself. How I can fly to a star 10-20ly away and then the plotter starts working again. Surely it should have seen the route between them? Perhaps it's still a bit buggy when there aren't more than a couple of options available.
This and the occasional point blank refusal to plot jumps that you can easily make. with 32ly clearance it refused a 27ly jump until i told it I would use boost...

Frustratingly this seems to have mean I sailed past a potential crossing a whole wriggly bunch of jumps back, should have been checking edsm all the time but at -90 i'm sure i didn't see squat. it's very thin past here (7000,-40,-7000ish) too but clearly there's a way or two - could have been a big conda though. each route deeper seemed to end with a 40ly jump.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom