- This topic has 81 replies, 26 voices, and was last updated 3 weeks ago by
.
-
Posts
-
@secretnetguy, So AI can be used to hack/crack software? That's brilliant! I'd love to have the new ACDSee image browser cracked so that it doesn't require a net connection.
Yeah, I don't support these scummy practices. Especially since this seems to be a very hypocritical "fine for me, but not for you" thing since the dude is on Zonegfx.
Looks like the thing they gave me was not v1.3 (provide me with it if you want me to nuke that as well). I've removed the integrity checks on the open beta one.
Patched exe: https://www.mediafire.com/file/61i92wbzd9dhmx7/render-accelerator-studio.7z/file
I patched out their integrity checks, set the expiration date to 2100 and removed the licensing screen completely. MAKE SURE YOU DON'T HAVE EXTRA FILES IN the app folder because I didn't bother with those checks or removing the anti-debugging shit.
This is of little value to me since I have dual 5090s and I rarely use my 4090 rig other than setting up work for the render queue of DAZ 6, but it was nice to spread the wings of my harness stuff.
EDIT: I've neutered its "call home" abilities, but I didn't patch out the connection requirement. I'll do that when I wake up so you can fully firewall it.
Yeah, this version won’t work, because he’s not nearly as clever as he thinks he is. License checks can obviously be bypassed, and the expiration date can be pushed forward. Anyone with even a basic understanding of software can do that. It definitely isn't something that takes 37 hours of work 🙂
This “supposedly cracked version” isn't actually cracked. A significant portion of the code responsible for making the program render, along with the computation model itself, is entirely server-side. Once a render actually starts, the program will throw an error because it doesn't have a valid license and therefore won't be able to access or execute that code.
He can try whatever AI tools or methods he wants. As long as that code remains on the server, he won't be able to crack the program, and he won't be able to access that code either.
Like I said, he can keep trying to crack the program as much as he wants. He can disable every license check and every internet connection he can find. He can modify whatever he wants, but the program still won’t work.
I was actually considering releasing an official free version soon for everyone here who wanted to use the program without paying. But after seeing that there are people here who are this hostile toward me, I've decided not to do that anymore.
Sorry about that. On it, I've terminated the online requirements (can be firewalled), there are 6 remaining checks I missed. Will update once it's up.
Oh boy I've got just the right episode for scum devs like you.
Oh boy I've got just the right episode for scum devs like you.
My intention isn’t to be hostile toward anyone here. I released my previous paid software as a pirated version on this site myself. You’re the ones choosing to turn this into a hostile situation. I made the program available to everyone for 7 days so that anyone could try it. If I wanted to, I could have simply released the paid version from the start. I was also considering releasing an unlimited free version, but I'm not going to do that anymore
This program isn’t built in a way where you can simply bypass a few license checks and call it cracked. Anyone can do that
You can try doing whatever you want to the program, but as I explained above, as long as the core architecture and model responsible for the render acceleration remain on the server, none of that will actually help. The moment you try to start a render, it will fail with an error
@Spache, I still find it laughable that you weep about not getting residuals from your product, yet you've been a member here for quite some time. Imagine if fillers started charging you for all the assets you've accumulated from us, especially from me. People like you are why I don't enjoy filling requests anymore.
"I thought about releasing a free version."
No, you did not. Ever. This is always online. This so tightly coupled with always online, with the DRM checks that you couldn't in a million years offer it for free in a privacy-friendly way. You could just offer a perpetual always online license. "But it's just width, height and yadda yadda", bro, the Tor browser messes the window size because it can compound with 2-3 other things to be uniquely identifying.
Alright, progress update.
It has fallen. Mostly. Baby's first attempt at Denuvo sans virtualization. Dude thought asymmetric crypto is slick. Your private key isn't worth shit when the code running on my machine decides your reality.
Many thanks for all these errors, basically I just patch them and the next one tells me where to find the next DRM check slop.This might be the biggest piece of AI slop I've ever worked on. It has Rust, it has Python, it has JavaScript, it has WebView (because LLMs can't do anything but web + security through obscuriy as it's decompressed online), IPC balls to the wall. It reads exactly how a headless agentic LLM would "reason" about software. It has enough DRM checks to smother a small rhino. The entire frontend is just DRM for other people's hard work.
I moved onto the Assassin's Creed 2 crack approach of spoofing the server itself (127.0.0.1 api.renderacceleratorstudio.com, my mock server responding to his asinine requests, ceiling, lease fabrication etc), this dude is sending your fingerprint data to the server (always online) regarding the scene and then computing the plan for rendering there and sending in back, so the whole JavaScript WebView Rust frontend is just a DRM charade.
This dude says he spent a year working on this. Yeah, working on the DRM. It's everywhere, once i beat /ceiling and other shit, I realized this dude slapped integrity checks into the fucking IPC stuff, had to patch Gate1Interceptor Gate1WhatNot and any time a file HIS APP doesn't properly clear, like current_session.txt, it refuses to start lmao. RAS.exe checks all the integrity of all the Gate1Shit, and vice versa, it's ridiculous, I've lost count of how many checks I've removed.
Anyways, I patched 99% of it, now am mostly dealing with him not testing this on system which have a 4090 and 5090 in tandem, so sometimes renders work, sometimes they don't. Also realized this shit pulls rendering device info from Daz's fucking log, and it won't work with Daz 4.24 Public Build because it's hardcoded for the log file of regular Daz 4.24.
I HAD TO REVERSE ENGINEER THE PLAN BITS HE COMPUTES ONLINE BY ERRORING OUT AND HIS OWN GUARDS TELLING ME THE ACCEPTABLE VALUES LMAO. And the ceiling fingerprint, lmao curr_w / curr_h. Bro. HAHAHAH.
I would not support this sham. In fact, I am considering making my own frontend and just publishing that for free and DRM free. Without all of the DRM-infested Rust + JavaScript WebView shit. The only valuable code is what he gatekeeps online (knobs for the actual quality software to ingest, hiding behind his DRM slop), which I solidly reversed and the community can finetune with knobs. I will apply all of this to one of his later releases once someone provides me with a dump, so he can't ask his his vibe coding LLM to hallucinate more checks.
Never in my life have I seen DRM this tightly coupled, this is 100% vibe coded. Or he is on steroid-infused autism. More thought went into DRM than anything else here, and I doubt even that was his original work.
Damn dude nice work. I knew it was a vibe coded app. You can feel the seething from this dev even mentioning AI and trying to win sympathy in his discord, "oh I gave it a free trial, I could have made it not public, see how generous I'm"
The trial was for fixing your stupid AI bugs, you needed testers because you have no idea what you actually "coded".
And then whole I worked for a year bullshit must be running out his monthly tokens.
What exactly does using Rust + Python + JavaScript + WebView have to do with something being “AI slop”? Every one of those technologies was chosen for a reason, and they work together as parts of the same system. Almost nobody writes software today without using AI somewhere in the process, but that does not magically make the result “AI slop.”
This application is not something you can dismiss with “lol, vibe coded” and pretend you’ve understood the architecture. Some things being pulled directly from the Daz log are intentional design decisions, not accidental leftovers.
You can reverse engineer the client for as long as you want. Patch every integrity check. Modify every request. Spoof every endpoint. Remove every license check. Replace the server with localhost. Build your own frontend from scratch if you feel like it.
None of that gives you the actual render-acceleration model, because that model is not inside the application you are reverse engineering. It runs on the server.
Eventually, you may be able to force the client to start a render. You may even be able to complete renders by feeding it values you guessed, fabricated, or reconstructed from observable client-side behavior. That still does not mean you have reproduced the acceleration system.
Without the server-side model generating the actual render plan, what you are essentially doing is making Daz render normally using parameters you invented yourself.
That is also why saying you have “patched 99% of it” means absolutely nothing. You cannot measure yourself as having reverse engineered “99%” of a system when the component responsible for the core computation is not even present in the binary you are analyzing.
The funniest part is that your own post confirms exactly what I have been saying from the beginning.
Bypassing client-side license checks was never the difficult part. Of course you can patch those. Anyone with some reverse-engineering experience can do that. The reason you ended up creating a mock server and trying to infer server responses is precisely because the client does not contain what you actually need.
And you are doing all of this against V1.1, an old beta build.
Reverse engineer V1.1 all you want. Patch every “Gate1Shit” you can find. Spend another 37 hours chasing checks around the client if that entertains you. The server-side model is not something you can extract from the executable, because it simply is not there.
That is the point I have been trying to explain from the beginning.
Cracking the client does not give you the thing that actually provides the render acceleration. The actual brain of the system is server-side.
So far, none of what you have done changes that.
Keep going.
I was already planning to release a completely free version of this application anyway. Believe that or don’t, I genuinely don’t care. I’m not hostile toward this community. I already said that I personally provided the pirated version of my previous application to this site myself. There’s even an old DM conversation I had with PeepShow45 about it. He may not remember it, but that conversation exists.
That makes spending days trying to crack an old V1.1 beta build even more pointless. V1.1 is an outdated beta with bugs that have already been fixed, and it doesn’t even include many of the features added in later versions. Spending days dissecting someone else’s application, patching every check one by one, chasing error messages, and building mock servers just looks obsessive and pathetic to me. All that time and effort could’ve gone into actually building something of your own instead of obsessively tearing apart someone else’s work. You can keep reverse engineering that old beta for as long as you want. It still won’t give you the server-side model that actually provides the render acceleration.
So after all that work, you’ll have spent days breaking an obsolete beta of something I was already going to release for free and you still won’t end up with the actual original application that works properly and provides the real render acceleration.
A little bit off topic, but i think it's the right moment.
@Spache
You wrote: "I’m not hostile toward this community. I already said that I personally provided the pirated version of my previous application to this site myself."Maybe, but there is one group, you are hostile to: Your own customers.
Even after the release of you Image to G8/G9 tool, i purchased it to support you and your efforts.
In return i still waiting to get the V2, because the download link on Discord was deactivated because the tool has been shared on piracy sites.
It's a bit off, people on sharing sites already have the V2, while your own fellow customers are locked out of it, right?My customers purchased V1.2, not V2. Even so, I said that I would upgrade everyone who bought it to V2 for free, and I did.
However, when you sell a product on the Daz Store, you sign an agreement stating that you cannot publish or sell the same product on any other website. Because of that, I temporarily stopped distributing V2 until it is officially released on Daz’s own store. A product that hasn’t even officially gone on sale yet ending up on piracy sites could seriously hurt its launch. In the meantime, customers still continued to have access to V1.2, which is the version they originally purchased.
I could have sold V2 to everyone separately as “Image to Pose 2,” but I chose not to. I even mentioned this on my Discord server recently. I said that once V2 is released on the Daz Store, probably next week, all of my existing customers will receive free access to V3.
- You must be logged in to reply to this topic.
