Raid Read Error

[Titonka]

This error occurs often and seemingly randomly including sometimes upon immediately pressing connect or advance date in Raidcrawler.

[LegoFigure11]

Could you please provide a dump of the save or the raid block when this error occurs? I've been running it for about 7 hours now and am thus far unable to replicate the problem.

[Banzail]

This seem to bite eachother with new event that got released recently. Got same problem

[LegoFigure11]

At least 6 of those hours have been on the new event, so I don't think that's it. Could you please provide a save file or a dump of the raid block?

[supersaiyajingoku]

Not OP but the same thing happens to me but only on my scarlet save file. Never got the error on violet. Raid Block: 01 00 00 00 13 00 00 00 01 00 00 00 06 00 00 00 54 53 3E C2 00 00 00 00 02 00 00 00 00 00 00 00

[Banzail]

Ah yes. Its in scarlet related with 6* (black) raids in dlc. Causing this error

[alemany89]

I was able to reproduce the same kind of issue on Scarlet, not for a black chrystal but with the events ones, heres the log file -> raid_dbg_BaseROM.txt

[alemany89]

i've sent you the save where is reproduced the issue LegoFigure11 via discord

[alemany89]

Im testing how to skip the issue and i've found something. I've disabled the following checkbox for kitakami and the issue is not reproduced anymore, it seems like a performance issue when trying to scan both regions (maybe for some switches? i only have 1 CFW switch in order to test it :/)

The moment that trigger the following errors messages is after changing the date when it goes to overworld to scan for the new teracrystals :

[Titonka]

Hello, I am the original poster. To be honest, I am new to CFW so I am not entirely sure how to upload my save file or raid block. I saved as soon as I got the error and saved my file in JKSV but I can't find the file to upload it :( For now, I have tried to attach the log of the message I am getting. In case this information is useful, I am also using Pokemon Scarlet, but I am still receiving the error when scanning only Kitakami. I was having this issue before the events as well. Thank you very much for looking into the problem and sorry I haven't been super helpful. On Sep 22, 2023, at 1:01 PM, alemany89 @.> wrote:Im testing how to skip the issue and i've found something. I've disabled the following checkbox for kitakami and the issue is not reproduced anymore, it seems like a performance issue when trying to scan both regions—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.> No encounters found. Den: 1 Progress: 4 Difficulty: 95 Group ID: -1 isFixed: False isBlack: True isEvent: False

[alemany89]

There are 2 types of issue here @Titonka, one is yours that is regarding a black crystal in dlc region, mine is related for the new event pokemons in the vanilla region:

so in summary there are two error files: your issue regarding black crystal in kitakami region -> raid_dbg_KitakamiROM.txt

The issue in the vanilla region regarding the new event pokemon -> raid_dbg_BaseROM.txt

The second one can be skipped by disabling the scanning into the dlc section, for the first one i dont have any clue yet

Notes: Regarding how to export the save file you can find on google tutorials about JKSV anyway if you have questions regarding CFW you can go to https://discord.gg/nintendohomebrew in order to know more about it

[CardBreaker]

I think I found the issue with Kitakami black crystals. It's a typo in GetRateTotalKitakamiSL. The value for 6 star raids should be 2475, not 2575.