i still record them manually
i think(!) it does not matter, which instance starts the demorec. so none of the viewers should feel a difference.
and i think the playback cannot be chosen that easily.
but i think this affects it:
UT.ini Original:
DemoRecordingDevice=Engine.DemoRecDriver
UT.ini Altered:
DemoRecordingDevice=udemo.uDemoDriver
(not sure which one of those two)
DemoRecordingDevice=udemo.udemo.uDemoDriver
(not sure which one of those two)
if you have successfully chosen the original playback, then slomo and seekto won't work.
but: when sniper-zooming the picture will actually be zoomed. this is not the case when using the demomanager-playback i think.
hmmmmmmmm..... the entry it is called "
recording device".not sure...
then again this entry in the UT.ini exists:
[Engine.DemoRecDriver]
;DemoSpectatorClass=Botpack.CHSpectator
DemoSpectatorClass=JoltDemoEnhancer2.DECHSpectator
MaxClientRate=...
ConnectionTimeout=...
which should be useless?? if you select
DemoRecordingDevice=udemo.uDemoDriver / udemo.udemo.uDemoDriver
but i am not sure, if an entry with the "udemo" name is created at all??
(i don't have one in my UT.ini but mine is write protected... so i dunno)
anyway Botpack.CHSpectator / JoltDemoEnhancer2.DECHSpectator
makes some kind of difference as well... but tbh I am also not sure, if the JoltDemoEnhancer2.DECHSpectator thingy is part of the demo manager. i only know, that before the demomanager was out, it existed as a standalone demo playback enhancer...
many dunno's
but in essence I think(!) you can control the playback with
DemoRecordingDevice=Engine.DemoRecDriver / udemo.uDemoDriver / udemo.udemo.uDemoDriver