Check out our timelapse of the "4th of July Pre-Party" event, working Potomac Approach's Chesapeake sector, here: https://youtu.be/FQAqoSGkGqs

Check out our timelapse of the VATUSA "Hidden Gateways" event from our vantage point at Norfolk Approach: https://youtu.be/_MjtmNj4cnQ

It's a couple days late, but, check out our timelapse from "ZDC Regional Night" featuring Raleigh-Durham (KRDU): https://youtu.be/AbzoOLJJTiE

"Never Dull at Dulles" AKA "ZDC Live!": https://youtu.be/FbhjuAkRsKk

Bold to see an FNO which didn't feature any of the same top-25 airports.  More typical of a weekday event.  But kudos for a really fun night.

There were a couple little issues (VATSIM-ims, maybe) with VFR handling outside of Bravo airspace, particularly among the S1s and S2s -- although, in the controllers' defense, I get that it's a topic that is covered in training and probably not well-exercised once out on the network.  Everybody was super cool and chill, and we got great service everywhere we went tonight.  Cheers!

I'm not sure I completely agree with the notion that most single-facility FNOs run fine.  But, I appreciate the response and the knowledge that the overall question of event design with acceptable versus unacceptable capacity is being considered.

On a separate topic, one additional thing I appreciate is the placement of "placeholder" events on the calendar indicating in general terms what FNOs are on tap.  For nutjobs like myself who literally plan what sorts of flights I'll be doing earlier in the month based on what events are coming up later in the month, it's good info to have.  Thanks sincerely for that.

To clarify slightly:
(a) the less realistic, more point-and-click software is called "VRC" not "VCR"; and
(b) *all three* of these are to be supplanted by the upcoming release of CRC.
With said release likely still being at least months away at this point, best course is to stay with VRC, vSTARS and vERAM for now instead of waiting for the software change.

VRC is the most common choice for beginning controllers, but some facilities are starting students on vSTARS which can be used for Delivery, Ground, and Tower services pretty easily also.  And I believe that vSTARS is the only one of the three which facilitates a proxy connection for a Tower View.  VRC definitely does not; I don't think vERAM does either but that one I'm not certain about.

Whichever facility you end up choosing and training with will advise whether they prefer you train on VRC or vSTARS, so, choose a facility and follow their Training team's guidance.  If you later wish to switch to another client once you're comfortable and familiar with how to provide ATC services at your desired level, that's up to you.

As someone who streams ATC and recently moved up from Tower to Approach / Departure, I can attest, as the streamer / controller in that situation it can be a really tough line to walk.

I don't know whether I'm one you've seen.  I do make an effort to be conscious of new folks and their knowledge gaps.  In fact I've long been one of the network's most vocal proponents for and providers of pilot training resources.  But sometimes "in the heat of the moment" it can be hard.  This past Monday I was working the APP/DEP sector around BWI and I had one in particular who, when told to Line Up and Wait, began rolling down the runway.  I didn't notice until I was watching the arrival come in on the crossing and saw him heading for the intersection.  When I reminded him what he'd been instructed, I was probably not very friendly.  But I also did not call him "stupid" or "goober."

There was one who (a) descended below the lowest altitude on his STAR, then when he got to the end of it, (b) turned from the last point toward the final approach course instead of maintaining the published heading.  After a VERY gentle reminder about (a), he mumbled some apology in response.  After a firmer admonition about (b) because he was turning without a vector, he disconnected.  Again, I probably wasn't as nice after (b) than I was after (a), but I didn't call him any names.

Then finally was the one who departed and immediately turned northeast, when the SID dictated Runway Heading (155).  I said "your departure calls for runway heading until vectored.  but it doesn't look like you're going to {first waypoint} either.  say intentions?"  he replied, "to fly to {destination}."  I said -- "were you going to go via the route you filed and got cleared on, or just direct, or what?"  and he disconnected.  again, I don't think I called him a name, but I'm sure he could tell by the tone of my question that I was definitely calling him out on his error.

Like Malcolm says, when it's busy -- or, even when it's not that busy but it's "the heat of the moment" like I said -- "excuse me dear {callsign} but you are doing {x} when you were instructed {y}" is not as straightforward as it seems like it could or should be.  I do NOT think it should be tolerated to call someone a derogatory name for a mistake, but, I do NOT think it's reasonable to expect the controller to be all smiles and reassuring pats on the back after one either.