Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Parzival

Pages: 1 2 [3] 4 5 ... 46
31
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 28, 2019, 10:39:14 am »
Can someone post the US SYMs for the first 2 gens please? I'd rather not build from source atm...
32
We could probably find a way, with GBA ACE and such...

HANGIN' OUT
ON ROUTE 128
THE SAME OLD THING
WE DID YESTERDAY

NOT A THIIING TOOO SEEEE
BUT MY BFF ARCHIIIIE
WE'RE ALL ALRIGHT
WE'RE ALL ALRIGHT

HELLO KYOGRRRRRE!
byootiful.
33
Generation I Glitch Discussion / Re: Brock Through Walls addendums
« on: August 26, 2019, 01:35:45 pm »
You can't fight any of them as controls are disabled, it's stated in the video.


Probably, but I wondered as the MissingNo. was for a bad Oak path, not Pewter Museum. Thanks though.
OH. my bad.
34
Generation I Glitch Discussion / Re: Brock Through Walls addendums
« on: August 26, 2019, 12:12:45 am »
You can't fight any of them as controls are disabled, it's stated in the video.
35
you could technically use item 1/2 as well as it seems to be looking for a word and not anything larger.
36
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: August 25, 2019, 05:43:40 pm »
wonder if anyone's been able to replace the GBx Boot ROM on an actual console... if so, can they do the same with a modded bootrom? I'd love to have my Gameboy blindly continue regardless of Nintendo logo validity! (No, seriously...)
37
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 25, 2019, 05:39:01 pm »
unpopular opinion: steamroll the POPs in the end of the VBlank handler, use a JP to go elsewhere, then re-push, then after, pop twice and use your own RET.
38
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 25, 2019, 12:19:49 am »
Confused as to how you would go about doing something like this.
Step 1: Write routine. (Check if SELECT isn't held (using game's registers, not hard registers.) If SELECT isn't held, check if CD38 is FD. If not, do nothing. If FD, write 00 to CD38. If SELECT is held, write FD to CD38. In all cases, don't RET, JP to 0043. This'll make sense later.)

Step 2: Find enough empty space in ROM Bank 0 to hold routine and paste it in (0000 to 3FFF range, usually at the end of the bank, to the tune of 3FBA or so. Japanese R/G/B and all Yellow ROMs require you JR over RST vectors at the beginning of the ROM, running bits of code in between... ugh.)

Step 3: Replace JP instruction at 0040 with a JP to new routine, then immediately after your pointer, insert the old JP command.

Step 4: Test by attempting boot. If you see normal things on screen, your code didn't immediately f**k everything up.

Step 5: Get in game, hold SELECT, and try to WTW. On SELECT down (give or take a frame or SIX) walls should be no obstacle, and after SELECT is let up, after another frame or 6, walls should be impenetrable again.

Step 6: Repeat for, like, 20 more ROMs.
39
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: August 24, 2019, 01:51:24 am »
For fun and out of boredom, I calculated out how many (whole) 0x4000-byte ROM banks some common storage sizes would hold (all unformatted, as I'm too lazy or unable to find the formatted capacity myself):
Diskette 1 floppy: 14
360KB floppy: 21 (a few bytes shy of 22)
400KB floppy: 24
720KB floppy: 45
800KB floppy: 48
1.2MB floppy: 73
1.68MB floppy: 102
1.44MB floppy: 90
2.88MB floppy: 175
650MB CD: 39,673
700MB CD: 42,908
1GB storage medium (take your pick): 61,035
4.7GB DVD: 287,000
8.5GB DVD: 519,000
9.4GB DVD: 574,000
10GB storage medium: 610,352
17.08GB DVD: 1,042,500
25GB Blu-Ray: 1,525,878
50GB Blu-Ray: 3,051,757
100GB storage medium: 6,103,515
128GB BDXL: 7,813,000
200GB BDXL: 12,207,031
300GB BDXL (yes, really): 18,310,546
1TB storage medium: 61,035,156


that was fun

(note: BDXL sizes over 128GB are currently theoretical but will probably happen.)
40
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 20, 2019, 09:19:34 am »
The Japanese ROMs are quite a bit different from the rest, but these are the main points as relevant to what i'm doing:
1. There's no free space AT ALL in Bank 0 except between RST vectors (lovely)
2. RST 38 junps to F080 or some such??? Why?????
3. All other versions have their VBlank handler at around 2024 or somewhere in the 1000-1FFF range. Japanese versions have it in the 0A00-0B00 range.
41
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 18, 2019, 03:05:13 pm »
If anyone has any info on any international equivalent of the RAM address used (CD38), i'll see if I can make a similar patch for said language. Also, request patch ideas if you have them, maybe I can pull them off (a better RAM Corruption On Demand set is in the works at the moment, so it may be a bit.)

In addition to CD38 (as 'non-00 is wtw' address) being the same regardless of Red/Green/Blue/Yellow, it is the same internationally (JP, EN, FR, DE, IT, ES).
Sweet, i'll churn some out for those soon.
42
Emulation & ROM Hacking / Re: Pokemon ROM Hacks - WTW On Demand
« on: August 17, 2019, 08:32:08 pm »
Nifty! I'm not sure what I would use this for yet, but it seems like it took quite a bit of problem solving.
Especially in Yellow, yeah. Slotting code between RST vectors in ~8 byte chunks is a bit of a pain...
43
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: August 16, 2019, 02:08:23 pm »
yeah, MFT/FAT got corrupted. Your data should still be there, though, so copy your stuff off and reformat.

Thanks for the advice. Yes, going to try that when I can.
Might try TestDisk if you're missing data or can't copy some off, etc. before reformatting.
44
Emulation & ROM Hacking / Pokemon ROM Hacks - WTW On Demand
« on: August 16, 2019, 01:56:45 pm »
Finally figured out why my attempts to add WTW on demand to Yellow weren't working and fixed it, so here it is:

Walk Through Walls On Demand!

Hold SELECT to enable WTW. Simple as that.

These shouldn't change anything data-wise (so no glitch Pokemon/items should behave differently) but timing-wise things may have changed, so these may be incompatible with other hacks that hijack VBlank.
Included are IPS patches for Red, Blue, and Yellow, all US versions (for now :D ). These should ONLY be applied to "known-good" ROMs (eventually i'll make some utility or something to apply multiple VBlank hacks to one ROM with timing measurements and such automatically taken into account, but that's probably quite a ways away) so make sure you check DAT-o-Matic and match your ROMs to the listed "good" dumps before applying.

(Patches are attached to the post, if you're still looking for them...)

If anyone has any info on any international equivalent of the RAM address used (CD38), i'll see if I can make a similar patch for said language. Also, request patch ideas if you have them, maybe I can pull them off (a better RAM Corruption On Demand set is in the works at the moment, so it may be a bit.)
45
General Discussion / Re: The Glitchy Thread of Topiclessness (#3)
« on: August 16, 2019, 01:05:45 pm »
Finally got the WTW hack working, but on Blue (since on Yellow i'm super strapped for space and trying to slot code in between RST vectors is a huge pain in the ass) so patches for Red and Blue will be coming soon. Current bugs:
- Pressing SELECT at just the right time when jumping off a ledge pops the Start Menu, corrupts the player shadow (with text, probably due to the Start Menu) and softlocks as controls are disabled. This isn't a bug in my code, as it does literally nothing different in this situation, so I guess i've somehow exposed a bug in the game itself...
- Usual WTW issues (nothing I can do about them)
Modified code and its effects on what we do here:
- VBlank is hijacked via putting a pointer to my code before the usual VBlank handler's pointer.
- Some unused space at the end of Bank 0 is changed (as it now holds my code, kind of a given)
I don't think anything really draws from the unused area in Bank 0, nor the area holding the VBlank pointer, so it shouldn't affect much. The VBlank code running after might change something due to timing, which is something I can't actually help without just... *not* doing a hack...

Wonderful glitch files seemingly caused by interrupting copying to a memory stick.


yeah, MFT/FAT got corrupted. Your data should still be there, though, so copy your stuff off and reformat.
Pages: 1 2 [3] 4 5 ... 46