Alien archeology and other mysteries: Thread 9 - The Canonn

Status
Thread Closed: Not open for further replies.
...so they couldn't have added in a line of text stating the system name like every other mission in the game? I understand that xDeath found it before it was ready, but that was MONTHS ago. This mission is brand new.

Edit: Didn't mean to sound harsh; I'm just about fed up with how Frontier are handling this and I'm just frustrated.

It sounds like a bit of delaying tactics or backfill. Wait for their planned storyline to catch up, open is bugged, so throw a CG to gather data, that puts things off, wait for him to anaylize it, what they should be doing is inserting the odd station upgrade or new colony building for the alliance and others. Dont stop one storyline just because another is moving at the same time. They must have at least 3 CGs running at all times tbh to keep everyone entertained
 
Delivered ~950 pieces of data and went to bed. Stayed in the top 10% the entire time. Appreciate all the Commanders who finished up the CG.
 
I would like to apologize for just criticizing the heck out of FD for this whole page or so, but it's really hard not to do so. In my opinion, the mysteries and aliens are without a doubt the coolest part of the game, and it saddens me that after all this time, Frontier just cannot get it right (excuse my phrasing). The alien hyperdiction was awesome, though. I want to hope that Frontier deliver with the alien gameplay, but I'm doubtful.
 
Pareidolia: the ability to see patterns in random noise, this applies to things like cloud watching, while it is a remarkable ability that we have, it also has it's drawbacks when tied too much to imagination, it's led me on many wild goose chases when exploring planets, it's why I believe it's best not to say anything until it's been checked out in detail.

Pareidolia specifically refers to seeing patterns that don't exist; a pattern recognition false positive. There's definitely a negative connotation to the word even though in some cases such as cloud watching the phenomenon can be a source of entertainment.

Our brains have evolved to recognise patterns to such an incredible degree (arguably pattern recognition is the brain's primary purpose and the foundation of intelligence) that false positives are inevitable as generally the cost of a false positive is way lower than the cost of a false negative. People who see tigers where there are none don't suffer the same consequences as people who don't see tigers that are there.
 
Anyone else concerned as to how close in proximity these ruins are to Earth? Makes me wonder if us "humans" were the warriors they created to fight their battles. Also, there's an ELW in the system next door. SYNUEFE SO-P C22-18.

In either case, I really hope that Ram Tah uses all of this data to create a blueprint that makes your DSS able to detect anomalies like this on a planet, or at least see persistent POI's on your scanner.
 
...We should have proper exploration tools now that we're multiple years into ED's life, but no, all we have is a damn space honk and a compass.


I’d be happy flying to lat/lon coordinates for the next 6 months if they’d just fix their networking problems. This is an on-line multi-player game isn’t it? But I’ve had more CTDs the last 2 weeks than probably 10 years of gaming. And there isn’t anything more “immersion busting” than a CTD.

And multi-player instancing problems aren’t new. I’ve watched Josh Hawkin’s Brocast on Sundays where usually they try to get a bunch of players into a single instance to do something fun, like climbing Mt. Neverest. But they spend the first hour juggling wing invites in a private group to try to get people together. This should take a few minutes. If this were easy we’d invent a lot of our own gameplay while waiting for plot development. SRV football with an Ancient Orb anyone?

I really wish FDev would have said, after the Ram Tah non-CG CG to decrypt the Obelisk data, “Hey guys, we’re seeing numerous adjudication errors and CTDs with multi-player, and much as we want to roll out the next clues, we really need to get this fixed first.”

But no, they start another CG that unleashed a hoard of new players coming to the ruins with the CG, making things even worse. I prefer playing in Mobius or even Open. Its much more fun with others working cooperatively. In Solo these ruins are really lonely. But I cannot get a stable group instance for longer than about 10 minutes.

So my advice to FD is to get their networking up to snuff first. You’re not in Alpha any more. Maybe that will give their art department and plot department a little breathing room to think things through a little more too.
 
I’d be happy flying to lat/lon coordinates for the next 6 months if they’d just fix their networking problems. This is an on-line multi-player game isn’t it? But I’ve had more CTDs the last 2 weeks than probably 10 years of gaming. And there isn’t anything more “immersion busting” than a CTD.

And multi-player instancing problems aren’t new. I’ve watched Josh Hawkin’s Brocast on Sundays where usually they try to get a bunch of players into a single instance to do something fun, like climbing Mt. Neverest. But they spend the first hour juggling wing invites in a private group to try to get people together. This should take a few minutes. If this were easy we’d invent a lot of our own gameplay while waiting for plot development. SRV football with an Ancient Orb anyone?

I really wish FDev would have said, after the Ram Tah non-CG CG to decrypt the Obelisk data, “Hey guys, we’re seeing numerous adjudication errors and CTDs with multi-player, and much as we want to roll out the next clues, we really need to get this fixed first.”

But no, they start another CG that unleashed a hoard of new players coming to the ruins with the CG, making things even worse. I prefer playing in Mobius or even Open. Its much more fun with others working cooperatively. In Solo these ruins are really lonely. But I cannot get a stable group instance for longer than about 10 minutes.

So my advice to FD is to get their networking up to snuff first. You’re not in Alpha any more. Maybe that will give their art department and plot department a little breathing room to think things through a little more too.

The recent networking changes have helped some and hindered others.

I think they should put any new ruin locations out quickly to keep it moving along , but for a commpany full of engineers its a bit iffy.

As far as art/plot departments, they need to start inventing more procedural content and art assets that can be generated procedurally a little like no mans sky to ligthen their workload

- - - Updated - - -

Anyone else concerned as to how close in proximity these ruins are to Earth? Makes me wonder if us "humans" were the warriors they created to fight their battles. Also, there's an ELW in the system next door. SYNUEFE SO-P C22-18.

In either case, I really hope that Ram Tah uses all of this data to create a blueprint that makes your DSS able to detect anomalies like this on a planet, or at least see persistent POI's on your scanner.

check signal sources in orbit around that ELW u might find something
 
To be honest, I'd be OK with this particular aspect of the game if it just worked. It's the fact that there seem to be myriad issues with it and nobody can even bother themselves to talk to us about it. One thing that particularly makes me laugh is that it was Obsidian Ant who made a thread asking for a comment and/or explanation what a week ago now? That's back on about page five of the forum because it was completely ignored. Now I don't do fanboying but seriously - how much publicity do you think FDev have got for this game, for free, from that guy? The guy who has a station in Maia named after him. But nope, nothing.

To play the devil's advocate, and as a software developer myself, I can fully understand why FD choose not to comment. Anything they say is either going to invite further questions and criticism and/or create expectations that wind being treated as promises by the community. So they can't really say more than what the support staff have already said on the bug reports: "we've seen your report and are investigating". We're certainly not going to get an ETA because there is no upside for FD in making an announced deadline vs an unannounced one, and there is certainly downside to missing an announced deadline. It would be nice to get a confirmation that a dev has looked into it and confirmed the issue but in the end the only thing that actually matters is that it gets fixed. I'd suggest that anyone that is finding the bugs too frustrating should focus on something else until they are fixed. The content will still be there in a month or whatever.

On the other hand there does seem to be a communications disconnect given that Michael seemed unaware of the issues when he commented here. You'd think someone in FD might have said to him "hey that ruins thing that is getting so much attention isn't working right". Still the bigger concern for me is just how buggy it is. These bugs really seem like something that a group of internal testers would have found very quickly, and there should have been some in-depth internal testing given that it wasn't fully deployed in the beta.
 
To play the devil's advocate, and as a software developer myself, I can fully understand why FD choose not to comment. Anything they say is either going to invite further questions and criticism and/or create expectations that wind being treated as promises by the community. So they can't really say more than what the support staff have already said on the bug reports: "we've seen your report and are investigating". We're certainly not going to get an ETA because there is no upside for FD in making an announced deadline vs an unannounced one, and there is certainly downside to missing an announced deadline. It would be nice to get a confirmation that a dev has looked into it and confirmed the issue but in the end the only thing that actually matters is that it gets fixed. I'd suggest that anyone that is finding the bugs too frustrating should focus on something else until they are fixed. The content will still be there in a month or whatever.

On the other hand there does seem to be a communications disconnect given that Michael seemed unaware of the issues when he commented here. You'd think someone in FD might have said to him "hey that ruins thing that is getting so much attention isn't working right". Still the bigger concern for me is just how buggy it is. These bugs really seem like something that a group of internal testers would have found very quickly, and there should have been some in-depth internal testing given that it wasn't fully deployed in the beta.

I dont think much in depth beta testing gets done on the top secret stuff. information might leak, and with the lack of procedural stuff, the storyline overfocused stuff becomes ultra top secret , the barnacles and formidine rift content was bugged as well. So there is a pattern of some level of mild internal incompetence creeping in as far as QA testing, but im sure that sort of stuff is easily fixed so wont be to critical
 
I dont think much in depth beta testing gets done on the top secret stuff. information might leak, and with the lack of procedural stuff, the storyline overfocused stuff becomes ultra top secret , the barnacles and formidine rift content was bugged as well. So there is a pattern of some level of mild internal incompetence creeping in as far as QA testing, but im sure that sort of stuff is easily fixed so wont be to critical

Yes, I agree. I think this stuff needs more internal testing, regardless of the risk of leaks. If necessary the designers and devs who already know what is going in should get together and do some formal multi-player testing. I suspect it's the multi-player angle that isn't getting tested enough at the moment, and it's clear that there are enough issues with instancing and such that they can't afford to exclude it from betas and just release it (relatively) untested.
 
On the other hand there does seem to be a communications disconnect given that Michael seemed unaware of the issues when he commented here. You'd think someone in FD might have said to him "hey that ruins thing that is getting so much attention isn't working right". Still the bigger concern for me is just how buggy it is. These bugs really seem like something that a group of internal testers would have found very quickly, and there should have been some in-depth internal testing given that it wasn't fully deployed in the beta.

I'm fairly neutral regarding the issues with the ruins, but this part did annoy me somewhat. How the hell couldn't he have known this? I belive his comment was 2 or 3 days after people had been tearing their hair out trying to understand what was going on, and then to be told that shouldn't be happening does and has irked a few people. and rightfully I'd say.
 
Last edited:
Howdy All CMDRS,
Tonight I explored all the other bodies around our Ancient Ruins site and out in the sticks I came across a convoy... they jumped system to boldly go where barely anyone has gone before.
anyway I had a frame shift wake scanner and got a 10/4 on there jump system and I recorded it using nVidia exp. I thought great I will go finish up scanning the rest of these bodies and look back at my reference video for their high wake location.
To my surprise that video wasnt recorded even tho I made double sure by recording it twice and still I cant find it.

So I was thinking maybe a convoy in this system can lead us to another system where the other sites maybe....
 
Howdy All CMDRS,
Tonight I explored all the other bodies around our Ancient Ruins site and out in the sticks I came across a convoy... they jumped system to boldly go where barely anyone has gone before.
anyway I had a frame shift wake scanner and got a 10/4 on there jump system and I recorded it using nVidia exp. I thought great I will go finish up scanning the rest of these bodies and look back at my reference video for their high wake location.
To my surprise that video wasnt recorded even tho I made double sure by recording it twice and still I cant find it.

So I was thinking maybe a convoy in this system can lead us to another system where the other sites maybe....

I had the same theory and did the same thing. Unfortunately all the NPC's seems to jump to random locations, and the one I followed was in a system with no planets. I wish FD would actually use NPCs to drop clues like this. I remember when we found our assassination targets by jumping into a USS and overhearing NPC's talking about them. Sadly I don't think there's anything to this.
 
To play the devil's advocate, and as a software developer myself, I can fully understand why FD choose not to comment. Anything they say is either going to invite further questions and criticism and/or create expectations that wind being treated as promises by the community. So they can't really say more than what the support staff have already said on the bug reports: "we've seen your report and are investigating". We're certainly not going to get an ETA because there is no upside for FD in making an announced deadline vs an unannounced one, and there is certainly downside to missing an announced deadline. It would be nice to get a confirmation that a dev has looked into it and confirmed the issue but in the end the only thing that actually matters is that it gets fixed. I'd suggest that anyone that is finding the bugs too frustrating should focus on something else until they are fixed. The content will still be there in a month or whatever.

On the other hand there does seem to be a communications disconnect given that Michael seemed unaware of the issues when he commented here. You'd think someone in FD might have said to him "hey that ruins thing that is getting so much attention isn't working right". Still the bigger concern for me is just how buggy it is. These bugs really seem like something that a group of internal testers would have found very quickly, and there should have been some in-depth internal testing given that it wasn't fully deployed in the beta.

We actually agree pretty much completely then because I wasn't expecting a deadline myself. I was however expecting confirmation that there is actually a problem, literally just that. I have no beef with support at all, I've always found them to be excellent when I've had to deal with them (the issue here isn't even on support - they report it up and I'm sure they've done that) but I can't credit that nobody even knows at this stage whether there's an actual problem.

As with many other aspects of the game I don't want to spend my time attempting to play broken content but the flip side of the coin is that I don't want to depreive myself of playing content if it's not broken. With this particular issue, we're coming up on the two week point and still nobody even thinks it's appropriate to open dialogue about the issue, or confirm that there is an issue. It's about acknowledgment and communication and the reason they're so important is exactly that reasonable people will make allowances but it's very difficult to maintain that approach in an information vacuum.

Today was, as I said, just the straw that broke the camel's back. Had one too many goes on this ride.
 
Last edited:
Anyone else experiencing more disconnects/crashes than usual tonight?

Yeah the disconnects are up today/tonight

- - - Updated - - -

Howdy All CMDRS,
Tonight I explored all the other bodies around our Ancient Ruins site and out in the sticks I came across a convoy... they jumped system to boldly go where barely anyone has gone before.
anyway I had a frame shift wake scanner and got a 10/4 on there jump system and I recorded it using nVidia exp. I thought great I will go finish up scanning the rest of these bodies and look back at my reference video for their high wake location.
To my surprise that video wasnt recorded even tho I made double sure by recording it twice and still I cant find it.

So I was thinking maybe a convoy in this system can lead us to another system where the other sites maybe....


See if u can get more information, replicate, gathere data and report on where these convoys are going, and then my guess is others will follow up by conducting some priliminary investigations of the systems where those convoys go
 
um no it doesnt. If you see the color red on an object, then what you are viewing is a slower longer wavelength of light. The only way that red light is traveling at the speed of light is in a vacuum and its source has to be created that singular 700nm wavelength of light as its source. The human eye cannot tell the difference between reflected or emitted light.

Here's a page that does a better explanation than I could.

http://physics.stackexchange.com/questions/173931/why-does-red-light-travel-faster-than-blue-light

3rd answers analogy for example is what I was trying to get at. Although I found the Feynman one the best for getting a headache trying to wrap my head around.
 
I had the same theory and did the same thing. Unfortunately all the NPC's seems to jump to random locations, and the one I followed was in a system with no planets. I wish FD would actually use NPCs to drop clues like this. I remember when we found our assassination targets by jumping into a USS and overhearing NPC's talking about them. Sadly I don't think there's anything to this.

Are the convoys carrying any cargo ?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom