Button presses in demo

[Dokujisan]

I would like to see the ability to display the buttons that are pressed during the demo. That way it would be easier to learn about what exactly is going on. This would help with learning some of the tricks that some advanced people pull off.

Below is the way that I imagined it.

You get the basic idea. You could have standard buttons on the left and the custom binds along the top. I didn't bother putting those in the mockup. I just wanted to show the basic concept I was thinking about. Just food for thought. Feel free to expand on the idea.

[Psychcf]

good idea, like how that screenshot has 6 FPS

It should be optional however.

[Dokujisan]

That's not my screenshot. I grabbed it from somewhere else on the forum.

Yeah, I was definitely thinking it would be optional. Some people wouldn't want to see that stuff. I don't really know how (from a technical standpoint) demos are recorded so I'm not sure if it would be an option when doing the recording or when doing the playback.

[Psychcf]

it would be tricky to do since some people don't use certain keybindings (see this for an example)
Good concept but I think we'd have to edit the game soruce, and I'm pretty sure the devs don't want to do that. (correct me if I'm wrong)

[Shoe]

Can anyone identify the map?

Also, while an interesting idea, I don't know that it's something that would be included as a regular feature as its functionality is pretty limited. It might be nice for someone to make a video tutorial, though, and use the editing tools to add stuff like that in.

[Dokujisan]

omg, I think that would be impossible to do manually. You would have to guess thousands of button pushes during one game. It seems reasonable that the demo recording process itself would be able to record the keypresses. I don't really know what the demo recording process entails. Does it record frames of action in a video format? Or does it record data for rendering a scene in the game engine? If it is the latter, then it should be doable to make the replay of that data display the button presses. Curious what the devs say about this. Maybe this should've been under "Nexuiz-Development".

[ai]

IMO the whole idea is kinda of stupid. But I don't know what other people might think, though if this even take a little effort to make I bet the devs won't even bother as if they would do that they would need to do an option whether you allow the buttons to be shown when pressed while recording a demo. For instance, what if a player doesn't want to show what he was doing but wants to share his/her demo's. Then there would need to be an option for them that buttons didn't record.
And also, this could also be treated as a security risk too. If buttons are recorded then they are stored somewhere and who knows what people can do with that code with this or other games, or even standard applications. People are smart and creative that's a fact.

[C.Brutail]

Can anyone identify the map?

Sure I can It's the CTF training map's gate leading out from a medieval castle-like room to the grapple training field.

[C.Brutail]

Curious what the devs say about this. Maybe this should've been under "Nexuiz-Development".

A quake demo is actually only the "happenings" listed on a map: who done what, gone where. That's why it's so small. When you play a demo, you load the map, and the engine just spawns the entities/models on the map and moves them by the intructions of the dem file

[divVerent]

More exactly, a demo is a raw network dump of whatever the server sent. However, with each such packet, the current view angles are also stored as these are handled by the client. Actually, you could almost record client demos on the server or any other machine the packets pass through - just the view angles are not contained. One can easily read a pcap dump (created by tcpdump) and convert it to a demo file where the player's view always points in the same direction - and with some more work, you can make a working demo of the server's view of what the player did (that is, with lagged input).

So from what is IN the demo, you can't infer which keys were actually pressed. And adding that to demos would not be possible without making a new demo format.