You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 calls sf_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:
The text was updated successfully, but these errors were encountered:
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:The text was updated successfully, but these errors were encountered: