Some odd news have reached my knowledge, about Datel's Action Replay, keep reading...


Some of you might have noticed one of the newest stuff released by Datel, the "Action Replay" that allows you (on the PSP we'r talking about of course, i already know there is also a version for the Amiga for it, and of course this post isn't about that revision) to cheat and to use some "powersaves" within it's 64mb memory between other stuff, and all this for ~40USD.

So, why would i or anyone care about this new release from Datel? Well, the point comes when you look onto how was it made.

The following information it's confirmed and it has been studied, so let's hope this clears some doubts on this.

* Datel' Action Replay does uses code that isn't from itself, code that isn't distributed to be used the way they use it anyway. The code involving this terms is, for first instance, the Pandora forged IPL block, and on second place but of course not less important, Booster's IPL SDK.

Also,

* It has been confirmed that Datel' Action replay does interfere on the Custom Firmware code

And also, less important but indeed interesting,

* They use a bigger memory footprint due to the graphics involved in it, and it's interesting also to mention that they had a pretty small database, that being compared it to cwcheat one, this first one isn't even a database tbh.

So, what's your choice? A stealing-code small device, or a Fresh homebrew development with a huge happy users history?

Thanks to VoidPointer and Dark_AleX himself for the tip and confirming this

Some odd news have reached my knowledge, about Datel's Action Replay, keep reading...


Some of you might have noticed one of the newest stuff released by Datel, the "Action Replay" that allows you (on the PSP we'r talking about of course, i already know there is also a version for the Amiga for it, and of course this post isn't about that revision) to cheat and to use some "powersaves" within it's 64mb memory between other stuff, and all this for ~40USD.

So, why would i or anyone care about this new release from Datel? Well, the point comes when you look onto how was it made.

The following information it's confirmed and it has been studied, so let's hope this clears some doubts on this.

* Datel' Action Replay does uses code that isn't from itself, code that isn't distributed to be used the way they use it anyway. The code involving this terms is, for first instance, the Pandora forged IPL block, and on second place but of course not less important, Booster's IPL SDK.

Also,

* It has been confirmed that Datel' Action replay does interfere on the Custom Firmware code

And also, less important but indeed interesting,

* They use a bigger memory footprint due to the graphics involved in it, and it's interesting also to mention that they had a pretty small database, that being compared it to cwcheat one, this first one isn't even a database tbh.

So, what's your choice? A stealing-code small device, or a Fresh homebrew development with a huge happy users history?

Thanks to VoidPointer and Dark_AleX himself for the tip and confirming this

Well, I'm not the only dev working on this and this update concerns me and two other devs.

1. My progress
I looked into the cache last night and found that the instruction list for the dynarec was being invalidated when it wasn't necessary. This eats up a small chunk of CPU cycles. So a bit more speed from better cache handling there. Also some new code I put in for GoldenEye had an adverse effect speed wise on other games so I'm going to look into making it game specific. (It only helps Golden and Army Men that I know of, but I can turn it on for other games that exhibit the same shaking they do.)

2. Wally's progress
Wally has been hard at work fixing some micro code issues which should help compatibility. At least one more game now runs with his new code.(Space Station Silicon Valley) I don't have it yet, but when I get it I'll test it for speed and see if I can further improve it.

3. Chilly Willy's progress
Chilly Willy has been working on something Strmn left off on that wasn't quite in the R14 betas that circulated around. He has just given me code to move audio processing to the ME. What this means is that with audio on it won't bog down the CPU quite as much(there's still a hit from it, but not as much.)

Side Note to #3: Audio code is currently based on Azimer's 0.55 plugin, but he has offered me a later version of the code which is now feasible to use thx to Chilly's new code.

With all three of these updates we now have better speed and compatibility than any prior version of Daedalus(R12-R14 included). There will be another Alpha in 2-3 days max. After this is tested(in bout a week), the SVN will go online. All the developers will have access. Then in December everyone will have read-only access with the developers having write capability. The first public beta will come out about that time. (Read: Early December.. 1st-5th time frame.)

Well, I'm not the only dev working on this and this update concerns me and two other devs.

1. My progress
I looked into the cache last night and found that the instruction list for the dynarec was being invalidated when it wasn't necessary. This eats up a small chunk of CPU cycles. So a bit more speed from better cache handling there. Also some new code I put in for GoldenEye had an adverse effect speed wise on other games so I'm going to look into making it game specific. (It only helps Golden and Army Men that I know of, but I can turn it on for other games that exhibit the same shaking they do.)

2. Wally's progress
Wally has been hard at work fixing some micro code issues which should help compatibility. At least one more game now runs with his new code.(Space Station Silicon Valley) I don't have it yet, but when I get it I'll test it for speed and see if I can further improve it.

3. Chilly Willy's progress
Chilly Willy has been working on something Strmn left off on that wasn't quite in the R14 betas that circulated around. He has just given me code to move audio processing to the ME. What this means is that with audio on it won't bog down the CPU quite as much(there's still a hit from it, but not as much.)

Side Note to #3: Audio code is currently based on Azimer's 0.55 plugin, but he has offered me a later version of the code which is now feasible to use thx to Chilly's new code.

With all three of these updates we now have better speed and compatibility than any prior version of Daedalus(R12-R14 included). There will be another Alpha in 2-3 days max. After this is tested(in bout a week), the SVN will go online. All the developers will have access. Then in December everyone will have read-only access with the developers having write capability. The first public beta will come out about that time. (Read: Early December.. 1st-5th time frame.)