Closed GoogleCodeExporter closed 9 years ago
OK, I want to do this with ALL my pro files. i.e. combine the PRO files into a
new CON file. You have oversimplified this, so let me review your steps so I
understand:
1. Take the CON file without PRO injected and extract it. (songs.dta, song.mid,
song.mogg, song milo.xbox, song_keep png.xbox). There should also be a
directory structure, not just the files.
2. I assume this means "complete your PRO upgrade file in the ziggy editor"?
3. I am not following this step at all. I am using v65. Are you stating that on
the TRACK EDITOR tab you should DRAG the completed pro tracks from the PRO side
over to the 5 button side? Or are you saying to drag all the 5 button tracks
over to the PRO side?
4. Do you mean "create a new CON package" from the Song Library tab?
EvinC wrote:
Just a little addon:
I've had weird experiences with customs and custom upgrades, where the song id
would match but the upgrade wouldn't show up in game.
Looking at a custom upgrade from C3 showed me that you can actually put the pro
tracks in the original midi and you don't need an 'upgrade'. The process I use
is -
1) Extract custom song into its bare parts
2) Make upgrade
3) In Ziggy's newer versions, you can merge a pro midi and a 5tar midi, it
helps a lot so using that simplifies a lot.
4) Repackage with the merged midi
Also you have to make sure to add lines in the songs.dta for real_guitar and
real_bass so that they don't show NO PART in game.
Original comment by columbo...@gmail.com
on 17 Jun 2013 at 6:55
I think if you DRAG the CON into the editor to start the process, and it has a
non-numeric SONG ID, it should visually flag that you did this and allow the
option of BUILD producing a new CON and/or the PRO upgrade.
Original comment by columbo...@gmail.com
on 19 Jun 2013 at 1:32
Original comment by columbo...@gmail.com
on 25 Jun 2013 at 2:50
This is no longer needed with the C3con tool which does and excellent job of
bundling, even correcting for the wrong songid in updates.dta
Original comment by columbo...@gmail.com
on 1 Apr 2014 at 5:26
Original issue reported on code.google.com by
columbo...@gmail.com
on 17 Jun 2013 at 6:52