StatusSpec 0.15.0 has been released.

It's a pretty expansive release. New features include the option to display something when the game is paused/frozen, a new module that allows you to highlight frags of a player just like in POV demos, and a new module that allows you to pull up a console and scoreboard while having the rest of the game HUD still visible. In addition, the killstreak and outline modules have been improved.

As always, feedback and suggestions is greatly appreciated. I would especially like feedback on the new features and improvements made in this release, as well as suggestions on what to add or change.

Make sure that the StatusSpec directory is installed within the custom directory, and make sure that you're launching the game with the insecure option. If you're doing both of those things, scan the console spew from the game when it's loading for mentions of StatusSpec, which should help clue you in to where StatusSpec is failing to load.

I need your help - I'm looking to expand antifreeze for the next release, but I don't have enough demos to test with. If you have SourceTV demos of matches where a pause occurred, I would appreciate it if you could send me the demo, along with estimates of the tick when the pause happened and the length of the pause.

Also, if you have ANY bugs, performance issues, feature suggestions, or anything of the sort, please don't hesitate to add me on Steam, post in this thread, or PM me. I'd like to nail down as much as I can with each release, but I can only do that with your help.

No, you have to send formatted UDP packets to grab the info. You can use a library like Steam Condenser to do the heavy lifting in that regard.

It's pretty much what you said. Using Git itself is really the best solution if you don't mind taking some time to learn how to use it, especially if you have custom modifications that you don't want to overwrite.

I don't think that instant replay is really that feasible, given that the cameraman doesn't always have the right POV of the action. Since you can't "rewind" SourceTV, which would be the best option, you'd want to grab the demos, which only appear post-match. The other option would be to have several instances of the game recording different angles, but that would use a massive amount of resources for little game.

I could see post-match analysis (similar to what was done at EMS One Katowice) happen sooner. You'd need to grab the demo (which is available more often than not nowadays) and have a general idea of the tick(s) that you want to review (which could be made possible). The really difficult part of that is the fact that you don't have commentators in control of the visuals, so there would be a lot of awkward fumbling to go along with what they are saying (similar to how the cameraman rushes to switch POV to whomever the commentator announces they are watching for a midfight).

As to how simple it is to rewrite P-REC... it's actually simple to write a cross-platform plugin given all of the interfaces given in the SDK.

I was going to write it myself (complete with new features), but I haven't started yet due to being busy with StatusSpec and research for a new project. If there is interest, though, I'll work on it and see what I can come up with.

I've been getting some reports of player outlines causing game lag. I'm trying to pin down the issue, but I can't replicate it on my system.

If you have been experiencing performance issues while using the player outlines feature, and wouldn't mind testing a few experimental builds, please add me on Steam.

StatusSpec 0.14.1 is now available. Some issues that I noticed with killstreaks are now fixed, and a new command to help combat issues with player outlines is available.

Do we know who's doing camera? I'd like to hopefully work with them to fix the remaining StatusSpec HUD issues.

StatusSpec 0.14.0 is now available. This marks the release of a new module which allows killstreaks to be globally enabled for all players.

Unfortunately not. You can try to replicate something similar with the health-based team-colored outlines that I implemented recently, but double outlines aren't possible within Source.

(If only we could do something like CS:GO...)

https://www.youtube.com/watch?v=Q7jFw_dqKjk

To actually answer the question, it's pretty difficult given that none of the competitive leagues except for ETF2L have an API.

Some good news - I've managed to create methods to grab some info about the spectator like the target, mode, and view. It won't be of immediate use to StatusSpec as its features stand right now, but I think Spec Tools will be making use of it soon.

Well, there are HUD animations triggered when an uber is ready and when an uber is popped, so I'm sure it's possible to show an indicator that makes it more clear. It would be up to users to actually implement that event in to do so, however. Otherwise, I would rely on stats for aggregate info.

He already heard about them during a cast for the Invitational he did last week.