REDRIVER2 VS ghidra

Please include ReDriver2! A recompilation of PS1's Driver 2. I finished it a few days ago and has a good set of advantages over emulating. There's a mini guide in an old post in this sub but I wanted to make a more datailed guide

But now there's NSA's Ghidra which has accelerated decompilations/reverse engineering a ton, it means that within a few years any active community can fully reverse engineer into human readable code and make major changes, it's why now there's a Driver 2 PC port and a Jak & Daxter PC port with 2 and 3 being in the works despite these games having basically no community before it, Nintendo games have a bigger modding community and a lot of games are on the way to being fully decompiled (bonus in that some games share a lot of stuff, so as one project completes it also makes it so that multiple games also advance faster

Driver 2, which is a PSX exclusive, was disassembled and rewritten so that it runs natively on Windows. Link: https://github.com/OpenDriver2/REDRIVER2

https://github.com/OpenDriver2/REDRIVER2/wiki/Installation-instructions (proof of your stupidness and laziness)

Heres a link to the projects Github page: https://github.com/OpenDriver2/REDRIVER2

Redriver2 - Driver 2

+ Analog stick should work, as well as remapping: https://github.com/OpenDriver2/REDRIVER2/wiki/Controls Try "Moving the left stick DOWN and pressing SELECT+START enables ANALOG mode

Driver 2 has been reverse engineered and is playable: https://github.com/OpenDriver2/REDRIVER2

Let's see what our beloved software reverse engineering framework Ghidra has to show.

Define war machinery. Contributing to Ghidra?

https://github.com/NationalSecurityAgency/ghidra

Binary Ninja likewise is empty and keeps up just fine as well. It's not a coincidence that the two commercial products that are funding it are both confident enough to put their stuff online like this.

And it's no conspiracy theory or intentional sandbagging, you can see the implementation: https://github.com/decompiler-explorer/decompiler-explorer

and if anyone can improve the other tools performance we'd be happy to accept it. We reached out to the Ghidra devs: https://github.com/NationalSecurityAgency/ghidra/issues/5228 but they didn't have any silver bullets for us either.

Nice, I'll give it a closer look. My only concern so far is memory hooking (still needed for hardware registers), which on Java side was called by FilteredMemoryState [1]. In memstate.cc it looks like just the simpler MemoryState is implemented [2], and there's no equivalent to MemoryAccessFilter. But it might not be that complicated to add...

[1]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...

[2]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...