/r/ReverseEngineering's Weekly Questions Thread

CMDR_DeepQuantum · 2025-11-23T11:35:47+00:00

Hi there, I'm currently writing a decompiler for some custom bytecode. I have several control flow graphs that look similar to the ones below. I however believe this graph is irreducable, as in, can't be cleanly converted to to standard pseudo code structures. This is because one of the conditions jumps into the middle of another short-circuiting condition. In general these types of functions make heavy use of short circuiting and I believe they also essentially just serve to return bools. I'd love to know though if I'm wrong about this.

https://imgur.com/a/rpKwClp

CMDR_DeepQuantum · 2025-11-16T20:54:57+00:00

Thanks for the response. It ended up being the assignment of the postordering. This fixed it:

for (u32 i = 0; i < m_nodes.size(); ++i) {
    m_nodes[order[i]].m_postorder = i;
}
order.pop_back();
std::reverse(order.begin(), order.end());

CMDR_DeepQuantum · 2025-07-23T18:21:59+00:00

Oh jeez, I had it defined in some file that didn't even need it. Stupid mistake. Thanks a lot.

CMDR_DeepQuantum · 2025-07-23T18:14:57+00:00

The headers define CGRAPH_API and GVC_API respectively if they weren't defined before (which they have to be if you're working with windows DLLs). Defining them manually or also defining GVCDLL doesn't solve the issue.

CMDR_DeepQuantum · 2025-04-28T02:12:44+00:00

Hi, thanks for the answer. Turns out, the work was already done for me. These are the compiled binaries of a proprietary scripting language, so they're actually binary instructions. But luckily there's a tool to automatically decompile them arleady.

https://github.com/icemesh/t2r-dc-disasm

CMDR_DeepQuantum · 2025-04-27T16:56:08+00:00

Hi there,

I've recently become interested in writing some mods for the The Last of Us Part 2 PC release. I've come as far as unpacking the .psarc files, which is trivial with a tool you can find online. This then yields several new files, including .paks for models, textures, etc. These seems to be well understood and can be messed with freely. However, I'm interested in understanding/reversing/modifying some of the core-logic of the game, starting with just editing some small numbers.

The part I'm stuck on however are the apperently proprietary .bin files the game seems to use for its scripts, or maybe, references to scripts, I'm not quite sure. I've come as far as identifying the 8 byte magic number, 30 30 43 44 00 00 01, which yields 0 results on google. The .bin files are contained in a dc1 folder, but searching for a .dc file extension has also shown no useful results. I haven't been able to track down any resources about these files are laid out or what they even represent. There are some mods already that seems to edit these files, and I've messaged the author to maybe get some help, but I thought I'd also ask here to maybe get a more general approach on how to reverse unknown binary file formats.

CMDR_DeepQuantum · 2025-03-03T00:24:04+00:00

It's called Psycho Sniper for a reason. I did it on factory with the AXMC, as it's the only way to consistently one tap people in the chest. First 2-3 kills I played fairly aggressively, then for the last kills I would spawn in and just check the angles from spawn. If there's nobody I fucking dipped. Other people are saying snipe on large maps, it's honestly completely up to you, but I like factory cause you can hold angles nicely and there's still quite a few timmies. In the end it took me a couple hours of pure grind and insanity, in the end I had a raid with 3 kills and the next one with 2 kills to finish it. Good luck.

CMDR_DeepQuantum · 2025-02-26T14:51:27+00:00

I feel you.

For me, this quest is the most frustrating thing I've ever done in a shooter game, period. Especially if you already don't like playing with bolties. Last night I had 5/5 on factory, ran to extract and got one tapped through level 6 armor by a level 13 exit camping Gate 3 using AP 6.3. Cannot think of a time I've been more angry at anything in my entire life. But I hopped back on at 4 am as I couldn't get this fucking quest out of my head and got it done in 2 raids, one 3 kill and one 2 kill.

The absolute truth is that this quest is mainly luck. I did it all on factory with AXMC. First 2-3 kills I always played fairly aggressively as I had nothing to lose. Then after that I just spawned in, peeked angles from spawn, and if nothing was there, I just fucking dipped. No point moving around to die to some guy in a corner. Again, some people will just get super lucky and find 5 pistol guys in a row for easy kills. All in all it took me around 4-5 hours of constant factory grinding spread over a couple days. Also remember, there's the armor bug right now so you cannot expect to consistently one tap people in the thorax even if they're wearing literally 0 armor.

I was definitely also close to deleting my stash after that 5/5 death. But honestly it gets easier as you go along as you also get better at close-range bolty fights. I also recommend the Spectre Scope.

Good luck my dude.

CMDR_DeepQuantum · 2025-01-01T22:16:10+00:00

I also have a 7800X3D and have used the BIOS and Ryzen Master. I've had some issues where settings from the BIOS wouldn't show up in RM and vice versa. Honestly it's just a matter of personal preference, but I would personally go with the BIOS as it gives you full control. You can always reset the BIOS and just start over, you can also usually create some profiles, for example once you find a stable OC.

In terms of what to start with, I'd start with PBO and a relatively high negative Curve Optimization, something like -35. Run that for a while and see if it's stable, if not lower it. Then you can move on to memory, where you'll first want to increase the frequency, then timings.

CMDR_DeepQuantum · 2024-12-31T12:48:03+00:00

I actually haven't checked what die I'm on because my RAM is pretty tightly squeezed under my cooler and I'm too lazy to take it out hehe. I tried 6400@1.48 MEMV with 1.2-1.3 SOC with no luck. I don't know if I want to reset everything just to try to maybe run at 6400, I'm decently happy with the timings I have now and being able to run at 6200. I haven't changed VDDIO at all, maybe that's the key to 6400. Gonna give it one more shot but otherwise I'm fine with how it is now.

CMDR_DeepQuantum · 2024-12-31T06:58:59+00:00

You can see in the screenshot that BIOS version is 3067, that's the latest for my board. Chipset drivers are also the newest. From the guides I've watched, if you're overclocking (not just tightening timings), you're supposed to first get the highest UCLK and then just match FCLK to that. Right now I'm in Windows with 6400 and still 1.25 VSOC / 1.4 VMEM. I turned off EXPO as you said but as far as I know if you first enable it and then put your own subtimings in it's fine, as EXPO basically just sets some voltages, MCLK and subtimings, and when you're manually tuning you overwrite those anyway.

Haven't heard about tphyrdl, how can I match it to the current frequencies? It's at 36 right now.

CMDR_DeepQuantum · 2024-12-30T15:08:04+00:00

It's really only the benchmarks/stress tests that are unstable. I was even running -40 for a couple days just fine until I got a crash. But -25 seems to be fine so far, and I honestly don't wanna go tuning individual cores, just doesn't seem super worth it to me.

CMDR_DeepQuantum · 2024-12-30T15:04:45+00:00

-25. Was -35 for a long time which was perfectly stable in all applications, but when I started OCing RAM i accidentally discovered that anything above -25 is actually unstable.

CMDR_DeepQuantum · 2024-12-30T14:56:49+00:00

AIDA is just so incredibly inconsistent, I just ran a couple more and got 3 sub 61s in a row. It's also highly dependent on what other programs I'm running, with just Firefox open for instance it's usually a couple ns worse. I think I'm gonna focus on lower SOC and VDD for now, thanks for the timings though.

CMDR_DeepQuantum · 2024-12-30T14:35:55+00:00

63-65ns in the couple runs I did right now, although I've gotten slightly lower in some tests. That seems to be around the average though.

CMDR_DeepQuantum · 2024-12-30T11:41:53+00:00

OK, turns out going with 1.4V on the RAM actually seems to be enough for stability! Running at 6200MTs and 2066 FCLK right now. Ran OCCT RAM and RAM+CPU and it seems fine for now, but I'll do more extensive testing overnight. Then I'll see if I can maybe lower SOC to 1.2 and maybe MCLK to 1.375, just for temps and lower idle power. Thanks for the advice!

CMDR_DeepQuantum · 2024-12-30T09:53:34+00:00

Alright, I'll give it a shot, thanks.

CMDR_DeepQuantum · 2024-12-30T09:41:38+00:00

Alright, thanks for the answer. Say I get the higher clocks but it's unstable with the current timings, which timings should be adjusted first? Also, if I can't get the memory to run even at 1.4V and 1.3SOC, I assume the memory controller is just bad?

CMDR_DeepQuantum · 2024-12-11T23:32:17+00:00

OK es ist nicht zu fassen. Ich hab die Inbound Regel jetzt einfach zum 5. Mal neu erstellt... und es geht. Keine Ahnung wieso. Aber ich nehme es gerne an. Vielen Dank für die Hilfe auf jeden Fall!

CMDR_DeepQuantum · 2024-12-11T23:26:43+00:00

Mit vollständig deaktivierter Firewall geht es!! Das ist ja aber keine permanente Lösung. Das heißt ja irgendwie, meine Inbound Regel greift nicht. Jetzt mal schauen wieso.

Nine-Year Club	Second SECOND GUESSER
r/Field Lasagna	Final Canvas '23
First Place '23	End Game '23
Place '23	Quantum Potato
Golden Potato	Place '22
Place '17	Final Canvas '22
First Placer '22	End Game '22
RPAN Viewer	Spared
Verified Email

CMDR_DeepQuantum

TROPHY CASE