I think I got the code wrong, it just displays the number 1, do you have any idea why?You're welcome. Hope to see some works of yours soon on this forum
I think I got the code wrong, it just displays the number 1, do you have any idea why?You're welcome. Hope to see some works of yours soon on this forum
I think I got the code wrong, it just displays the number 1, do you have any idea why?
Sorry, I forgot to use that one and was excited to use my own code but it was a number 1 before I used yoursProbably not the number 1 but the cursor arrow (use SDL_ShowCursor(false); to hide it
For the image not showing, did you used the makefile and the code in my zip?
Sorry for the double post, but did you set it to use SMDH by default? Because I tried using NO_SMDH after I got an error that said "Could not load PNG: C:devkitProlibctru/default_icon.png" (Which I think is an error on my side since you were able to compile) and it I got "Cannot open SMDH file!" after setting it.Probably not the number 1 but the cursor arrow (use SDL_ShowCursor(false); to hide it
For the image not showing, did you used the makefile and the code in my zip?
Sorry for the double post, but did you set it to use SMDH by default? Because I tried using NO_SMDH after I got an error that said "Could not load PNG: C:devkitProlibctru/default_icon.png" (Which I think is an error on my side since you were able to compile) and it I got "Cannot open SMDH file!" after setting it.
Thanks but I have to ask why did you edit these functions?With NO_SMDH i was having an error, so I enabled it. Don't know if it's something related to using romfs or something I cjanged by mistake
SDL_Surface* tempImage = NULL;
tempImage = IMG_Load("romfs:/ssgss.jpeg");
image = SDL_DisplayFormat (tempImage);
SDL_FreeSurface (tempImage);
I tried compiling your fixed version of the homebrew, and my version, but the both give me a red bottom screen with some glitched pixels at the bottom left of the top screen, any idea what this is about?you created a 32bit screen, but the loaded image could have another format.
If you blit ( i.e copy pixels) from an imange to a screen with a different format, the result will be fuzzed color. With this code the loaded image is converted in another one with the same format of the sceen.
It's a common coding path with SDL. You can avoid it only if you know that image and screen have the same format.
It should be a problem of the HB Launcher with 11.4 FW. The red screen should be a visual alerto of the launcher for a payload problem, not something related to your code.I tried compiling your fixed version of the homebrew, and my version, but the both give me a red bottom screen with some glitched pixels at the bottom left of the top screen, any idea what this is about?
I'll just wait for a fix, since I can't do either of thoseIt should be a problem of the HB Launcher with 11.4 FW. The red screen should be a visual alerto of the launcher for a payload problem, not something related to your code.
Try the code with the Citra Emulator or build a CIA package and install it with FBI.
Result createPath(const char* path, PATH_TYPE type, Path *p, u32 flag) {
Result ret;
p->path = fsMakePath(PATH_ASCII, path);
p->archive = (FS_Archive){ARCHIVE_SDMC, (FS_Path){PATH_EMPTY, 1, (u8*)""}};
p->type = type;
ret = FSUSER_OpenArchive(&p->archive, ARCHIVE_SDMC, p->path);
printf("OpenArchive: %d\n", ret);
if (p->type == F_FILE) {
ret = FSUSER_OpenFile(&p->handle, p->archive, p->path, flag, FS_ATTRIBUTE_ARCHIVE);
printf("OpenFile: %d\n");
} else {
ret = FSUSER_OpenDirectory(&p->handle, p->archive, p->path);
printf("OpenDirectory: %d\n");
}
return ret;
}
OpenArchive: -522172738
OpenDirectory: 2
Could not open the Archive for whatever reason.
Press any button to exit.
Code:OpenArchive: -522172738 OpenDirectory: 2 Could not open the Archive for whatever reason. Press any button to exit.
3DBrew has no documentation on the Response Codes AFAIK, last time I checked.
You need to look at the error code as an unsigned hexadecimal number, not as a signed decimal/integer value.
https://www.3dbrew.org/wiki/Error_codes
This particular error translates into:
0xE0E046BE
Module: FS (17)
Description: Invalid path? (fs) (702)
Summary: Invalid argument (7)
Level: Usage (28)
As for the solution, I don't have one right now, but hopefully that provides some insight as to what might be wrong.
Is there a script or anything that translates these error codes, or would I have to go about this myself?
AFAIK the bot on the Homebrew Discord has a function like this, but I was wondering if there was a tool I could use locally.
https://gist.github.com/ihaveamac/e68022bac625ff9bdd4487c8bd5d1368
This is old though, so you might need to fill in missing descriptions and such from the Error Codes page.
(Or steal them from Kurisu's source: https://github.com/916253/Kurisu/blob/master/addons/err.py )
I have the exact same problem, how'd you fix this?I removed sftdlib from TWLoader, and replaced it with citro3D for rendering text in the system font.
With citro, the text shows up just fine, but after a second, the text disappears.
Am I missing something?
Do you have files called "citrostuff", or basically, do you have a file that contains the citro3D functions?I have the exact same problem, how'd you fix this?
Yes.Do you have files called "citrostuff", or basically, do you have a file that contains the citro3D functions?