Bias Amp 2 models' cabs not working
-
I purchased Bias Amp 1 and a few packs years ago. I was recently automatically updated to a locked version on Bias Amp 2. Now there are several amp models where the cabinet does not work. Pulling the cab down to the signal chain does not work. I found that I had to switch the cabinet to Open Back, which then popped up a warning a "Not Purchased" message. I click OK and I can add the cab to the signal chain. There are several amps like this now.
British 900 Clean
Hiway 103 Clean
Mini Duo Reverb
British Plexi 50w
British Lead 800
Hiway DR 103
'69 Super Lead
British Rock 50
RB 101B
SLO 100
Monster VH4
5153 MK II
Triple Treadplate
Mark IIc+
SLO SP-88I think I'll stop there. I purchased Amp 1 and don't mind the idea of paying for the additional Amp 2 features. But the upgrade is 75% of the full purchase price. Will I have to repurchase the packs for Amp 2? Are the amps from the packs I purchased for Amp 1 no longer available? I reset the app to see if that would clear the cabinet issue.
What I have purchased should still be working regardless of whether I pay to unlock Amp2, but it is not right now.
-
@kungfoolou We've confirmed that this might be a bug, we're looking into this issue now, it might need few more days for us to identify the root cause of this issue, we'll keep you posted on this, thank you for your understanding
-
@mike Nice work PG (No sarcasm) get those bugs!
-
How did it automatically update?
-
This post is deleted! -
@tannhauser The app store app does this.
-
@mike is there an ETA on this. I checked the 5/12 release and it is still loading models with the unusable closed-back cabs after a factory reset.
-
@kungfoolou We've found the root cause and fixed it, the fix will be included in the next BIAS Amp 2 update v2.0.3, thank you!
-
EXCELLENT
-
@kungfoolou said in Bias Amp 2 models' cabs not working:
@tannhauser The app store app does this.
What platform?
-
@mike Thanks for the update. Looking forward to trying Amp 2 again... for the first time.
-
It’s working as of a couple of days ago. Thanks PG for knocking this out. I did notice that it was 1 of the listed bugfixes too.