![]() Upon completing a mission, some of the blue lights in a circle in the middle of the table turn on. The "fuel" lights go out one by one at a time interval, and can be re-lit by having the ball go over them, or all at once by going up the launch ramp again. Missions end either by being completed, or by being aborted due to running out of "fuel", as indicated by the lights in the passage that passes under the launch ramp. Some missions involve a number of steps which must be completed in sequence. Each mission has a set number of things for players to do, such as hitting the "attack bumpers" (which are a set of four bumpers at the top of the table) eight times (this is the "target practice" mission). Players accept a mission by hitting "mission targets" which select which mission they will take, and by going up the "launch ramp". Players can attain nine different ranks (listed from lowest to highest): Cadet, Ensign, Lieutenant, Captain, LT Commander, Commander, Commodore, Admiral, and Fleet Admiral. and the decompiler has misinterpreted it as a longlong because of the access patterns (64bit pointers).The table features the player as a member of a space fleet that completes missions to increase rank. So I think this might be part of an initialization function for some property on top of a object that exists at *param_1. The 0x2b part I'm not sure about myself but it looks like some other kind of similar checks.Īnd actually then thinking about the way it's calling it, i'm wondering if this is actually from some C++ standard library code for doing stuff with a vtable, looking up the vtable entry and checking it's validity before calling it (in this case, location 0x18, and checking some kind of RTTI at 0x28 and 0x2b) and storing that it's been initialized in 0x21. From my memory, the windows ABI uses the first two bytes of functions for installing hooks/debugging by patching the first two bytes into some kind of jump (while originally being nops). This particular one looks like it's taking a function pointer in and checking if it's a valid function (not null) and then checking the first two bytes of the function. The sibling comment covers it a bit more in detail, but it's largely just some guessing and as much an art to figuring out what the types are or could be. ![]() (disclosure: per the child post, my original assumption that OpenRCT2 was copied out of Hex-Rays was inaccurate, since it was originally written in assembler it didn't follow a standard C ABI and the decompiler wouldn't work properly anyway). For example, OpenRCT2 started as a repository full of manually created source with Hex-Rays names and slowly evolved module-by-module into readable source code. Highly manual process, for some files it's just pattern matching / renaming and goes really quickly, for others it's full reimplementation and a bit harder.Īnd, if you look at most "decompiled game" projects, I think this is the industry standard way to do this. When I've done this in the past, it basically consists of:ġ) Decompile project using Ghidra/IDA, first pass.Ģ) Load symbols if present (sounds like there was a PDB for this one, which makes things a lot easier).ģ) Read decompilation/asm for unnamed subs and try to name them based on what they do.Ĥ) Export all decompiled source into an editor and start copy/paste/editing into readable source. I'm not aware of any good general-case automation for this.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |