iminashi

I have been working on a new chordshapes.xml file that includes all the shapes from the old one (with a couple of fingerings changed), with many new common and not-too-obscure chords added. I've divided it into sections and added comments so if you want to find a specific chordshape, it should be a bit easier now. Testing would be appreciated. Let me know if you find a chord that gets a wrong/weird fingering or a common chord that doesn't get a fingering automatically. https://drive.google.com/file/d/1lBGYF3T39Ww5e1xAe6dp32jNA0aRtPM8/view?usp=sharing (Updated 2021-03-31, contains 159 chordshapes) Download the file (the download button is in the top right corner) and move it to the EOF folder, overwriting the old one. A few observations for raynebc: A chord using the thumb (0) doesn't get applied correctly. When asked to automatically apply fingerings, they are not applied to frethand-muted chords, though I think they probably should be. At least it would save me some time.

Couldn't you do it like this? Unpack the custom, edit the numbers in "DynamicVisualDensity" in the manifest file for the arrangement and then repack it.

I did some quick testing. One problem that's immediately obvious for not having an empty phrase at the beginning (doesn't matter if it's called "COUNT" or "default" or whatever) is that the first phrase will be invisible: http://i.imgur.com/AhUNnG0.jpg The END phrase controls where the note highway cuts off. The ODLC "Yasashiku Naritai" doesn't have it in the rhythm arrangement, and the note highway doesn't cut off as the song fades out. However, in the two tests that I did, it does cut off right at the end of the audio. Also, EOF gives a warning if there is no intro section, but that is not needed either.

Yep, same thing with handshapes.

There is a FHP defined at the middle of the arpeggio. This will break it. http://i.imgur.com/LnHC9IQ.png

Personally I don't see what would be the downside of that.

In "Painkiller" all those notes have the ignore status. The notes are completely ignored all right, the crux of the problem is this: Unless they are also marked as 'ignore', accuracy will not equal mastery. Which was not the case before Remastered. I've made a test case that has half notes <22nd fret and half notes >22nd fret, without the ignore status. Hitting all of the notes (though you only have to hit half of them) gives you 100% accuracy and 50% mastery.

"Holy Wars... The Punishment Due" has notes on the 23rd and 24th frets and they all have the ignore status.

So, the Remastered version changed something about how notes beyond the 22nd fret are handled. They seem to be automatically ignored, but unless they are also marked as 'ignore', accuracy will not equal mastery. Not sure if this needs to be handled in EOF or the Toolkit, but something should probably be done about it.

Unless you check "Preserve Existing Song Stats", CFSM will create new arrangement identifications for the CDLCs, which resets the song stats. But it also means that the arrangements will get new leaderboards, which will be different for everyone who does the repair.

I don't recall scoring 100% last week... or did the MIB erase my memory? :ph34r:

I should probably be doing something more productive, but here I am, trying to see if I can change the texts in the game. http://i.imgur.com/35RzBzc.jpg

The release date information for RS1 DLC and some early DLC (like Cherub Rock) is stored locally somewhere. I would guess the "metadata" file in the Rocksmith folder, but since it's a binary file I'm not sure. For newer DLC I think the information is downloaded from Ubisoft. You can take a look at it in the file "Rocksmith2014/Tmp/metadata.psarc", which despite its file extension is just a plain text file.

http://i.imgur.com/8y3D8PO.jpg http://i.imgur.com/3bAesLx.jpg http://i.imgur.com/qKXhk4q.jpg

I like "Moth Into Flame" better. http://i.imgur.com/UTSlnQa.jpg http://i.imgur.com/CQp82pR.jpg

Here's my sight-read for Metallica: http://i.imgur.com/NRPn9hH.jpg

A few tries on the guitar: http://i.imgur.com/pnkCRky.jpg http://i.imgur.com/yp52qRV.jpg

I went and bought a bass guitar as an early birthday gift for myself. I can now start filling my application for The Society of Basstastic Peoples. :P Not sure what's up with the mastery for Rize Of The Fenix, since I played it from start to finish without pausing. http://i.imgur.com/Bga7xcn.jpg http://i.imgur.com/xohcPC3.jpg http://i.imgur.com/2hclnpv.jpg http://i.imgur.com/LctuZHW.jpg

I came across that file too when I was looking through the files in the game. Probably should have made a post about it. :) Those are definitely(?) the characters that can be used in lyrics by default. There are some characters that I don't see in there, but that do work in artist names and song titles, for example: ŁŽ®‡

Haven't participated in a while. :ph34r: Sight-reads: http://i.imgur.com/RXccFJS.jpg http://i.imgur.com/r56OJ6r.jpg This one I have played before: http://i.imgur.com/iRBTFDD.jpg

Tried it. Seems to be fixed. Thanks.

I came across a case of notes going missing when using DDC in a custom of mine. I have isolated the part where it happens into a test custom: https://drive.google.com/open?id=0B_0HDnEbZi4PNzVDX0NDTXdvdUk After using DDC, the two slides (at 7.624 and 8.153) that come after the chords are missing. Also, the slide at the beginning of the next section (at 13.271) is not found at max difficulty, but it does appear at a lower level.

As far as I can tell, there is nothing wrong with the XMLs. The problem is with the tone names and what gets written into the SNG file. Because of the similar names, the tone is replaced for some reason. Tones named "StareAtTheSunL", "StareAtTheSunLe", "StareAtTheSunLea", "StareAtTheSunLead" get replaced with "StareAtTheSunLeadIntro". A tone named "StareAtTheSun" (or "StareAtTheSunC" etc.) gets replaced with "StareAtTheSunClean". For example: <tones count="6"> <tone time="32.589" id="1" name="StareAtTheSunLeadIntro" /> <tone time="62.106" id="0" name="StareAtTheSunClean" /> <tone time="116.544" id="2" name="StareAtTheSunDist" /> <tone time="290.36" id="3" name="StareAtTheSunLe" /> <tone time="385.405" id="2" name="StareAtTheSunDist" /> <tone time="445.571" id="0" name="StareAtTheSunClean" /> </tones> (PART REAL GUITAR XML) Becomes: <tones count="6"> <tone time="32.589" id="1" name="StareAtTheSunLeadIntro" /> <tone time="62.106" id="0" name="StareAtTheSunClean" /> <tone time="116.544" id="2" name="StareAtTheSunDist" /> <tone time="290.36" id="1" name="StareAtTheSunLeadIntro" /> <tone time="385.405" id="2" name="StareAtTheSunDist" /> <tone time="445.571" id="0" name="StareAtTheSunClean" /> </tones> (SNG file converted back to XML) Changing the tone name into something more unique makes it work as expected. The id="x" is just something the Toolkit writes into the XML when you generate a custom. I don't think removing all tone changes and re-adding them is ever necessary (at least it shouldn't be). You might need to remove and re-add the arrangement to the custom template if you edit the tone changes in EOF and that should make them work again. Except in cases like this. :)

I would, but I already went ahead and made the DD manually. :) It is the same issue that Berneer is describing, so it should be solved.