A brief PSA.  I just started working with 3.3 and it’s pretty great.  When I booted up my Apex Processor, though, the screen showed this: 

“Output Network Not Configured”

I expect to be able to touch the little I in the blue circle to get more info, but it didn’t work that way.  I’m a very pattern-based thinker, so the fact the console had never “said anything like that before” was very confusing to me.  Eventually, I called into tech support and they helped me realize two things, one of which is embarrassing:

1. I should have just checked the CIA to get an expanded explanation of the problem Eos perceived, because it instantly gave me the information.  The issue was I had some channels set to output to Artnet in patch, but I had Artnet turned off in Setup>Network.  This is a common work flow for me since I avoid using Artnet, but sometimes it solves a problem on set.
2. 3.3 now examines your network in a very different way than it has before.  The release video pointed out the much higher emphasis on your network, I just didn’t think it would suddenly care if I had a protocol turned off.

I’m sure this is the just beginning of really getting to know 3.3 and all the great new features it contains.  Along with the excitement of getting distributed processing, I expect I’ll have several more humbling moments like this one.  

Anyone already had an interesting discovery with 3.3?  Hit me in the comments.