indeed, one thing I can say about @Laf111 is that he's a very determined, helpful, and polite person.
I second that motion! Thanks again Laf!
indeed, one thing I can say about @Laf111 is that he's a very determined, helpful, and polite person.
I had issues for a while trying to compile the wfs extract and injector. there's a part of the code that's been delisted in compiling with visual studio 2019, so I had to use 2015 to get it compile. I have both installed on my computer. one of the options to change the sdk used windows 8.1 or windows 10 didn't seem to exist in 2015 after changing it on 2019, so I had to redownload the source files. not sure what happened, but I compiled them eventually. anyway, I asked Laf for help when I couldn't figure it out. it mentions 2015 on the source page, but I must've missed it.
I guess some of the stuff for the wii u is so old that you have no choice. one of the dependencies for that app to run the gamepad on the pc using linux has also been delisted, and it was a nightmare with dependency after dependency to get it to install. I think it was gksu. I got the .deb file, but too many dependencies, so I gave up.
I am not into software development but more into data analysis. Still: maybe one of the programming gods that is familiar with all software (versions) required and has it setup locally could also setup a working VM or docker / singularity container (dunno if Win and Linux are equally suited to do software development for the Wii U). That would lower the threshold for beginners and facilitate testing shared code.Yep it's a crying shame that the effort required to dev in this environment saps every last bit of passion you once had for programming in general LOL. Well in my case at least. There's still *some* left, but I tell ya, it's waning pretty damn quickly. That's why I keep jumping on and off this WiiU-Shell project when I either a) hit too many brick walls, b) get too busy with work/personal life commitments, or c) both of the above.
I'm determined this time though. I'm going to stop worrying about the niggly little things like not being able to debug properly, and just do it old skool like everyone has had to. It's time to get out of my 21st Century habits and go back to printfs and deciphering assembly!
The hbl RPX version does exit to the hbl as it should, its just when its made into a Channel the RA code doesn't have the required procui stuffs to exit as a Channel (its all so confusing)he can probably do it. his channel exits to the wii u menu while the hbl version or rpx exists to the homebrew launcher iirc.
ye, FailST edits files that are very brick sensitive, so there are tons of checks when you install (rightly so)failst is out, but I heard that it's buggy. and, the developers of aroma mentioned that aroma has checksums, so if you used failst as it is now, chances are it will fail to install. I think it's part of the cos.xml or something iirc.
afaik, failst at least can work like cbhc, but it can be installed to any title (maybe not the disc channel though, not sure). so, it's best to put it in one of the default apps like download play on the 3ds. it should be something you don't use, I guess. right now, failst isn't a coldboot hack. it opens the homebrew launcher from any app. however, aroma is going to be paired with a coldboot type hack of some sort.I think I'll just wait it out, or if by some miracle it can be reworked to work with CBHC
I guess the Health and Safety Channel would probably be the Heathiest and Safest Pafaik, failst at least can work like cbhc, but it can be installed to any title (maybe not the disc channel though, not sure). so, it's best to put it in one of the default apps like download play on the 3ds. it should be something you don't use, I guess. right now, failst isn't a coldboot hack. it opens the homebrew launcher from any app. however, aroma is going to be paired with a coldboot type hack of some sort.