I had rocksmith up and running for months with no problem using cdlc. Last week the debug console stopped appearing and the cdlc locks up the game either right after tuning or selecting play song if already tuned. I've tried everything I can think of. Using the rocksmith patcher with no luck. Also downloaded the .dll file everyone suggests. I don't have a original .dll file in the rocksmith folder to replace and putting the file in the root folder doesn't allow rocksmith to even launch. Tried overwriting the .dll file in my /system32 folder and no luck either. After that I installed the game on another pc and am having the same issue. The game does work fine with all official content and dlc and I do have Cherub Rock. From my searching for an answer this seems like a common problem. I've also been wondering if Windows or one of its components or settings may be blocking the debug console from launching...? but I haven't seen anything suggesting this is the problem and I lack the know-how to figure it out.
I am running windows 10 on the first pc and also installed it on a pc running windows 8.1.
Any insight or solutions to this problem would be greatly appreciated.
I had rocksmith up and running for months with no problem using cdlc. Last week the debug console stopped appearing and the cdlc locks up the game either right after tuning or selecting play song if already tuned. I've tried everything I can think of. Using the rocksmith patcher with no luck. Also downloaded the .dll file everyone suggests. I don't have a original .dll file in the rocksmith folder to replace and putting the file in the root folder doesn't allow rocksmith to even launch. Tried overwriting the .dll file in my /system32 folder and no luck either. After that I installed the game on another pc and am having the same issue. The game does work fine with all official content and dlc and I do have Cherub Rock. From my searching for an answer this seems like a common problem. I've also been wondering if Windows or one of its components or settings may be blocking the debug console from launching...? but I haven't seen anything suggesting this is the problem and I lack the know-how to figure it out.
I am running windows 10 on the first pc and also installed it on a pc running windows 8.1.
Any insight or solutions to this problem would be greatly appreciated.