as I wrote if something would crash or whatever it would say so still and launching a game does not take more than 10 seconds for me anyways. if you really want to be sure everything is going well I would suggest you to just not use another loader for it anyways and just use nintendont itself simply because it displays more and you can be sure no IOS conflict occurs.
ah sweet, didn't see the original post, just the quote.
I'd like to but I'm afraid this is a bad timing for me, I'm sure by the time I get around doing so testing would be done and over already ^^;You could help test it by converting images to CISO and testing the v4.422-CISO-test2 build I posted above.
Guilty
You know, this may be stating the obvious but you CAN keep multiple versions of Ninetndont, just keep an older version to test in case you got black screen to check.Good reason not to update for me. Wii seems too temperamental to trust a black screen. Especially when Nintendont can occasionally take minutes to create memory cards.
I'd think it's frozen again and end up shutting it down and corrupting something else. lol
Still got 800gb free on my Wii HDD, so ciso is of 0 interest also. Seriously, who is that tight on space to mess with such tiny ISO images anyway?
Use the money you obviously didn't spend on the games and just buy a bigger HDD.
Sent from my Nexus 5 using Tapatalk
Plus, ya know, it's totally optional?
People requesting for black screen at the loading screen since 2013, now we finally get that and they complain they don't want it, lol.ah sweet, didn't see the original post, just the quote.
Loading is generally quick here too, just creating memory cards on the first boot occasionally takes its time or freezes leaving a 0 byte file.
Just don't wanna reset the system if it's actually doing something still behind the blank screen.
Edit: what about a basic animated Nintendont logo or something? Gotta be better than staring at a blank screen for 10 seconds to 2 minutes? Or was this done to speed things up?
Sent from my Nexus 5 using Tapatalk
Haha, hence why I said I wouldn't upgrade just yet. Might go hunting for my gecko later n try find out why it fails creating cards occasionally.
This is actually pretty useful, i still use dollz 3.0 all the time. Any advantages with your tool over softdev's version? and out of curiosity, why 1 executable per-system instead of one?
gba connection only works with native set to on, and on originals wiis with gc ports. Is native set to on?
well then dont force it? not all games are compatible with forced settings, since those are general hacks and obviously wont work for every single game, since each game has its own manner of handling hacks.
So the first very obvious advantage is that it compresses much better because it uses LZMA2 instead of zlib, also the extract loader I wrote does not include any linked standard libraries so it is very tiny and efficient (16kb for gc, 15kb for wii), also it properly supports command line arguments so you can call these .dol files through some other loader for example and let that autoboot whatever you selected in the other loader, dollz3 did not have any command line argument support at all. The entry point of all dolxz files are also as low as possible (0x80003100 on gamecube, 0x80003400 on wii) so you can fit as much data in as possible, dollz3 did not always support big files. And now we come to why there are two versions for both gamecube and wii. First you can see the entry point on wii has to be higher because more low memory is used by the system which we cant touch on wii without breaking something. Also because the wii has some extra devices its initialization code is slightly longer to properly set those up. After a dol file is loaded up I move it into another memory region so I can safely set up MEM1 from there. That memory region is different, on gamecube its ARAM and on wii its MEM2, so since I was unable to find a way to properly auto-detect if your input file is a wii or gamecube one I decided to just split them up to ensure it does not try to include the wrong loader.
I would have thought that reporting when a feature does not work is a positive thing to do. How are developers to know when an issue is widespread or just exceptional?
every single forced hack doesnt have 100% compat and never will, its like every one reported forced widescreen doesnt work on manny games so they need individual hacks for each game, wich finding anyone to do is probably impossible since no one wants to loose hours and hours on each game making a widescreen hacks or forced progressive or whatnot, if you are a codder and find a solution or know a codder willing to go trough them you can go right ahead, reporting foced setting x doesnt work with Y game doesnt help anyone much you can fill in the wiki but that is about it.
Veho
K3Nv2
DinohScene
@
SylverReZ:
@
SylverReZ:
@
Maximumbeans:
I'm no good with hardware for now. I'd like to get into hardmods in future though
@
SylverReZ:
@
SylverReZ:
@
Maximumbeans:
@
SylverReZ:
@
SylverReZ:
