Jump to content

Aquilae

Member
  • Content Count

    121
  • Joined

  • Last visited

Everything posted by Aquilae

  1. Thanks again for the help @@raynebc, @@Rockfirstlast. The custom I was working on for this topic is now complete. Metric - Blindness.
  2. I've had it pop up in a few weird locations. In one example I had removed all of the handshapes in a difficulty level since they no longer had more than one note. The editor gave me that error when I tried to save. I looked through the difficulty levels and came back and then re-saved and it no longer gave me the issue. I couldn't track down or re-create the issue, unfortunately. It would be nice however if the editor would shift the view to the beginning of the handshape in question, much like it does with fret hand position errors.
  3. Also regarding Handshapes, I've recently seen a few errors when saving along the lines of "Handshape can't be matched with chord template" but it doesn't seem to offer any help tracking down which handshape is causing the problem, other times it seems to solve itself.
  4. Yeah, I think that would be helpful. Currently I just manually add an extra ghost note somewhere in the handshape. It works but takes extra charting time and clutters the file up a bit, plus ghost notes still 'click' or play if you have midi notes enabled which can be a little annoying.
  5. http://i.imgur.com/zTDAQI2.png So this is what I'm looking at. The pink lines mark the handshape boundaries, and the little text inside is the handshape for that box. When building these handshapes I would extend the note sustain all the way to the next note, create the handshape, and then remove the sustain. This gave me handshapes that reached until the next change. The green arrows mark ghost notes that I had to add in order to fill in those handshapes where only one note was played in that shape. These notes did nothing in-game but allowed it to save and export without any issues.
  6. Sure, I'll post some examples later when I get home.
  7. I was using ghost notes to retain the correct handshape when moving other fingers around. In this song you have to anchor a finger on a bass note and let it ring out while adding or removing fingers on another string. Some of the notes are only played once before moving the finger again, so the ghost notes allow me to keep that handshape marking on the board and show that finger staying in place.
  8. Trip report with the new handshape changes: It works pretty damn well. I had to chart some extra ghost notes to get things just right but hopefully the result in-game will be worth the extra effort for charters. The only graphical hitch I've noticed is moving from a single finger to a barre requires the game to remove the single finger graphic before placing the barre graphic on that same finger causing it to look a little flicker-y compared to the other fingers. This is just how the Rocksmith graphics are going to work though, nothing any of us could do I think, unless it was possible to ma
  9. Right, good point there. Thanks for the hotfix again, raynebc, you're a champ. I'll try to play around with my project more tonight and get something worked out.
  10. I'm playing around with the latest hotfix. My lead guitar part will now compile without errors, but my rhythm and bass charts still fail. The XML errors point to a handshape bracket in each chart that end with a /, though neither of the chart have handshapes charted. The error'd ones never contain any information either: <handShapes count="0"/> </handShapes>I'm guessing that / shouldn't be there on the first line. A few side comments: I noticed in my project that if a handshape crosses the boundary of a phrase then in-game the handshape will cut-off when that phrase starts.
  11. Great to hear. I'm getting an issue with compiling anything now but I've posted that in the EOF topic itself.
  12. Looks like you might have an issue with handshapes somewhere, the XMLs are failing to load or compile in the toolkit and it looks like this may be the cause: A closing handshape bracket is added before each handshape in the arrangement. </handShapes> <handShapes count="13"> <handShape chordId="9" endTime="132.694" startTime="124.922"/> <handShape chordId="4" endTime="137.249" startTime="133.497"/> <handShape chordId="5" endTime="141.803" startTime="137.784"/> ... etc ... </handShapes> This is being added to
  13. In the webm I posted earlier was a result of my stretching out the handshapes in EOF with sustains, so at least in the editor it looked like one unbroken handshape but it exported as you see it in the video. I'll play around with the ghost note technique to see how that turns out. Out of curiosity @@Rockfirstlast what did that example look like in EOF?
  14. Yeah, pretty much exactly that. I'm just trying to make it look as clean as possible and clear what the hand is supposed to be doing since in this case the bass note is supposed to ring out the whole time. Otherwise players may try to play it like a riff with individual notes.
  15. What you posted works to a point, the 5-9 section works though the highlighted handshape bar seems to get gaps in it instead of matching the duration marked in the editor. The 5-5 part still has issues though since it is only a single note. Maybe this will help: http://www.gfycat.com/LameRevolvingHoki
  16. Since the note has no sustain it created a handshape that only lasted a few frames before disappearing. EOF would also give me the warning "At least one arpeggio phrase doesn't contain at least two notes. You should remove the arpeggio phrase or add additional notes into it." But these are handshapes phrases and not an arpeggio phrase. I tried adding a sustain before marking the handshape and then pulling the sustain off so the handshape would have a duration to it but that didn't seem to help either.
  17. I've got a question about how to author handshapes in sections where fingers are added or removed from a chord. Im my case I have arpeggio-like sections like a 5-7 where the bass note is left ringing out while the note on the next string is strummed. Marking a handshape as-is works fine for this. However, later in the riff a finger added to play 5-9 or pulled off to play 5-5, and I'm not sure how to author the handshapes to properly support this. Each individual note has the correct fingering applied to it. http://i.imgur.com/ET8xyhR.png In this case the added/removed note is only played
  18. Thanks. Latest beta once again allows me to import tones from my older package template files.
  19. This must be the issue I'm having. I recently updated the toolkit and now whenever I load any of my old project files the tones are all gone, only one tone named Default in their place. This is a massive issue for me, so I may need to revert to an older release until this issue is fixed.
  20. I think I may have tracked down an issue with the XML export for tone changes. I'm using r1417. EOF will save tone changes to the XML file in the order that they were added to the track. If these were not added in sequence it will cause the tone changes to fail in Rocksmith. Example from my XML: <tones count="6"> <tone time="93.222" name="MetricHelpImAliveChords"/> <tone time="125.627" name="MetricHelpImAliveReverb"/> <tone time="175.247" name="MetricHelpImAliveChords"/> <tone time="207.652" name="MetricHelpImAliveReverb"/> <tone time="
  21. Ghost is out! Now I can play some Dark Souls 2 without that hanging over my head!
  22. I gave the update a shot and it looks like it works now. Great! Thanks for your help.
  23. The great news is that the last beta update of the toolkit fixed capo support so I'll finally be able to finish Ghost. I'm at work right now but I hope I'll get it out sometime tomorrow.
×
×
  • 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