Jump to content

cozy1

Developer
  • Posts

    1,095
  • Joined

  • Last visited

  • Days Won

    1
  • Country

    United States
  • Donations

    0.00 USD 

Community Answers

  1. cozy1's post in Errors repairing (some) CDLC was marked as the answer   
    The first access error for RocksmithToolkitLib.TuningDefinition.xml is very strange.  If access is denied to that file, I would have expected this error for every single CDLC.  Plz check and confirm the access properties of the file.  The best solution would be to download the newest Beta of CFSM and try again.  Be sure you delete the CFSM folder in MyDocuments before reinstalling.
     
    The other errors are good (valid) errors.  You have CDLC that have real problems/corruption.  The error message explains exactly what the issue is with these CDLC.  The newest Beta version of CFSM will allow you to ignore the multitone error and convert the CDLC to a single tone.
     
    To fix Max Playable Arrangement (Max5) error you need to select this option in the repairs dialog along with 'Remove Bonus Arrangements'.
     
    To fix the vobis error you would have to reauthor the CDLC in the toolkit.  Something is wrong with the BNK file in that CDLC and it needs to be repackaged.
     
    Looks like CFSM is doing its job and found problems with your CDLC.  Now you have some options for how to handle.
  2. cozy1's post in CFSM Beta 1.2.7.9 was marked as the answer   
    Sheryl Crow Soak up the Sun is a LaceyB charted CDLC.  Start with an original copy of the CDLC.  You need to apply the Max5 Bug repair and check the box to Remove Bonus arrangements ... in addition to other repairs.  If you check the CFSM logs you will see that this CDLC gets flagged as a Max5 and moved to (.max) backups if you don't select the repair Max5 options.  Max5 Bug CDLC are known to crash the game.
  3. cozy1's post in CFSM 1.2.7.0 beta bug was marked as the answer   
    There was a Null Exception bug in 1.2.7.0.  Please try 1.2.7.2 when you can.
  4. cozy1's post in CFSM issues/questions was marked as the answer   
    Thanks for the report about inlays issue.  I will look into it.
     
    Your other CDLC are actually corrupt if reported as such.  The CFSM Log window at the bottom of each page reports details about what was corrupt.  (Click on 'Show Log' if  you are not seeing the Log)  You can find the parallel "debug.log" file in the My Documents/CFSM folder if you want to see the Log details again.  These are your options for corrupt CDLC:
     
    1) Continue to use your existing CDLC 'as is' and wait for it to break something
    2) Repair corruptions as indicated with the toolkit CDLC Creator feature
    3) Report corruption to CDLC charter and let them fix it
  5. cozy1's post in Disk space was marked as the answer   
    What is the full path to the temp folder on your OS?
     
    Found a bug in the cleanup routine.  Fixed it and implemented new feature to do a periodic temp folder cleanup during processing.  Let me know if 1.2.6.7 works for you now.
  6. cozy1's post in Beta 1.2.6.5 - Songpacks still not working for RS1 DLC was marked as the answer   
    I just check the latest beta release of CFSM.  I am unable to reproduce the error.  I think you may have a corrupt compatibility file.  Redownload it and try again.  This error "Object reference not set to an instance of an object" is the tip that your file is corrupt.
  7. cozy1's post in DDC bug with latest toolkit was marked as the answer   
    It may be that the CDLC you are trying to add DDC is non-compliant.  It looks like a multitab per the CDLC file name.  You will have to unpack and then manually select which xml arrangements to add DDC.  This is not a toolkit issue but a charter issue.
  8. cozy1's post in Drag and drop in DDC tab no more possible was marked as the answer   
    Please check latest toolkit beta and report back.  Thanks
  9. cozy1's post in Tone names containing an underscore broken in the latest build was marked as the answer   
    Fixed
  10. cozy1's post in Not moving into own folder was marked as the answer   
    Added file path name and file length validation to CFSM Beta 1.2.5.3, Renamer feature.  User will get a notification error message.
  11. cozy1's post in Not more "release notes" since 1.2.3.2 ? was marked as the answer   
    It's ok.  Release notes are updated again in 1.2.3.7.  Give it a try.  Thanks
  12. cozy1's post in UBISOFT Support was marked as the answer   
    Could be a PID (Persistent ID) conflict between ODLC and CDLC.  If you have two songs with same PID one of the songs may not show up in setlist or game may even crash.  Try as others have said to remove all CDLC from the 'dlc' folder.  For purpose of testing, you may just want to remove all ODLC and CDLC from the 'dlc' folder and only install the ODLC Good Charlotte song pack.  Also create a new clean game save (user profile) so that there are not any conflicts in the game save. 
     
    If ODLC still does not work then IDK.  Could be corrupt ODLC.  Re-download it and try again.
     
    You can check your ODLC and CDLC for PID conflicts with CFSM.
  13. cozy1's post in Thread Exception Catched! Error on Win10 was marked as the answer   
    Download and install this version of Audiokinect Wwise.  Make sure you are using 32 bit installer even if you have 64 bit machine.  After install make sure you run the Wwise GUI.  Once GUI is confirmed to run, close Wwise.  Open toolkit and change Configuration setting to point the the proper 32 bit Wwise installation path.  Post your followup success here.
  14. cozy1's post in Error when making Song Pack was marked as the answer   
    One of the songs that you are trying to put into the SongPack is probably corrupt.  Use CGT to find and remove the corrupt song before attempting to make a SongPack.  Or it could be that you have a Mac CDLC mixed in with your PC CDLC.  This will also throw an error.
  15. cozy1's post in Change tone problem was marked as the answer   
    See if this helps.
  16. cozy1's post in Two cdlc packages will not work together, only one of them was marked as the answer   
    @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.
  17. cozy1's post in Bulk Unpacker Batch file was marked as the answer   
    Try using:
     
    Packer.exe -u -f=Pc -v=2014 -i=D:\Program Files(x86)\RockSmith\dlc\some_p.psarc -o="D:\Program Files(x86)\RockSmith\dlc"
     
    You need to specify the -f and -v parameters if you are going to use the Packer CLI.
     
    Also have a look at the UnpackerCLI.bat and PackerCLI.bat files.  These may help you.
     
    Send me a copy if you end up developing your own cool batch file.
  18. cozy1's post in Commas in lyrics not transferring from EoF to RS was marked as the answer   
    I believe we confirmed and killed the issues with extended characters in vocals.  Both toolkit and EOF are working smoothly together now.  I have not heard of anymore reports of corrupt CDLC with the latest revisions of the tools.
     
    All you need to do is ask yourself:
    Do official DLC vocals contain commas?  Answer: None that I have seen.
    Do offical DLC vocals contain apostrophes?  Answer: YES
    Do official DLC vocals contain special characters?  Answer: None that I have seen.
     
    Just because you can do something, doesn't mean you should.  Just my two cents.
  19. cozy1's post in I can't do this stuff. was marked as the answer   
    @Raamie  You may want to repost your request in this thread.
     
    Not sure what you mean by you don't have the equipment to actually make it.  You can use any image editor to produce inlay artwork. 
     
    Here is is the DIY Inlay Tutorial.
     
    Here are ready made shared templates you can use to produce your own custom inlay if you don't want to or know how to use image editor software.
  20. cozy1's post in End of stream reached with 4 byte left to read. was marked as the answer   
    This is a followup with fix for this error in case any other users experience it when converting CDLC from one platform to another:
     
    1.  Go to 'CDLC Creator' tab menu.  Select 'Import Package', if import fails then go to Step 6 below.
    2.  Re-enter a valid Song Year, and re-enter valid Average Tempo information and change the Song Version to '2'.
    3.  Press 'Generate' button.   Acknowledge the 'Arrangement Identification' popup.  Press 'Yes' button
    4.  Go to 'Converter' tab menu, and set Source and Target then press 'Choose CDLC and Convert'
    5.  Select the CDLC and make sure it is Version 2 that you created above.  Wait for song to convert.
     
    Hopefully you do not receive any error messages (I didn't during testing).  Play the converted song.  Stop here.
     
    6.  Go to 'Packer/Unpacker' tab menu.  Checkbox 'Decode Audio' and press 'Unpack' button.
    7.  Go back to 'CDLC Creator' tab menu. 
    8.  Create the CDLC from the files you unpacked.  Essentially you will be repackaging the song.
    9.  Follow Steps 3 - 5 above to generate and convert.
     
    There are other ways to do this repair and conversion with the toolkit which you may have in mind and can attempt.  This method happened to work for me.  Let me know if it works for you.
  21. cozy1's post in Getting error loading package with latest release was marked as the answer   
    Give new toolkit beta/test release a try.  Should be fixed and I think you will be able to use your old templates again.  Plz let me know if it works for you.
  22. cozy1's post in Default folder for backup was marked as the answer   
    Follow the link in my signature and download the latest beta build of CFSM.  This feature was added long ago in 1.1.2.1.  We are now at 1.2.0.0.
  23. cozy1's post in Album art too big in-game was marked as the answer   
    @@RyanBurnsRed
    Specifically, which build revision number has problem and which is ok?   Thanks
     
    EDIT: Think I found the problem.  Will have it fixed today.
  24. cozy1's post in Song artist not accepting symbols anymore in beta builds. was marked as the answer   
    Done.  Check out newest beta build.
  25. cozy1's post in Not able to play song after using "Fix Bass Tuning" was marked as the answer   
    @@SickSonicXXX So part of the problem with applying Low Bass Tuning Fix was that the songs you are trying to fix were created with a older version of the toolkit which applied a different tuning storage method for Bass Arrangements than is currently used.  The old method would zero out strings4 and string5.  This meant there were no 5 string bass arrangements.  We have since moved away from this format and are now using standard guitar tuning to represent all instruments.  The new method has far fewer issues with in game hanging or CDT caused by tuning issues.  Also the same tuning definitions may be used for both guitar and bass.   I applied a fixed to the toolkit so that it recognizes old EOF/toolkit xml files and upgrades the XML tuning to the new method.  Download the latest beta version of the toolkit and give Packer/Unpacker feature Low Bass Tuning Fix a try on your songs.  (Note: If you are trying to play bass on a guitar the strings may fall off with Low Bass Tuning Fix.)
     
    I also fixed the Creator function which had the same tuning issue when old songs were imported.
×
×
  • 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