You are, have, or tried contacting PG on this? (because this looking 99% like an actual tech issue .)


One last hail Mary (and it's just a hail Mary) - exit BIAB, then DELETE the " DefaultDXiSynth.tgs" in the "x:\ …\bb\DX settings"

Next time your start BIAB, BIAB will rebuild it using the " Factory_DefaultDXiSynth.tgs" and then update with what it sees


some comments:

1. It's a very unlikely Sforzando had anything to do with issues with BIAB and it's ability to see DXi's because SForzando is a VSTi (so it’s as related as apples and rifles)

2. By having Forte DXi show up in RealBand (and it is RB 2017 correct ? not Real 2016?)- PROVES you have Forte DXi installed correctly. There is no reason BIAB can't "see it" so there is nothing you can on that front (Forte DXi ain't broke so you can’t fix it).

3. You can quit copying the " DXiPluginList.ini " file into BIAB's \bb directory because that idea was a "let's try that just for for grins because it's a million to one long shot." Besides, every time you do a "scan" for new DX's, that scan updates that file with what it finds, which appears to always report ZERO Dxi's .

Win10Pro,i9,64GB,2TBSSD+20TBHDDs,1080TI,BIAB'24,Scarlett18i8,Montage7,Fusion 8HD,QS8,Integra7,XV5080,QSR,SC-8850,SPLAT,FL21&others,Komp.14,IK suite&others, just a guitar player-AXE FX III &FM9T, FishmanTP, MIDIGuitar2, GK2/3'sw/GI20