[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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.

Sign up for GitHub

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

Jump to bottom

Collision surface information #34

Open
JayFoxRox opened this issue May 19, 2018 · 2 comments
Open

Collision surface information #34

JayFoxRox opened this issue May 19, 2018 · 2 comments

Comments

@JayFoxRox
Copy link
Member
JayFoxRox commented May 19, 2018 •
edited
Loading

(Patched US version)

char __cdecl sub_454060(int a1) reads flags from *(_BYTE *)(a1 + 44) and then decides what kind of surface name it is? The output is then send to a text printing function.

The names and values have been extracted to the wiki.
@JayFoxRox
Copy link
Member Author
JayFoxRox commented May 19, 2018 •
edited
Loading

(Patched US version)

(gdb) set *(uint32_t*)Memory(0x50C88C)=1 turns on a string display near the "repair" text.
I'm not sure which podracers it relates to. Seemingly more than the player ones.

@JayFoxRox
Copy link
Member Author
JayFoxRox commented May 19, 2018 •
edited
Loading

(Patched US version)

void __cdecl sub_476EA0(float a1) could be responsible for handling the surface types.
It has stuff like:

[...]
      v14 = *(_DWORD *)(v3 + 44);
      if ( v14 & 4 ) // if this is a "Fast" surface..
        v39 = 200.0; // ..set speed boost to 200
[...]

@JayFoxRox JayFoxRox mentioned this issue May 19, 2018
Closed
@JayFoxRox JayFoxRox mentioned this issue Jul 21, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JayFoxRox