Homebrew Coverflow DS (New project)

  • Thread starter Thread starter spinal_cord
  • Start date Start date
  • Views Views 238,782
  • Replies Replies 1,667
Xenon++ said:
A Gay Little Cat Boy said:
How do I boot into Wood after using the R4 wood loader?
Every time I try it loads into the game I loaded last
Use iniclear. Or possibly DSCovered external loading works?

As far as I can remember, all of the loaders included with the main download should be able to load their respective firmwares if they are selected in DSCovered and homebrew is set to load externally.
 
spinal_cord said:
Xenon++ said:
A Gay Little Cat Boy said:
How do I boot into Wood after using the R4 wood loader?
Every time I try it loads into the game I loaded last
Use iniclear. Or possibly DSCovered external loading works?

As far as I can remember, all of the loaders included with the main download should be able to load their respective firmwares if they are selected in DSCovered and homebrew is set to load externally.
Well that worked
 
@Spinal_Cord can you make a function in the Windows app that we can sort the Games???I know that i can change the list.dat but thats much complicated every Time.
 
schraat said:
@Spinal_Cord can you make a function in the Windows app that we can sort the Games???I know that i can change the list.dat but thats much complicated every Time.

You can currently sort the games by clicking the header in the list box, which will sort them by name/code. The next version will currently sort by name, publisher or genre.
I currently have no plans to do anything more complicated just yet, but I will look into the possibility.
 
I know covers are in CODE.bmp format but how does app regonize homebrew? Auto-coverloading doesnt load homebrew covers and sometimes its hard to find covers for homebrew so there should be some homebrew cover pack?
 
Mario92 said:
I know covers are in CODE.bmp format but how does app regonize homebrew? Auto-coverloading doesnt load homebrew covers and sometimes its hard to find covers for homebrew so there should be some homebrew cover pack?

If anyone wants to put together a homebrew cover pack, I wouldn't stop them. The next update will have a change in naming though, so I would wait if you intend to do it yourself.
The next update will use both front and back covers, the homebrew covers will be named using the CRC32 of the file, so, ysmenu would be CF232764.bmp for the front and CF232764b.bmp for the back.

It would be good if someone would put together a collection of un-converted images ready for the next release.
 
I could attempt making some covers for homebrew (I have a lot of homebrew titles xD and I'm pretty sure I have a cover template somewhere...) at least, I'll make covers for the homebrew that I like xD.

-edit-
It doesn't matter what the dimensions are, right? (Or maybe I should follow the dimensions from advanscene?)
 
jurassicplayer said:
-edit-
It doesn't matter what the dimensions are, right? (Or maybe I should follow the dimensions from advanscene?)

Dimensions don't really matter, the manual cover importer requires the front and back to be separate images though, unlike the ones downloaded from advancene.

cover_import.jpg
 
http://www.mediafire.com/file/xmgcm5hljrt/m3dscover.7z
Reviced loader_m3.nds, give it a try...
Faster and stabler much than before...

PS
I don't think classifying with CRC32 is a good idea.
Firstly, the files can be easily modified with DLDI.(Well in this case you can skip DLDI area)
Also, Applying fatpatch or yspatch easily changes CRC32.

Alternative method? nope lol
 
Xenon++ said:
PS
I don't think classifying with CRC32 is a good idea.
Firstly, the files can be easily modified with DLDI.(Well in this case you can skip DLDI area)
Also, Applying fatpatch or yspatch easily changes CRC32.

Alternative method? nope lol

It's the only way I could think of to uniquely identify homebrew as very few homebrew coders actually add/edit the internal title and obviously the ID code is almost always ####.
 
spinal_cord said:
Xenon++ said:
PS
I don't think classifying with CRC32 is a good idea.
Firstly, the files can be easily modified with DLDI.(Well in this case you can skip DLDI area)
Also, Applying fatpatch or yspatch easily changes CRC32.

Alternative method? nope lol

It's the only way I could think of to uniquely identify homebrew as very few homebrew coders actually add/edit the internal title and obviously the ID code is almost always ####.
Well putting the same covers with different filenames will work...
But anyway we have to make a hashing tool which skips DLDI. (guidpatch in mshl2pack_r21 might be a reference)
 
If homebrew coders added the ID code to all of their homebrew, there would be a real problem with Moonshell2 since it seems to check if the file has a game ID before it will load the .nds file or not xD (I learned this through PPSEDS).

On the topic of back covers, are the back covers actually going to even be readable? From the looks of it, the text is pretty small when converted...unless you use really big font.
 
I dunno why.. but I always get problems with this thing.. .-.


So I'm trying to using the woodmod... I got the akmenu4 file and the rpg file, put it on the root of my card. Then I renamed the akmenu4 to akmenu. Next i got the d_system file, and put the akmenu4 file on the root of my card. I imported covers, and blah blah..


But when I turn it on, it says DS_MENU is missing...
 
obito said:
I dunno why.. but I always get problems with this thing.. .-.


So I'm trying to using the woodmod... I got the akmenu4 file and the rpg file, put it on the root of my card. Then I renamed the akmenu4 to akmenu. Next i got the d_system file, and put the akmenu4 file on the root of my card. I imported covers, and blah blah..


But when I turn it on, it says DS_MENU is missing...

o.0 Generally when something says _DS_MENU.dat is missing, that means A) You are using an R4 original/sd clone if you can use wood and B) You don't know too much about the R4's setup. (Thus I'll help you out xD)
_DS_MENU.DAT is the first file that will be loaded and is an encrypted .nds file. So, you have to choose what you want as your initial firmware (the one that loads up first) which could be any firmware/homebrew provided it is a working .nds file. Then you need to encrypt it using a tool like 'R4denc' to encrypt the .nds file and then rename it to _DS_MENU.dat. Apart from that, the rest is hopefully easy to figure out (since the rest of it is just placing it on your card and making sure the reference paths are correct).
 
jurassicplayer said:
On the topic of back covers, are the back covers actually going to even be readable? From the looks of it, the text is pretty small when converted...unless you use really big font.
I think they are for looks and spinal is making spinning covers
smileipb2.png
 
Well i looked back a few pages but could not find a similar problem and the search button didn't help much but I can't seem to load commercial backups using the YSMenu loader, whenever i try, it just boots to YSMenu rather than loading the ROM.
YSMenu boots everything fine.
To be honest i think my YSMenu may be slightly out of date but DSCovered is definitely not up to date.

The root of my SDHC card is so messy i can't remember what has been renamed what but i do believe i have the following files:
Dscovered.nds => ttmenu.dat for auto-boot
YSMenu.nds => Ysmenu.nds
ttdldi.dat
ttmenu.sys
ttpatch.dat

Any ideas?
 

Site & Scene News

Popular threads in this forum