Edit son_lzuw for labyrinth zone underwater pallete, and son_sbzuw for sbz3 underwater colours. It usually should be a bit darker than the original colours, but is mixed with the UW palette. So if most underwater palette in LZ is green, try getting a green shade to your character.
Branch offset </138> out of range at address... This is the error message I get when using the goggle monitor tutorial. Code (Text): Obj2E_ChkS: cmpi.b #7,d0 ; does monitor contain 'S' bne.s Obj2E_ChkGoggles ; if not, branch to Goggle code nop Obj2E_ChkGoggles: cmpi.b #8,d0 ; does monitor contain Goggles? bne.s Obj2E_ChkEnd ; if not, branch to ChkEnd move.b #1,($FFFFFFFB).w; move 1 to the goggle check Obj2E_ChkEnd: rts
Probably a stupid question, but would someone mind explaining Solid Angles to me? You know what it's like, when you have Sonic simply walking up a 45 degree slope with no problem. :P
I hate branch out of range errors... but you should check this thread out, it explains how to fix branch out of range errors I hope this helps. ^^
This should solve the problem. Thank you very much! I won't be tweaking on it again until tommorow evening so if I don't have any joy with this, I'll pm you if you don't mind? Code (Text): Obj72_Main: ; XREF: Obj72_Index addq.b #2,$24(a0) move.b $28(a0),d0 add.w d0,d0 andi.w #$1E,d0 lea Obj72_Data(pc),a2 adda.w (a2,d0.w),a2 move.w (a2)+,$3A(a0) move.l a2,$3C(a0) move.w (a2)+,$36(a0) move.w (a2)+,$38(a0) The line of error is the line directly below this, on an empty line.
I don't know why, but I'm unable to play the no flickies hack of Sonic 3D Blast without getting the blue screen of death on Kega Fusion. :/ The program also says the game is a bad rom. Has anyone else had these problems?
No, but I have had no problems with Fusion in the past and I don't know how redownloading the rom would help the situation. :/
Well, it may be a faulty download. Sometimes bits get lost in the download. Just re-download and see if it helps.
Gens alone is unsatisfactory. Gens/GS, on the other hand, is much more accurate to actual hardware than regular Gens. It's maintained by our very own GerbilSoft, and can be found in the community project section. I'd definately reccomend it. For your problem, however, I'd suggest re-downloading the ROM. I've had no problems loading the ROM in Kega Fusion in the past, so it must be a faulty download.
How do you change the size of a rom? I've cleared out some music tracks from S3K, and now I have all these 00 bytes that are taking up space. I'd like to get the rom under 3.5 megabytes.
The 00 bytes are padding. The MegaDrive can only read ROMs whose lengths are a power of 2. You could truncate the ROM, though. Most emulators will work fine with ROMs with incorrect lengths.
Mind telling me how to do that? Sorry if my words earlier are confusing, I'm so used to Pokemon rom-hacking. All I want to do is remove all unused bytes, thus changing the size of the rom.
Well, it will depend on your hex editor. I'm not sure of the quickest way of doing it, but in xvi32, you can simply go to the end of the ROM and hold down DELETE.
Stupid question time, but I thought I'd ask anyway. Why are there so few Sonic 3/S3&K hacks? Implementing new characters/palettes etc seem to be a constant thing for 1 and 2 but nothing for 3 If someone could either prove me wrong and provide links to some good sonic 3 hacks then that would be awesome. Also, I remember a little hack a while back that basically ported Angel Island and I think Ice Cap into Sonic 2, does anyone have this still?
S3K is a much more complicated game and we don't have the whole engine documented, not to mention S3K has a lot of character specific hacks and optimizations (shared mappings, etc.). Documenting everything will take time, but it's being done.
That's most likley becase there is no split disassembly like there is for S1 and S2. Even though there is a file that can be edited and assembled, it's bloddy huge of 12MB and only like 2% labeled and commented (however, the stuff which is labled, is good for people who want to port things, like the code for the elemental shields). Besides that, it seems that S3 is using a completly different engine when it comes to coding. Unlike the old games, there are multiple error exeptions instead of just one, which somehow causes problems. But yeah, once there will be a split disassembly, the number of hacks would go up, but it won't be a groundbreaking number like the other games for sure, as they are much more "explored" and easier to work with, well, at least for now. EDIT: Beaten by Andlabs. ._.
