Open bakapear opened 7 months ago
I wouldn't use the streams editor because those commands are ran every frame for every stream. Rather, I would give it its own section in the GUI.
As for the commands, they could look like this:
sf_cmdqueue_tick 500 "sf_recorder_start path\to\my\folder"
sf_cmdqueue_sec 120.0 "sf_recorder_stop"
sf_cmdqueue_min 95.0 "sv_cheats 1"
sf_cmdqueue_min 95.0 "sf_recorder_start path\to\other\folder"
sf_cmdqueue_min 110.3 sf_recorder_stop
Currently to automate recordings so that it records only a specific timeframe, one would need to create a VDM file alongside the demo that fast forwards the demo to the start tick, calls
sf_recorder_start
and at the specified end tick callssf_recorder_stop
.A command to queue commands would make creating a VDM obsolete, as you could then just run
demo_gototick 1234; sf_recorder_start folder; sf_cmdqueue_tick 5000; sf_recorder_end
to record a demo from the ticks 1234-6234 for example.Alternatively could also add a feature to the
Streams
system in the GUI that allows a stream to be active in a specified tick range instead. Then the above could be implemented like this: