gamedragon2k / rasuite Goto Github PK

The hitcounts appear to be slower than expected compared to previous versions, perhaps 1/3 the original speed.

If the memory view is opened, hitcounts count at approximately 10x their previous amount. Closing the mem viewed doesn't change anything. And an emulator restart is required to return to the previous slow speed.

There's nothing here in the new dll. You can still upload new badges. Tested on RAP64 0.057.

When I'm using freeze if I freeze a value like 2 it becomes 22(hex)
1 -> 11
5 -> 55 etc

They should turn black after being saved.

They stay red until the achievements are reloaded.

minor issue.

It seems if you have a chain of add source reqs and a hit in the final one the value carries though into additional achievements.

Also if there are a large number of add source reqs (in my test ~30 with 2 groups of 15 added sources) having a delta/mem check on the two final addresses of the groups wasn't working when tested. Sorry if this is a bit vague, let me know if you need a clearer example.

In the achievements window,

Example: If I'm in core Achievements with "Processing Active" unchecked, and then go to Local the "Processing Active" checkmark will appear unchecked even though processing is active in Local.

Each group still has it's own avctive or inactive state, but the checkmark is not reflecting this state.
Also the checkmark will invert the current state, not go to the correct visual, after selected.

Including:

Achievement Editor window hitcounting
Memory inspector results
Mem viewer?

If I had a game open that has an entry, and then I open a game that's not linked to anything but cancel, not creating a new link, the system will still consider me playing the first game, and load all the achievements and dev notes, etc, for it.

Example:
0x16e0a4 for Star Fox 64 v1.0

Tested 3 times. Did not test other notes.

Intermediate bug.

DLL: 0.069
Emulator: RANes 0.013
Game: Castlevania: The holy Relic

After freezing any address and attempting to change any other address the emulator will crash. You can make changes to the frozen address. Tested 6 times.

There are too many ways to abuse this to get unfair scores.

I think it's ideal to leave enough for debugging, but no true score submissions.