i can see it fine...I don't know if anyone has already mentioned this, but Hykem has made his Twitter private:
https://twitter.com/hykemthedemon
i can see it fine...I don't know if anyone has already mentioned this, but Hykem has made his Twitter private:
https://twitter.com/hykemthedemon
i can see it fine...
i can see it fine...
IOSU access would mean that we can have emunand like the 3ds has.
So the sysnand would stay at a valuable firmware version and we can upgrade the emunand to the latest version.
IOSU access would mean that we can have emunand like the 3ds has.Firstly great thread, its nice to see people wanting the develop on WIIU and you make some very good points.
I understand why the exploits are held back until patched or real reason for them needing to be released. One thing that really confuses me though is this..
IOSU is supposed to give us everything, so no need for a kernel exploit. So if IOSU is so special why are they not holding IOSU back until that's patched and just releasing one of the kernel exploits instead ?
What I mean is once IOSU is released it will be patched so game over. I just don't understand why IOSU being the most important of the exploits is being rushed to release and the kernel exploits being held back, surely it should be the other way around?
As far as I know you'll need kernel access to apply an IOSU exploit (Hykem's exploit being the exception)IOSU is supposed to give us everything, so no need for a kernel exploit.
They want to be sure that the update from Nintendo blocks the exploit so most will update and get fucked. And then release it. What's the logic? I don't know.may be a noob question but how would nintendo patch the exploit without it being released?
To be very careful about updates when an exploit is pending should be normal!They want to be sure that the update from Nintendo blocks the exploit so most will update and get fucked. And then release it. What's the logic? I don't know.
You really do not understand the source code and the purpose of it in loadiine gx2. You just said you use official libraries and documents and that loadiine gx2 is all but copy/paste of official headers in one post... Did you even look into libwiiu? Do you really think that the examples there work or are any different? Hilarious. Especially since what you and all the other "homebrews" out there do currently is nothing different....but lets not go that way. Though I am really interessted in what you think is "legal" libraries you say in your post and what you think you can achieve with those.I've got all the development tools I need by going through the official documents for the official libraries. Problem is, I can't use the sound library, for one example, with just user space, unless I am really doing something wrong, which I don't think so. Getting a handle to sndcore2 results in a mess, and getting a handle to sndcore works, but any attempt to use the library results in a lockup. I could try to use "legal" libraries, but hell, Loadiine GX2 all but copy/pastes the official header files in their source, so ...
You did an amazing job on Loadiine GX2 ! I spent hours trying to understand your code and eventually i managed to make a working code (just to display an image on TV screen ). Now i'm looking into your code again because deallocating all my shaders pointers causes problems when i want to set a new shader. I'll try your solution to deallocate asynchronously (using mutex and a new thread).The dynamic rpl functions are just a small fraction of the code. Loadiine gx2 was to show other developers how to use the available dynamic rpl library resources and all that needs to be done around them to get some proper results (which is a lot more than you might think). It is there so developers dont have to look into the "official documents" to understand the way the hardware access works. Well it seems its not taken as it was intended to i guess, seeing how you are trying to figure things out from the documents yourself from scretch instead of using the already working sources in loadiine gx2. Maybe I should have started with a different application than a loader and people would look different onto it. Since the sources are not used and not appreciated I guess there is no point in releasing any sources to the public then .
So im guessing 5.5 STILL isnt out
np, i am patient i can wait till summer, then ill lose my mind
Thank you for this post, and yes I think you are wrong on that one Also thanks again for the help with getting my game to run in Homebrew Launcher.Sorry to go so far off topic (in a way it is adding to the topic because it shows what is possible with the user exploit in a browser and what is not and requires more access rights) but this really annoys me to see something like that come from a developer who should really know better and be able to read and understand source code and the work behind it. If it is really like that and the developers just bark at each other instead of working together then there is no hope for this scene anymore and I dont wanna waste any more of my time into it in that case. I hope I am wrong on that one..
nice post @dimok . maybe 12 year old @brienj finally gets his head around it and either leaves forever,or actually starts reading up... most of the naysayers are young and clueless,but also wellmeaning somehow. i guess that excuses some of the shitposting. btw.. : does androids dream of electric sheep?grownups know that answer....
brienj isn't really one of those "12yo trolls" he's a homebrew developper and a very good asset to have in theWii U homebrew scene, but he did act a bit unprofessional the way he expressed himself, I hope he can continue contributing in the scene and focus more on working together with other developpers instead of acting this way in public. So no we don't want him to leave forever ^^.
@dimok I think what I said, was interpreted incorrectly, and it was in no way any sort of attack against you. What you did is very brilliant. I was just saying that the functions used through the official rpls would be very difficult to reverse every one of them without using the SDK documentation as a reference, and there is only a small sample of all of them on wiiubrew.org. There I go again, by using "small", someone will bend my words that I am saying that there isn't anything documented on there, but if you did it without looking at the official SDK documentation, then I am even more impressed by the amount of time that would have taken.You really do not understand the source code and the purpose of it in loadiine gx2. You just said you use official libraries and documents and that loadiine gx2 is all but copy/paste of official headers in one post... Did you even look into libwiiu? Do you really think that the examples there work or are any different? Hilarious. Especially since what you and all the other "homebrews" out there do currently is nothing different....but lets not go that way. Though I am really interessted in what you think is "legal" libraries you say in your post and what you think you can achieve with those.
The point is those "dynamic_libs" are a hardware accesses. You have to go through them to do anything with the wiiu hardware unless you do have access to the hardware registers and do know how to work with them (I would know how to work with many of the wiiu hardware registers and how to implement the necessary layers above them such as the EHCI driver but its a shitload of work and some require a lot of reversing). Though the hardware registers are only accessible through the IOSU.
Well that is what loadiine gx2 does with the rpl libraries, only the hardware access which can not be done in any other way currently. The rest around that, how and in what order the funtions from the rpl are used and what needs to be processed in what way, e.g. converting sounds to correct format or textures to the GX2 usable format, now that is what loadiine gx2 was all about for me. Do you think those several thousand lines of code and the use of several open libraries such as libfreetype, libpng or libmad are just overhead? The dynamic rpl functions are just a small fraction of the code. Loadiine gx2 was to show other developers how to use the available dynamic rpl library resources and all that needs to be done around them to get some proper results (which is a lot more than you might think). It is there so developers dont have to look into the "official documents" to understand the way the hardware access works. Well it seems its not taken as it was intended to i guess, seeing how you are trying to figure things out from the documents yourself from scretch instead of using the already working sources in loadiine gx2. Maybe I should have started with a different application than a loader and people would look different onto it. Since the sources are not used and not appreciated I guess there is no point in releasing any sources to the public then .
Anyway I can tell you why you cant get the sound library to run. You are trying to access it inside the browser exploit environment on your 5.5 exploit in which it is already acquired and in use by the browser application. What you do is jump into an already running and working environment with almost all resources such as the heap memory already in use and try to put things on top of it. You wont get very far with that. This is the reason you fail, assuming you do everything else correct with the rpl functions. It is not that you cant access the library through user space, afterall its a user space library, it is that you do not have enough resources left to do that or because you disturb a running environment. That is why you need the kernel exploit or at least write access to the coreinit library memory region, to actually hook yourself in a better position where the application you hook is still "fresh" and the resources are still usable.
Sorry to go so far off topic (in a way it is adding to the topic because it shows what is possible with the user exploit in a browser and what is not and requires more access rights) but this really annoys me to see something like that come from a developer who should really know better and be able to read and understand source code and the work behind it. If it is really like that and the developers just bark at each other instead of working together then there is no hope for this scene anymore and I dont wanna waste any more of my time into it in that case. I hope I am wrong on that one..
I am 45 years old, have a beautiful wife, 5 kids, three that still live at home, and sometimes I am not the best at communicating properly. I have over 25 years of programming experience. That is all, have a nice day.brienj isn't really one of those "12yo trolls" he's a homebrew developper and a very good asset to have in theWii U homebrew scene, but he did act a bit unprofessional the way he expressed himself, I hope he can continue contributing in the scene and focus more on working together with other developpers instead of acting this way in public. So no we don't want him to leave forever ^^.