REQUIREMENT: ezQuake 1.9 stable


QTV experience can be finetuned to a certain point. The most important things should be always on the QW-DEV QTV developer site, but there are certain really informative guides like this and this and even this around.

The most common commands for QTV are (when watching games):

/cmd users or /qtvusers to check connected clients

/cmd lastscores similar to KTX lastscores command

/demo_autotrack 1/0 uses KTX autotrack information stored in the stream (so they should be identical in KTX and QTV).

/autotrack with ezQuake 1.9 stable will be the same as above. So you can use your existing 'autotrack' bind for the same function while on QTV

[ deurk - updated url ]

I use plain autotrack to toggle autotrack on/off.

It's not the same thing. /demo_autotrack (KTX /autotrack) is serverside autotracking where the server sends you info who to track and the client obeys. Using /autotrack during demoplay or QTV stream enables clientside autotracking where your client makes the decisions depending on the MVD information.

That is only true in some cases. Newer mvd's have KTX's autocode suggestions (who to spec/when) in the demo, therefore ezQuake will use demo autotrack if it exists over it's own autotrack. More often than not, it's just more convenient to use /autotrack because newer ezQuake's have very similar algorithms iirc

Ye, I just discussed with Qqshka and msg'd johnny about it.

If this is the case, then I suggest that you differentiate the message being sent to the console. For example if you are on QTV stream, then it should say something like "QTV autotracking enabled" instead of "MVD autotracking enabled".

Edit: it seems to be so that you can indeed use /autotrack for just about everything.