So you want to know about the Formidine Rift? (Part 3)
- Thread starter Legacy_LuckyLuke
- Start date
Rep to take the sting away a little. That sucks, CMDR. Did you just take damage or lose it entirely?
I agree with MassBStruction, whatever mystery is out there, we're still not touching on it. And IMO, feel free to shoot me down on this, but we're wasting resources if we're going to ground exploration too when the mystery has been discoverable since launch. It's also worth reiterating that the mystery is not a POI, or USS from what I've seen from Drew and co. Gutted I'm at work, but I am on my way to the area.
What is an orbital red POI? I've seen the planet red on the radar, but is this something else?
I don't think it's a poi, but when you are close to a planet, the border of orbital flight shows/planet's gravity starts to take more affect.
I think the CG is going to help Salomé out, in some fashion, so I would definitely turn in data within the two weeks, but I agree our resources should go beyond the 200ly area and keep searching for "it". "It" is "more nuanced" (quoting Drew) than a simple POI or USS, and is more about the narrative, and the CG is linked to the progression of the narrative.
total bang and rebuy screen
a red glow on map when orbital cruising... https://forums.frontier.co.uk/showthread.php/205129-Planetary-Radar-Red-Zone
Last edited:
I'm surveying the crater you crashed in, so far nothing out of the ordinary. and no poi.
Met you earlier in the system. Sorry to hear about your crash. Ill continue to survey EAFOTS GL-Y E2 6.
Just timed my normal pattern (There's many, many light years to go!), and from arrival at one star, scan, check local map, back to main screen and scan complete, skim the corona with my R6 FSD and leaping out to arrival at the next, looks like my time was 1:18, or 78 seconds including the load screen in between... and even with my much larger FSD (60ly average jump, max 62.78) I'm doing 17 to 18 jumps per 1000ly... so er, 23.4 minutes it says here at 18, so even then I'm somewhat behind your pace! 3000ly for me would be 1 hour 10... wonder where you're shaving the time off?
I aim for the closest edge of the sun to the target system, activate the FSD when I am still in the "hot" zone, and then go to system map pointing at the target star. I normally touch 95% heat before she starts to cool, by then, I have checked the sys-map for anything interesting, and have time to stop the countdown if I see something of note.
I suspect where I save time is that my FSD is spooling up when most people are still waiting to clear the hot zone.
One thing to note - An A, B, O, or even an F star will add 5-10 seconds, as they take longer to clear, and it takes longer before I can spool up the FSD. I usually check the system map first on those.
Oh, also, to be clear, I don't scan the main star unless there is something worth scanning in the system.
Z...
Last edited:
Here are two more "flat views" views looking at the x-y plane and the x-z plane. I'm still focusing on the "where" not the "why."
Oh crap - sorry to hear the CMDR. I don't feel so bad now, my controller totally failed to respond on dropping out of a jump, and headed straight for the main star at full throttle with the usual results. My damage is, of course, just a few %, so insignificant compared to a splash. I hope you didn't lose too much data...
Z...
dam sorry to here that cmdr!
My hunch is that someone in the bubble is preparing for a military action against something out there in the Rift. Remember the hint, “Winter is coming”.
So many new beacons, makes me wonder what else is out there waiting to be found…
Last edited:
In the Galaxy Map, the Heart Nebula is wholly inside EAFOTS. Soul Nebula is just outside the EAFOTS border.
Seems like a defensive/attack line...satellites kinda like watch towers or strike points
They may go out of standby when something not human gets near them, anyone tried bringing UAs to/near them?
Very good point. Could be the whole reason the CRCR (corrosion resistant cargo racks) exist. The only thing is that the beacons don't seem to be actively scanning.