Anyone can tell me if makcu is safe to use in CoD/WZ? I m currently try to write my own firmware and recently bought a makcu since hv is down to switch to dma. So now I’m confused…what setup should I use since makcu was recommended before.
It is what i use since i got mine a year ago, have also heard about this but i am pretty sure it is what most people use, i could get the ferrum one just to try but i keep on playing every day with the Macku, no issues.
Anyone can tell me if makcu is safe to use in CoD/WZ? I m currently try to write my own firmware and recently bought a makcu since hv is down to switch to dma. So now I’m confused…what setup should I use since makcu was recommended before.
I doubt anyone would speak badly of Blurred, how can't they do it with Evo!I've been using Blurred since day one of their code and the progress has been immense.
regarding makcu and ferrum:
Quote:
According to information from the creator of MAKCU, **Ferrum is no longer a safe device**.
Based on the information he provided, the **Ferrum administration acted negligently and ignored detection methods**, thereby exacerbating the situation,** which resulted in numerous bans.**
We kindly ask that you refrain from using it for the time being or** switch back to MAKCU**.
All listings for Ferrum on our marketplace have been froze, it is **no longer possible to purchase them**.
and after:
Quote:
**Ferrum situation — short update**
I spoke directly with both **ihack** and **GameGuy** after the original post.
At this point, both sides actually agree on the most important part:
**ihack's position:** low software output rate / incorrect movement timing can create a detection vector, especially when the software output does not match the polling rate the user expects from the device.
**GameGuy's position:** he agrees that this detection vector is real and that the problem is broader than Ferrum alone. He also agrees that Mouse Interpolation should have been implemented earlier. Ferrum has now added interpolation intended to address this mismatch.
Where they still disagree is mainly **how complete the current fix is**.
ihack believes the current solution may still be more of a workaround and that the deeper **XY+DT** behavior may remain identifiable. His opinion is that a better long-term solution may require a different/newer hardware architecture and possibly lower-level implementation.
GameGuy believes the current Ferrum hardware + interpolation is sufficient and says Ferrum can correctly support 2K/4K/8K.
**Important:** GameGuy did provide raw **1K** captures. However, the broader claims around **8K**, XY+DT behavior and Ferrum being the safest option have not been independently demonstrated to me with equivalent raw data yet.
GameGuy is currently away and said he may collect additional 8K data later. I don't know exactly when that will happen, and people have already been waiting for an update, so I'm posting the current state of the situation now rather than leaving everyone waiting indefinitely.
If additional raw data is provided later, especially the discussed **8K captures**, I will make another update.
Also, ihack and GameGuy have now spoken directly and appear to have resolved their personal conflict, so this should no longer be treated as a personal fight between them.
**TL;DR:** the original technical concern was real and both sides acknowledge that. Ferrum has implemented a fix. What remains disputed is whether the current fix completely solves the deeper detection problem, especially at 2K/4K/8K and at the XY+DT level.
I doubt anyone would speak badly of Blurred, how can't they do it with Evo!I've been using Blurred since day one of their code and the progress has been immense.
regarding makcu and ferrum:
and after:
Quote:
Recent Misinformation
Recently, we've been under a personally driven attack, where misinformation has been used to question our product's safety.
Where is the Misinformation from?
The person behind this is the developer of Makcu, iHack. Makcu is a product that I have personally supported on numerous occasions, from fixing mouse compatibility via adding a dynamic Max Packet Length to Makcu V2, to explaining and fixing the G Pro Superlight running at 100Hz with Full-Speed. For Makcu V3, I even implemented the first bidirectional passthrough. In fact, I'm listed as the top listed contributor to Makcu in iHack's own server.
Despite the support we've given, iHack has told me that he believes Ferrum is responsible for the "entire community [hating on] Makcu," and that for that reason, he deserves revenge against us, to "ruin Ferrum's reputation" in the name of "karma." As ridiculous as this sounds, it seems to be the basis of this attack.
What is True, and what isn't
It's still worthwhile to address the claims claims directly, as there is some validity, as well as extreme misrepresentation.
iHack's claim revolves around the fact that in the Optimized CPU Mode with older versions of Ferrum, when software output >=1000hz, and the user wasn't moving their mouse, 950Hz would be output. He claims this is the reason for a series of bans, and that Ferrum has "scammed" its customers by having such behavior while claiming 8K support. The problem with this claim is that it requires all software to be outputting at 1000hz, when in reality the vast majority outputs at 200~300hz, and no software outputs above 1000Hz. When outputting at 200~300hz, this no longer becomes a Ferrum-specific issue, and instead becomes and issue with the entire hardware market, including Makcu.
Overall, this universal issue is being misrepresented as a Ferrum-specific issue, which we fixed prior to the tirade of misinformation.
5 days ago, we discovered a way to implement Mouse Interpolation safely and universally to Ferrum. Initially it was going to come out with the Driver Update, but after a couple of days, and seeing the recent increase in behavioral detections, further reported by Moon, we decided to release it immediately.
Despite us fixing the issue, iHack, instead of fixing it in his own firmware, decided to attempt to spread the word that Ferrum had this behavior previously, trying to declare us a "scam," even going so far as to claim that our hardware was outright detected.
Makcu itself is Detected
Ironically, Makcu itself is outright universally detectable on a passthrough level, and despite us raising these issues with iHack in the past, nothing has been fixed yet.
Unfortunately, iHack has since dropped support for the Makcu firmware, having not released a beta version in 10 months, and a release version in over a year. We do not want to harm any users, which is why we haven't gone public with any of this information up until now, with the hope that it would be fixed in MAKXD, and ideally fixed in Makcu retroactively.
Attached below is a video showing a critical detection vector of Makcu, in which its passthrough allows the main PC to instantly detect a connected Makcu, even without any software input. We will not be providing any more information publicly on this, as we do not want anti cheats to catch wind and detect every makcu user. Unfortunately this is just one of many detections that Makcu suffers from, such as passthrough timing issues, and various other vectors that are equally easy to for kernel mode anti cheats to use. We hope that both the new MAKXD includes fixes for these problems, as well as the original Makcu firmware.
This video was recorded on a Linux machine, as Linux apps have more USB control than Windows Apps, however Windows Kernel Mode anti cheats can do significantly more than what is demonstrated.
In the past, when users have asked what the difference is between Ferrum and other devices, this is one of the key things that we have purposefully not stated publicly. Trying to avoid conflict, we have historically broadly stated that our firmware has security and safety improvements, without making direct comparisons. However, low level USB detections like these have been have been thoroughly analyzed and optimized/solved on Ferrum, which comes alongside the other major benefits of our fully custom USB Drivers.
Why Ferrum is the Safest Option
Getting back to the topic of input and output rates, some testing has been performed on the latest version of the firmware. Attached below is some data comparing the latest version to both prior versions and the latest Makcu release, showcasing how software outputting at typical output rates (200~300Hz) is blatantly inhuman, until using the latest version of Ferrum, which includes Mouse Interpolation. Furthermore, users which previously would encounter behavioral temp bans on both Ferrum and Makcu when using rage configs are now no longer experiencing them on the latest version of Ferrum. It will take some time to notice the full effects, as some users may be flagged or in a wave already, but this update is a major step forwards.
We've also been monitoring new technology closely, such as machine learning based aim models, and implementing new APIs that give full frame-perfect reception and control over the entire 8k input stream.
We are committed to providing the best possible user and developer experience, and to remaining the safest Aim Device on the market. If you have any questions, feel free to reach out to us either via tickets, or to myself directly via DMs.
Further third party testing and validation is underway. Unfortunately they were not complete at the time of this post, as this post had to be made quickly to reduce the damage caused by the aforementioned misrepresented statements.
Summary
So no, Ferrum itself wasn't directly detected, but the behavioral checks of anti cheats are getting more advanced, leading to more universal aim detections, which leads to bans for users of Ferrum, Makcu, and all aim devices. We need to keep working as a community to stay ahead. This means new advancements from us hardware developers, and matching implementations by the software developers. Most of all, we can't fight each other. We're all on the same side here, and the best way to push forwards is to build up together, rather than making large public spectacles tearing each other down.
We didn't want to have to make this post, and we hate to hit back against other developers in the community, but there aren't many other options when the safety of our device is being extremely misrepresented.
^^^ from ferrum, not a third party dev, direct, who has nothing to do with either project. Moreover, ihack made it clear in Direct's discord that Makcu is only "good" because it's open source, and you're better off using ChatGPT to make your own fw than use public ones.
^^^ from ferrum, not a third party dev, direct, who has nothing to do with either project. Moreover, ihack made it clear in Direct's discord that Makcu is only "good" because it's open source, and you're better off using ChatGPT to make your own fw than use public ones.
At least tell people what you're pasting.
Can you share Ferrum´s discord official pls, looking for a safe place to get it, just in case, i´m in no ruch of switching right away but i´d rather have it at hand and the other iHack guy, i don´t think he will be releasing anything else, loser
[Selling] Razzosx Makcu Color | ⭐ Perfect Tracking | 🔗 1 PC SAFE | 📗 WEB BASED 10/16/2025 - Valorant Trading - 0 Replies 📘 | INFORMATION
- Windows 10 & 11 (All Winver)
- 1 PC & 2 PC Soon
- AMD & Intel Processors
- HVCI Enable / Disable
🖱️ | SUPPORTED HARDWARE
- Makcu
🎯 | AIMBOT
[Selling] SAFE TARDEING ! SAFE SAFE SAFE 11/15/2015 - League of Legends Trading - 0 Replies Ich verkaufe mein LOL ACC/ I sell my LOL acc
-Eu N&E 0 rp to change server !
- Gold 3
- 100 Champs
- Skins 12 !
- Last season Diamond 4 !
Makcu safe?
