-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splash occasionally appears messed up. #42
Comments
Can confirm that it happens with the latest commit as well. |
Not able to reproduce this. I need more infos. When does it corrupt? While entering the menu (through the HOME button) or quick boot? |
I usually use quiet mode, so I originally noticed it while entering menu, but it definitely happens with other two boot modes too. For quick mode even the "Press HOME to enter menu" text that appears on bottom screen also gets corrupted. All of that happens with default builtin splash, I've never actually tried using custom splashes (neither from SD nor by replacing the builtin one), but I can try when I have some time later, if that can help. P.S. Changing splash duration, whether it's shorter or longer, doesn't seem to help either. |
Yeah, i can't reproduce this. It's working on my o3DS with debug and release builds. You are building under Windows, correct? Possibly the link order affects this and changes timing. I built everything under Linux. Can you upload one of these broken builds? I have an idea what the problem could be. The last commit i just pushed is unrelated btw and can be ignored. |
Yeah, I build under Windows. |
Same with your build. Ok, a blind attempt at this. Try the attached build. [removed build] |
With this test build there seems to be no corruption with both normal mode and while entering menu with quiet mode. Quick mode still has some minor corruption on both screens… Does it matter what was used to flash the firm? I used GM9 for both builds, latest commit from the staging branch. |
Ok. All i changed was the 3 ms wait in GFX_init() waiting for VBlank instead. At least this confirms it's timing related. Doesn't matter. [removed build] |
No change unfortunately, the quick mode is still corrupted. |
What about this one? I'm running out of ideas to be honest. [removed build] |
Same. :( Actually, the corruption is random almost every boot now, no matter whether SD is present or not. I'm sorry for not being of much help here, and thank you for your patience. |
That kinda looks like the corruption i was getting a long time ago on N3DS XL which seemed texture copy related and got "fixed" with a workaround. I recently pushed a fix which was supposed solve this properly. Looks like this is an entirely different bug after all and was never properly fixed. I'm going to take another look into the gsp module because i remember some unknown reg writes which could be related. If that doesn't work i'm going to try another workaround. |
Oh, yeah. That was the workaround i was talking about. I thought this was the same bug but it's not. I still want to try fixing this correctly. |
Ok, what about this one? If you have more than one 3DS test it on all of them. [removed build] |
Sorry for late reply, I went to sleep. |
I basically only wanted to know if this build works and if it does, does it work on all models? Since it doesn't work the other tests are superfluous. I thought maybe these extra reg writes will do it but unfortunately not :/ |
This happens at least on commit c417a8a, though i do not know if it happens in ef732dc, the latest commit at the moment.
I would add an image, but I do not have a means of such at the moment
The text was updated successfully, but these errors were encountered: