🔒 SS1 EE Reactor code randomization fix
1 Guest is here.
663c2167028ab
11. April 2018, 22:29:25
You probably have already checked the sources, but if you have not code is randomized in PLAYER.C.#25
11. April 2018, 23:15:51
What exactly happened to break the randomization in EE?#26
12. April 2018, 05:10:09
#27
Quote by JosiahJack:
Unknown.What exactly happened to break the randomization in EE?
Wild theories follow:
Assuming that the Enhanced Edition was created without the sources, so, based on reverse engineering / patching the executable, it may be that some initialization order and/or pointers were messed up. The randomization is based on the effects-randomizer. So, it could be that this randomizer is affected.
Or - Remember when the OpenSSH library was broken by satisfying a static code checker to initialize a variable? Something similar could have happened here: Instead of reading to-be-believed random memory as a seed for the randomizer, this memory locaion is now pre-set, with always the same value.
12. April 2018, 21:46:31
#28
TurboSnailQuote
Ok,Well the Data Reader is behaving better but the Automap on level two is refusing to work now. It will not draw the map or move the arrow.
I am using "archive.dat" [CRC-32: 214f9e1f]
I just checked the older "archive.dat" and found it also had an Automap issues. The arrow was duplicated (One purple stationary and one red which moved), the arrows would not rotate and the map did not auto scroll but it did draw.
Very strange. Thank you for your effort!
13. April 2018, 05:08:42
Thank you for testing!#29
This whole thing is getting weirder and weirder. I might have time on the weekend to investigate.
[edit] First test: This seems to affect only level 2 (tested R up to 6), and only the left MFD. The right one is fine.
Legal stuff
Privacy Policy & Terms of Service Contact