How was JJ-386 found?

DukeIronHand · Dec 5, 2017

Let me start with a semi-apology here. Plus I am not sure this is even the right forum. Info is everywhere.
I have checked multiple threads, nosed around reading here and there and find much discussion and theory. But I can't find a direct answer to one question:

How exactly was Cmdr Jameson's Mk III located?

I had a minorly difficult time with system and planet name plus lon/lat. Course why lon/lat is tough to find in a 34th century spaceship is another story.

I have to assume there was some kind of trail there and this wasn't a random discovery?
Especially since the Canonn folks found it?

Factabulous · Dec 5, 2017

https://forums.frontier.co.uk/showt...ed-Ships-etc?p=6162301&viewfull=1#post6162301

Jmanis · Dec 5, 2017

Factabulous said:
https://forums.frontier.co.uk/showt...ed-Ships-etc?p=6162301&viewfull=1#post6162301

*chuckle* Texture bug. Let's add that one to the list...

- First Guardian ruins: found by aligning features in a trailer to the Galaxy map
- Subsequent Guardian ruins (pre-appearing on scanner and excluding ones with galnet hints): found by timing lag when dropping out of supercruise.
- Thargoid Scout: Found by scanning bug putting all POI on your nav panel, regardless of if you'd discovered it or not
- Barnacle Forest: Found by scanning bug putting all POI on your nav panel, regardless of if you'd discovered it or not
- JJ's Ship: Found by observing texture bugs

This is why I keep suggesting that the bullet gets bitten and just introduce some simple ways to *actually* find this stuff.

To be somewhat balanced, these discoveries are somewhat less absurd:
- UA convoys discovered by chance encounter
- Free-floating UAs/UA shell found by continued interest in the Pleiades
- First barnacle found accidentally when canyon-racing
- UPs discovered by chance when floating near a planet with requisite conditions
- Thargoid Structures found through actual developed mechanics and a relatively good ability to MK-1 eyeball them
- Various abandoned bases found through actual developed mechanics using Unregistered Comms Beacons

Bob McBobblehead · Dec 5, 2017

Tinfoil hat mode:

The CD version of Frontier First Encounters had loads of source code exposed because of a cache file on the CD. By taking bits of the code and running them on a Genuine Intel 386 CPU, Cmrd Jameson co-ords were triangulated.

GluttonyFang · Dec 5, 2017

Jmanis said:
*chuckle*

*Sneezes*

Man I must be getting a cold ._.

DukeIronHand · Dec 5, 2017

Well...that was kinda...unexpected. A "texture bug."
Seems quite odd and like the finder is not giving all information.

Some folks complain about the "pace and narrative" of the Thargoid story and I have to wonder if it's because of silly things like this ruining whatever FDev had planned.

Thanks.

CmdrZaratan · Dec 5, 2017

DukeIronHand said:
Well...that was kinda...unexpected. A "texture bug."
Seems quite odd and like the finder is not giving all information.

Some folks complain about the "pace and narrative" of the Thargoid story and I have to wonder if it's because of silly things like this ruining whatever FDev had planned.

Thanks.

I don't think it's that....FD like to do the slow drip reveal, and there would doubtless have been an unregistered comms beacon soon revealing the location or at least pointing at the planet. We were pretty close to that part of the story from the INRA base logs, having already found the one (from a comms beacon) that told the story of an independent pilot being selected for the mission and being sabotaged so he wouldn't return.

Factabulous · Dec 5, 2017

DukeIronHand said:
Well...that was kinda...unexpected. A "texture bug."
Seems quite odd and like the finder is not giving all information.

Some folks complain about the "pace and narrative" of the Thargoid story and I have to wonder if it's because of silly things like this ruining whatever FDev had planned.

Thanks.

Texture bug gave away the final location, didn't give the planet to search - that was down to being a curious CMDR who has found things before. Some CMDRs have more experience searching, so have more chance of finding things - I see that as a chance to learn new tricks rather than to get ... salty, but each to his own

DukeIronHand · Dec 5, 2017

Interesting. Thanks for the additional.
Since you use the word "We" I will guess you are part of Canonn?
If so a hearty congratulations to your group for all you do.
I have my alt career DBX down in the area looking around trying to get into the story.

EDIT: Meant for CmdrZaratan.

DukeIronHand · Dec 5, 2017

Factabulous said:
Texture bug gave away the final location, didn't give the planet to search - that was down to being a curious CMDR who has found things before. Some CMDRs have more experience searching, so have more chance of finding things - I see that as a chance to learn new tricks rather than to get ... salty, but each to his own

Simultaneous post as I was doing mine above.
I have only had one coffee but if you think I was being negative or disparaging toward the finder, Canonn, CoR, or FDev I wasn't. I meant that I was wondering out loud if, because of enterprising Cmdr's and groups, the Thargoid story isn't progressing exactly as intended.
I am trying to catch up!

CmdrZaratan · Dec 5, 2017

DukeIronHand said:
Interesting. Thanks for the additional.
Since you use the word "We" I will guess you are part of Canonn?
If so a hearty congratulations to your group for all you do.
I have my alt career DBX down in the area looking around trying to get into the story.

EDIT: Meant for CmdrZaratan.

I think I am a member of the Canonn group from ages back, though I never did join their discord and I missed out on the decal due to injury

I used "We" as in we the players. I did spend a bit of time searching for the cobra, but I was waaaaay off. I haven't spent any time looking for INRA bases so I'm living vicariously through others there.

Rob At Work · Dec 5, 2017

Late one night in a seedy back street Cambridge pub (the Old Bell), a piece of paper with some numbers on changed hands across a battered oak table...

...again....

MUSKETEER · Dec 5, 2017

It was meant to be found... what better way to give a clue to its location than making a huge texture square on the surface of the planet lol

Factabulous · Dec 5, 2017

MUSKETEER said:
It was meant to be found... what better way to give a clue to its location than making a huge texture square on the surface of the planet lol

In some ways it would be nice if FD would just draw something on the HUD to make it look like it's not a bug - then they could say it's the Mega-POI indicator (M-POI

).

DukeIronHand · Dec 5, 2017

CmdrZaratan said:
I think I am a member of the Canonn group from ages back, though I never did join their discord and I missed out on the decal due to injury I used "We" as in we the players. I did spend a bit of time searching for the cobra, but I was waaaaay off. I haven't spent any time looking for INRA bases so I'm living vicariously through others there.

So I can try to get into the story a bit and not live it on YouTube is there a tidbit thread somewhere that explains or hints how the original finder looked in/on this system/planet in the first place?

CmdrZaratan · Dec 5, 2017

DukeIronHand said:
So I can try to get into the story a bit and not live it on YouTube is there a tidbit thread somewhere that explains or hints how the original finder looked in/on this system/planet in the first place?

You know as much as I do there. As he said in his post he was checking out the planet because it was small enough to search. He spent 6-7 hours flying over the surface till a graphical glitch caused him to check a particular area more thoroughly. He also said he wasn't looking for the cobra specifically.

However if you want to work through the INRA base stuff, try the stickied INRA thread in the top section of this forum.

If you want to hit the listening posts/unregistered comms beacons, Jorki Rasalas keeps an updated spreadsheet of locations here (not just INRA): https://drive.google.com/file/d/0B0Czj1J7kmgNZE1uMC10bW1aWG8/view

Jmanis · Dec 5, 2017

Factabulous said:
Texture bug gave away the final location, didn't give the planet to search - that was down to being a curious CMDR who has found things before. Some CMDRs have more experience searching, so have more chance of finding things - I see that as a chance to learn new tricks rather than to get ... salty, but each to his own

Don't get me wrong, credit where it's due for at least finding the right planet, and to the pilot's patience which at 5-7 hours of searching is much longer than my own. But if it's salty for me to be critical of a game whose design means some of it's most significant discoveries are enabled by bugs and glitches rather than gameplay elements, then call me NaCl.

I mean, you read this and it sounds great, until you realise it was achieved by repeatedly logging in and out to cause a bug that meant additional obelisks would light up and provide entries not normally available, rather than the intended mechanic of finding enough sites to give a full set of data (which ironically, was always impossible until much later than the date of that article).

Did someone achieve something? Sure, but it takes some of the sheen off.

Factabulous · Dec 5, 2017

Jmanis said:
Don't get me wrong, credit where it's due for at least finding the right planet, and to the pilot's patience which at 5-7 hours of searching is much longer than my own. But if it's salty for me to be critical of a game whose design means some of it's most significant discoveries are enabled by bugs and glitches rather than gameplay elements, then call me NaCl.

I mean, you read this and it sounds great, until you realise it was achieved by repeatedly logging in and out to cause a bug that meant additional obelisks would light up and provide entries not normally available, rather than the intended mechanic of finding enough sites to give a full set of data (which ironically, was always impossible until much later than the date of that article).

Yeah, I wasn't clear - the game is pretty broken (and FD never seem to admit this). I don't think this shouldn't detract when CMDRs have spent a long time searching & refining their techniques.

I would write more about how they keep shipping bugs and not fixing broken content, but I'm getting salty, so will stop now

Brrokk · Dec 5, 2017

My guess is that we were going to be led to it by messages or puzzles from the INRA bases, but it was found the hard way first. The same thing happened with some alien ruins. It's amazing the tenacity some people have.

DukeIronHand · Dec 5, 2017

CmdrZaratan said:
You know as much as I do there. As he said in his post he was checking out the planet because it was small enough to search. He spent 6-7 hours flying over the surface till a graphical glitch caused him to check a particular area more thoroughly. He also said he wasn't looking for the cobra specifically.

However if you want to work through the INRA base stuff, try the stickied INRA thread in the top section of this forum.

If you want to hit the listening posts/unregistered comms beacons, Jorki Rasalas keeps an updated spreadsheet of locations here (not just INRA): https://drive.google.com/file/d/0B0Czj1J7kmgNZE1uMC10bW1aWG8/view

Uh...wow. That almost sounds like a random find. Searching "a" planet for 6 or 7 hours just because it was small enough?
I have to think, if nothing else based on the sheer numbers of planets there must be more.
Unless he is a truly dedicated soul looking at the Pleiades area in general as that's where all this stuff is happening. - and I am quite jealous of his playtime!

And thank you for the link.