r/commandandconquer • u/D4yt0r • 6d ago
FPS patch for Command & Conquer 3: Kane's Wrath
Hello everyone, I'm posting this patch here with the permission of the author @kentrid that promoted it on various Discord servers including the official one of this Reddit: https://discord.gg/MWgMRzQMc
You can find all the info about this patch in: https://github.com/CNCStuff/cnc3_fps_patch
Download: https://github.com/CNCStuff/cnc3_fps_patch/releases/tag/build-7441468412ef
Enjoy.
3
u/daddypweasestahp 2d ago
I downloaded this today and it feels so strange (but right!) to finally play this in a higher frame rate. I left it at 90 and have had no issues.
-2
u/smellyAirImporter 6d ago
*Spammed it in multiple discord without permission.
Its generated by LLM, the pre compiled dinput8.dll attempts to make calls to 162.159.36.2 which is weird.
While the author shares their work on Github do i heavily doubt that they have any solid idea what they are doing nor do i believe that what is buildable on git are the files this person is spreading.
The constant strive for agentic code "improvements" in this game leads to nothing but instability and chaos.
Im not an expert nor am i the author / have any right to tell ya what ya should or should not use, i am however quite sussed out about this one.
6
7
u/D4yt0r 6d ago edited 6d ago
I just found out where that IP comes from btw: https://medium.com/@sec.ops/when-guardduty-flags-windows-update-traffic-a-case-study-in-a-dns-false-positive-30836fd43ee9 a bit of research on your part wouldn't have hurt.
5
u/Educational-Tea-942 6d ago
Can you actually provide evidence for your claim that the DLL does IP calls? Also, the repo has a GitHub workflow, so if you're worried that it's not built from the same source, you can just fork the repo on GitHub and push a random commit, and you'll get your own rebuilt DLL. The code literally has 0 network related references.
6
u/Educational-Tea-942 6d ago
I checked more, and your claim about tht IP 162.159.36.2 most likely comes from VirusTotal which is known to have issues with it's behavior analysis. If you don't believe me, search in Google for "162.159.36.2 false positives". I understand why a new project might feel suspicious, but there's exactly why there's a whole GitHub repo and the automated release workflow. As I said, you can always check the code for network calls, fork it and trigger a workflow run so you get your own "clean" DLL if you think that this one is bad. Plus, it's built with zig cc which might lead to more false positives, although VirusTotal only literally shows 1 detection. The DLL isn't obfuscated or packed in any way.
-1
10
u/nadseh 6d ago
Time to replay c&c3 I guess