Oh, if it can compile for Wii it can for Wii U, probably, I'm sure it generates ELFs which is what we need to convert to RPX/RPL. Someone'll just need to tinker and document that process
Yes, Mono/.NET's native executable format is .exe which contains intermediate code that the JIT (or AOT, if you decide) using Mono's native or LLVM will convert to native code.Well, i never used Mono so i might not know but:
I installed Mono and the newest version of MonoDevelop (Xamarin Studio)
I only can compile an .Exe either for x64 or x86
To my understanding that is even correct because on the target System there has to be Mono installed aswell.
But there must be a way to output other things then .exe because the wii surely never had a mono Interpreter homebrew
I wish people could learn to never mention a project until it was in the final stages - with all the functionality, being polished and some final bugs resolved, with a POC video. Inevitably, development takes a lot longer than anticipated and the scene gets shirty. Then the devs get upset at people getting shirty - when it's the exact same thing that's happened four or five times before. Isn't the definition of insanity doing the same thing over and over and expecting a different result??Its so entertaining to watch you guys fantasize about what we WILL BE ABLE TO DO, for the past what...3-4 years. What homebrew we need, and what kind of backup loaders, that everything and more will be possible....
Meanwhile theres aboslutely nothing new on the IOSU hack but rumors that are coming from people who know some peoples people.
Oh and someone who isnt even involved with the hack, saying we update because ITS COMING SOON (that was said what..1 month ago already)
So much bullshit and I still havent learned not to be hyped.
If this doesn't look modern I don't know what doesWii U graphics look outdated too compared to new games
If this doesn't look modern I don't know what does
I really dont understand this mentality. I can only attribute it to age because I don't know any adults that would go to the forums of a given product and try to make a case what a piece of crap it is.True words @fatsquirrel somewhat I feel getting old on this thread it has been 1000+ pages and in reality Wii U graphics look outdated too compared to new games. But All we still have is hope.
I wish people could learn to never mention a project until it was in the final stages - with all the functionality, being polished and some final bugs resolved, with a POC video. Inevitably, development takes a lot longer than anticipated and the scene gets shirty. Then the devs get upset at people getting shirty - when it's the exact same thing that's happened four or five times before. Isn't the definition of insanity doing the same thing over and over and expecting a different result??
what does this have to do with anythingthread it has been 1000+ pages and in reality Wii U graphics look outdated too compared to new games
This is the interesting part. It is GREAT to have public projects - anyone who is capable can contribute, so the project moves along as fast as possible, and maybe even gains features that the original dev never even thought of. If it's secret, then it only moves as fast as the people involved are able to. In the case of IOSU projects (all of them ... ) it is a closed group of devs, so not a public project where lots of people can contribute, and yet there are still announcements about it. Keeping people aware is important if it's a public project, so as to attract the attention of as many devs as possible, in case there's someone out there with just the right skill set to solve a particular problem on it so they will find out about it and contribute. However, here it is a private project, and it can't help the project any if people know about it (and could even hurt the project). So why tell anyone until it's finished?As a developer myself, I can pretty well say we don't like to be ignored and we don't like our project ignored either, so keeping everything under wraps isn't the way to go (you'll end up with a heck of a lot of half-finished projects). I find the solution to this issue is to keep everything public. I've started projects several times and not finished/used them (mostly due to stuff being outside my skill range), but people don't seem to mind because they've been able to see this in action from the start. Here's a few examples of such projects.
They already told so why should they backpedal =PThis is the interesting part. It is GREAT to have public projects - anyone who is capable can contribute, so the project moves along as fast as possible. If it's secret, then it only moves as fast as the people involved are able to. In the case of IOSU projects (all of them ... ) it is a closed group of devs, so not a public project where lots of people can contribute, and yet there are still announcements about it. Keeping people aware is important if it's a public project, so as to attract the attention of as many devs as possible, in case there's someone out there with just the right skill set to solve a particular problem on it so they will find out about it and contribute. However, here it is a private project, and it can't help the project any if people know about it (and could even hurt the project). So why tell anyone until it's finished?
The nature of this project ('these projects', really) doesn't really let us develop publicly. There would be an insane amount of userbase fragmentation between various versions, for one. For example, it's easy to have three people reformat/rearrange their redNANDs if the format needs to be augmented (which has happened like 3/4 times so far), but not so easy to have X number of thousands of people do the same. We're very fond of a day one release that Just Works(tm) for everyone, causes no issues, and has a solid set of features anyone can make use of. Maybe we'll nab a few testers very close to release, but as-is things are working out fine for how we develop stuff.This is the interesting part. It is GREAT to have public projects - anyone who is capable can contribute, so the project moves along as fast as possible, and maybe even gains features that the original dev never even thought of. If it's secret, then it only moves as fast as the people involved are able to. In the case of IOSU projects (all of them ... ) it is a closed group of devs, so not a public project where lots of people can contribute, and yet there are still announcements about it. Keeping people aware is important if it's a public project, so as to attract the attention of as many devs as possible, in case there's someone out there with just the right skill set to solve a particular problem on it so they will find out about it and contribute. However, here it is a private project, and it can't help the project any if people know about it (and could even hurt the project). So why tell anyone until it's finished?
Just to preserve this pic.twitter.com/isFmAruP8r
— EpicLPer (@EpicLPer) September 18, 2016
https://twitter.com/EpicLPer/status/777460334110052352
He posted a tweet he later deleted showing a Homebrew Launcher icon "accidentally". Just gonna preserve this here, nothing else to see.
I wouldn't read too much into this, if anything you're gonna get a bunch of random people harassing him after they see that image.
It literally is "nothing to see here folks". People who are waiting are still gonna be waiting regardless, even if it was something to get hype about (which it's not).
The symbol right next to it reads something with "Ran" on it, Random maybe?GBAtemp is a hub for information, this post was made public so i see no issue discussing it.
I wish people could learn to never mention a project until it was in the final stages - with all the functionality, being polished and some final bugs resolved, with a POC video. Inevitably, development takes a lot longer than anticipated and the scene gets shirty. Then the devs get upset at people getting shirty - when it's the exact same thing that's happened four or five times before. Isn't the definition of insanity doing the same thing over and over and expecting a different result??
True words @fatsquirrel somewhat I feel getting old on this thread it has been 1000+ pages and in reality Wii U graphics look outdated too compared to new games. But All we still have is hope.