Rcam Tutorial->timed path

[DEVIL_77]

ok i know understand how the rcam works and the timepath....but the problem is that than i reload the demo, it dont stop on the right time, sometimes.....why?

Yeah, i got this problem sometimes too  

Before doing your campoints, don't play too much with the right arrow it's more longer but there is less surprises like that

What i do is :
Edit the file UTRypelCam.ini
(in C:\Users\DEVIL \Documents\My Games\Unreal Tournament 3\UTGame\Config)
And change this value TimedPathStartTime=287.590942 to 286.790942 (it's an exemple^^) but, it hard to find the right value (Close UT3, change the ini, load UT3 & your demo and wait ZZZzzzZZZzzz  ) ... Good luck  

@Devil: I have no idea why its so dark on youtube. When I watch it on my pc everything is bright and fine

You can change the contrast & color on your "TV" & on your graphics card Bloody
I think that your contrast & color on your graphics card are too Dark & your TV too clear no?

[DEVIL_77]

haha my pc is not the problem, i play vctf with 100FPS and bta with 200-300 FPS
but when im playing and record at the same time it lags so badly...

i wanne record my airrockets XD, the demos wich are taken by UTcomp are clientside... so Ryplecam is useless i guess ?

omggggggggggggggggggggg 300 FPS lollllllllllllll 

I only work on demo without this shit of UTcomp & server demo ...So, it's hard to help you...
Maybe look to your UTEngine.ini

[Engine.DemoRecDriver]
NetServerMaxTickRate=30 <= dnc-mafia, don't tell me that you put 300 here??? lol 
LanServerMaxTickRate=30

[Bloody.Bender]

Can't u guys read? Vegas wrote that you should read the Readme.txt. Its rly helpful!

[DEVIL_77]

You're right bloody, Vega explained it too & "There is no knowledge, that is no power"  

(Good luck guys...)   

[VegasKill]

long post, just ignore it if you don't care about problems to start an rcam path.

[Engine.DemoRecDriver]
NetServerMaxTickRate=30 <= dnc-mafia, don't tell me that you put 300 here??? lol 
LanServerMaxTickRate=30

These are the animation frames that are written to the demo files. The value should be the same on client and server, and to leave it at the default of 60 is recommended. The lower the tick rate the more your characters will warp. Higher tick rates will increase the cpu load and the amount of data packages sent to the server (if online).

If you want to limit the screen frame rate, do it with the smooth frame rate setting. Use the same value for min & max.

I have same problem too.
For example i have demo action in 3:20 min: i create campoint's path, save this way (F4), open demo again, next pause demo on start, F5, "j", i wait, when action come (or use right button to speed) and... rypelcam pause demo in 3:50   Then i open demo again and try. If is bad again, make new campoint's path. To the effect. Or deactivate automatic path ("j" to disable) and use numpad3 and 1-9 keys, when my action come. 

The time in ut3 demos is buggy if you alter the playback speed.
The correct answer comes from devil:

Before doing your campoints, don't play too much with the right arrow it's more longer but there is less surprises like that

After saving the cam points in real time, if you get problems to start the rcam at the right time, leave away the ffw at all and run the demo at realtime, again. Give it a try, if it works correctly, you know you're using a ffw too high for your machine. 

What i do is :
Edit the file UTRypelCam.ini
(in C:\Users\DEVIL \Documents\My Games\Unreal Tournament 3\UTGame\Config)
And change this value TimedPathStartTime=287.590942 to 286.790942 (it's an exemple^^)
I think that your contrast & color on your graphics card are too Dark & your TV too clear no?

Not only the 1st cam point has its PCtime. You'd have to add 0,8 seconds to every cam point.

[DarkHunteR]

anyway... dident read the comments but only for this:

ok i know understand how the rcam works and the timepath....but the problem is that than i reload the demo, it dont stop on the right time, sometimes.....why?

by Sev


it  happend to me ,too

and my problum was that im -pause - marker - unpause too fast for rypelcam to remeber it ( the time and all this..)

so every this i press 5 for marker im wait a little bit and then press pause. :)

[Bloody.Bender]

Again too dark. Even in the preview-render window its not so dark. It gets dark as soon as you upload it to youtube...

[DeadlySev]

MEGAMAN!....ja it also works with sniper^^

[DarkHunteR]

Finally my hax work properly!

lol

lol it is not dark all lol..
nice

[PainSavour]

 

I love when I get killed by impossible shots trough wall (fury!!), bio I just deflected with shock, invisible core combos, or get stuck on invisible destroyed vehicles. Epic did a smashing job with all the nice bugs.

[Bloody.Bender]

btw that combo is fuckin hard to do. Try it with 72 ping =O

[Wojci]

sry i cant cause i never get a ping above 70

[aka_sova]

btw that combo is fuckin hard to do. Try it with 72 ping =O

Easy... 

[VegasKill]

@Cr4zyB4st4rd: If you got problems with the time being buggy in demos, I think there is also an other approach you could try. There is an option in the rcam.ini, if I remember right, that swaps the timed path start mode from PCtime to a player coordinates mode. It is actually always logged in the ini who was spectated with rcam. I'm not going to test it / not until Christmas holidays, so I can't confirm this method works better. But it should be worth giving it a try, since any frag @ 15 minutes demo time recovers the time to test it.

Gl and pls tell if it works out.

[Bloody.Bender]

I don't get it :D But I'm not a good testee anyway XD

[VegasKill]

TimedPathsPosCheck=true confirmed not to work with Rcam3.05 and ut3 patch2.x.
Timedpaths will depend on the UnrealEngine timing, as long Rypel doesn't fix the broken rcam functions. And he didn't log in for several months on his website, so I guess rcam for UT3 is obsolete. :'(