sven450
Well, I just experimented with a new project, and now it is NOT working!  Same exact set up in a new project, same drum map, but now the solo of individual kit pieces is NOT working without soloing the midi track too.  THis is quite strange.  More to follow....
 

Since it's probably just MIDI and no audio in the project can post a DL link to the .cwp? I'll be happy to give it a try.
 
Or PM me and I'll give you my email address.

Sven I just tried a new project with the same drum map ad it works.
 
Then I tried a new project with a new drum map, made edits and it worked.
 
Wish there was away to look over your shoulder while you did it to see if it's something in your workflow that is different than mine.

are you all using the Sonar supplied AD2 map supplied here?
https://www.cakewalk.com/Support/Knowledge-Base/2007013364/Setting-up-a-Drum-Map-for-Addictive-Drums-2-in-SONAR-X3
 
I think maybe my lack of success is because I am using a template originally created in X3 when I insert my drums.  Maybe?  I'll try making a new setup from scratch and see if it works.

Oh Yeah!!! :) Glad this one is killed..

sven450
are you all using the Sonar supplied AD2 map supplied here?
https://www.cakewalk.com/Support/Knowledge-Base/2007013364/Setting-up-a-Drum-Map-for-Addictive-Drums-2-in-SONAR-X3
 
I think maybe my lack of success is because I am using a template originally created in X3 when I insert my drums.  Maybe?  I'll try making a new setup from scratch and see if it works.

Yup, tried that and it works too.

After much fooling around, I've figured out the issue:
 
By default when you let SONAR create audio and MIDI tracks for a synth, it inserts the MIDI track at the bottom of the stack. I've always personally felt that $h!+ should flow downhill so I've always created my templates with the MIDI track above the audio outputs. Well, guess what... this breaks the new solo functionality. Take a working setup with an audio track soloed across a drum map, drag the MIDI track to the top of the stack, and voila!, no audio.
 
Also, this implementation still doesn't let you solo MIDI tracks in the PRV and continue to hear audio from a drum-mapped synth, so for me it's not a full solution even if they get the track-order thing fixed.

brundlefly
After much fooling around, I've figured out the issue:
 
By default when you let SONAR create audio and MIDI tracks for a synth, it inserts the MIDI track at the bottom of the stack. I've always personally felt that $h!+ should flow downhill so I've always created my templates with the MIDI track above the audio outputs. Well, guess what... this breaks the new solo functionality. Take a working setup with an audio track soloed across a drum map, drag the MIDI track to the top of the stack, and voila!, no audio.
 
Also, this implementation still doesn't let you solo MIDI tracks in the PRV and continue to hear audio from a drum-mapped synth, so for me it's not a full solution even if they get the track-order thing fixed.

Me too , I always put the midi track above audio outputs :-) nice catch , brundlefly ! 
Made a little video http://www.screencast.com/t/9WYxvGfSFPX
All the best
Jan

I tried it on an old project with BFD2 as the drum synth and it works as described above - i.e. I can solo a kit piece from the drum map and this will be the only drum sounding.
 
This is without the Midi track being soloed.
 
I'll try dragging the Midi track to the top when I get home and report back.
 
They've clearly done some work on this function but soling any of the audio tracks does not solo the midi track, and neither does soling the midi track solo any of the audio tracks.
 
It's an improvement (for me) but falls short of perfection.

We'll look into it. There were quite a few updates to the synth solo behavior based on some lengthy threads on the forum. Also some old bugs with drum maps were addressed as part of us adding the VST3 multi MIDI bus support.

I always leave the MIDI at the bottom. It's just how I roll.