Mayriad-70 2nd PDF - Possible puzzle to solve?

Archive Waking Titan Investigation
41

That’s all right! I really hope this image can be “repaired”, because it somehow gives me the feeling it is more substantial than other clues yet have been. Maybe because it’s a picture xD commendations to your efforts!

42

If you find something different coming through for you let me know or maybe post it here and I may be able to clean it up or search the trash

43

Just to note, even with the “realigned” variant that someone did (minus the “glitchy” mess at the bottom), the shine on the orb at the bottom is not uniformed naturally, as if it’s not an in-game 3D model but more like concept art (possibly watercolor) or a filter was used to dither it. The problem is that there’s been a lot of concept art for No Man’s Sky over the years and I don’t have the book that was sold back when it was released so I don’t have much to reference from but there are 4 possibilities at the moment.

  1. A building (most logical as the orb could be a portal).
  2. A weapon (tilted vertically).
  3. A ship (unlikely as the “sail” like part is too bulky and ornate in nature).
  4. A Gek (my personal theory as the “orb” may be an “eye” and that “sail” may be a “helm” or “crest” much like many Geks have).
44

In my mind it most resembles concept art of the Korvax science ships with the swooped back and bubble cockpit, though that’s not to say it is that.

1920×1358 282 KB

I have the Limited Edition of NMS and looked through the art book, but didn’t see anything that was close to our image.

2 Likes
45

I feel like that bottom section is masking something, but I’ve been working top to bottom, there is a lot of junk throughout the image. I wonder why it is, and if I can clean it up enough to make sense of it.

46

What stands out to me most is the yellow/gold decorative like part that starts like a thick line and ending floral or leaf like. This does not appear to match anything currently in NMS or in any of the concept art for NMS we know about.

The light part on which this decoration appears to be drawn, certainly looks like panelling of some kind of structure. This seems to be modern or maybe even sci-fi/future like.

Then we have the round shape at the bottom of this, which many see as some sphere, but in my opinion can very well be a hole too. Depending on how you look at it, it could be the surface reflection, or it could be the other end of a tunnel of some sort as well.

I agree that this may certainly have been concept art, but not necessarily so. As @Difficultlevel pointed out, it may even be a collage of some sort, where two or more images have been put together.

I have been messing with byte removal in several sections, mainly focused on areas with abundant zeros, like others have done as well. It appears the more data we remove, the more we lose quality of the image. Removal of bytes in different areas within the file, will have different effects on the outcome. I can personally not find any logic within the hex editor that stands out to know what has changed and can therefor be reverted. I really believe this is not the way to go (personal opinion) and does not yield improved results, but the contrary appears to be the case. I have checked the source code of some of those JPEG glitchers and it appears that data is often actually being overwritten, which means there is no way to retrieve what used to be there.

Maybe we should try focus on different methods. See if we missed any other ways of hiding clues, because I do believe it is trying to tell us something.

47

See the JPEG entry on Wikipedia if you want to go deep on the file format and the math behind what’s going on. I think without really understanding that format specification, modifying sections of the file will just have haphazard results.

48

Sometimes the jpg looks more corrupted but there are simple things to fix big errors…

Please post what you have so we can all try to improve and further your work.

49

Also, a note. I would share this program but there are two problems.

  1. The program is a registered product.
  2. You cannot find it anywhere online anymore.

So I’m sorry, but I can’t help with specialised products, but I can work on images

50

@Drakonslayor, you may or may not know this, but regarding the pixellated object at the bottom, is this something that could have started as a real image and then was heavily corrupted? Or was this a deliberate modification of the JPG in order to show this…whatever it is…and wasn’t part of the original image? Meaning, could someone have distorted the JPG in a specific way in order to create this pixel art?

51

Yes it is highly possible. As I said earlier I haven’t had a chance to get to it, but it is possible it is either distorted or that “image” itself is covering something.

52

Has anyone noticed in the corrupted image pdf, near the top of the fin shape there are 4 small squares of colour if you zoom in you can see them easier, could this be a key to decrypting the image?

53

No, this is the corruption… and usually the key to color correction when repairing the images.

54

It could actually be 3 seperate images: 1. The fin on top 2. The orb in the middle 3. The pixels on the bottom

55

The fun and the orb are definitely the same image. But I think the fish thing is an image all itself.

56

i just KNOW I have seen this structure before. The problem is… it can be from a movie (Star Wars, Star Trek perhaps one of the later Aliens or whatever they named them) it can be from a game (Although I kinda doubt that) or a book cover (I have been reading so many books in my life that I don’t know where to look. Asimov? Heinlein? Clarke? Wells, Verne… sigh)
I keep digging in my book collection, running through space related games and watching my eyes out on movie clips. I know what I am looking for. A tall building with a green “fluid like” orb on a triangular base. The orb seems to be hovering or at least not attached directly to the structure. I am unsure about the other colors but white with yellow accents would certainly be possible, however white/green as well.

btw did anyone noticee on the gamepedia, the entry for monolith_Type_12 has been removed as “merged with type 11” (just 2 weeks ago) bringing the total number of different monoliths to… hold on… here it comes… 16

3 Likes
57

Though I’m not completely sure on the colour of the orb (Though I feel like it is a liquid metal black colour like a ferrofluid) you’re are right that the colour of the tower is white with gold accents.

It does seem very similar to something but I can’t think of what… my thought is, when you say aliens, does it point to anything in Prometheus? Since he was atlas’ s brother it would make sense.

1 Like
58

I have reasonable knowledge to figure out file specific markers and what the byte info may represent. Thank you for linking the wikipedia page though @solarparty. I just gave up on trying to fix the corruption as I personally saw no way to achieve this. No offence to those who wish to continue trying though and if anyone can it will be awesome.

Below I will however share my notes on the pdf image when it comes to headers:

Source image

[details=StegSolve Info] File format report (StegSolve)

File: s01-091d12cf-befd-4f85-8644-3a2e74d56a8a.jpg
Read 206a6 bytes
Start of Image

Application data
Length: 18 (24)
Dump of data:
Hex:
0018457869660000 49492a0008000000 0000000000000000
Ascii:
…Exif… II*… …

Application data
Length: 11 (17)
Dump of data:
Hex:
00114475636b7900 0100040000005000 00
Ascii:
…Ducky. …P. .

Application data
Length: 32f (815)
Dump of data:
Hex:
032f687474703a2f 2f6e732e61646f62 652e636f6d2f7861 702f312e302f003c 3f787061636b6574 20626567696e3d22 efbbbf222069643d 2257354d304d7043 656869487a726553 7a4e54637a6b6339 64223f3e203c783a 786d706d65746120 786d6c6e733a783d 2261646f62653a6e 733a6d6574612f22 20783a786d70746b 3d2241646f626520 584d5020436f7265 20352e362d633133 382037392e313539 3832342c20323031 362f30392f31342d 30313a30393a3031 2020202020202020 223e203c7264663a 52444620786d6c6e 733a7264663d2268 7474703a2f2f7777 772e77332e6f7267 2f313939392f3032 2f32322d7264662d 73796e7461782d6e 7323223e203c7264 663a446573637269 7074696f6e207264 663a61626f75743d 222220786d6c6e73 3a786d703d226874 74703a2f2f6e732e 61646f62652e636f 6d2f7861702f312e 302f2220786d6c6e 733a786d704d4d3d 22687474703a2f2f 6e732e61646f6265 2e636f6d2f786170 2f312e302f6d6d2f 2220786d6c6e733a 73745265663d2268 7474703a2f2f6e73 2e61646f62652e63 6f6d2f7861702f31 2e302f7354797065 2f5265736f757263 6552656623222078 6d703a4372656174 6f72546f6f6c3d22 41646f6265205068 6f746f73686f7020 4343203230313720 2857696e646f7773 292220786d704d4d 3a496e7374616e63 6549443d22786d70 2e6969643a303933 4444433436353833 3231314537423643 3338464346314639 3039464142222078 6d704d4d3a446f63 756d656e7449443d 22786d702e646964 3a30393344444334 3735383332313145 3742364333384643 4631463930394641 42223e203c786d70 4d4d3a4465726976 656446726f6d2073 745265663a696e73 74616e636549443d 22786d702e696964 3a30393344444334 3435383332313145 3742364333384643 4631463930394641 4222207374526566 3a646f63756d656e 7449443d22786d70 2e6469643a303933 4444433435353833 3231314537423643 3338464346314639 3039464142222f3e 203c2f7264663a44 6573637269707469 6f6e3e203c2f7264 663a5244463e203c 2f783a786d706d65 74613e203c3f7870 61636b657420656e 643d2272223f3e
Ascii:
./http:/ /ns.adob e.com/xa p/1.0/.< ?xpacket begin=" ..." id= "W5M0MpC ehiHzreS zNTczkc9 d"?> <x: xmpmeta xmlns:x= "adobe:n s:meta/" x:xmptk ="Adobe XMP Core 5.6-c13 8 79.159 824, 201 6/09/14- 01:09:01 "> <rdf: RDF xmln s:rdf="h ttp://ww w.w3.org /1999/02 /22-rdf- syntax-n s#"> <rd f:Descri ption rd f:about= "" xmlns :xmp="ht tp://ns. adobe.co m/xap/1. 0/" xmln s:xmpMM= "http:// ns.adobe .com/xap /1.0/mm/ " xmlns: stRef="h ttp://ns .adobe.c om/xap/1 .0/sType /Resourc eRef#" x mp:Creat orTool=" Adobe Ph otoshop CC 2017 (Windows )" xmpMM :Instanc eID="xmp .iid:093 DDC46583 211E7B6C 38FCF1F9 09FAB" x mpMM:Doc umentID= "xmp.did :093DDC4 7583211E 7B6C38FC F1F909FA B"> <xmp MM:Deriv edFrom s tRef:ins tanceID= "xmp.iid :093DDC4 4583211E 7B6C38FC F1F909FA B" stRef :documen tID="xmp .did:093 DDC45583 211E7B6C 38FCF1F9 09FAB"/> </rdf:D escripti on> </rd f:RDF> < /x:xmpme ta> <?xp acket en d="r"?>

Application data
Length: e (14)
Dump of data:
Hex:
000e41646f626500 64c000000001
Ascii: …Adobe. d…

Quantisation table
Length: 84 (132)

Start of frame : Baseline DCT (Huffman coding)
Header Length: 11 (17)
Precision: 8
Image lines: 5af (1455)
Samples per line: 41c (1052)

Huffman table
Length: 118 (280)

Start of scan
Header Length: c (12)
Detected 131443 bytes in scan

End of Image[/details]

[details=JPEG Markers / Hex]* SOI

  • FF D8 - 2 bytes 0 - Start Of Image
  • DQT
  • FF DB - 2 bytes 880 - Quant. Table
  • 00 84 - 2 bytes 882 - Length of QT 132
  • 00 - 1 byte 884 - QT Info 00
    bit 0…3: number of QT (0…3, otherwise error)
    bit 4…7: precision of QT, 0 = 8 bit, otherwise 16 bit
  • Followed by n bytes: bytes 885 - QT values, n=64*(precision+1)
  • SOF0
  • FF C0 - 2 bytes 1,014 - Start Of Frame baseline DCT
  • 00 11 - 2 bytes 1,016 - SOF0 length, equals 8+components*3, means 3 components (see below)
  • 08 - 1 byte 1,018 - Data precision (bits/px/color component) 8
  • 05 AF - 2 bytes 1,019 - Image height 1455px
  • 04 1C - 2 bytes 1,021 - Image width 1052px
  • 03 - 1 byte 1,023 - Number of components 3 (=color YYCbCr(YUV) or YIQ)
  • In sets of 3 bytes each, as follows:
  1. 01 - 1 byte 1,024 - Component ID, 1 (=YY)
  2. 11 - 1 byte 1,025 - Sampling Factor 17 (1=vert., 7=hor.)
  3. 00 - 1 byte 1,026 - Quant. table nr., 0
  4. 02 - 1 byte 1,027 - Component ID, 2 (=Cb)
  5. 11 - 1 byte 1,028 - Sampling Factor 17 (1=vert., 7=hor.)
  6. 01 - 1 byte 1,029 - Quant. table nr., 1
  7. 03 - 1 byte 1,030 - Component ID, 3 (=Cr)
  8. 11 - 1 byte 1,031 - Sampling Factor 17 (1=vert., 7=hor.)
  9. 01 - 1 byte 1,032 - Quant. table nr., 1
  • SOF2
  • FF C2 - N/A (progressive DCT)
  • DHT
  • FF C4 - 2 bytes 1,033 - Huffman Table
  • 01 18 - 2 bytes 1,035 - Length of Huffman Table 280
  • 00 - 1 byte 1,036 - HT Info, number of HT 00
    bit 0…3 : number of HT (0…3, otherwise error)
    bit 4 : type of HT, 0 = DC table, 1 = AC table
    bit 5…7 : not used, must be 0
  • Followed by 16 bytes: bytes 1,037 - number of Symbols with codes of length 1…16 (sum = number of codes)
  • Followed by n bytes: bytes 1,053 - Table with symbols in order of increasing code length (n=total number of codes)
  • DRI
  • FF DD - N/A (Restart Interval)
  • SOS
  • FF DA - 2 bytes 1,315 - Start Of Stream
  • 00 0C - 2 bytes 1,317 - length, (6+2 * the number of components) 12 bytes
  • 03 - 1 byte 1,319 - number of components (1-4) 3
  • 01 00 - 2 bytes 1,320 - Comp. ID 1 (YY), using HT AC 00(AC/DC)
    bit 0…3 : AC table (0…3)
    bit 4…7 : DC table (0…3)
  • 02 11 - 2 bytes 1,322 - Comp. ID 2 (Cb), using HT 11(AC/DC)
    bit 0…3 : AC table (0…3)
    bit 4…7 : DC table (0…3)
  • 03 11 - 2 bytes 1,324 - Comp. ID 3 (Cr), using HT 11(AC/DC)
    bit 0…3 : AC table (0…3)
    bit 4…7 : DC table (0…3)
  • Followed by 3 bytes 1,326 - Ignorable Bytes
  • RSTn
  • FF Dn - N/A (no Restart)
  • APPn
  • FF En - N/A (no App specific markers for metadata)
  • COM
  • FF FE - N/A (no Comments)
  • EOI
  • FF D9 - 2 bytes 132,772 (End Of Image)

Corruption takes place between SOS and EOI
Note: Hex values and addresses in bold[/details]
Hope this might be useful to someone …

59

Thank you, do you have the images that you worked on? If you could upload I can compare at my end.

60

Ummm did you just edit that or did I completely miss it the first time?