I've been pretty vocal about my problems with Sonar obliterating plugin settings, having lost countless hours of work because of it. Recently it's been Waves Q10 EQ and Waves SSL Channel, although I've heard other people mention different plugins. I recently discovered that it does the same thing to FabFilter Pro-Q 2 as well - sometimes completely resetting the plugin, other times doing something like resetting my high and low pass filters while leaving the bells untouched. 
 
Now it didn't do this ALL the time - sometimes a project would load with all settings intact, but most of the time either all of the plugins or a select few of them would load without their settings. Because of this, it's really hard to pin down a cause (although I'm sure the Bakers could have figured out ways in which it could happen if they'd really pulled out all the stops). 
 
So I've tried various things without success but yesterday when I was racking my brain trying to think of ways in which Sonar could be telling these plugins to reset themselves (if that's what's happening as opposed to Sonar simply not saving the settings properly with the project file), it occurred to me on a whim that perhaps the problem is that these plugins are configured as tempo-based effects by default. I'm guessing that when they are configured so, Sonar will be passing data to them about the tempo and the song position, and perhaps somehow this data has been sent incorrectly or is ending up in places it shouldn't. 
 
This idea was partly fueled by someone else who was experiencing the same problem as I used to with the Quadcurve EQ, and he said that he actually saw it happen in real time when he was clicking to position the playhead in various places on the timeline. So there's one clue that playhead position data could be causing problems in plugins. 
 
Anyway I unchecked "configure as tempo-based effect" for FabFilter Pro-Q 2 last night, and I loaded a problematic project this morning and found that all of my Pro-Q's were intact with their settings left alone. Too early to say of course and I'll have to observe things more over the next few days but just wanted to report this slight glimmer of hope!

Excellent detective work. scook will often show people that you need to go into the settings menu on plug ins and make sure the settings are to your liking. Most people are unaware that plug ins all have settings. 
 
I'm fighting with Air VST's not maintaining pre sets. 
I think I'll see if they have a forum. 
The worst is the Mini Grand Piano the Reverb gets cranked to MAX. And the patch keeps reverting to the wrong patch ignoring the track inspector settings. The DB33 is the same issue. 

Cactus Music
 
I'm fighting with Air VST's not maintaining pre sets. 
I think I'll see if they have a forum.

I have found two sources of wisdom (ha!) regarding AIR plugins.
 
http://community.airmusictech.com/airmusictech
 
http://www.kvraudio.com/forum/viewforum.php?f=265
 
The former is moderated by staff from the company, that offers some how-to info, and there is some user to user help.
 
The latter does not have much traffic, but Simon Bangs, inMusic Brands, software Brand Manager occasionally checks in.
 
In either case, if you have a real technical issue or bug to report, you will usually get referred to tech support > http://airmusictech.com/support

Thanks John, I posted a question on the community forum waiting for answer.. Have you had this issue? I know you use these same VST's. 
It's very odd as the Mini grand goes to the Ambient patch with the reverb on almost full. 
These are my own from scratch midi tracks with no extra data anywhere in the projects. 
 
I tried making a custom pre set and setting the inspector to NONE for bank and patch. 
I tried putting the bank and patch in the track inspector. 
Changing channels. 
It seems to be a bug but I don't see anyone else complaining. 
And the DB33 won't stay on the patch I assign to. 

Yup, that's a weird one Johnny!  I have not experienced the bug you have described, but I have heard at least one other user mention it, with patch selection being offset by one on recall.
 
My only thoughts are that the VST may be reacting to some MIDI event buried in the track events somewhere, but I dunno why that would be?

I don't know if anyone remembers but recently I posted a video showing a phenomenon I discovered whereby if you turn the ProChannel
off and then adjust a parameter on the Waves Q10 plugin (for example) in that ProChannel, turning the ProChannel back on would change that parameter again. I posted a video of it happening. I'm not sure how this relates to any of the above, but it was a demonstration of how Sonar appears to pass stray signals to plugins under some circumstances.

I've also experienced a lot of cases of MIDI being thrown around a project erroneously. For example, the MIDI created by plugins like Jamstix can end up where it's not supposed to, and I've even seen cases where toggling mute or solo on a track can trigger a synth note on a completely unrelated track. Sonar definitely has some issues with stray MIDI data.

And I think that if that was the case, some VST plugins may be more receptive to stray data than others, so YMMV...

I don't understand the ins and outs of the VST standard but I do find it curious how this problem has seemed to disproportionately affect EQ's (I've had Sonar destroy settings for 4 different EQ's so far). Is it that the VST standard has common ID's for certain common plugin parameters, like frequency and gain? So that for example the Waves Q10 and the FabFilter Pro-Q share parameter ID's?

Well after a couple of hopeful days in which it looked like this "tempo based effect" thing might be a solution, it appears not. I just loaded a project in which all of my Pro-Q 2 plugins have been reset to default. I give up. Sonar is unusable. Whomever buys this thing has an uphill struggle on their hands. 

HI:)
 
I found out that if you save a preset of a plugin, you have to save it twice for really saved.
If you just save it once, at next start your preset is not there anymore....
 
Bassman