DMA Setup and Firmware Guidance for EAC

Hey everyone,

I'm pretty new to the world of DMAs and just got started with a bundle that includes a Captain T75, a fuser, and a KM. Right now, my focus is on using ESP for Rust (EAC), so I don’t really need the KM at this point. And yes, I’m aware there isn’t much performance difference between the 35T and 75T models, but I got a great deal, so I went for it.

Now, my main challenge is figuring out the firmware (FW). The DMA I purchased came from a Chinese provider who claims the card includes supported FW for PUBG, but honestly, I’m skeptical about its reliability. From what I’ve seen, most other FW providers seem ridiculously overpriced.

After some digging, I learned that creating regular FW yourself isn’t too complicated, so I planned to go that route initially. However, I’ve come across posts saying that EAC can detect regular FW pretty easily. It seems like what I actually need is emulated FW with features like passing DRVSCAN, dynamic responses, and other advanced safeguards. That sounds like a whole new level of complexity.

I’ve got some coding skills, but I’m a complete beginner when it comes to FW development and emulation. On top of that, I haven’t been able to find much reliable information about FW emulation or a reasonably priced provider that offers truly 1:1 emulated FW.

So, I have a few questions:
1. How significant is the difference between using regular FW I create myself and a more complex emulated FW in terms of detection risk?
2. How realistic is it for someone with basic coding experience to create their own emulated FW that meets these advanced requirements?

Cheers,

Gates

for simplicity reasons I would just buy 1:1 fw from someone trusted, I don't think its worth trying to make it yourself if you don't have any experience :mofo:

Quote:

Originally Posted by gatesscripts Hey everyone, I'm pretty new to the world of DMAs and just got started with a bundle that includes a Captain T75, a fuser, and a KM. Right now, my focus is on using ESP for Rust (EAC), so I don’t really need the KM at this point. And yes, I’m aware there isn’t much performance difference between the 35T and 75T models, but I got a great deal, so I went for it. Now, my main challenge is figuring out the firmware (FW). The DMA I purchased came from a Chinese provider who claims the card includes supported FW for PUBG, but honestly, I’m skeptical about its reliability. From what I’ve seen, most other FW providers seem ridiculously overpriced. After some digging, I learned that creating regular FW yourself isn’t too complicated, so I planned to go that route initially. However, I’ve come across posts saying that EAC can detect regular FW pretty easily. It seems like what I actually need is emulated FW with features like passing DRVSCAN, dynamic responses, and other advanced safeguards. That sounds like a whole new level of complexity. I’ve got some coding skills, but I’m a complete beginner when it comes to FW development and emulation. On top of that, I haven’t been able to find much reliable information about FW emulation or a reasonably priced provider that offers truly 1:1 emulated FW. So, I have a few questions: 1. How significant is the difference between using regular FW I create myself and a more complex emulated FW in terms of detection risk? 2. How realistic is it for someone with basic coding experience to create their own emulated FW that meets these advanced requirements? Cheers, Gates

1. It depends what you mean with regular FW? EAC became stronger, even in Rust, but if you have good idea about the firmware you can make it's much better. But yea, you would need full emulation to make sure you are safe.

2. If you have coding experience it is definetly realistic.

Quote:

Originally Posted by A.taxia 1. It depends what you mean with regular FW? EAC became stronger, even in Rust, but if you have good idea about the firmware you can make it's much better. But yea, you would need full emulation to make sure you are safe. 2. If you have coding experience it is definetly realistic.

You don’t need coding experience for firmware, you’re not writing code. Your copy pasting IDs when you dump them into a file. Only think that helps is knowledge with RE tools to reverse a driver.

Quote:

Originally Posted by Relentless You don’t need coding experience for firmware, you’re not writing code. Your copy pasting IDs when you dump them into a file. Only think that helps is knowledge with RE tools to reverse a driver.

Ofc you are not writing code. What I say about coding experience is just about the skills that can only help you.