Complete "How to Change the Music in MVC2 + How to make your game selfboot" Thread

[System_1]

Anyone down with posting up a zip of their PLxx.bin files similar to what was on zacks webpage? Im not a h4x0r like you dudes to edit palettes

[fobi0]

Re-clarifying Storm edits, but not dealing with Hail, etc:
So, for each color you want to edit for Storm:
LP: edit Extras 19-1b
LK: edit Extras 1c-1e
HP: edit Extras 1f-21
HK: edit Extras 22-24
A1: edit Extras 25-27
A2: edit Extras 28-2a

Probably want to just add +6 luminance each time.

edit: fixed per eidrian

So all I have to do with Storm is to add luminance to those extras and that’s it?

[Big3D]

So all I have to do with Storm is to add luminance to those extras and that’s it?

yes that all

[Preppy]

Anyone down with posting up a zip of their PLxx.bin files similar to what was on zacks webpage? Im not a h4x0r like you dudes to edit palettes

But that would mean that you would be forced to have all of that person’s colors, which seems like overkill… learn to copy the palette strings and you can be happy easily. :tup:

[fobi0]

One more quick question regarding Storm.

Say I edit 19-1b for LP. Do I add +6L to all three extras or just 1a and 1b or it doesn’t matter?

It’s probably really simple and that I’m just making it complicated, but I just want to be sure.

[eidrian]

One more quick question regarding Storm.

Say I edit 19-1b for LP. Do I add +6L to all three extras or just 1a and 1b or it doesn’t matter?

It’s probably really simple and that I’m just making it complicated, but I just want to be sure.

How to.

[Big3D]

One more quick question regarding Storm.

Say I edit 19-1b for LP. Do I add +6L to all three extras or just 1a and 1b or it doesn’t matter?

It’s probably really simple and that I’m just making it complicated, but I just want to be sure.

no the way its done is
19 normal +0 lum
1a +6 lum
1b -6 lum

[fobi0]

Ohh.

Alright. I got it now.

Thanks.

[System_1]

But that would mean that you would be forced to have all of that person’s colors, which seems like overkill… learn to copy the palette strings and you can be happy easily. :tup:

Im toooootally happy with that!

[BeaTs]

Ok, in regard to burning custom MvC2.

Does the audio.raw REALLY need to be burnt to the cd, before I do anything else in creating the ISO? I just want to create the ISO so I can burn any time later on, but in the instructions it says that audio.raw needs to be burnt to the cd first before I continue (after creating the dummy file, but before creating the ISO and putting the IP.bin) Is that true, and if so why?

[shoultzula]

Ok, in regard to burning custom MvC2.

Does the audio.raw REALLY need to be burnt to the cd, before I do anything else in creating the ISO? I just want to create the ISO so I can burn any time later on, but in the instructions it says that audio.raw needs to be burnt to the cd first before I continue (after creating the dummy file, but before creating the ISO and putting the IP.bin) Is that true, and if so why?

hmm I’m not a pro but I think I can help you out.

When you burn the .raw first, it allows you to get the msinfo value afterwards. That msinfo value comes in two forms, 11702 and 11700. That # is then added to different parts of the entire process before you come to the point where you have to create the ISO so its essential that you do that first. If you try to guess the msinfo value, you could fuck up the entire process and just end up frustrating yourself.

Follow the directions :rock: they’re there for a reason.

once you follow the directions properly and your custom actually works, you can just keep the ISO you created on your computer and just burn off of that.

[GOLDN-NZ]

man can’t wait for that the next palmod update!!!

anybody got some DL info on this :bgrin: ???

[Big3D]

man can’t wait for that the next palmod update!!!

anybody got some DL info on this :bgrin: ???

it will be worth the wait thats all i can say
look forward to amazing things in the future

[BeaTs]

hmm I’m not a pro but I think I can help you out.

When you burn the .raw first, it allows you to get the msinfo value afterwards. That msinfo value comes in two forms, 11702 and 11700. That # is then added to different parts of the entire process before you come to the point where you have to create the ISO so its essential that you do that first. If you try to guess the msinfo value, you could fuck up the entire process and just end up frustrating yourself.

Follow the directions :rock: they’re there for a reason.

once you follow the directions properly and your custom actually works, you can just keep the ISO you created on your computer and just burn off of that.

so is it just for the msinfo? because I’ve done it plenty of times before and it’s always been 0,11702…so technically THAT is the msinfo and I don’t have to do the whole audio.raw process again?

also I get a lot of problems…when I even do the shit right!!! lol I’ve finally been able to create a few burns of it…but there’s still random problems…like whenever I try to burn the audio or the iso, it just doesn’t work…and I have to close cmd and try again, sometimes more than once.

also, near the last steps, when you type in “mkisofs -C msinfo -V custommvc2 -l -o data.iso data” when creating the ISO…what is “custommvc2” and does it have to stay saying that or can I rename it?

because I tried making an iso and I put “mkisofs -C 0,11702 -V PsynalAudition -l -o PsynalAudition.iso PsynalAudition” and of course it didn’t work.

[eidrian]

Everything listed in a guide follows a process, you can’t randomly change something and expect it to work. The audio.raw is burned to ‘fake’ the inner data track the original GD-roms have, it is required to get it working. -V in the command line input is for ‘Volume Name’, the syntax is as follows:

mkisofs -C (x,y) -V (VolumeName) -l -o (destination and name for iso) (folder to load data from)

Of course you’re gonna get problems, especially if you don’t follow the instructions. They are written down for a reason.

[BeaTs]

Everything listed in a guide follows a process, you can’t randomly change something and expect it to work. The audio.raw is burned to ‘fake’ the inner data track the original GD-roms have, it is required to get it working. -V in the command line input is for ‘Volume Name’, the syntax is as follows:

mkisofs -C (x,y) -V (VolumeName) -l -o (destination and name for iso) (folder to load data from)

Of course you’re gonna get problems, especially if you don’t follow the instructions. They are written down for a reason.

but I’m not burning the ISO to cd yet, I just want to create an ISO. so the audio.raw process sounds like it’s not neccessary to that (though when I do burn, I shouldn’t forget it)

ok, yeah I though “Volume Name” could be named whatever just like the ISO name and “Data” folder could be changed.

[Preppy]

Sakura notes:
11 Extra - same as LP - for Kei
13 Extra - same as LK - for Kei
15 Extra - same as HP - for Kei
17 Extra - same as HK - for Kei
19 Extra - same as A1 - for Kei
1b Extra - same as A2 - for Kei
1d Extra - LP Dark Sakura
1e Extra - LK Dark Sakura
1F Extra - HP Dark Sakura
20 Extra - HK Dark Sakura
21 Extra - A1 Dark Sakura
22 Extra - A2 Dark Sakura

edit: updated per eidrian

[eidrian]

Sakura: Variant Data

[Deth-Scyanyde]

Sry but has anyone figured out the palettes/extras for Blackheart yet…I don’t have the time to check the entire thread if it was posted some time ago for I’m at work at the moment…

[shoultzula]

I need some help burning the TDCfinal v2

will this work with a 700 mb cdr if I overburn it?

Do i need to burn that audio.raw first, then burn the TDC.cdi?

:wasted: