PDA

View Full Version : F3 Fly by change time



Buk_Nekkid
06-10-2005, 12:34 AM
Hi guys,

Can the amount of time that it takes for the F3 (fly-by) cam takes to change over be decreased?

I understand that just by pressing F3 again will change the cam, but I would like to watch the track without having to press F3 every time I want the camera to change. Sometimes the camera doesnt change for what seems like ages.

Any help truly appreciated.

Cheers, Buk http://forums.ubi.com/groupee_common/emoticons/icon_cool.gif

Fliegeroffizier
06-10-2005, 11:19 AM
My guess is that you can adjust the flyby parameters by experimenting with these lines in the config.ini

For example, I Think that the DeltaZ may adjust how "close" the camera is to the path of the acft flying by.

[HookViewFly Config]
timeFirstStep=2.0
deltaZ=30.0

[HookView]
MouseLeft=Len

[HookView Config]
AzimutSpeed=0.1
TangageSpeed=0.1
LenSpeed=1.0
MinLen=1.0
DefaultLen=20.0
MaxLen=3000.0
Speed=9

Asgeir_Strips
06-10-2005, 02:35 PM
You know, i think oleg should have implemented a Forward-rewind feature in the track "player" . Unless he already have, and i haven't discovered it yet..


anyone?

JRJacobs
06-11-2005, 06:30 AM
Everyone WISHES for the same, it's just not possible using the game engine.
the recorder uses the same technology the online engine uses.
as an example
0001 sec, x=1.1111 y=1.1111 z=0.000 dir=120 speed=0
0002 sec, x=5.2833 y=2.3493 z=500.000 dir=180 speed=100
0005 sec, x=2.1089 y=3.4922 z=400.110 dir=020 speed=300
0019 sec, x=4.4393 y=2.1387 z=300.0 dir=310 speed=150
now nobody knows the REAL format because the info is encoded but the game does the physics and the only thing that gets transmitted/recorded are the changes you start at 0001, then CHANGE at 0002, then CHANGE at 0005, then CHANGE at 0019.
notice this only WORKS if you go in that order, if you start at 0005 you have no input as to what happened at 0001 and 0002 and trying to go backward has the same problem as you need to start at 0001 - it's actually much more complicated than this but this also explains why your tracks sometimes get out of sync and your recorded plane is shooting at thin air