So, my recent blog post wasn’t clear enough. Obviously one retard, not you “anon”, didn’t really know about the whole situation and how it went and totally misses the topic. Nice comment btw. From whoever it was, I don’t care. But it definitely shows that some people don’t even try to get the very essence out of my posts. Well, as expected. So, I’m going to re-post this again, without directing it towards the one person, so even the dumbest person on this planet is able to understand it, yes even you. The older blog post was also from a while ago when I was annoyed like fuck of that useless conversation with p4. I told him that it IS actually possible on hardware, YET he didn’t listen. Currently however we don’t have any problems anymore. So I guess the “direct” fight is over.

Also, thanks to anon for speaking the truth. It’s good to see that I actually receive thanks for ripping off my ass for my CajeASM assembler, especially for discovering the RSP assembly which was a true pain to the ass.

So, let me start again, this time more clear and more descriptive:

I’m a SM64 ROM Hacker. I know enough stuff about the N64 Software as well as the hardware. Now, here the thingy comes: I’ve modified the PJ64 emulator to allow the user to use more than 8MB RDRAM for their ROMs. I’ve allowed up to 32MB RDRAM. Not any further. I see this as a milestone in SM64 Hacking, and so do many others, including skelux and kazeshin. So, what’s the problem here? Exactly, there’s none. But obviously some people don’t like it. Yes, I can agree that some people don’t like it, but really why do you people have to be fucking annoying me with this? Yes, I’ve been recently getting continuously messages like: “Why don’t you fucking support hardware?” etc. etc. messages, which I honestly don’t give a fuck about. I’ve answered always: “It’s possible on N64 Hardware. You just need the experience and the material.” While I have some experience, I never really “worked” with hardware and I also don’t even own a N64 console or even a cartridge. I never had one in my entire life. Only a NES and SNES are somewhere in my house. I repeated it like 300 times, but no one listens. “No u cum ash0le. im a fgt and i want hardware supp0rt na0” That’s what I often get to read. Really sad. ROM Hacking communities are dieing out and don’t really care anymore, indeed they just want to fap on their hardware which only 2% care about. You can be sure that every 2nd or 3rd ROM Hacker won’t give a fuck about hardware and just wants to finish his/her ROM Hack to be playable on an emulator. The rest is done by those who want to see it running on a console and sooner or later forcing the ROM Hacker to do it cause if he doesn’t he gains “negative reputation” or is a “bad ROM Hacker” etc. Communities like SMWCentral.net don’t accept modified emulators. Yes, cause we then would “force” people using one emulator. However, no one said that my emulator is a “standard” or even “forced” upon others. It’s optional and people can decide whether they want to use it or not. And it’s definitely a good option if you’re creating a bigger hack as usual. The next argument I often get to hear was: “PJ64 code is totally instable and people would have to use your modified version to get even further extended RDRAM.” This is not exactly true. If anyone took a look at PJ64’s recompiler code and has some knowledge, you would quickly realize that the code is pretty stable and can be considered conformable to people who just want to play ROMs and don’t intend to hack or program a plugin. The next thing is, that I actually said that I also do the same with the newer, more accurate and better (and that’s true, I admit) N64 emulator, called Mupen64++. I’ve got the extended RDRAM successfully working in there already and didn’t experience any errors so far with all ROMs. And the MP64++ code is even better than the PJ64’s one. So, still any counter-arguments? No? Good.

So, what’s with this strange sexual addiction to hardware? I seriously have no idea. Personally I don’t see a point for trying to get your ROM Hacks running on a the hardware, except for if I want to look “how it looks like” and that’s it. If it doesn’t work or crashes on hardware, well so be it. I don’t invest my time to get it working if only 1% of people test it out for “how it looks like”. People like to play on emulators more often anyways. Trust me on this, especially when older generations don’t own these consoles anymore and/or when newer generations never actually had one.

If you’re also one of my kind, who thinks that it doesn’t matter whether you play ROM Hacks on Emulator or N64 and most likely would prefer the emulator over the N64, then I guess this community is true freedom for anyone of you:
http://origami64.net/

This is a very nice, friendly community, which doesn’t disallow emulator modifications and is open minded for anything. It’s also a forums which doesn’t keep endless question topics in their forums which only spam the forum like it’s done in this place:

Origami64 is definitely your choice, if you’re searching for a neutral, competent and serious community as well as staff. We’re not like those oppressors who keep denying facts even if you have inevitable proof and evidence. And we obviously don’t make up useless rules for useless reasons like you can see above in the picture. (“If question topics are deleted, new people wouldn’t find SM64 Hacking Forums anymore.” Haha, this is classic!)

Here a little preview of our new beautiful, true utopia:

http://i.gyazo.com/c0fc9f3f62ea716b9a1e91bdf63aab24.png

What a nice place, isn’t it? Well, then join us and see more!

CajeASM v7.0 (Development Updates)

Recently I’ve been working on CajeASM v7.0. CajeASM is going to be completely re-coded once again. Currently it’s really fast and efficient and I completely re-wrote the command line parser, as well as the lexer and parser rules for my assembler. The visitor code and listener code has also been re-written and CajeASM v7.0 is currently able to assemble in little-endian, big-endian and middle-endian (or byteswapped). I didn’t consider this before, which is also the reason why CajeASM didn’t work for ROMs which had a different endian format other than big-endian.

CajeASM v7.0 is also most likely to get the disassembler (GUI) and a few new assembling features like writing .word/.float/.byte numeric values and including binary files by .incbin “binfile.bin”. Expect some big stuff.