Homebrew Homebrew Development

  • Thread starter Thread starter aliak11
  • Start date Start date
  • Views Views 1,475,135
  • Replies Replies 6,048
  • Likes Likes 54
its nothing like selling a concept car, in fact most most concept cars dont even run, because they are just that, concepts and in fact 90% of concept cars never even enter the physical world
you cant compare the 2, what you are doing is essentially being the rich kid in school going hahaha look what i have, i know people who got pissed that chevy sold the C7 early to rich people, in fact they felt it was discrimination towards them because they couldn't afford to buy one early since it had such a ridiculous price tag

basically to compare what you are doing to something very real that relates to everyone, its like adobe saying look at CS8 its so cool, it can do XYZ better than CS7 can but you cant have it because someone could use it to pirate images online and remove watermarks, sorry...

i cant make you release anything, thats a fact, and im sorry if i offend you but i think what you are doing is selfish and stupid, and when i say you i mean everyone who is doing what you are for the exact same reason

Ok guys. Enough of this. This thread is for Homebrew Development, not homebrew discussion.

I've updated my post at http://gbatemp.net/threads/speculation-current-state-of-affairs-for-3ds-flash-cards.363645/.

Please read through update 3.
 
Alright everyone, enough is enough.
First, profi200 said it already, his CFW is not stable, starting a homebrew only once in a blue moon and actually having a risk of bricking a 3DS. I for one wouldn't want to put something like that on my own console.
Second, judging from the way he said some stuff, it COULD be ASSUMED that he is using some copyrighted tools for it (3DS SDK? Something else? Who knows) and he simply can't LEGALLY release it. He is not from China to be able to risk it.
 
Alright everyone, enough is enough.
First, profi200 said it already, his CFW is not stable, starting a homebrew only once in a blue moon and actually having a risk of bricking a 3DS. I for one wouldn't want to put something like that on my own console.
Second, judging from the way he said some stuff, it COULD be ASSUMED that he is using some copyrighted tools for it (3DS SDK? Something else? Who knows) and he simply can't LEGALLY release it. He is not from China to be able to risk it.

He's using code from other developers. Code he hasn't made and doesn't have the right to release to the open. In general it's very frowned upon to release something you don't own, especially if the owner/creator has said not to. profi200 could do whatever he wants with his own code, but as mentioned already by himself (and smea and many others) they choose not to. At least for now, since they don't have something foolproof and useful to the general public.

To everyone in general:
Lets face it. Anyone could do the same as these developers. Learning to code is not impossible, since people can learn to read and write without any prior knowledge in the matters. Do they do it? No for the most part. Wait or participate in the development phases. The third option of complaining about no releases or, even worse, attacking and blaming the developers is just not cool and will lead to nothing (or something with the people giving up their development efforts).

Kudos to everyone making things possible, it's a pleasure to see progress being made. Hopefully we can see some kind of homebrew on the 3DS.
 
He's using code from other developers. Code he hasn't made and doesn't have the right to release to the open. In general it's very frowned upon to release something you don't own, especially if the owner/creator has said not to. profi200 could do whatever he wants with his own code, but as mentioned already by himself (and smea and many others) they choose not to. At least for now, since they don't have something foolproof and useful to the general public.

To everyone in general:
Lets face it. Anyone could do the same as these developers. Learning to code is not impossible, since people can learn to read and write without any prior knowledge in the matters. Do they do it? No for the most part. Wait or participate in the development phases. The third option of complaining about no releases or, even worse, attacking and blaming the developers is just not cool and will lead to nothing (or something with the people giving up their development efforts).

Kudos to everyone making things possible, it's a pleasure to see progress being made. Hopefully we can see some kind of homebrew on the 3DS.



Agreed, and I for one would like to apologise to the devs on these boards for bringing my thoughts on the subject of piracy vs homebrew into this particular thread. From this post on I won't be 'contributing' anything to this thread as I have honestly nothing to offer other than for my unreserved apology for having even a little part in the leaving of profi200.

Discussion / battles should be fought in separate threads and the coders left to their own dev world. I implore anyone else to follow suite if they have any designs on going 'off topic' here.

I have respect for the coders, without whom globally we wouldn't even have the devices and tools we use daily to cry on these boards. I'm sorry guys, I hope profi200 comes back.

Peace.
 
  • Like
Reactions: daicon
Speaking from the prospective of someone who knows how to code, but not quite at the level of some of the more talented people here, I appreciate all the work that's been done thus far. Rom loaders will likely come one way or the other eventually, but really I don't think it's something to get all up in arms about. Enjoy the system and games you already own, and if you're THAT concerned about running pirate games, then by all means buy a rom cart.
 
I assume all current unsigned code efforts that are not using undisclosed game save exploits, are still using the NATIVE_FIRM mset NVRAM stack-smash method for 4.5 consoles? I don't want to start playing around in the wrong sand pit.
 
Thank you, Foxi.

So, is anyone able to confirm, or comment on my previous question?
I assume all current unsigned code efforts that are not using undisclosed game save exploits, are still using the NATIVE_FIRM mset NVRAM stack-smash method for 4.5 consoles?
 
Thank you, Foxi.

So, is anyone able to confirm, or comment on my previous question?
Yes - the method remains unchanged, which is why any development beyond 4.5 is effectively stalled. If I remember correctly, firmwares onwards from that point introduced changes to how NATIVE_FIRM works.

If you want to start doodling in 3DS Mode, grab yourself a ROP Installer, the devkitPro kit or gcc ARM embedded kit and you should be almost good to go. Study the homebrews already released and keep 3DBrew handy for reference.
 
Yes - the method remains unchanged, which is why any development beyond 4.5 is effectively stalled. If I remember correctly, firmwares onwards from that point introduced changes to how NATIVE_FIRM works.

If you want to start doodling in 3DS Mode, grab yourself a ROP Installer, the devkitPro kit or gcc ARM embedded kit and you should be almost good to go. Study the homebrews already released and keep 3DBrew handy for reference.


Awesome. Thanks for the confirmation. I didn't want to begin building around it, if it was obsolete.
 
Awesome. Thanks for the confirmation. I didn't want to begin building around it, if it was obsolete.
You can freely start building around it, however keep in mind that ctrulib and ARM11 access are heading our way, or so we can only hope, so the days of using ARM9 as the central processing unit for applications are numbered. If I'm not mistaken, soon enough it will be relegated to background tasks, much like it was the case with ARM7 on the DS.

EDIT: I am a total dumbass - you'll also need/might want to use Python Tools for 3DS, the script will help you for obvious reasons. Further setup information is available in the OP of this thread.
 
  • Like
Reactions: josh_axey
Just a friendly reminder from your friendly temperhood Spiderman, opinions are to be respected and not shot down. Also, lets stay on topic here. This thread is to talk about actual homebrew development, not about ethics, piracy, or rom launchers.
 
Hey guys, a few other I have talked to have recommended that I should learn how to program DS Homebrew (in C++ of course) to prepare for a eventual (hopefully) 6.X exploit to come around (I have a 6.3 3DS). I was wondering if anyone knew any other good resources I should study to prepare myself? I know when I'm getting home I'm going to look at other people's Homebrew to learn, but any other recommendations?
 
Hey guys, a few other I have talked to have recommended that I should learn how to program DS Homebrew (in C++ of course) to prepare for a eventual (hopefully) 6.X exploit to come around (I have a 6.3 3DS). I was wondering if anyone knew any other good resources I should study to prepare myself? I know when I'm getting home I'm going to look at other people's Homebrew to learn, but any other recommendations?
https://github.com/smealum
Have a look through that, should be something helpful there :lol:

Buttt....whilst a 6.3 exploit is starting to look likely, there is still no concrete proof that one will be made available...just something to bear in mind
 
Hey guys, a few other I have talked to have recommended that I should learn how to program DS Homebrew (in C++ of course) to prepare for a eventual (hopefully) 6.X exploit to come around (I have a 6.3 3DS). I was wondering if anyone knew any other good resources I should study to prepare myself? I know when I'm getting home I'm going to look at other people's Homebrew to learn, but any other recommendations?

here are some tutorials for DS homebrew. http://gbatemp.net/threads/ds-programming-for-newbies.322106, http://patater.com/files/projects/manual/manual.html, http://www.dev-scene.com/NDS/Tutorials
 
https://github.com/smealum
Have a look through that, should be something helpful there :lol:

Buttt....whilst a 6.3 exploit is starting to look likely, there is still no concrete proof that one will be made available...just something to bear in mind
And that is why I remain hopeful (but I'm not going to be blinded in thinking there is one right now, but I do have belief that "Failure is Always an Option" when it comes to software made by people).

Thank you kind person.
 

Site & Scene News

Popular threads in this forum