Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenJKDF2 Correlation? #36

Open
shinyquagsire23 opened this issue Oct 26, 2020 · 0 comments
Open

OpenJKDF2 Correlation? #36

shinyquagsire23 opened this issue Oct 26, 2020 · 0 comments

Comments

@shinyquagsire23
Copy link

shinyquagsire23 commented Oct 26, 2020

I took a look through some of the files out of curiosity, and it seems there's a lot of correlation between SWE1R and JKDF2's helper functions. I think this is in the main repo wiki but LEC has a common std library and the renderdroid library, and for JKDF2 the Sith engine is just built on top of that.

Grim Fandango Remastered on Android has a .so file which leaks all the canonical names for std and rd* functions, it may make it a lot easier to reverse SWE1R. vec.c is rdVector, I think File-access.md is stdConffile, I'll have to see if I can figure out a few more but I have a good portion of the matrix/vector stuff implemented at https://github.com/shinyquagsire23/OpenJKDF2/tree/master/df2_reimpl and a function listing for JKDF2.

Anyhow it might be a good idea to have a common codebase for the std and renderdroid libraries, maybe not right away but at least keep names the same that way improvements can be ported across maybe.

EDIT: actually last thing, I also noticed between JKDF2 and Droidworks/MoTS/probably SWE1R, they switched compilers. JK keeps a lot of unreferenced functions and has a lot more inlining, whereas after JKDF2 the compiler strips out unused functions more often, but inlines less aggressively I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant