studiodude1
Craig : Just setting a simple restore point will take me right back to X3b? Awesome! I wasn't aware that it would be that simple. Thank you.
Vastman : Are you saying that X3c is Heaven on Earth?

When I put in the patch for 3B, I had several crashes. I did a restore back to X3A and it was all better. I didn't try a reload of 3B since I knew 3C was coming. With all the problems I have read about 3C and the fact that 3A is working just fine for me, I'll monitor the forums until the dust settles.
Having a blast with X3a!
 
Walt
 

X3 made major improvements and fixed some major bugs, too.
 
X3a/b/c were mainly to fix bugs found in X3.
 
What I’m looking forward to in X3d is MINOR BUT IMPORTANT improvements, with some more fixes. I still don’t understand why muted MIDI clips have to appear in the track when the lanes are collapsed. Also, I’ve found a serious color-coding bug in X3. If you select multiple MIDI clips that have different foreground and background colors and then change the background (or foreground) colors to a desired color, the foreground (or background) colors also change, to one of the colors of the clips. This may not be important to you, but for someone like me who use tons of linked MIDI clips with different colors, this is a PITA and I’m hoping it will be fixed in X3d. I reported this to support the other day and the ticket has been submitted to development. 

No... don't do it... wait for the "G"od patch! 
 
I would just say that since starting with sonar back in the "5" days, X3 is pretty much how I'd imagine heaven to be, if there were a heaven, which there isn't but I will say that what's godly or heavenly is in the eye of the beholder and you'd have to be blind not to "see" the awesomeness of their latest incantation...
 
If you wait till next year, i'm sure it'll even be better... guess that was my snarky intent...

im enjoying C fine.
don't know what all the hub bub is.

mudgel
As for the logic that one forumite used; it worked with the last version so it must with this current one. Well that's a myth that my personal experience well and truly debunked. It's just false reasoning. Sometimes a version release will just expose weaknesses in your hardware, OS combination etc that previous versions didn't.

Every PC system is custom-made and unique; hardware drivers are not perfect; whatever the origin of the problem is, Sonar gets the blame when it crashes. So it's up to the developers to get it as stable as possible, even if the things it depends on behave badly sometimes.
I reckon that sometimes previous versions could cope better with driver deficiencies due to more testing and solid internal error handling.
 
Edit: If you are selling upgrades, you must ensure that systems that worked, continue to work ...

X3c is working fine here. 

X3 "vanilla" was flawless for me up to X3(C)...
 
I'll be uninstalling it completely today and reinstalling to see if it helps. If problems persist I will cease work in X3 until X3(d) is released.
 
X2a continues to run perfectly on the same system.
 
My X3(c) issues are documented here http://forum.cakewalk.com/Exceptionally-frustrating-X3c-experience-m2923620.aspx#2924033
 

X3c is working great for me. In general this version of Sonar has been the most productive update I can ever remember going through. When I installed X3 I patched up to X3b right away and never had any major issues with that. All I've really been doing in X3b and X3c is extensive tracking and only light mixing using 99% PC plugins and even then it's not often. We've been doing most of our EQ by moving the mic.
 
My track counts are passing the 30+ at 96k and I've never had my system working this responsively this far into tracking. I push play and it's almost instantaneous. For some tracks recorded by the console I can hear the mechanical click of the record button coming back up at the very beginning of the wave file when I roll from full stop.
 
I have seen some threads about certain plugins not totally working yet but since I'm not into mixing at the moment I haven't been putting any UAD or waves plugins into the projects. I haven't had time to open any old mixes to see if they're jacked up or not.

I had to rollback to X3b. When I installed X3c it messed up all my plug ins lists. It renamed dll's (lord knows how), totally messed up my Waves VST3s ( I could only load one instance of a Waves plug in. If I tried to load another one my PC crashed ). X3b was working fine for me anyway so I am happy. But I have to say, I have used Sonar since Sonar 5 and have never had such a massive nightmare with an update. I am no expert but it seems some people have had no problems with the update and other people have had a shizz storm, seems fairly random. My PC was completely fine and stable before the update and a random headless chicken afterwards. How can it be explained that when I open T-Racks CS Standalone (yes standalone) after the update, it messed up my soundcard (Roland Quad Capture) drivers to the point I had to uninstall the drivers and reinstall them? I tried it three times with the same result each time. When I rolled back to X3b I have had no such problems since. Very weird. For the record my Trillian Dll was renamed Florence ( I am not joking). I obviously did a very in depth virus check with Malwarebytes and spybot with no negatives. Like I said, none of these discrepancies existed before I updated to X3c and now no longer exist with the roll back to X3b. I wish I could be more helpful to the guys at Cakewalk and try and explain these random goings on, it might help them. I will be waiting until a stable update before I update again. X3b seems to run fine for me. Good job we don;t have to pay for updates.

X3c is working fine for me. I'd say go for it.