Leaderboard

First up in LEGO Worlds: first-ever tree generation (tweet from the other day). And just now, LEGO Worlds is 30% off ($10.49 USD, £8.39). Tad strange why it is already on sale ($15 is already a good price), but whatever. http://steamcommunity.com/games/332310/announcements/detail/110692387531684992

So, yeah, the two upcoming musics are going to have this kind of names. I love this one, I hope you'll like it as well! Listen on SoundCloud: https://soundcloud.com/officialshadowblaze/shadowblaze-storm-district

I think I'm on to something but had to leave for work before I could follow it through. Will update as soon as possible, there is still hope.

Well let us know how it goes. Oh wait, you shoulda let us know afterwards so we don't have to wait to respond in case it fixed your problem. In any case... I'm still not sure regardless if .NET framework isn't the problem.

I've looked a bit more into this too, I can confirm that your sequence for 0x8000 bytes works for multiple files (for blocks of that size), and even better - the sequence seems solely dependent on the block size! For example for block sizes of 33 bytes, the following sequence works as a key (there are two files of 33 byte size which is how I can test it): 4D 6F AE AC 0A E6 CB 00 02 84 46 00 11 E6 2C ED CE 13 B5 44 F1 62 70 5C 9E 41 0A 28 0E C2 DC E4 D7 Now the question is how to derive this key from the block size - could it be an LCG with the block size as seed? I'll try and run some tests when I get the time. Update : it doesn't look like an LCG - plotting the values as triplets in 3d space doesn't reveal any patterns. I also checked the keys of a 32 and 33 byte chunk, hoping that there might be an obvious connection (since the seeds are off by one) - I couldn't see one: 32 byte key : 2f 61 17 d9 57 57 67 01 4b 11 63 c1 61 97 42 de 75 29 c9 a4 9e 8e 5c 7f 87 ee fa 22 0b 16 55 a9 33 byte key : 4d 6f ae ac 0a e6 cb 00 02 84 46 00 11 e6 2c ed ce 13 b5 44 f1 62 70 5c 9e 41 0a 28 0e c2 dc e4 d7 (I did spot the 57 57 in the 32 byte key - probably not significant but you never know)

I am not sure, if I get all of what you wrote, but I think it is an offset based encryption. I searched for texts in the old-files and searched for the matching values in the new-files. Then I sorted them by the new-values and detected equivalent positions. I searched for 0000 and lego. Here are the results: 0000 30 30 30 30 // in the old file 1 0001 695f: 28 4f 9b b4 // in the new file 2 0000 695f: 28 4f 9b b4 1 0001 50cd: 3c 63 fd 65 2 0000 50cd: 3c 63 fd 65 1 0000 81a3: 3f 07 98 4f 2 0000 01a3: 3f 07 98 4f 1 0000 dcaf: 4c e3 99 0a 2 0001 5caf: 4c e3 99 0a 1 0000 b553: 4e eb f8 b3 2 0000 3553: 4e eb f8 b3 1 0000 4a34: 56 90 cd 86 2 0000 ca34: 56 90 cd 86 1 0001 2411: 6c cb b6 49 2 0000 a411: 6c cb b6 49 1 0000 4b78: 8d ef e3 51 2 0001 4b78: 8d ef e3 51 1 0000 e7c4: 8f 56 a5 a5 2 0000 67c4: 8f 56 a5 a5 1 0000 2aee: a2 5c f8 71 2 0001 2aee: a2 5c f8 71 1 0000 205d: a9 d8 4a 3e 2 0000 a05d: a9 d8 4a 3e 1 0000 4d73: b6 67 e1 2b 2 0001 4d73: b6 67 e1 2b 1 0001 3983: be 0f 08 9b 2 0000 3983: be 0f 08 9b 1 0000 0c26: e3 cc 99 fb 2 0001 0c26: e3 cc 99 fb 1 0000 8ba3: ea 0d ae 0a 2 0001 0ba3: ea 0d ae 0a lego 6c 65 67 6f // in the old file 1 0000edae: 06 fd a8 00 // in the new file 2 00016dae: 06 fd a8 00 1 00010bab: 09 ed cb c7 2 00008bab: 09 ed cb c7 1 0000e201: 11 63 eb 01 2 0001e201: 11 63 eb 01 1 00004d7b: 18 a1 bb bd 2 00014d7b: 18 a1 bb bd 1 0001b41a: 18 ad bf 5f 2 0001341a: 18 ad bf 5f 1 00019692: 1e 81 84 f9 2 00009692: 1e 81 84 f9 1 0001f50a: 20 95 05 8e 2 0000f50a: 20 95 05 8e 1 00013f4e: 31 c6 e7 aa 2 0001bf4e: 31 c6 e7 aa 1 000150d5: 33 48 97 66 2 000050d5: 33 48 97 66 1 0000e7cc: 38 7b 31 df 2 000067cc: 38 7b 31 df 1 0000b55b: 42 21 68 09 2 0000355b: 42 21 68 09 1 0000133a: 42 58 8a 47 2 0001133a: 42 58 8a 47 1 0000ee96: 44 91 15 e4 2 00016e96: 44 91 15 e4 1 0001e823: 49 35 3c 3f 2 0000e823: 49 35 3c 3f 1 0000e0bb: 4d 16 7e 72 2 0001e0bb: 4d 16 7e 72 1 0001571e: 5c fe 5a fc 2 0000d71e: 5c fe 5a fc 1 0000dcb7: 6d fb 9f e9 2 00015cb7: 6d fb 9f e9 1 000020e4: 71 17 4e 89 2 0000a0e4: 71 17 4e 89 1 0000ca3c: 71 20 57 26 2 00004a3c: 71 20 57 26 1 0000202a: 72 c0 db de 2 0001202a: 72 c0 db de 1 00014b80: 78 3c 02 11 2 00004b80: 78 3c 02 11 1 00002997: 78 91 e9 a3 2 0000a997: 78 91 e9 a3 1 0000a419: 80 2b 02 cf 2 00012419: 80 2b 02 cf 1 0000e24d: 83 82 a3 7f 2 0001e24d: 83 82 a3 7f 1 00016e05: 8c d5 55 14 2 0000ee05: 8c d5 55 14 1 00011ace: 9a b1 64 43 2 00001ace: 9a b1 64 43 1 00007816: ad 43 70 2d 2 0001f816: ad 43 70 2d 1 00005fd4: b2 f8 4e 82 2 0000dfd4: b2 f8 4e 82 1 00002065: b7 62 66 04 2 0000a065: b7 62 66 04 1 0001398b: b8 d5 bc a8 2 0000398b: b8 d5 bc a8 1 0001b9c8: be 6d ac 9c 2 000039c8: be 6d ac 9c 1 00002162: c5 36 fc 42 2 0000a162: c5 36 fc 42 1 00001a62: c6 70 cf b7 2 00019a62: c6 70 cf b7 1 00012af6: cc f7 0b d8 2 00002af6: cc f7 0b d8 1 0000169a: d4 e2 40 9a 2 0001169a: d4 e2 40 9a 1 00010c2e: d7 ad a5 94 2 00000c2e: d7 ad a5 94 1 0001c982: d9 94 43 55 2 0000c982: d9 94 43 55 1 00018332: db 73 3c 82 2 00010332: db 73 3c 82 1 00001978: db a0 c3 4b 2 00019978: db a0 c3 4b 1 00002575: df 45 f8 b5 2 00012575: df 45 f8 b5 1 00016f27: e0 a5 70 47 2 0000ef27: e0 a5 70 47 1 000108a0: e8 96 88 06 2 000188a0: e8 96 88 06 1 00016967: fa 07 71 92 2 00006967: fa 07 71 92 1 000081ab: fa 35 1c 5e 2 000001ab: fa 35 1c 5e 1 0001bdb8: ff 58 19 49 2 00013db8: ff 58 19 49 You can see that when the last 15 bits of the position are the same the encryption is also the same. But I did not found the algorithm by now.

Unreal 4 has full support for OBJs. The issue is that the file format lacks itself support for some of the nice safety features that FBX includes. If you screw up and export it with an FBX, generally you'll be okay (but his screenshot indicates significant issues that go beyond the file format). If you screw up and export it with an OBJ, those errors will become more obvious. I prefer to export with OBJ when I'm testing meshes since it's quicker, but I switch to FBX for the final import and I use the guides in the documentation to double-check everything. I'm willing to go along with Skanibani if he thinks he's got this (for now), but I'm going to continue being critical and post any relevant, helpful links I have so that this project can be successful, providing that he's got the effort and isn't going to cheat on it.