Alien archeology and other mysteries: Thread 9 - The Canonn
- Thread starter Ian Phillips
- Start date
- Status
I haven't had time to look closely yet, but someone a few pages back reminded me that our pilots wear helmets, which could explain the moving ghosts as you move your head and make it more likely there is a meaningful "primary" image with out of focus duplicates.
How come? Don't they already cite time dilation as the reason for the use of Supercruise? (Ignore the fact that we can get close enough to stellar mass black holes to "see" their event horizons without suffering any loss of time while in normal drive. [big grin])
That too is deliberate
Michael
Damn you! Stop teasing!
Reminds me of the last time I was in Amsterdam! Do you take dollars?
Ahhhh...Amsterdam [smile]
Masheikh Scytale
Banned
I wont debate this in a background where even light is "faster than light" (communications, GalNet,...).
That too is deliberate
Michael
What does that mean? I dont understand
Wait, they let you in?
XD Fair point.
I wasn't wanting to debate, anyway, I just wanted to clarify what you were getting at.
I did try this method this afternoon. Didn't get yarked out of witchspace unfortunatly.
Ozric
Volunteer Moderator
It means the UA using morse and the UP using Octal is deliberate.
Masheikh Scytale
Banned
No worries. I just assume not to think relativistic anytime in this game. (Which is a good thing !) [yesnod]
Remember when I had that multi race theory? where the UA was thargoid and the UP was Oreosian? also Oreosian or however you spell it is hard to spell haha
Attempt number one to activate Unknown Probe near alien ship.
[video=youtube;J5FMzY6a0FA]https://www.youtube.com/watch?v=J5FMzY6a0FA[/video]
Two conclusions can be made from this:
1. It didn't go off because I was too far. I tested this over and over, the range of the activation for the ADS scanner on the probe is 300 meters. It's possible it didn't go off because again, I was too far away.
2. It doesn't go off period while the ship is near.
I'm leaning more towards the first simply because I'd rather doubt then jump to conclusions...HOWEVER. There is one problem.
Simply put, I have no idea how I got more then 300 meters away from the probe. If you look at the video the part where my ship was moving the fastest...I was going in reverse. Since jettisoning cargo always puts it behind you wouldn't that have put me closer to it? In addition it took me about 10 seconds after regaining control of my ship to when I activated the ADS. In the second part of the video where I test ejecting and activating the ADS, I waited 11-12 seconds and it worked perfectly. It works perfectly no matter how many times I practice doing it.
The only time it didn't work, was when the ship was there. So my question is, was I too far away or does the ship prevent it from going off?
Purely speculation but if it is the latter (and I'm not saying it is) then we have to ask why that ship is suppressing it.
Also as a last note, you can jettison all cargo and be pressing the ADS scanner button at the same time and still activate the probe. This is important because it means you don't have to wait for the probe to appear on the radar before starting the ADS to honk it, you can press it and activate the countdown till the ADS honks as soon as you eject cargo saving you a few seconds.
[video=youtube;J5FMzY6a0FA]https://www.youtube.com/watch?v=J5FMzY6a0FA[/video]
Two conclusions can be made from this:
1. It didn't go off because I was too far. I tested this over and over, the range of the activation for the ADS scanner on the probe is 300 meters. It's possible it didn't go off because again, I was too far away.
2. It doesn't go off period while the ship is near.
I'm leaning more towards the first simply because I'd rather doubt then jump to conclusions...HOWEVER. There is one problem.
Simply put, I have no idea how I got more then 300 meters away from the probe. If you look at the video the part where my ship was moving the fastest...I was going in reverse. Since jettisoning cargo always puts it behind you wouldn't that have put me closer to it? In addition it took me about 10 seconds after regaining control of my ship to when I activated the ADS. In the second part of the video where I test ejecting and activating the ADS, I waited 11-12 seconds and it worked perfectly. It works perfectly no matter how many times I practice doing it.
The only time it didn't work, was when the ship was there. So my question is, was I too far away or does the ship prevent it from going off?
Purely speculation but if it is the latter (and I'm not saying it is) then we have to ask why that ship is suppressing it.
Also as a last note, you can jettison all cargo and be pressing the ADS scanner button at the same time and still activate the probe. This is important because it means you don't have to wait for the probe to appear on the radar before starting the ADS to honk it, you can press it and activate the countdown till the ADS honks as soon as you eject cargo saving you a few seconds.
Last edited:
I ll share here my encounter, i ve not posted it on youtube as I believe compression spoils the video, (you'll hear me speak french...) and you get a very clear view of the "bar codes" . You will see its positioning thrusters at work, an okay view of the cockpit. https://drive.google.com/drive/folders/0BzePz_dq1O08WmpRZVpOalJ6UnM?usp=sharing
At first I, too, believed that there was some code in the lens flare. Having studied it some more, I no longer believe that to be the case.
Lens flare is caused by light bouncing around inside a camera's optics. There are three main factors which influence the shape of the flare: the shape of the light source, the configuration of the camera optics, and the angle that the light enters the optics.
In the case of the unknown encounter videos the flare does look rather like a bar code of some kind at first glance; on closer inspection though, it looks to me like it is simply a 'double flare' that keeps getting repeated - here two short vertical lines; there two short fat blobs; and there, two little dashes. And so on. As the view moves each pair moves together, over and across the other pairs. The vertical displacement that some people have noted, which makes it resemble the obelisk spectrogram, also changes as you look up and down.
I believe now that the flare pattern that we see is not a code, but results from the fact that the light beam is actually two beams, very small and very close together, and it is the sheer intensity of the light which is causing such a dramatic effect.
Dang. And I so wanted it to be a message
I may be wrong, of course. I don't suppose there are any optics experts lying around that we can interrogate?
Anyway. If you want to see the video I have been studying it is one I made myself, here: https://www.youtube.com/watch?v=fDpWnqJcfnA
There's a good bit at the end showing the UA activity after the encounter, for anyone interested.
Lens flare is caused by light bouncing around inside a camera's optics. There are three main factors which influence the shape of the flare: the shape of the light source, the configuration of the camera optics, and the angle that the light enters the optics.
In the case of the unknown encounter videos the flare does look rather like a bar code of some kind at first glance; on closer inspection though, it looks to me like it is simply a 'double flare' that keeps getting repeated - here two short vertical lines; there two short fat blobs; and there, two little dashes. And so on. As the view moves each pair moves together, over and across the other pairs. The vertical displacement that some people have noted, which makes it resemble the obelisk spectrogram, also changes as you look up and down.
I believe now that the flare pattern that we see is not a code, but results from the fact that the light beam is actually two beams, very small and very close together, and it is the sheer intensity of the light which is causing such a dramatic effect.
Dang. And I so wanted it to be a message
I may be wrong, of course. I don't suppose there are any optics experts lying around that we can interrogate?
Anyway. If you want to see the video I have been studying it is one I made myself, here: https://www.youtube.com/watch?v=fDpWnqJcfnA
There's a good bit at the end showing the UA activity after the encounter, for anyone interested.
Short for ..... "To you, hi !" .....or in Sci Fi terms .... "Greetings Earthling"
What about the beeps the scout makes.... its the same on every video clip...
I may have missed the boat on this, but is it possible to get the UA to morse the outline of the "thargoid" ship? The UP won't disable it, but the UA does it's thing automatically, without honking, so maybe?
No, if you watch the video you'll note that the UA scans me as soon as I eject it out. And even then it will only "morses" the outline when we have it in our cargo holds.
- Status