PC Plum

That's actually a bit of a large assumption "you overwrote it not erased it" :D The problem might be to do with the fact the tone change lies exactly on a new beat, bar and section/phrase. The must be some lingering data in the XML somewhere. Its just too much of a coincidence that when you started this project the intro tone was the main lead tone, and now you spearate them this problem appears. What I did was - Erase existing change to Lead tone at solo - Create a new tone change a few milliseconds prior to the beat/bar/section change using a brand new unique tone name - Save EoF - Open toolkit project - Remove all arrangements - Edit Lead tone name in the tones section to reflect what I used in EoF - Re-add the arrangements (which are now "fresh" EoF XMLs) - Build To be honest I jumped a few steps through laziness. If I had been more patient I would have did smaller steps to nail down the problem exactly. But hey, it worked :D I have a number of little quirks and processes when I make customs. Some people do not agree with me on some things, and others have other ways of doing things. Fully accepting that these statements may get hate mail... - I never ever make tone changes exactly on beats. I always seek to a beat, then move ever so slightly before it, then create the tone change - If I need to edit the positions or names of tone changes I generally erase all tone changes in my EoF arrangement, save the project (i.e. blank with no tone changes), then re-add them again. This does not take as long as it sounds and it removes a fair bit of doubt for me. I have ran into issues in the past editing tone change positions and names. Better to spend 5 mins re-doing some work than 7 hours troubleshooting eh... :D ------------------------------------------------- Edit In the lines you posted from the XMLs, mine has id=3 written in it. Is this because I used a unique name? Maybe because yours does not specify an id=n then the game gets confused. Also, it might be worth searching the document for "290.360" to see what else occures exactly oon that new beat/bar/section.

The problem is your EoF file. You did not erase the tone change to the solo, you overwrote it. Given that the tone change occurs on a brand new beat/bar/section, it is more than likely that the overwrite occured on an identical millisecond (to the nearest millisecond denomiator EoF allows) The game engages the intro tone at the solo (as opposed to the "Lead" tone meant for the solo), manifesting all your problems. There must be some lingering/conflicting tone change data in the XMLs produced by EoF. Can provide evidence if requested. Pretty damning stuff here though :D https://drive.google.com/file/d/0B2oZs0ta32KyTzhkUmtNZmlTTVk/view?usp=sharing They way I built the custom that tone change should have said "Lead" not "Low Output". The only tone with Low Output tag is the intro tone. And I know from experience that the intro tone and main lead solo tone used to be identical. I have subsequently built a working custom and have PMd you.

FIrst thing I noticed was your IntroLead tone is classed as "Lead" (in the dropdown box) and your Lead tone is also called "Lead". I would change one to be "Low Output" or something unique at least. I tried to make my own build using your files but with the newest toolkit rstoolkit-2.7.1.0-1fb0b831-win I get this error https://drive.google.com/file/d/0B2oZs0ta32KybVItNVFhRnhJOXM/view?usp=sharing and when I hit generate a second time I get https://drive.google.com/file/d/0B2oZs0ta32KySVRYZmx2VDVzZDQ/view?usp=sharing I think it has something to do with the .wems but I am not sure. Maybe @@cozy1 could shed some light? Its the first time I have tried to use this newest version of the Toolkit so maybe its unique to this version. I'll try an old one... Edit Yep, loaded up the Toolkit save using rstoolkit-2.7.1.0-835b0852-win and it generated no problem I'll pm you the .psarc (don't want to "release" something which isn't mine :D ) Basically I made sure all the tones had a unique tag (Distortion/Lead/Bass/Low Output etc etc). I can't actually test it until later when I am on my own pc.

Does the re-mark function not complete that task for arpeggios and handshapes anyway? I'm struggling to visualise what would be different from using a re-mark?

I never got to use any version on my alternate pc though. I dl'd #4 cause it was the newest at the time and it never worked.

Makes projects so much neater (you get the beat lines on the highway from 0 seconds), and for a while now I have been setting projects up so I can re-import on a whim. So many reasons to re-import over an existing beat map that I could not begin to list them all. Editing a gp file track then re-importing over your existing beat map, so helpful. Like merging all the "Lead" tracks onto 1 rail, and trying out different combinations and being able to re-import 50 times :) Just remember to delete existing tech notes too before re-importing! Enjoy :D

Its a Windows 10 update (or generic Windows update) that is causing it. Update #2 now hangs for me on my own pc when it worked flawlessly before. Update #4 version hangs on my alternate pc (which is also fully updated Win10 pc). Fix #7 now works yaaaaaaaaaayyyyyyyyyyyyyyyyyyyyyyyyyyyyy!!!!!!!!!!!!!!!!!!!!!!!!!! @@cozy1 - you've been a busy boy :D

A good start would be to insert 3 (probably 4) bars of leading silence to the gp file, save it again and import it again. But there is still a long way to go... You should watch some tutorial videos :D

@@SmellsLikeMonkey - can you not just double the bpm and use 46 not 92? I had a few songs where I needed more accuracy in a few places, so i would grid snap then change the 5 or 6 notes that needed changing, but if you working on a song with a lot of these notes then I could see where it would become nippy. There is also tolerance in arrangements for note hits in RS (few milliseconds and it still registers) so I tend not to get too pernickety nowadays, but when notes start snapping together it gets into the realms of impossible. A trick I used a few times - Import GP file to EoF at 120 bpm - Change bpm to 60 with "Adjust Notes" unselected - Change bpm to 120 with "Adjust Notes" selected Has the effect of doubling bpm while retaining accuracy. Using numbers like 120 and 60 makes the math easier for EoF. You can then change to desired bpm after.

From the outset it is NOT a "100% Mastery" bug, it's a "increase overall mastery by the coefficient you played in that run" kind of bug.

From the outset it is NOT a "100% Mastery" bug, it's a "increase overall mastery by the coefficient you played in that run" kind of bug.

100% Mastery, fried or baked? https://drive.google.com/file/d/0B2oZs0ta32KyMjdNVXBvaG1xUWM/view A good start to understanding me thinks.... I put this in Toolkit as I wanted cozy just to fix it :D

100% Mastery, fried or baked? https://drive.google.com/file/d/0B2oZs0ta32KyMjdNVXBvaG1xUWM/view A good start to understanding me thinks.... I put this in EoF as the simplest solution might be to write extra XML info.

I edited this post in case you read it... I now understand... For easy double stop bends you need some Bend=0 https://drive.google.com/file/d/0B2oZs0ta32KydXZaTjhoVXJXb2c/view?usp=sharing For complex bends try this https://drive.google.com/file/d/0B2oZs0ta32KyVWlMM0MwM2xSa0E/view?usp=sharing Enjoy :D

I have had many problems with bends on double stops. Can you post a pic of the EoF i.e. normal view in EoF and tech view in EoF of the same notes? Also, I often make new sections not on the main beat. But my priority is camera angle for non-DD songs, so I guess it does not relate to the problem here really...

I see I typed it to imply the played note comes after the unpitched slide :( I simply meant played notes onto unpitched slide at the end. I have made those types of notes hundreds of times and if I am going for outright score in a song then I generally hit the note again just before the unpitched slide to make sure it registers, especially if it has been a long sustain. I could see why Ubi would "ignore" them, they are for garnish and they want players to score as high as possible. I just watched quickly a couple of halsb's vids again, and I'm still not convinced the unpitched slides are scoring notes (at least the ones tagged onto the end of something else). But I've been wrong before, lets face it :D Edit - well I am right and wrong... https://drive.google.com/file/d/0B2oZs0ta32KyVm00aTRhWEUwWU0/view?usp=sharing I opened the official Purple Haze, and I found instances of unpitched slides being scoring notes and ignore notes (see pic). I guess they turn it on and off when they see fit. Most unpitched slides I seen were scoring notes to be fair, including ones tagged onto the end of other notes. But I knew I'd seen it in his vids where it does not register but he still gets 100%.

Watching some of them halbs 100% vids on Youtube, it's clear that Ubi use ignore status liberally on things like unpitched slides - especially if they are linked next onto an actual played note. I don't believe they hide the note or the note head, they just don't count as misses when they are not successfully hit. And the word "MISS" does not appear on screen. UK Looney used to make play vids by making everything "ignore status". He would let the chart play and not play along, but you would not get "MISS" on every note as they had ignore status. Example https://youtu.be/LtC3AlG_Yak Although he never let any go to the end to see how it effected the scoring :(

If you can play other custom songs fine on your setup then I'd suggest it was the cdlc itself. Download the toolkit and alter the volume of the tone yourself. Then re-build the custom and you're off. Granted, the first time you try this it might take a while. But if you stick at it and persevere, you can then change any custom to your liking in quite literally seconds. You can also change details, add DD and swap out tones altogether for your own favourite tones. Use the "Import" button on the front of the toolkit and point it straight to the .psarc

You don't need a monster pc either, I've ran rs14 on some pretty old and cheap laptops. It's not buttery smooth like a decent gaming pc, but its ain't half bad either :D

I cannot play the game just now to test it, I thought my .psarc would work. Maybe you did not use "Set Table Granularity to 16384" when you made the audio .wem? What Wwise are you using? Try to use 2013 version (you can download from Wwise website) and make .wem again. Make sure it goes 16384.

Can you play any customs? How many have you tried?

You made mess with FHPs. I think the game was crashing because RS could not display what you were telling it to display. You ignored EoF warnings? Try this https://drive.google.com/file/d/0B2oZs0ta32Kya0tQUFNFV2hWQm8/view?usp=sharing Enjoy :D

Look at the tutorial. A short explanation would be to think of the game having a zoom camera. It zooms in and out to accomodate the notes (frets) that it is playing at any given time. You can control this using simple tricks when building your custom(s). Sections control the zoom camera. Sections also control Riff Repeater. Look at the tutorial and implement the desired effect to your own taste. Using DD greatly enhances the zoom camera effect. Enjoy :D

Make the files public. We will look.

All this hassle and it ain;t even Jack Bruce on bass??? Aludog how could you :lol: