Jump to content

Two cdlc packages will not work together, only one of them


Recommended Posts

Hello,

I have created two packages. I wanted an audio track with and without lead guitar, so I found a backing track I wanted to use in the second package. I have generated all the files I need for Custom Song Creator and used 2 different *.wem files for each package. In the song creator I generate one package, replace wem file with the new one and change the song names and generate another package, so that the arrangements and other files are same in both packages. Now each package works fine when adding it into Rocksmith DLC folder separately but when having both in the DLC folder, only one package appears in the song list. Package A is listed only if package B is removed from the DLC folder, they are never there both.

I thought that changing the DLC name or Song title in the song information will help but it does not work for it.

These are the two packages which won't work together:
http://www.mediafire.com/download/ryg52bo5j3kc8jc/Joe-Satriani_Always-with-Me-Always-with-You_p.psarc

http://www.mediafire.com/download/ktcy7a0a7ag263f/Joe-Satriani_Always-with-Me-Always-with-You-backing_p.psarc

 

Can someone check and advise, please?

Link to comment
Share on other sites

  • Developer

I changed the DLC keys to "JSAwMAwY" (from "joe-satriani-always-with-me-always-with-you") and "JSAwMAwYbacking" (from "awyawm-backing") and regenerated them and they both show up in my game.

 

I'm not sure what the actual problem is. Maybe a developer of the Toolkit knows.

Link to comment
Share on other sites

  • Administrator

The problem comes from the fact the the Arrangement ID haven't been modified between creating both psarc (likely because you change everything except the arrangement) making RS incapable of displaying both at the same time cause he can't identify them correctly.

 

The last few version of the toolkit should ask you if you want to regenerate the arrangement ID to avoid those conflict. You can always correct this by removing the arrangement and adding them again which will generate new ID.

Firekorn's workshop
In Flames Discography

#FirekornHasDoneNothingForTheCommunity

Link to comment
Share on other sites

  • Developer

@richardholly

The problem is that your two CDLC have the same Persistent ID.  CFSM has a Duplicates finder feature which will even tell you which CDLC have the same Persistent ID.  In CFSM Duplicates menu click on 'Select SongInfo/PersistentID' in the lower right corner of the GUI to see which songs have the same Persistent ID.

 

As, firekorn has pointed out, when the toolkit prompts during package generation ... 'the song information has changed.  Do you want to update the 'arrangment identification'?" Be sure you answer 'Yes'.  If for some reason you don't get this prompt then just change the song version information in the toolkit Package Creator GUI before generation and you will then get the prompt.

Are you tired of AV False Positives???  Now accepting donations on my website (Click Here)  Your donation will be used towards buying a code signing certificate.   CGT is now compatible and safe to use with Rocksmith® 2014 Remastered ... 

 

Latest Build of Custom Game Toolkit (CGT) w/ Game Save Gigbox       Latest Build of Rocksmith Toolkit       Latest Build of Customs Forge Song Manager (CFSM)

 

All bug reports and help requests please include your: OS, CPU, AV, .NET Framework versions along with a description of the issue (include screenshots of error if possible).  It should go without having to say ... make sure you are using the latest build before submitting bug reports or asking for help.

 

*  Remember to use your magic words (please and thank you) if you would like a response.  Don't use phrases like 'thanks anyhow' as it is demeaning.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Privacy Policy